DVL troubleshooting can be a complicated process with multiple variables that need to be accounted for. Every system and application is unique, but there are a few standard bullet points that can be used to establish an understanding and allow our engineers to find an efficient resolution.
This FAQ will cover the details and documentation necessary to begin the conversation.
Whether the issue you are having is related to communication or performance, the first steps are fairly similar. The more details that can be provided, the better. The best way to get in touch with us will be to send an email to email@example.com with the following information provided to the best of your ability. In addition to this, linked below is our Noise Measurement Guide which covers the potential causes of noise and some initial methods to begin troubleshooting.
Please provide details of:
- Your DVL frequency and depth rating, ideally the serial number of the unit would be best
- The issue being experienced, are you losing range of the instrument, is data not being transmitted correctly, etc.
- How the DVL is interfacing with the vehicle or application
- How is power being routed to the DVL, is it dedicated to just the DVL, wiring schematics if relevant
- How is data being parsed or transmitted
- A description of the power supply; voltage, switching frequency
- Physical details about mounting, power line insulation and routing, location of the DVL in relation to other sensors, how it is grounded, etc.
- Any details about other sensors, their power requirements, physical locations, and any acoustic frequencies that they are operating on
Pictures can be worth a thousand words, if you can provide pictures of:
- Mounting location and method
- Integration and cabling
- Any other sensors and their proximity to the DVL
- Any thrusters or moving parts and their proximity to the DVL
Some of the most important information can be found in files generated on the DVL itself. These files are necessary to evaluate performance and determine what the DVL is experiencing: