Welcome!

Share and discuss the best content and new marketing ideas, build your professional profile and become a better marketer together.

Sign up

You need to be registered to interact with the community.
This question has been flagged
8 Views

Drift is a velocity error integrated over time, so the useful question is not accuracy in percent but how long you can run before the position error exceeds your mission tolerance.

The error budget has three terms:

  • Scale-factor error. A velocity bias of a fraction of a percent of speed becomes a position error that grows linearly with distance travelled, not with time.
  • Heading error. This usually dominates. A small heading offset rotates the whole velocity vector, so cross-track error grows with distance and is much larger than the along-track term.
  • Bottom-lock gaps. Every dropout is integrated as dead reckoning on the last good velocity, and the error made during the gap is never recovered.

Practical consequence: a DVL alone is rarely enough for long missions. Aid it with a heading reference (gyro or FOG), reset position with USBL or a surface fix at intervals, and log bottom-lock quality so gaps can be flagged instead of silently averaged. For short, slow, well-tracked runs the DVL-only solution is perfectly adequate; for multi-hour AUV work it is not.

See DVL systems and navigation case notes.

Avatar
Discard