After connecting to the DEXI wifi, we open a browser and go to the dashboard. When we do this we do not see “Pi Camera” as is seen on the final video of the droneblock curriculum series for Sensor Wiring and Programming with ROS2 and Node-RED. Could this be an issue with the installation of the dexi-os or something else?
If you can ssh into your DEXI Pi and run the following:
sudo dmesg | grep imx919
and share the output. Here’s what mine says (with a working camera):
[ 8.678238] imx219 10-0010: failed to read chip id 219
[ 8.701992] imx219: probe of 10-0010 failed with error -5
[ 8.710418] imx219 0-0010: Consider updating driver imx219 to match on endpoints
The last line shows that the driver was loaded for my Pi cam on cam0. The error above states that it can’t be found on cam1 (where I don’t have a camera connected).
I’m assuming it may be a cable connection issue. Double-check that and please be careful with the camera locking tab on the ARK Pi6X Flow side. Those connectors are very fragile! Let us know what you find out.
They have not been able to ssh into DEXI. When they enter the IP they’re prompted for a password. They put droneblocks but it says its invalid.
They double checked the cable and it is installed correctly.
Password for SSH is different than DEXI’s wifi network. SSH pass is here:
Let us know.
Thanks.
They ssh into dexi and run the command but nothing comes back. We tried another cable and camera as well. They also followed the steps to comment out the camera_auto_detect=1 line and add start_x=1.
You shouldn’t need to change anything in the config. We use Ubuntu 22.04 LTS for DEXI-OS and spend quite a bit of time making the camera work out of the box. As I was reviewing my post I realized I made a typo! The command should be this:
sudo dmesg | grep imx219
Not 919 like put in my original post. Sorry about that. I would recommend reverting config.txt to its original values. I thiink that means removing start_x=1 based on what you shared. Make sure to reboot and then run the dmesg command from above. Once again, my apologies for the typo.
Really sorry for the delay. Been traveling this week. I’m going to bring this up to our team today and get back to you.
Any chance you can send us a photo of the cable connected on the CM4 side as well as the cable connected to the camera? If there’s not an issue with the connection then we believe the camera is likely bad and we can ship you a new one. Feel free to email support@droneblocks.io to begin the replacement process. Thanks and apologies for the inconvenience.
By new camera do you happen to know which Pi camera version it was? If you’d like to schedule a realtime call so we can work through this please send an email to support@droneblocks.io and we’ll get something going!
V2 os the one we bought. I sent an email to set up a call. Thanks.
@droneblocks thank you for the support. Another update to the software resolved this issue. We may be having issues with trying to do updates on our schools network. We will do them from a hotspot or personal network in the future.
1 Like
Thank you for confirming.