Waterlinked DVL only found when tether attached

Hi all,

My current setup is a blueROV2 with the blueOS/Navigator retrofit and a waterlinked DVL A50. Additionally, we are converting the vehicle to an AUV, so I have installed a removeable tether that connects to a tp-link nano router as discussed in this link

https://www.ardusub.com/developers/wireless-topside.html

This setup is working for me. But I have one thing that is causing issues. It seems the Waterlinked DVL extension cannot find the DVL unless the tether is attached with the router turned on. In the case the tether is attached, it says that it is searching on [192.168.2., 192.168.3.] and finds it rather quickly. But, if the tether is not attached, then it tries searching on [192.168.3.*] and returns the possible DVL’s as .

My current workaround is to start the vehicle with tether attached, wait until it is found, then detach the tether and run tests. This tends to work for around 1-2 hours then the DVL disconnects from the extension and I’m in the same boat of having to restart with tether attached again

Any thoughts on how to get around this?

Hi @cmarq,

Maybe it is relying on the tp-link nano router for the dhcp server?
what ip is it usually found at?

Could this step be causing the issue there?

@cmarq

Those instructions are outdated, but that should do no harm.

Try enabling the dhcp server in Blueos and restart (by power-cylcing, so the dvl restarts too) the whole system.

That button to enable the dhcp server is greyed out for me. I cannot click it

Hi @cmarq -
Does it look like this?

You should be able to click Enable DHCP Server despite the different color of the button… you’ll need to select the gateway option when it opens the pop-up- there should only be one. A static IP must be present before you can enable the DHCP server.

I can’t even express how awesome it is that that worked. Even proxy setup works now to be able to see the DVL status and turn it on/off without the tether

Thanks so much