ROV2 Heavy having video connection problems. Started out intermittently but today went off and wouldn’t come back on.
Latest Cockpit
1.4.2 Blue OS
BR low light camera.
Camera was working on Blue OS but had a very serious lag approx 1-2 secs.
Went back to Cockpit and still no picture. In video configuration/ allowed webrtc protocols i unchecked TCP box and camera came on. Worked ok for about 10 sec then became jerky/ laggy with no smooth image.
Rechecked TCP then unchecked UCP and camera worked ok again for 10 secs then same jerky image.
Carried on messing then rechecked both and camera appears fine again. For how long i don.t know.
Does restarting Cockpit has any effect over the video problem? Does it stay fine for a while once you restart it, or does it start problematic already?
Restating cockpit sometimes worked but today it went off and never came back on until I messed with the settings mentioned in original post. Although the settings are now back to what they were when the problem originally occured .
I’m wondering if heat is a problem within the electronics enclosure. I have accessed some info via blue OS system info/ kernel which appears to have some kind of log files. They are numerically ordered with no dates or times and the info means nothing to me. However, there are a number of entries in red which suggests problems.
Can anyone explain what they mean? Especially the ones related to USB.
As far as I can tell, none of those warnings are relevant. The element most sensitive to heat in the main electronics enclosure is actually the USB low-light camera. If you’re operating with your system closed up, especially if it is in the sun, it can reach temperatures where the stream from the camera reduces frame rate, drops frames, and generally struggles along doing less in an effort to not overheat… because this is happening onboard the camera, this makes the source stream problematic, and wouldn’t show up in logs until the device actually disconnects entirely from USB.
If the Pi running BlueOS has heat issues, a red thermometer icon will appear in the upper right, likely accompanied by a speedometer icon, indicating the pi cpu itself is thermal throttling.
You’re not running the latest stable version of BlueOS (1.4.3), but I’d actually recommend going to 1.4.4 latest beta - it is about to become stable, and includes some major improvements in video streaming pipelines. You’ll need to be in pirate mode for this update to show up, and have a wifi with internet connection in BlueOS (icon in the upper right.)
I have installed BOS 1.4.4 beta 11 this morning and still the same. Also changed camera no change. Had to manually reverse a vertical thruster after this as the reverse detection failed to detect No 6 wasn’t turning the right way?
Unchecking TCP in Allowed WebRTC protocols does bring the camera on with lag but eventually goes off again. Then when i check it again it may or may not stay on. It can be ok for a while but then randomly goes off again.
We are also getting a return to losing full connection and the network icon going red? Again randomly. Fathom X shows 2 green lights so its not that I assume? Also we lose connection to our Oculus sonar which is then not detected.
Full restart required, sometimes several to get connection.
Also randomly stating 2 game controllers detected although only one is seen in Cockpit and Win 11. According to logs Component 240 is the problem with multiple game controllers detected? No idea what this means.
When I lose the video only, I still have full control of the ROV.
When starting up in a fresh session everything comes on for a minute but then problems start.
Here are the screenshots you requested plus some other things that looked concerning.
Try changing your stream from UDP to RTSP on the video streams page, that could help with video quality / consistency.
The good news is everything in your screenshots looks normal - you see a lot of mysterious devices because you’re in pirate mode!
Your autopilot process looks suspiciously busy… can you share what version of ArduSub you’re using?
However if you’re losing network connection to your sonar, then the Fathom-X is likely having moments where no connection is present. How long is the tether you’re using? If you ping the sonars IP address, how often do those pings fail?
I’ve swapped out the fathom X board in our topside box with an enclosed one. Early testing shows promise but only tested in a tub so far. Be a few days till it goes out into open water.
Not sure on the Ardusub. Again be a few days until I can check.
My multiple joysticks detected issue seems to stem from the fact it’s not recognised. I believe this is an known issue in our version of Cockpit. Win11 sees it as the Logitech but not in copilot.
