DVL A50 rangefinder capability

[Sammi]

I have been trying to use waterlinked DVL A50 altitude measurement in ArduSub but I am running into some problems.

Background: DVL integration has gone smoothly and Position hold is working fine. I can see DVL’s readings in its GUI and they look good.

Approach: I activated RangeFinder option in waterlinked tab of the companion website and added a case MAVLINK_MSG_ID_DISTANCE_SENSOR in GCS_Mavlink. ArduSub does receive a measurement but the latter doesn’t track altitude and seems to catch up with a very long lag (~10s) and the measurement update rate is only 1Hz.

Any pointers to fix these problems? Or perhaps I should take a different approach?

Thanks!

[EliotBR (Eliot)]

Hi @Sammi, welcome to the forum

@Sammi

Background: DVL integration has gone smoothly and Position hold is working fine. I can see DVL’s readings in its GUI and they look good.

Glad to hear it - sounds like a solid start

@Sammi

added a case MAVLINK_MSG_ID_DISTANCE_SENSOR in GCS_Mavlink.

I’m a bit confused here - the rangefinder messages are sent to the autopilot, and get automatically forwarded to QGC. What modification(s) are you trying to make in ArduSub?

@Sammi

ArduSub does receive a measurement but the latter doesn’t track altitude and seems to catch up with a very long lag (~10s) and the measurement update rate is only 1Hz.

The rangefinder updates are at the same time as the velocity updates. If position holding is working fine I expect that must be faster than 1 Hz.

If I’m understanding your intent correctly, this thread may be worth having a read of.

[Sammi]

Hi @EliotBR,

Thanks for taking the time to reply! These resources have been very helpful to better understand ArduSub background.

Regarding my problem, it turns out it disappeared when testing in deeper water. I haven’t tested again in shallow water but that may have been the problem…