BlueROV2 was working great. Yesterday went out to connect to the ROV and cannot access 192.168.2.2 or blueos.local. QGroundControl cannot connect and my ping 360 and ping2 are not being discovered in PingViewer. I am only able to access the ROV through http://blueos-avahi.local/ when they are both on the same Wifi connection. Cockpit will also connect only via http://blueos-avahi.local/ and keep dropping and picking up the connection.
Anyone have any ideas for help? Tried multiple laptops that were setup to run the ROV and they are all doing the same thing so it seems to be something changes in the ROV.
Thanks!
Hi @MichiganDiver -
I’d guess the link light on your blue FXTI topside box is not staying lit after power up. Check the resistance of the tether pair used, and try swapping to another one if possible (both in the FXTI box and in the ROV.) This comes up frequently on the forums!
Thanks Tony. Will take a look at that tonight. I noticed that the second set of “beeps” from the ROV are seeming to take a lot longer than normal as well. I also noticed that the link light wouldn’t stay on all the time. Sometimes on, and sometimes it would start blinking. Not sure if any of that helps as well. Thanks!
Hi @MichiganDiver -
Without a link light on, and never going off, you won’t get a connection to the system!
Verifying the tether pairs are connected and at similar, low resistance is key - if not, another available tether pair may resolve your issue. If that still doesn’t do the trick, you may need to replace one or both Fathom-X modules - please reach out via the help center.
