Pathfinder DVL Guide April 2018
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Page 53
Describe Deployment Environment & Operational Conditions
It is important to document the deployment environment of the test or mission that has occurred. The fol-
lowing parameters are important:
• Location
• Water description
• Bottom Type – topography and bottom type
• Depth
• Sediment conditions
• Temperatures
• Salinity
• Proximity to ocean structures or acoustic reflectors
• Speed through water
Describe the System Installation
Provide a description of your vehicle, and more specifically a description of the system, ADCP and/or
DVL, installation(coupling with the vehicle, material used for the mounting plate, beams behind a fair-
ing, voltage sent to the unit, triggering scenario implemented, etc.).
Provide Raw Data & Describe Issue for Analysis by TRDI
• Describe the performance issue or problem.
• Recover the raw data from your instrument. This will preferably be done in the PD0 output for-
mat. The information will be sent to TRDI with the complete deployment data if it is not possible
to provide PD0 data please identify the data format in which the data was collected.
• Provide screenshots or ensemble numbers to locate region(s) showing the unexpected data be-
havior.
Provide Additional Data for Analysis by TRDI
If the data you recorded does not match alternate instrumentation providing the same data in the same
reference frame, please provide the other device(s) data in a text file or an ASCII Text comma (or other
ASCII character) delimited format file. If none of the above are feasible, screenshots of data plots could be
provided in place of the above. Attach a description of the data and of the instrument from which it was
recorded.
Record Engineering Data for Analysis by TRDI
Re-deploy in the closest conditions and location from where the previous deployment occurred. However,
prior to deployment add the following commands to your Script File or set-up commands.
If you are already decoding PD0 and your decoding algorithm can handle more bytes in each
ensemble [engineering data bytes] then you can record this Engineering PD0 data into a file
for us to review it with our Engineering software suite. It is not mandatory to use the MR1
command to enable recording onto the loop recorder, nor to erase the loop recorder first as
described below.
Before new data can be acquired, the recorder has to be erased. This is done by opening a TRDI Toolz
session (see Connecting to the Pathfinder) and then send the command me ErAsE to your Pathfinder.
This will erase the recorder.
To Next Page
Loading...