Hi,
I’m jumping into this active DVL thread with a follow-up to my prior post (not sure what the best procedure is when returning to questions in conversations that have since moved on…).
Still no connection to DVL after taking these steps:
- installing a new Navigator board and Pi4 (works fine; running BlueOS 1.0.1, Ardusub stable 4.1.0)
- following the instructions in this post, I updated the DVL docker container to Willian Galvani’s current version. I accomplished this using ssh from a CMD prompt, because the BlueOS terminal is not working for me (is this relevant somehow? I just get a spinny wheel when trying to start the terminal in Pirate mode). LATER EDIT: I followed the tip in this post and installed the latest BlueOS version (“master”) using the version chooser; this fixed the Terminal problem, but did not succeed with the DVL connection.
- tried again to connect directly to the DVL to configure the IP address per WaterLinked instructions, but can’t establish a connection
- verified that the DVL board is working (can see green flashing on the LED for port 3 on the ethernet switch). Also tried a second DVL board (from my other ROV); same result.
During all this, the DVL is in a water bucket and is displaying a steady green LED. I do see the DVL service running, and the Status on the DVL driver page at http://192.168.2.2:9001/ says "could not talk to dvl at waterlinked-dvl.local, looking for it in the local network…
Any ideas @EliotBR or @williangalvani? I’m pushing hard to get on the water here but totally stuck at the moment.
Thanks,
Scott