We have previously used our BLUEROV with no issues, but when we tried to use it again we are unable to connect to blueos with the error that the IP cannot be found. We have manually changed the IP as per the setup instructions, but we cannot ping the IP of the robot itself (192.168.2.2). All lights are on correctly, we are truly stumped. Does this mean it is a hardware issue? Using claude.ai to help troubleshoot this is the only conclusion we could come to, but this would be unusual given we used it previously and it was fine. Any other suggestions before we look at the hardware/raspberry pi?
Hi @drfeebz
Is the green link light on, and staying on alongside the power LED on your blue FXTI topside box? If it’s not, then the issue is 100% with your tether connection. You could reach the device via its Wi-Fi, AP if you’ve connected it to the internet at your location before, and then install and check the tether with the tether diagnostic extension. In this way you can reach the vehicle even if the tether is not functioning on the bench.
If it is, then the issue is 100% with your IP address or subnet configuration. Please share screenshots of how you’ve set this up.
Assuming you hear a beep from the thrusters a couple minutes after connecting the battery, the issue is not with the pi running BlueOS.
Finally, do you know what BlueOS version the system is using?
Kia orana Tony,
Thanks for your email.
I will try to summarize what we have done but it would be great to hop on a call some time to troubleshoot.
We have used the ROV previously with no issues so we know that it can work.
We set it all up but it was unable to ping the robot at 192.168.2.2. We used the correct IP settings etc when setting up the ethernet link.
My colleague then reinstalled the OS on the SD card in the robot itself, turned it all off, then the next morning when he turned it on it was all working again.
We then took it out on the boat but then the same issue happened again where it could not connect to the robot (destination host not reachable), the lights on the router were all working and we could not see what the issue was.
The only thing I can think of is that we have another ethernet connection showing up in the network and sharing center that perhaps was the ‘original’ connection but now the ethernet shows up as Ethernet 4 and perhaps they are getting confused? We are really struggling to see what the issue is given it worked one time while troubleshooting but then stopped working again.
The current software version we are now using 4.7.1 (STABLE)
The ROV IP address is 192.168.2.2
Any advice most welcome!
Kind regards,
Phoebe
Hi @drfeebz -
You’ve not shared the state of the link light on the FXTI blue topside box. This is the most critical piece of troubleshooting information! If it is off, your tether connection has an issue and no connection to the vehicle will be possible. Jumping straight to a reflash of the OS is typically not necessary - better to fix the root issue!
The second most useful step you can take is to install and use the tether diagnostic extension.
Once you’ve shared one or both pieces of information, we’ll know if a further troubleshooting is required - if it is the help center is the best way to setup a meeting with the support team!
Hi Tony,
Both status lights are on and working but the blueos interface still won’t load.
Many thanks,
Phoebe
Hi @drfeebz -
If the link light is on, and staying on, and you can’t reach 192.168.2.2 in your browser, your computer either doesn’t have a correct IP on that network, or the Pi is failing to boot. Do you hear a beep 2-3 minutes after connecting the battery to the system? If so, this confirms the Pi is starting up ok, and isolated the issue to your computers configuration. Double check your network settings !