Closed matthieu-lapeyre closed 7 years ago
Ok so same setup with a new camera does not raise the error and the ergo seems to work fine.
If it is indeed a problem with broken or nearly broken camera, maybe should we add more explicit error and start the ergo with the camera disabled ?
Explanation here: https://www.raspberrypi.org/forums/viewtopic.php?t=35689&p=300710
The problem is that this segfault is not so easy to try/catch. I think we should at least explain this in the FAQ.
I'll try to see if we can do better.
I have the same problem now. The camera worked fine this morning and stop working, now I have the "select timeout" error. I tried the explanations from https://www.raspberrypi.org/forums/viewtopic.php?t=35689&p=300710 but I do not have the same system module, I am not sure what can I do. I reinitialize the camera raspi-config, seemed to sound OK but always 'select timeout' after reboot. The camera red light lights for some seconds and stops.
Help @pierre-rouanet please
Hi @lpierron,
You should check if the cable is still plugged correctly. We also had a lot of issue with camera burning :(
Unfortunately from a software point of view, there is not much that can be done. It's directly the camera driver that crashes.
Thanks @pierre-rouanet the cable was unplugged !
We have a strange issue with a standard Ergo Jr kit (Pixl, rapsberry pi, pypot v2.11.1).
The robot instanciation raises this error:
Communication with motors seems ok:
But not the camera ...