Instructions for Checking ADCP Data Collection
Note: For CalCOFI, DO NOT use (click on) the three "View/Edit" buttons on the
right hand side of the AutoADCP window. These files are configured for
CalCOFI, any changes may result in loss of data.
Note: For CalCOFI, when using AutoADCP, DO NOT use (click on) the pull down word-icons at the
top of the "RD Instruments VmDas" window, "File View Options Control Chart Window Help".
These change parameters in the control files for data collection using VmDas.
We want to keep AutoADCP in control of data collection. If any changes are made to
the VmDas control files, the changes may override AutoADCP CalCOFI configured files
and may result in loss of data.
Note: When in the shallow.ini mode (broadband, os75_bt.txt) the ship must be in at least
21 meters of water to get any data in bin1. Chances are good data wont be collected
until the second station stop, station 28. If numbers do not start showing up in
all the "tabular" collumns ( that is bm(1)m/s, bm(2)m/s, bm(3)m/s, bm(4)m/s ) when the
ship is in 100m of water, something could be wrong.
***************************************************************************
**** BELOW is how to fill out the top of the log sheets
Cruise Name:
Standard is xxyymm where
xx is ship name (nh=New Horizon, dj = David Jordan )
yy is year, mm is month
Cruise Dates:
Fill in approximate start and end days of the cruise
Regions File (auotadcp):
Fill in the entire path from the AutoADCP screen.
This path and file should always be
C:\CalCOFI\AutoADCP\position.dat
Ini/Options File (auotadcp):
Fill in the entire path from the AutoADCP screen.
The path should always be the same
( C:\CalCOFI\AutoADCP\ ), but the
file should start as default_CalCOFI.ini, and then
switch between deep.ini and shallow.ini, depending
if the boat is in deep or shallow water. There
is a column on the logsheet to fill in the specific
file name (see ".ini file" below).
ADCP Text File (auotadcp):
Fill in the entire path from the AutoADCP screen.
The path should always be the same,
C:\CalCOFI\AutoADCP\ , but the
file will switch between os75_nb16.txt (shallow) and
os75_bb.txt (deep). These two files tell the
instrument whether to use the broadband or
narrow band capabilities.
Data Files (auotadcp):
Fill in the entire path from the AutoADCP screen.
The path should always be the same,
C:\ADCPDATA\ , but the file name will be increasing
numerically. The file name should be CalCOFI???_*.* .
There is a column on the logsheet to fill in the
specific file number (see "Data File" below).
***************************************************************************
**** BELOW is how to fill out the log sheet table
Date (leader panel):
In the leader panel of the VmDas window (click icon near top that
says "LDR"), record the GMT Date. Make sure it is updating.
Time (autoadcp or leader panel):
In the leader panel (VmDas window, click icon near top that
says "LDR") or the AutoADCP window, record the GMT Time. They
should be the same. Make sure it is updating.
Latitude (autoadcp or nav panel):
In the leader panel (VmDas window, click icon near top that
says "NAV") or the AutoADCP window, record the latitude. They
should be the same. Make sure it is updating.
Longitude (autoadcp or nav panel):
In the leader panel (VmDas window, click icon near top that
says "NAV") or the AutoADCP window, record the longitude. They
should be the same. Make sure it is updating.
Ashtech logging ( tail N2R, PASHR, time):
Open a dos prompt window. Go to the directory
"cd C:\ADCPDATA\". Find the most recent *.N2R file, which
is the ashtech logging file, with
"ls -lt *.N2R | head".
Tail the most recent file found in the previous ls command, using
"tail CalCOFI???_000000.N2R" ( ??? are the numbers in the file name )
Check the time stamp GPGGA, and make sure it is a current,
and make sure there is a nearby PASHR lines. Please log the 4th column
(columns are separated by commas) which is the ashtech heading. Is it realistic?
That is, is the ship really heading in that direction? If there are no PASHR lines,
the ashtech has stopped logging and needs to be restarted. See
instructions To RESTART ASHTECH
IMPORTANT: Another way to check if Ashtech is working is to
look at the MET computer/monitor. There is a
about in the center of the screen that shows the
Ashtech heading value. I have seen the value report
"INOP" when Ashtech is not working. I can not guarantee
that this is a foolproof method of checking Ashtech. but
it is worth keeping an eye on.
Gyro Heading (leader panel):
Fill in the Heading from the leader panel (VmDas window, click icon near
top that says "LDR"). Make sure it is updating.
Data File (autoadcp):
Fill in the 3 numbers after CalCOFI in the Data Files box in the
AutoAUTO window. The file name should change about every 2 hours.
.ini file (autoadcp, shallow or deep):
Fill in "shallow" or "S" if the Ini/Options File in the AutoADCP
window says shallow, or fill in "deep" or "D" if the Ini/Options File
in the AutoADCP window says deep. deep or shallow will also be
displayed as the window name on the VmDas window.
Switch Box Lights Blinking:
In the computer room, check that the ashtech antenna box lights are
blinking green most of the time and red every 5th or so time. If
they are not blinking green, are blinking red all the time, or not
blinking at all, ashtech needs to be checked.