VAOC 3DO Cam broken after Crowsnest update
Hi, I did the update of Crowsnest, from v4.1.11 to v4.1.13-1.
After the update the VAOC Cam stopped working.
I tried to uninstall and reinstall crowsnest more than a couple of times, also changing the Git tag back to v4.1.11, but the problem seems not solvable.
Anyone had the same issue?
I noticed some stange behaviour in the logs for the 3DO cam.
I attached the debug logs produced from crowsnest, clean with the option "delete_log: true".
Additional infos.
I also tried to change the device IDs to by-id, obtained with the command below, and I have also tried to change from camera-streamer to ustreamer, but the 3DO cam does not give signs of life, even if I enable rtsp.
Thanks!!
6 Replies
I add some infos, maybe it's easyer to spot the problem.
Within the crowsnest log filles, in both pre and post stream load, you will find:
Why the 3DO Cam "handshake" gives back a resolution of 1920x1088 px?
An extract of the new crowsnet log file attached has this output:
Aaand those are some Raspi dmesg outputs realtive to the camera:
More.
Outuput of direct dump of a video file through v4l2-ctl:
So after more tries, I think I have addressed the problem root cause: BAD USB CABLE.
Why it has been so perfectly in time with the Crowsnest Update, it is not to be known, so it seems unrelated.
By the way, connecting the camera to a Win PC showed the same behavior as on the RPi: the camera is detected and controllable (through VLC in this case) but no video stream is coming.
Then I tried another cable from another webcam with the same pinout and the 3DO just worked.
The original cable is integer and undamaged.
I have detached the extra ground pin from the camera side connector, from the original cable and is working fine, but the video feed from time to time freezes for a brief.
I suspect there is a shielding problem on the cable and when the camera tries to stream the USB diff. pairs can't keep up the bandwidth, maybe a bad impedance too affects the working condition.
Anyway, the camera works a bit choppy, but now I miss a properly working USB -> Cam cable.
For the records, if you want to playout with camera settings (not recommended but necessary if you fuck up something), you can set it back with v4l2-ctl:
Disclaimer: try/fiddle at your own risk!
I found the challenge. When I first set it up using 2.10RC3… Here is the fix..
With the 4.13 update crowsnest updates the conf file, you think you are working when you are not.

If you change them back to what the Visualizer is looking for the camera works again.
