Diagnostic log🔗
A diagnostic log contains DVL logs and measurements that help Water Linked support investigate issues such as loss of bottom lock, invalid velocity, weak signal, communication problems, or unexpected behavior.
When to collect a diagnostic log🔗
Collect a diagnostic log when:
- Water Linked support requests it.
- The DVL loses bottom lock unexpectedly.
- Velocity becomes invalid or drops out.
- Measurements are weak or noisy.
- You experience communication or web GUI issues.
How to collect a diagnostic log🔗
- Put the DVL in the same environment where the issue occurs.
- Open the DVL web GUI.
- Open the diagnostic log or diagnostics page for your DVL model.
- Follow the instructions in the web GUI to create and download the diagnostic log.
- Send the diagnostic log to Water Linked support together with relevant installation and test information.
Demo GUI links🔗
For more context on the web GUI pages, see DVL A50/A125 web GUI and DVL A100/A250 web GUI.
What to include when contacting support🔗
Use the support package checklist when preparing a support request.
See How to diagnose for troubleshooting guidance before contacting support.
Transducer numbering and protocol IDs
Mechanical/transducer diagrams number the transducers from 1 to 4. In protocol messages and diagnostic logs, the transducer id uses zero-based numbering from 0 to 3. The id is therefore the transducer number minus 1.