SonTek/YSI Argonaut-XR Technical Manual - HydroScientific West

SonTek/YSI
• Check the standard deviation data. See Argonaut Principles of Operation for a description of
the expected behavior of these data. Check that the standard deviation values are reasonable
based on the values of averaging interval and measurement volume size. Large standard
deviation values may be caused by motion of the deployment package. Look at the
compass/tilt sensor data to see if the system orientation shows large changes.
• Look at the compass/tilt sensor data. In particular, look for large tilt values that may indicate
the deployment package is not lying flat (or is even upside down). Also, look at how these
values change with time to see if the deployment package is moving.
• Consider any possible influences of the deployment environment. Common problems include
underwater structures, boundary interference, deployment lines and cables, and schools of
fish attracted by underwater moorings. Also, consider possible nearby sources of flow
interference (bridges, piers, etc.) that might change the expected velocity signal. Areas of
highly turbulent flow and large amounts of submerged bubbles can also affect velocity data.
• Look at the data from the temperature and pressure sensors to see if these are reporting
reasonable values.
• Re-evaluate the deployment parameters used (particularly measurement volume location and
timing parameters) to see if these might have had some unforeseen effect on performance.
Cannot retrieve data from internal recorder
Below are common causes of communication errors when retrieving data from the Argonaut
internal recorder.
• The software is being run from a DOS prompt within Windows rather that a dedicated DOS
environment. Memory resident features of Windows interfere with serial port operation. All
Argonaut software should be run from a dedicated DOS environment.
• The data-extraction baud rate is too high for reliable operation. This can be a function of the
length and quality of cables, the computer, and the operating environment (for external
sources of noise). Run SonRec using a lower extraction rate (see Argonaut Software Manual).
• Some computers have poor quality serial ports and are unable to retrieve large amounts of
data at high baud rates. Run the data retrieval software using a lower extraction rate (see
Argonaut Software Manual). If problem persists, use another computer if possible.
If you are still unable to retrieve data from the internal recorder using SonRec, establish direct
communications with the Argonaut and use the recorder commands to access data files directly
(§3.11). Check that the file size and number of samples recorded is reasonable based on the
deployment length and user-setup parameters. Download the configuration and some portion of
the data manually to verify that all data are present.
Missing data from autonomous deployment
The Argonaut internal recorder was designed for extremely high reliability, and we have not had
a single recorder failure. The only data losses that have occurred are because of problems with
the Argonaut power supply. If you have a deployment that appears to be missing data, look at the
battery voltage recorded with each sample. Check that these values are reasonable based on the
type of power supply used and the length of the deployment. If you cannot determine exactly
what has occurred, place the data file on our FTP site and contact SonTek directly (Section 8).
72
Argonaut Operation Manual Firmware Version 7.9 (May 1, 2001)