We are using a navigator and raspberry Pi 4 for our ROV, everything was connecting and working fine for a few days until one day it just stopped connecting. No wires changed and we have tested all ethernet connections between the TIB’s and the tether and they seem to be working fine when tested. The only thing that seems off is the green light on the ethernet port of the rapsberry pi does not turn on, only the yellow light next to it turns on when ethernet is connected. The ROV does not connect to Blue OS or QGC like it used to, is it possible that this could be a issue with the raspberry pi? Maybe it overheated because on the day it stopped connecting we were doing testing at the pool but most of the time the ROV was out of the water and in the sun while the power was on. we tested it with a raspberry pi 5 and still same problem. On both TIB’s we have 3 green lights which indicates a good connection but no data seems to actually be reaching the surface computer to allow it to connect.
Hi @Rhys_Sellahewa -
Do you hear the normal beeps from the ROV thrusters a few minutes after connecting power? A blue light should start flashing at the same time this happens. If this is the case, the ROV is fine and you have a networking issue.
If no blue flashing light begins on the Navigator (or does your system use a pixhawk?), then yes the Pi or its SD card could have potentially been damaged due to the extreme heat. When you tried a Pi5, was it connected to the same SD card? It would require the correct version of BlueOS, you can’t swap a Pi4 sdcard to a pi5 and have things just work…
We heard the normal beeps and saw the flashing blue light immediately after connecting power but the beeps we usually hear a few minutes later when the ROV is ready to connect to blue OS are not heard. Instead after about 10 minutes or so we hear the same beeps as when you first connect power. (We are using a navigator)
Hi @Rhys_Sellahewa -
That definitely indicates that the Pi is having trouble booting up. You could try re-flashing the SD card, or flashing another one for your Pi5 (rather than re-using what you have.) You could try the old sd-card too, and see if the issue was it or the Pi itself!
We were using the pre flashed blue os SD card that came with the navigator and we tried it on the Pi 5 as well with no luck. We will re flash or flash a new one and see if that fixes the issue. Thanks
Hi @Rhys_Sellahewa -
As mentioned, the pi4 image is not expected to work on a pi 5. You can download a pi5 build though, and flash that!
Thank you! We re flashed the SD card and everything is working normally again, just out of curiosity what could have caused this type of issue. Our team knows very little about software and we’re eager to learn. Thanks.
Hi @Rhys_Sellahewa -
Did the original pi 4 return to working, or did you flash the sd card image for the pi 5 and use it?
If the pi4, do you happen to know what version of BlueOS you were running when you lost connection?
We re flashed the Pi 4 SD card and it worked, when it lost connection we were running 1.4
Hi @Rhys_Sellahewa -
It’s hard to say without examination of the SD card before re-flashing, but some aspect of your BlueOS installation had become corrupted and was not starting up. Connecting a hdmi monitor may have shown more information. If it happens again, the SD card itself may be damaged?
Got it, Thanks.