- most UHDAS computers are set to autologin upon boot
- in a terminal window, “UHDAS”
- click on the little ADCP icon on the task bar
A gui tool (“UHDAS”) comes up with tabs at the top, starting you in the Control Tab (Control over logging).
UHDAS will ask you for a cruise name. Enter something like nbp0407 or lmg0413a, (usually matches the ship schedule cruise name). This cruise name is used in several contexts, and must have only upper or lowercase letters, underscore, or digits (not the first character).
If you need to log data to a pre-existing cruise directory (e.g., you only wanted to stop data acquisition temporarily but chose to “End Cruise” as well), you can resume logging to it by giving the same cruise name again and confirming your choice in the UHDAS dialog box that appears. If in doubt, start another cruise leg. See the Control Tab in the Gui Tour for details.
- In the Control Tab, change any values needed for the cruise. Usually, the defaults are appropriate. Some cruises benefit from a few hours of bottom tracking at the beginning or end; see nots below on bottom tracking.
- Check that the RDI deck units are on.
If a trigger is used with the Ocean Surveyor, be aware that data quality will be reduced as fewer pings are used. If the ADCP is triggered
- USE ONLY ONE PING TYPE, i.e.
- do not use interleaved pings
- do not use bottom track
Click “Start Recording” to initiate data collection
Ocean Surveyors with old firmware occasionally got hopelessly confused. Cycle deck unit power to clear, and start over with UHDAS logging.
Once recording starts, green is good
After logging starts, UHDAS switches over to the Monitor Tab, showing green panels for each data stream being logged.
- Each panel is labeled with the instrument name and the serial port used. Ascii messages are displayed in the panels if the serial stream is ascii. If the serial stream is binary (e.g., ADCP raw pings) the panels contain a timestamp and number of bytes for each message recorded. Small colored buttons in the upper right corner reflect the status of the data being logged.
- If any of the logging panels in the Monitor Tab do not start acquiring data within a few seconds, check that the appropriate instrument, i.e., one or both of the RDI deck units and the necessary serial navigation devices, are up.
- After about 10 mins, there should be 5-min profile plots that display from the “Plots” tab. After 30 minutes, there should be a plot that displays from the “Average Plots” tab, as well as other diagnostic plots.
- Green is Good. Look at the panels in the Monitor Tab If everything is logged correctly, there will be no red status warnings.
- Red is Rubbish. If a data stream is lost for some reason (serial port failed, instrument failed) then part of the panel will turn red, as will the button in the top right corner. If this happens, check the instruments and serial cable connections. It may be necessary to change logging ports if one of the ports fails. If any of the physical configuration changes, the configuration file will also have to be altered.
- A daily email message will be sent to the ADCP Operator’s email account(eg. ET@nbp.usap.gov) containing information about the UHDAS ADCP computer system, logging, and processes. These messages should help in identifying and debugging problems.
- The UHDAS ADCP website (http://currents/adcp) will have figures that are updated regularly. Figures that update every 5 minutes are in the Plots Tab of UHDAS. Figures that update once per hour are in the Average Plots Tab. Figures should be updating regularly. If for some reason the figures quit updating, check the logging panels under the Monitor tab and make sure everything is green. If they are, DON’T ADJUST ANYTHING: the raw data are good, but the processing software hit a glitch for some reason. See UHDAS Troubleshooting for more detail.
Green panels indicate that a serial message was received with a valid checksum. This does not say whether the message is useful. This is usually only a problem with a flaky Ashtech. ADU units can lose their satellites and send messages with lots of commas or zeros, so the panel is green, but the data are worthless. For Ashtech specifically, look at the messages and make sure they are not junk. This link illustrates Ashtech message faliure modes.
- go to the Control tab
- click the button for Bottom Track (for the ADCP of interest) to toggle it. This enters the bottom track command but does not send it to the instrument. Do this before you stop recording to minimize downtime in pinging.
- Stop recording (wait until UHDAS is back at the CONTROL tab) and start recording with the new parameters. No need to end cruise or exit UHDAS.
- NB150 Bottom Track: switching between Bottom Track
on and Bottom Track off is a simple toggle.
- Ocean Surveyor Bottom Track for NB mode: switching
between Bottom Track on and Bottom Track off is a simple toggle.
- Ocean Surveyor Bottom Track for interleaved mode:
we always want TWO kinds of pings, but NOT THREE kinds of pings. If Bottom track is off, we want BB and NB pings. If you turn Bottom Track on, please turn NB off (the deepest mode). When you turn Bottom track off, turn NB pings back on (see table at the end of this section).
- click “Stop Recording”
- A pop-up box will ask you [...text...] “Do you want to stop data acquisition?
- Click “Yes”
- click “Start Recording” (again, wait a moment for it to think)
- Watch the dialogs as it starts communication with the ADCPs. It is at this point that the new command is sent to the instrument.
- Watch the Monitor tab to ensure that all panels come up green, with scrolling messages in them.
- Click back to the Control tab to verify that bottom tracking has changed status. Then return to the Monitor tab to leave the system with the green panels showing.
EXAMPLE: Ocean Surveyor Bottom Track for interleaved pinging
Bottom Track OFF
(deeper than 500m) –default–
Bottom Track ON
(shallower than 500m)
BB pings ON ON NB pings ON (off) Bottom Track (off) ON
UHDAS computers are often set up with a second internal disk as a data backup. UHDAS can also write the data to an external disk (eg. USB disk) or an accessible network (nfs) directory on another computer.
The status of the backups should be indicated in the daily ADCP Operator email.
The cruise data are shared via NFS and SAMBA, accessible as network shares using “currents” or the IP number, depending on the ship’s network configuration.