WaterLinked DVL A50 integration not working

[EliotBR (Eliot)]

I spoke with @williangalvani about this, and was told that there were some recent mavlink2rest and water-linked API changes that are causing the issues here. The updated DVL extension should support the latest BlueOS and DVL firmware versions, as well as the api for older DVL firmware versions.

You can beta test it via the following instructions:

@williangalvani

EDIT: modified to automatically find the container name, and stop it

# first, make sure to get rid of the older version
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

@Jnyberg

What is the most recent configuration of the OS and Ardusub is that the DVL works with? Maybe running into connection issues due to versions.

It’s a bit unclear, but it looks like the mavlink2rest API might have changed on the 1/March, in which case the latest version before that would be 1.0.0-beta13. That’s from before the first stable release, so is likely not advisable to go back to. If that is the case it at least makes some sense, because the idea was that once BlueOS was stable the core APIs should stop having breaking changes wherever possible.

I’m also unsure whether it’s possible to access older water-linked DVL firmwares, so if you’re already on the latest one then you may need to use the latest DVL extension, or wait until it’s released in stable form.