Hi, I’d like to follow up on this issue, as no significant improvements have been made. As I said earlier, we have a BlueROV2 R3, we’re connecting to ping1d through USB to serial adapter, we’re using BlueOS 1.3.1 and we recently upgraded Ardusub to v4.5.3.
Yesterday I couldn’t connect to the echosounder using either PingViewer or BlueOS (through “ping sonar devices”). I’ve tried to connect it manually following this video from this post with the following configuration:
→ Device: Ping1D
→ Communication: UDP
→ UDP Host/Port: 192.168.2.2:9090
After trying the ROV in a pool (ping1D not detected), I connected the ROV again in my house, and ping1D was working/detected! What is happening?? I haven’t changed anything, and suddently it works?? Probably it has nothing to do with this, but upgrading Ardusub has caused some misconfiguration in the autopilot output channel configuration, maybe it afects other things?
The truth is that I have a number of issues in BlueOS: sometimes cockpit doesn’t appear in the menu (it looks like if it wasn’t able to charge, and I have to refresh the BlueOS page), or cockpit stops working while piloting the ROV (a “page not found” message appears). Imagine this happening during a open water mission! For the moment, QGC seems more reliable in this sense. Could all these issues be related?
Following the indications of @tony-white in this post (see below), I attach a screenshot of the surftrak fixit page:
Could someone help me understand what these messages mean?
Thanks in advance.