I am having trouble detecting the BlueROV2 on my laptop (Ubuntu 24.04). I have been able to establish a connection for the past couple of months, but suddenly I can no longer connect to BlueOS. When I try to ping 192.168.2.2, I receive a “Destination Host Unreachable” message, indicating that there is no established connection to BlueOS.
The RPi inside the ROV has three Ethernet ports, and I noticed that two of the three show a yellow light with no green light. Other system indicators appear normal: both LEDs on the Fathom-X are on (power and link active), the red LED on the RPi is on, and both blue LEDs inside the BlueROV are behaving as expected (one solid, one flashing steadily).
I would appreciate any help understanding and debugging this issue. I have seen in other posts that this could still be an RPi issue, possibly due to a corrupted SD card, but I would like to exhaust all other options first.
Sorry about your issue - older versions of BlueOS sometimes had an issue where they would “lose” the IP address used on the ethernet port. If you’ve previously connected the system to a WiFi networ you can potentially reach the vehicle at that WiFi IP address (found on your WiFi router client list) and then add the static IP back in BlueOS via the network computer icon in the upper right.
If that isn’t possible, your only remaining option is to flash the vehicle SD card with the latest stable version!
I’d also point out that no Raspberry Pi has 3x Ethernet ports - I think you’re looking at ports on an ethernet switch or Fathom-X tether interface in addition to the one on the Pi?
Thank you for your response. I had luckily connected the vehicle to a WiFi network and was able to access the vehicle via its network address. When you mentioned adding the static IP back in BlueOS, can you explain a bit further? While in pirate mode, in the top right I see a globe looking icon which directs me to the network interface priority and DNS config settings. The other icon is the computer to computer icon which indicates I have no Ethernet interfaces available. There is also a wifi icon that indicates the network I am connected to. FYI, I am running BlueOS 1.4.2.
I am getting a constant ETHERNET_AVAILABLE_FETCH_FAIL message on the Ethernet Manager as well.
Also to clarify, the Ethernet port on the RPi is connected to an Ethernet switch. Both Ethernet ports on the switch show just yellow lights.
Hi @akshayn3 -
Glad you got access to BlueOS via WiFi! It’s unusual that the “computer to computer” icon has no information under ethernet interfaces - that tends to make me think the Pi hardware could be having an issue?
If you can download the system logs from the settings gear in the lower left of BlueOS and attach here, or link in some way we can access, we can take a look and see what may be going on.
I assume the orange light you do see on the ethernet jacks is flashing? Are the green lights on the ethernet switch flashing for connected devices (2x?)
Here is a google drive link to the system logs from BlueOS. The two jacks on the Ethernet switch have the yellow/orange light on and periodically flicker off and then back on, but the green light on the jacks is not on for the connected device.
Following up on my previous message. Are there any updates on next steps we can take? We are still running into the same connectivity issue via Ethernet. The system logs are provided above. Please let us know if you have any difficulties accessing them.
Hi @akshayn3 -
It’s possible the ethernet controller on the Raspberry Pi has been damaged, as you’re not able to configure the interface in BlueOS. Your best bet is to swap the Pi, using the same SD card / Navigator, and see if that resolves things!
Thanks for your response. We swapped the original raspberry pi with another pi 4 and we are still having the same issue. Could this be a software issue? Is there a way to debug this further and check if it is an issue with the Fathom X Interface board or even the tether without getting a new board and tether?
Hi @akshayn3 -
If you connect an Ethernet cable directly from the Raspberry Pi to your computer, bypassing your tether and the Fathom-X, and things work ok, then the issue is clearly with one of those two items.
As far as checking if it is a software issue, flashing a new SD card with BlueOS and swapping it in would let you determine if the issue was linked to something you did on the software side, or if the problem is indeed with the Pi.
Quick update - we were able to resolve the connectivity issue.
It turned out not to be hardware related. The Ethernet interface on the Raspberry Pi was not retaining its network configuration, so BlueOS was unable to bring the link up properly.
We fixed the issue by setting a static IP directly on the RPi via the terminal using dhcpcd:
sudo nano /etc/dhcpcd.conf
Added:
interface eth0
static ip_address=192.168.2.2/24
After restarting networking, the Ethernet link came up immediately and we now have reliable connectivity through the Fathom-X tether.
One small note: the BlueOS GUI still shows “no Ethernet interfaces available” and reports an Ethernet fetch failure, even though the connection is active and fully functional. Not an issue for us now, but possibly something to look into.