We have alredy integrated DVL driver, but cannot display dvl position data in QGC. Also we cannnot switch GUIDED mode. I think causes of that is we cannot Enable odometry support. VISO_TYPE 1 We search VISO_TYPE paramter in QGC>Parameters , but we cannot find it.

[image] EliotBR: I believe you’re after the PSC_POSXY_P parameter. Sorry, I describe it wrongly. PSC_POSXY_P parameter is recommended 2.5, but its maximum is 2.0.

[image] yuki: PSC_POSXY_P parameter is recommended 2.5, but its maximum is 2.0. Right, I’ve just confirmed that in QGC, so it seems our recommendation hasn’t been updated to match the new firmware. I’ve put a comment about that in my documentation update pull request, but I don’t know what t…

[image] EliotBR: I’ve put a comment about that in my documentation update pull request, but I don’t know what the new recommended value is so we’ll need to wait for the software team to be online tomorrow. Thanks, I’ ll be wait for it. By the way, is QGC EFK data(LOCAL_POSITION_NED) an integ…

[image] yuki: By the way, is QGC EFK data( LOCAL_POSITION_NED ) an integration of DVL velocity data and ROV IMU data or DVL dead reckoning data , when integrate DVL? At this stage the DVL’s dead reckoning message isn’t used in the DVL integration - the position reported in QGC is calculated b…

[image] EliotBR: I’ve put a comment about that in my documentation update pull request, but I don’t know what the new recommended value is so we’ll need to wait for the software team to be online tomorrow. Apologies for the delay on this. You should be able to just use 2.0 :slight_smile:

I have my DVL configured to IP Address: 192.168.2.95. And on dashboard I am getting a valid velocity reading. [image] But when I go to waterlinked driver set up it tries to connect but then says unable to. [image] … [image] … [image] I am curious if that message saying “Trying to talk to dv…

I have the same problem with BlueOS integration and seems that it is something wrong with the driver.

I don’t believe that’s an issue we were aware of, but the DVL extension is currently being rewritten to add some extra functionality and improve the interface, so this issue should be resolved with the release of that new version. It should be available within the next couple of weeks :slight_smile: …

Thanks for update on that! 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. Currently using BlueOS version 1.0.1 and Ardusub firmware 4.1.0.

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…

WaterLinked DVL A50 integration not working

Third Party Products Sonar and Acoustics

Topic		Replies	Views
Water Linked DVL A50 Support Sonar and Acoustics water-linked , dvl , positioning	57	9438	August 15, 2022
Ongoing DVL-A50 issues Third Party Products	43	4541	August 24, 2023
Integration of DVL into ArduSub on NVIDIA Jetson boards ArduSub	23	600	February 5, 2026
DVL A50 integration with GPS position BlueOS dvl , positioning	24	1185	April 28, 2026
Unable to connect to DVL A50 Sonar and Acoustics dvl	14	2715	April 6, 2023

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

WaterLinked DVL A50 integration not working

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

WaterLinked DVL A50 integration not working

Related topics