First of all, this procedure is tested with Raspicam v1.3, v2.1 and v3. But should work in the same manner with Arducams (not tested yet). For this example I used the v3 model.
Open crowsnest.log and look for an entry like this:
[05/25/23 19:12:07] crowsnest: Detected 'libcamera' device -> /base/soc/i2c0mux/i2c@1/imx708@1a
{% hint style="warning" %} See the Troubleshooting section if such an entry does not exist. {% endhint %}
Open your crowsnest.conf in Mainsail and look for the device: entry. Now set the device to the one, grabbed from your log.
device: /base/soc/i2c0mux/i2c@1/imx708@1aNow you have to use camera-streamer as your stream service with:
mode: camera-streamerAfter you finished these steps, please click on SAVE & RESTART. Now your camera stream should show up.
Here is a good crowsnest.confexample for a Raspicam v1. The whole explaination can be found in this post on github.
[cam 1]
mode: camera-streamer # ustreamer - Provides mjpg and snapshots. (All devices)
# camera-streamer - Provides webrtc, mjpg and snapshots. (rpi + Raspi OS based only)
enable_rtsp: false # If camera-streamer is used, this enables also usage of an rtsp server
rtsp_port: 8554 # Set different ports for each device!
port: 8080 # HTTP/MJPG Stream/Snapshot Port
device: /base/soc/i2c0mux/i2c@1/ov5647@36 # See Log for available ...
resolution: 1280x720 # widthxheight format
max_fps: 15 # If Hardware Supports this it will be forced, otherwise ignored/coerced.
#custom_flags: # You can run the Stream Services with custom flags.
#v4l2ctl: # Add v4l2-ctl parameters to setup your camera, see Log what your cam is capable of.Thanks to ytugarev for spending time on this example
Login to your Pi (or Linux machine) and type:
libcamera-hello --list-cameras
If your output looks like this, your /boot/config.txt is probably misconfigured:
pi@mainsailos:~ $ libcamera-hello --list-cameras
No cameras available!
Run this command via terminal to open your /boot/config.txt with nano as editor:
sudo nano /boot/config.txt
Look for the following entries and change it:
start_x=1this value is deprecated. If you have it in your/boot/config.txt, delete this line.camera_auto_detect=0this value is deprecated. If you have it in your/boot/config.txt, delete this line.- Double-check if you have
camera_auto_detect=1in your/boot/config.txt. If you don't have it in your config, please add it at the bottom of this file. - Check if you have
dtoverlay=vc4-kms-v3dordtoverlay=vc4-fkms-v3din your/boot/config.txt. If you don't have one of these options in your/boot/config.txtwithout a#in front of the line, please adddtoverlay=vc4-kms-v3dto your/boot/config.txt.
{% hint style="warning" %}
start_x=1 and dtoverlay=vc4-(f)kms-v3d are also important for DSI displays. Please double-check the compatibility with your display.
{% endhint %}
Press CTRL-s to save and CTRL-x to close the nano editor. Then reboot the machine.
After the reboot, please reconnect your ssh client with your machine. Type libcamera-hello --list-cameras again. You should see something like this (a Raspicam V2 was used in this example):
pi@mainsailos:~ $ libcamera-hello --list-cameras
Available cameras
-----------------
0 : imx219 [3280x2464] (/base/soc/i2c0mux/i2c@1/imx219@10)
Modes: 'SRGGB10_CSI2P' : 640x480 [103.33 fps - (1000, 752)/1280x960 crop]
1640x1232 [41.85 fps - (0, 0)/3280x2464 crop]
1920x1080 [47.57 fps - (680, 692)/1920x1080 crop]
3280x2464 [21.19 fps - (0, 0)/3280x2464 crop]
'SRGGB8' : 640x480 [103.33 fps - (1000, 752)/1280x960 crop]
1640x1232 [41.85 fps - (0, 0)/3280x2464 crop]
1920x1080 [47.57 fps - (680, 692)/1920x1080 crop]
3280x2464 [21.19 fps - (0, 0)/3280x2464 crop]
If you get No cameras available! a second time, please check connections and the ribbon cable. Also avoid running the ribbon near stepper motors, stepper drivers and/or power supplies. They can interfere with the signal.
For some users there are problems with the OV5647 sensor module or a Raspberry Pi camera module in combination with klipperscreen. These issues appear to be a problem inside the kernel of the Raspberry Pi itself with the new camera stack libcamera. The easiest option to fix this for now is to use the legacy camera stack of the Raspberry Pi (not to be confused with the legacy branch of crowsnest!!!).
{% hint style="danger" %} This will not work for Raspicam v3. Same goes for most Arducams (not tested yet). {% endhint %}
{% hint style="info" %} We don't provide support for klipperscreen. If you still have problems with your klipperscreen after these changes, please reach out to the klipperscreen support. {% endhint %}
Run this command via terminal to open your /boot/config.txt with nano as editor:
sudo nano /boot/config.txt
Look for the following entries and change it:
start_x=1this value is needed for the legacy camera stack to work. If you don't have it in your/boot/config.txt, please add it at the bottom of this file.camera_auto_detect=0is needed for the legacy camera stack to work. If you don't have it in your/boot/config.txt, please add it at the bottom of this file.- Double-check if you have
camera_auto_detect=1in your/boot/config.txt. If you have it in your config, delete this line.
Press CTRL-s to save and CTRL-x to close the nano editor. Then reboot the machine.
After the reboot, please reconnect your ssh client with your machine. Type vcgencmd get_camera. You should see:
pi@mainsailos:~ $ vcgencmd get_camera
supported=1 detected=1, libcamera interfaces=0
{% hint style="info" %}
libcamera-hello --list-cameras will now output "No cameras available!"
{% endhint %}
If you get anything else, please check your /boot/config.txt again and the ribbon cable.
Open your crowsnest.conf in Mainsail and look for the device: entry. Now set the device to /dev/video0.
device: /dev/video0
With this setup you should be able to use either ustreameror camera-streamer. Sometimes it occurs that camera-streamer doesn't run stable enough with this setup. If you have problems with camera-streamer then change your mode to ustreamer:
mode: ustreamerAfter changing the mode, please click on SAVE & RESTART.