Water Linked DVL extension failing to connect after reboot

Blue Robotics Software BlueOS
,
21

So i boot up the ROV.
Go to 192.168.2.95 to check the DVL and its always working.
Then go to 192.168.2.2, available services, waterlinked and then i check the DVL connection. Its never there on startup so i then go to the terminal, and put in:

red-pill
# find the name of the DVL container, and stop and remove it
export OLD=$(docker container ls --format='{{.Names}}' | grep -i dvl)
docker container stop $OLD
docker container rm $OLD
# pull the new image and start the new docker
docker pull williangalvani/blueos-dvl:latest
docker run -d --net=host -v /root/.config/blueos:/root/.config --name=BlueOS-Water-Linked-DVL --restart=unless-stopped williangalvani/blueos-dvl:latest

I then checked the DVL in available services again. This time it shows “running”. I then go to QGC and go into position hold mode, which then work as expected holding the ROV in place.

Upon checking that its functioning, I then power the ROV off via the switch (just cuts battery power to the ROV), then power the switch back on. ESC’s boot up and i go back to 192.168.2.2 to check the waterlinked, it now says it cannot find the DVL in the local network. I go to QGC I can no longer use position hold mode. I check 192.168.2.95 and the DVL is still working fine there.

22

Thank you for the report.

I’ll try to replicate the issue here tomorrow. It is pretty late right now at my side of the globe. I’ll let you know how it goes.

1 Like
23

@Qlowe I managed to replicate your issue.
It should be fixed now. Please update your image and try again.
It was a race condition where one of the APIs used by the dvl service was not ready when we tried to use it.

1 Like
24

I can confirm it is also working correctly on my side as well now. Thanks a lot for the help.

1 Like
25

I’m glad it is working.

Thank you for reporting the issue.

1 Like