a few days ago we took our new BlueROV2 on a first real test. It was working perfectly in our lab and when tested in shallow water (<2m). We were operating on a ship and just before our first scheduled dive BlueROV decided not to work. We weren’t able to establish communication. I have (quite a bit) experience with bluerobotics products at this point so it wasn’t any software/hardware setup issues. Topside computer was set at 192.168.2.1 address, firewall rule was added etc. I wasn’t able to ping Pi at 192.168.2.2. Several battery restarts did not help. At that point I had the ROV disassembled and checked, everything seemed fine. After some time I finally (by pure luck I guess) managed to access http://192.168.2.2:2770/system and restart Pi. After that we did one dive and everything worked perfectly. On our second dive everything worked fine just till the end of the dive when we had video artifacts, but no other major problems. Next day, on our final dive we weren’t able to establish communication and just gave up. Disassembled ROV again, restarted it several times, nothing. We had no leaks or any other issues.
Last couple of days I am trying to debug ROV in our lab. When Pi is connected directly to a computer via ethernet there are no issues at all, everything works perfectly. I have tested tether and tether spool connection from topside interface box to the Fathom X board on a ROV and everything is fine. Power and link active LEDs are ON, on both sides. Pi seems to be working normally since everything is working when tether is bypassed. So I have narrowed down the problem to either Fathom X interface boards on either end or USB to ethernet adapter in the FXTI.
Since I have no spare Fathom X boards nor USB to ethernet adapters, have you got any advice on how to test them?