Screen Blanking and Pi Camera not working on 3.52

misterjtc

I recently had an SD card failure and did a fresh install of the latest pi image. I recovered my sys config files from github and everything appears to work as it did before except two things.

The touch screen attached to my pi does not go to sleep. It stays on indefintely. I've enabled screen blanking but it hasn't helped.
I reinstalled the motion plugin but my system cannot connect to my camera. Running some commands it looks like the raspberry pi is no longer detecting the camera but I have no idea why since I haven't changed anything hardware wise.

A few questions:

Is there somewhere that I can get a previous DuetPi image (ie 3.4)? This would help to see if something has changed with the latest image.
Does anyone have any advice on how I can resolve these issues on the latest image?

Additional info:

I thought there used to be an option in raspi-config to enable the legacy camera but this option seems to be gone. Is there no longer anything that needs to be done to enable access to the pi brand camera?

Here is what I get when I run "vcgencmd get_camera":

pi@prometheus:~ $ vcgencmd get_camera
supported=0 detected=0, libcamera interfaces=0

The above tells me that no camera is detected, but I have no idea why... Everything worked fine until I updated my sd card and pi image.

Here is the results from "journalctl -u duetpluginservice -f":

pi@prometheus:~ $ journalctl -u duetpluginservice -f
Jul 06 14:38:35 prometheus DuetPluginService[1572]: [info] DuetPluginService.Program: Plugin MotionWebcamServer loaded
Jul 06 14:38:35 prometheus systemd[1]: Started duetpluginservice.service - Duet Plugin Service.
Jul 06 14:38:35 prometheus DuetPluginService[1572]: [info] Plugin MotionWebcamServer: Process has been started (pid 1862)
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /opt/dsf/sd/sys/motion.conf
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [ALR] [ALL] conf_cmdparse: Unknown config option ""
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] Above message repeats 49 times
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] motion_startup: Motion 4.5.1 Started
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
Jul 06 14:38:36 prometheus DuetPluginService[1865]: [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (CRT)

Any advice is greatly appreciated!

jay_s_uk

@misterjtc what type of camera is it? A RPI one or usb?

misterjtc

@jay_s_uk I am using one of the raspberry pi official cameras. Not usb.

jay_s_uk

@misterjtc have a look at using spyglass instead of motion and the plugin

andiwinter

@misterjtc can you post the content of your /boot/config.txt

misterjtc

@andiwinter the content of the /boot/config.txt file is below but I assume its the other file it references that you are looking for. It is also shown below.

Contents of /boot/config.txt

pi@prometheus:/boot $ cat config.txt
DO NOT EDIT THIS FILE

The file you are looking for has moved to /boot/firmware/config.txt

Contents of /boot/firmware/config.txt

pi@prometheus:/boot/firmware $ cat config.txt
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[all]

andiwinter

@misterjtc can you try loading the vc4-fkms-v3d overlay instead of the vc4-kms-v3d one, this is the one we are using in our setup

misterjtc

I am here to close the loop on this in case anyone runs into a similar issue. Below is what I found.

Screen blanking not working
I switched from the Wayland desktop to the X11 desktop
This means that I needed a different way auto launch duet web control on the pi on boot, I did this with the following:

nano /home/pi/.config/lxsession/LXDE-pi/autostart

Added the following to the autostart file:

@chromium-browser -start-fullscreen http://127.0.0.1/

I did not confirm on the official Duet3D image but I suspect the reason for no screen blanking is potentially because of using kiosk mode, but that is just an unsupported theory.

Raspberry Pi Camera not working
I could not get the RaspberryPi camera to work with the Motion plugin, but I was able to get it working with the Spyglass plugin. This leads me to belive there is some issue with the motion plugin.

chrishamm

@misterjtc said in Screen Blanking and Pi Camera not working on 3.52:

I suspect the reason for no screen blanking is potentially because of using kiosk mode

DSF ships its own launch-dwc script which basically does nothing else than launching Chromium. It does not start it in kiosk mode.

@misterjtc said in Screen Blanking and Pi Camera not working on 3.52:

but I was able to get it working with the Spyglass plugin. This leads me to belive there is some issue with the motion plugin.

Motion requires the libcamerify wrapper in order to work with RPi cameras but we've had reports of that wrapper hanging up after a while, so we recommend usng Spyglass for RPi cameras instead. That one uses the native RPi camera interface. Motion is fine for USB cams, though.