Basic Information:
Printer Model: Creality Ender 3
MCU / Printerboard: BTT SKR Mini E3 -v- 3.0
Host / SBC: Raspberry Pi 4B, 2GB
klippy.log
klippy.log (13.5 KB)
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Don’t understand this… in Mainsail, all I get from the raspicam is “No signal.” However, if I directly access the RasPi4 with a keyboard and display attached directly to the card, and I enter “libcamera-hello,” I get about five seconds of video, then it cuts out and leaves the following lines:
karl@mainsail:~ $ libcamera-hello
Made DRM preview window
[0:12:23.608590019] [3747] INFO Camera camera_manager.cpp:297 libcamera v0.0.5+83-bde9b04f
[0:12:23.637574982] [3748] WARN RPI vc4.cpp:383 Mismatch between Unicam and CamHelper for embedded data usage!
[0:12:23.638366091] [3748] INFO RPI vc4.cpp:437 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media1 and ISP device /dev/media3
[0:12:23.638417665] [3748] INFO RPI pipeline_base.cpp:1101 Using configuration file ‘/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml’
[0:12:23.639299736] [3747] INFO Camera camera.cpp:1033 configuring streams: (0) 1640x1232-YUV420
[0:12:23.639814383] [3748] INFO RPI vc4.cpp:565 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA
I’m guessing I don’t have the crowsnest.conf file set up with accurate information… what’s in it now doesn’t match with the output of the RasPi from the “libcamera-hello” command. Do I need to take the information from the Pi output and plug it into the crowsnest.conf file and do a software reboot? Attaching the crowsnest.config.
crowsnest.conf (2.0 KB)
Thanks in advance!!
Basic Information:
Printer Model: Creality Ender 3
MCU / Printerboard: BTT SKR Mini E3 -v- 3.0
Host / SBC: Raspberry Pi 4B (2GB)
klippy.log
klippy.log (13.5 KB)
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Don’t understand this… in Mainsail, all I get from the Raspberry Pi camera is “No signal.” However, if I directly access the RasPi4 with a keyboard and display attached directly to the card, and I enter “libcamera-hello,” I get about five seconds of video, then it cuts out and leaves the following lines:
karl@mainsail:~ $ libcamera-hello
Made DRM preview window
[0:12:23.608590019] [3747] INFO Camera camera_manager.cpp:297 libcamera v0.0.5+83-bde9b04f
[0:12:23.637574982] [3748] WARN RPI vc4.cpp:383 Mismatch between Unicam and CamHelper for embedded data usage!
[0:12:23.638366091] [3748] INFO RPI vc4.cpp:437 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media1 and ISP device /dev/media3
[0:12:23.638417665] [3748] INFO RPI pipeline_base.cpp:1101 Using configuration file ‘/usr/share/libcamera/pipeline/rpi/vc4/rpi_apps.yaml’
[0:12:23.639299736] [3747] INFO Camera camera.cpp:1033 configuring streams: (0) 1640x1232-YUV420
[0:12:23.639814383] [3748] INFO RPI vc4.cpp:565 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected sensor format: 1640x1232-SBGGR10_1X10 - Selected unicam format: 1640x1232-pBAA
I’m guessing I don’t have the crowsnest.conf file set up with accurate information… what’s in it now doesn’t match with the output of the RasPi from the “libcamera-hello” command. Do I need to take the information from the Pi output and plug it into the crowsnest.conf file and do a software reboot? Attaching the crowsnest.config.
crowsnest.conf (2.0 KB)
Thanks in advance!!
Note: this post was previously and mistakenly placed in the “Frontends” category, and I’ve no idea how to move it (or if I even can move it), so apologies for the same topic double-post.
Please don’t multiply your threads.
For it refers to camera stuff, it belongs to frontends, in your case to Mainsail.
1 Like
Apologies for the duplicate… I didn’t realize camera issues went into Front End, though in retrospect that makes sense.