Download Print this page

Advertisement

Quick Links

CiTaDel / WorkHorse ADCP Interface
1.
Introduction
This application note describes how a Teledyne RD Instruments WorkHorse ADCP
with Firmware 16.20 and greater can be interfaced with a TRDI CiTaDeL CTD with
Firmware 5.12 and greater.
The TRDI CiTaDeL CTD is attached to the WorkHorse via an adapter cable (see
Interface
Cables) that connects the WorkHorse RS-485 communications to the RS-
232 communications of the TRDI CiTaDeL CTD.
The WorkHorse interrogates the TRDI CiTaDeL CTD and stores the TRDI CiTaDeL
CTD data in the WorkHorse.
Figure 1.
TRDI CiTaDeL CTD Connected to the WorkHorse in Self-Contained
Configuration
Important Points:
FSA-028 (April 2011)
Information included herein is controlled by the Export Administration Regulations (EAR) and may require an export license,
license exception or other approval from the appropriate U.S. Government agency before being exported from the United
States or provided to any foreign person. Diversion contrary to U.S. law is prohibited.
To enable the TRDI CiTaDeL CTD interface you must add the
CC000000001 command to the command file.
Data is stored in the WorkHorse, not the TRDI CiTaDeL CTD.
The data stream stored in the WorkHorse from the TRDI CiTaDeL
CTD can be as long as necessary and easily exported using TRDI
WinADCP.
Application Note
FSA-028 (April 2011)
page 1 of 22

Advertisement

loading
Need help?

Need help?

Do you have a question about the CiTaDel and is the answer not in the manual?

Questions and answers

