Hi @cmorri24 -
Happy to assist. Can you describe the behavior of the LEDs on the Raspberry Pi, at the front of the ROV?
Have you verified your IP address configuration, and the status of the link light on the FXTI topside box?
Finally, if an HDMI adapter isn’t available to monitor the Pi start up process, you could re–flash BlueOS on the SD card - if you haven’t already? If your system is older, it could be running Companion OS, and have the configuration interface at 192.168.2.2:2770….
Thanks for the help Tony. The LEDs on the Navigator and Pi are as follows:
For the Navigator:
On the Raspberry Pi I only see two lights. Solid Red for power, and blinking green for ACT.
Regarding IP Address config: I have connected my computer to the ROV via the tether/FXTI, and I have configured the IP address to 192.168.2.1 and the subnet mask to 255.255.255.0. I am unable to access the interface either via 192.168.2.2 or blueos.local. On the FXTI both the power and link active lights display solid green.
I will attempt reflashing BlueOS to the SD card today. However, this is a brand new Navigator/card purchased from Blue Robotics earlier this year, so it should be good. Regardless, I will reflash it and update you if that changes anything.
Also, in case it is helpful, I have attempted to connect to the pi directly via ethernet cable. I was still unable to access the interface this way.
Hi @cmorri24 -
A re-flash should correct your issue - or you could monitor the boot-up with a monitor and HDMI cable as mentioned to see where things are going wrong… if you didn’t re-flash the SD card after installing the new Navigator / Pi, it’s not expected for Companion OS (which was on your old SD card potentially?) to work on the newer hardware!
Ah apologies, I should have clarified but this isn’t the old SD card. This SD card is new, and came bundled with the Navigator/Pi which we recently purchased. I believe it came with the blueos software preloaded.
In any case, I have reflashed the card with blue os. Unfortunately, the ROV still cannot be accessed via ip address or blueos.local. I waited several minutes for it to boot up, and I have verified that the network is configured correctly as we discussed earlier.
Hi @cmorri24 -
Do you hear a beep a couple minutes after connecting power, indicating the Pi finished booting?
If you do, and can’t ping 192.168.2.2 after that start-up noise, then I’d suspect your tether - connecting an ethernet cable directly from Pi to control computer can confirm this.
If you don’t hear the beep, you may not have flashed the card correctly, or your Pi has been damaged.
It’s also worth confirming you’ve configured the correct interface - it should disappear when you disconnect the blue FXTI box. That link light also needs to stay illuminated, and never turn off….
After connecting power, the ROV immediately gives 3 beeps. It does not beep again following this.
As you said this suggests the sd card or the Pi are faulty/damaged. However, this problem has persisted through 2 SD cards flashed with blueos and through 3 Pi, is there another component which could be causing the issue?
By correct interface, are you referring to the ethernet connection that appears in the network connections section of the network and sharing center when the FXTI box is connected to my computer? If so, I can confirm that the IP address is set to 192.168.2.1, and the subnet mask to 255.255.255.0. When plugged into my computer both the power and link active signals display solid green. When I unplug the FXTI box both turn off.
Also, if it’s useful, I did attempt to ping the device. 3 of 4 ping attempts failed and the request timed out. The fourth request was received, but displayed “Reply from 192.168.2.1: Destination host unreachable”. Lastly, I did attempt to connect an ethernet cable directly to the pi, but this did not resolve the issue.
Thanks for your patience and help @tony-white!
Hi @cmorri24 -
Do you see a blinking blue light coming from the autopilot after connecting power? Or any lights from the Pixhawk (?)
If things have worked, but you keep finding your system stopping booting and requiring a re-flash, I’d suspect your 5V BEC could have an issue? That’s a bit of a stretch though - I assume you’re not running any custom software on top of BlueOS? Have you installed any extensions?
And yes, it’s important to make sure the interface that corresponds to the FXTI is what’s properly configured. The pings would all go through if the Pi had booted and was communicating over the network correctly.
Is this system still using the (old) Pi 3 and Pixhawk?
Hi @tony-white -
No custom software or extensions. It’s a clean flash of BlueOS. The system currently has a new Navigator and Pi4 installed.
Re: 5V BEC, is there a way to test if that component has failed?
Hi @cmorri24 -
Pictures of the lights on the Navigator and Pi would be helpful. You can use a multimeter to verify the output of the BEC is 5V. You should see both red and flashing green light on the Pi, close to the front of the ROV, and multiple LEDS on the Navigator.
You could also plug in an HDMI adapter and monitor to see where the boot process is having an issue. Maybe the SD card used is having issues? How big is the capacity of the SD card, and what rating is it (number inside a circle indicating speed on card.)
The link light on the FXTI box is coming on, and never turning off correct?