Summary of Contents for Teledyne RD Instruments CiTaDel

  • Page 1 Introduction This application note describes how a Teledyne RD Instruments WorkHorse ADCP with Firmware 16.20 and greater can be interfaced with a TRDI CiTaDeL CTD with Firmware 5.12 and greater. The TRDI CiTaDeL CTD is attached to the WorkHorse via an adapter cable (see...
  • Page 2 Both are communicating in RS232 mode with a baudrate set at 9600bds. 1.1.1 WorkHorse Setup Checklist a. The CC command is used to enable the TRDI CiTaDeL CTD interface. The command CC000000001 and SB0 must be added to the command file. b. The WorkHorse ADCP baudrate must be set to 9600bds.
  • Page 3: Timing Description

    At the start of the ensemble the WorkHorse sends the retrieve data command (@@DATA01) and reads the response from the TRDI CiTaDeL CTD. The data is stored in a field in the ensemble data and the TRDI CiTaDeL CTD is powered down (@@PWROFF).
  • Page 4 CiTaDel / WorkHorse ADCP Interface CAUTION. The WorkHorse will not attempt to interrogate the TRDI CiTaDeL CTD if less than 5 seconds has elapsed since the last TRDI CiTaDeL CTD data but uses the last good sample 1.1.4 TRDI CiTaDeL CTD Battery Life In order to calculate Battery Life please used CTDPro as follow: a.
  • Page 5 Application Note FSA-028 (April 2011) Check Interval and Click Next. g. Manually set the following and Click Next: • Interval Time= Time Between WHADCP pings = TP • Record Time= 10seconds FSA-028 (April 2011) page 5 of 22 EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 6 Find the resulting Battery Life. Figure 2. WinADCP Export Options NOTE. You must use WinADCP version 1.11 to export TRDI CiTaDeL CTD data. page 6 of 22 Teledyne RD Instruments EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 7 The WH ADCP will capture the data exactly as it is output from the Citadel CTD into a 256byte data buffer inside the WH PD0 string. The WH ADCP PD0 data ID is 0800h and the data will follow this data ID.
  • Page 8 CiTaDel / WorkHorse ADCP Interface c. Verify that you are in Run Mode by sending ‘MODE’ command which should return ‘Run Mode’. If not then send ‘***R’ and then send ‘MODE’ [note: if you get a ‘BAD COMMAND, TYPE ?+Enter’ simply resend the command] d.
  • Page 9 Application Note FSA-028 (April 2011) NOTE. It is strongly advised to use PlanADCP to create your original Scirpt File. d. Set a delayed start using the ‘TF’ command to at least 1hour in the future to leave you enough time to setup your ADCP and CTD and then plug the Inter- face Cables between them.
  • Page 10 CiTaDel / WorkHorse ADCP Interface e. A new dialog window will open: Click Cancel g. Go To menu Functions > Import Planning File: h. Select your Script File: Go To menu ADCP > Settings or Press ‘F5’ key: page 10 of 22 Teledyne RD Instruments EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 11 Application Note FSA-028 (April 2011) Setup the communication link with the ADCP to 9600bds then click OK CAUTION. The WorkHorse ADCP and the CTD must be both set to communicate at 9600bds. k. Go To menu Functions > Deployment Wizard: Check the Skip Planning Step checkbox and click Next: FSA-028 (April 2011) page 11 of 22...
  • Page 12 TRDI CiTaDeL CTD Setup a. If you have not already installed the program CTDPro, then do so now. You should have a copy on the CD you’ve received with your TRDI CiTaDeL CTD or you can download it from our support website here.
  • Page 13 FSA-028 (April 2011) d. Select CTD >Communication > Setup and enter the correct Baudrate and Comport Number for your TRDI CiTaDeL CTD. e. Select CTD >Communication > Find CTD Select CTD >Communication > Settings and set the baudrate to 9600 bds.
  • Page 14 CiTaDel / WorkHorse ADCP Interface g. Set your Sample Rate and leave the Average Time to zero. Click OK. h. Select CTD >Configure and Deploy Set the Time of the CiTaDeL to the PC time Select Continuous for the Running Mode k. Hit Deploy!
  • Page 15 Send ROP to see which channels are set for output d. Send CHx=ON to enable one of the channel output to be added to the CiTaDeL CTD stream which will be stored in the WH ADCP (Where x= channel number) e.
  • Page 16: Bench Test

    CiTaDel / WorkHorse ADCP Interface NOTE. Refer to the TRDI CiTaDeL CTD Manual for more details. Bench Test It is very important to test the interface by running a Bench Test in order to verify that all parts of the system are properly setup and that your WH/CTD integrated system will work as expected during the length of the deployment.
  • Page 17 Application Note FSA-028 (April 2011) NOTE. The first ensemble sometimes does not have the CTD sample available due to tight timing on first ping, as long as the second ensemble and following ones have the CTD data embedded the setup is working as expected. NOTE.
  • Page 18: Data Recovery

    CiTaDel / WorkHorse ADCP Interface Data Recovery The TRDI CiTaDeL CTD data is part of the WorkHorse raw data. The TRDI CiTa- DeL CTD data can be exported from the WorkHorse data using the Export menu in WinADCP. a. Start WinADCP and load your data file.
  • Page 19: Interface Cables

    Application Note FSA-028 (April 2011) Interface Cables Figure 4. WHADCP/CTD/Bentos Modem Interface cable FSA-028 (April 2011) page 19 of 22 EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 20 CiTaDel / WorkHorse ADCP Interface Figure 5. WHADCP/CTD Interface cable page 20 of 22 Teledyne RD Instruments EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 21 Application Note FSA-028 (April 2011) Figure 6. WHADCP/CTD to External Battery Pack or Std WHADCP cable Interface cable FSA-028 (April 2011) page 21 of 22 EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
  • Page 22 CiTaDel / WorkHorse ADCP Interface Appendix-A Interface your Teledyne RDI CiTaDeL CTD/WorkHorse ADCP system with a Tele- dyne Benthos modem. WorkHorse ADCP Setup Teledyne Benthos modems can support serial baud rates of 9600 baud with all generations of hardware and the newer equipment can support up to 115,200 baud though 9600 is still preferred.

This manual is also suitable for:

Workhorse adcp