Nortek Signature Series User manual

Integrator's Guide2
© 2017 Nortek AS
Table of Contents
Ch. 1 Introduction 5
Ch. 2 Basic interface concept 6
................................................................................................................................... 62.1 Modes
................................................................................................................................... 72.2 Break
................................................................................................................................... 72.3 Dual Processor
Ch. 3 Interfaces 8
................................................................................................................................... 83.1 Command interface
................................................................................................................................... 83.2 Telemetry
................................................................................................................................... 93.3 Ethernet Operation
.......................................................................................................................................................... 10
Telnet Connection
.......................................................................................................................................................... 11
Raw Connections
.......................................................................................................................................................... 11
FTP
.......................................................................................................................................................... 12
HTTP
.......................................................................................................................................................... 12
UDP
.......................................................................................................................................................... 12
PTP
Ch. 4 User Cases 13
................................................................................................................................... 134.1 Average velocity data and NMEA, Signature 55
................................................................................................................................... 154.2 Download telemetry file via FTP
................................................................................................................................... 174.3 Download telemetry file over serial port
................................................................................................................................... 184.4 Erase telemetry file
................................................................................................................................... 194.5 Checking instrument state over Ethernet
Ch. 5 Commands 20
................................................................................................................................... 215.1 List of Commands
................................................................................................................................... 245.2 SETINST/GETINST/GETINSTLIM
................................................................................................................................... 245.3 SETCLOCK/GETCLOCK
................................................................................................................................... 245.4 SETCLOCKSTR/GETCLOCKSTR
................................................................................................................................... 255.5 SETPLAN/GETPLAN/GETPLANLIM
................................................................................................................................... 265.6 SETAVG/GETAVG/GETAVGLIM
................................................................................................................................... 275.7 SETBURST/GETBURST/GETBURSTLIM
................................................................................................................................... 285.8 SETBURSTHR/GETBURSTHR/GETBURSTHRLIM
................................................................................................................................... 285.9 SETECHO/GETECHO/GETECHOLIM
................................................................................................................................... 295.10 SETBT/GETBT/GETBTLIM

3Contents
3
N3015-007
................................................................................................................................... 295.11 SETALTERNATE/GETALTERNATE/GETALTERNATELIM
................................................................................................................................... 305.12 GETMEM
................................................................................................................................... 305.13 SETTRIG/GETTRIG/GETTRIGLIM
.......................................................................................................................................................... 30
TRIG
.......................................................................................................................................................... 31
Triggers
................................................................................................................................... 325.14 GETPWR
................................................................................................................................... 325.15 GETPRECISION
................................................................................................................................... 325.16 GETPRECISION1
................................................................................................................................... 335.17 SETUSER/GETUSER
................................................................................................................................... 335.18 GETHW
................................................................................................................................... 335.19 ID
................................................................................................................................... 345.20 SETDEFAULT
................................................................................................................................... 345.21 SAVE
................................................................................................................................... 355.22 DEPLOY
................................................................................................................................... 355.23 FWRITE
................................................................................................................................... 365.24 POWERDOWN
................................................................................................................................... 365.25 ERASE
................................................................................................................................... 365.26 FORMAT
................................................................................................................................... 365.27 SECREBOOT
................................................................................................................................... 365.28 LISTFILES
................................................................................................................................... 375.29 DOWNLOAD
................................................................................................................................... 385.30 INQ
................................................................................................................................... 395.31 GETSTATE
................................................................................................................................... 405.32 GETERROR
................................................................................................................................... 405.33 GETALL
................................................................................................................................... 415.34 RECSTAT
................................................................................................................................... 415.35 GETMISCLIM
................................................................................................................................... 425.36 GETXFAVG / GETXFBURST
................................................................................................................................... 435.37 SETTMAVG/GETTMAVG/GETTMAVGLIM
................................................................................................................................... 445.38 SETTMBURST/GETTMBURST/GETTMBURSTLIM
................................................................................................................................... 445.39 SETTMALTI/GETTMALTI/GETTMALTILIM
................................................................................................................................... 455.40 SETTMBT/GETTMBT/GETTMBTLIM
................................................................................................................................... 455.41 TMSTAT
................................................................................................................................... 465.42 DOWNLOADTM
................................................................................................................................... 465.43 STOREHEADERTM
................................................................................................................................... 465.44 ERASETM
................................................................................................................................... 475.45 TAG
Ch. 6 Data formats 48
................................................................................................................................... 486.1 Header Definition

Integrator's Guide4
© 2017 Nortek AS
.......................................................................................................................................................... 49
Checksum Definition
.......................................................................................................................................................... 50
Burst/Average Data Record Definition (DF3)
.......................................................................................................................................................... 62
Bottom Track Data Record Definition (DF20)
................................................................................................................................... 676.2 String Data Record Definition
................................................................................................................................... 676.3 Data Limit Formats
Ch. 7 Telemetry Data Formats 68
................................................................................................................................... 687.1 Averaging Mode
.......................................................................................................................................................... 69
AWAC NMEA Format (DF=100)
.......................................................................................................................................................... 71
NMEA Format 1 and 2 (DF=101/102)
.......................................................................................................................................................... 74
NMEA Format 3 and 4 (DF=103/104)
.......................................................................................................................................................... 75
RDI Workhorse PD0 data format.
................................................................................................................................... 767.2 Burst
.......................................................................................................................................................... 76
NMEA format 1 and 2 (DF=101/102)
................................................................................................................................... 807.3 Altimeter
................................................................................................................................... 817.4 DVL Bottom Track
................................................................................................................................... 827.5 ASCII Data Input Using Ethernet

Introduction 5
© 2017 Nortek AS
1 Introduction
The primary objective of this manual is to provide the information needed to control a Nortek
product that is based on the AD2CP hardware platform. This includes all instruments in the
Signature series. It is aimed at system integrators and engineers with interfacing experience, but
it also includes examples on how to configure and start the instrument for more unexperienced
integrators. The document's scope is limited to interfacing and does not address general
performance issues of the instrument. For a more thorough understanding of the principles, we
recommend the Principles of Operation and for information about how to operate the
instrument, we recommend the Operation Manual.
The document is complete in the sense that it describes all available commands and modes of
communication. For most users, it will make sense to let the supplied Nortek software do most of
the hardware configuration and then let the controller limit its task to starting/stopping data
collection.
As always, these types of documents are subject to change. We recommend that you check
http://www.nortek-as.com/en/support or contact Nortek to ensure you have the all the latest
information and versions of any software you plan to use.
If you have any comments or suggestions on the information given here, please let us know. Your
comments are always appreciated; our general e-mail address is [e-mail].
Revision
Version 1 - Initial Document
Version 2
20.10.2015
Version 3
01.03.2016
Version 4
14.03.2016
Version 5 - New commands
30.09.2016
Version 6 - Release 1, 2017
10.02.2017
Version 7 - Release 2, 2017
20.10.2017

Integrator's Guide6
© 2017 Nortek AS
2 Basic interface concept
The Nortek Signature Series products command interface are ASCII based and line oriented.
Before diving into the chapters covering interfaces and commands, the operational modes and
how to change between the modes are described. Understanding the use and constrains of the
modes is important as it is used frequently when communicating with the instrument.
2.1 Modes
The current profiler operates in distinct modes. These modes will have several explicit commands
in order control the instrument. The majority of the commands are initiated from the Command
mode. The possible modes for the instrument are:
Command = Command and control
Data Retrieval = Data download from recorder
Measurement = Data collection mode
Confirmation = Confirmation mode
Figure: Instrument modes of operation
Initializing communication with the instrument is performed by sending a <BREAK >, which is
defined below. The <BREAK> will either set the instrument in Confirmation mode or restart
Command mode. The options for changing mode depends on the present mode of the instrument
(see diagram above for clarity). The timeout shown in the diagram occurs if no commands are
received in the various modes. A timer will then ensure that instrument operation continues. The

Basic interface concept 7
© 2017 Nortek AS
timeout value in Confirmation and Data Retrieval modes is 60seconds. There is also a timeout in
Command Mode when operating over the serial interface. If no commands are received for 5
minutes, a break or a sequence of @@@@@@ must be sent to wake up the processor.
2.2 Break
<BREAK> over the serial RS232/RS422 interface is defined as:
@@@@@@<delay 100milliseconds> K1W%!Q <delay 300 milliseconds> K1W%!Q
The @@@@@@ are used to wake up the processor when it is in sleep mode since the instrument
will only be able to monitor activity on the serial line when it sleeps. The second sequence of the
actual break characters is there to ensure that a break is detected even when the instrument is
waking up due to some other cause (e.g. alarm from the real time clock). This ensures that the
processor will interpret the following command correctly.
The figure and the table below show the specified timing of the BREAK sequence:
K1W%!Q
K1W%!Q
@@@@@@ t1 t2 t3
Figure: Break timing
Symbol
Parameter
Min.
Typical
Max.
Unit
t1
Time from end of @-sequence to start of first K1W%!Q-
sequence.
100
150
ms
t2
Time from end of @-sequence to start of second K1W%!
Q-sequence.
500
1000
2000
ms
t3
Time between first and second K1W%!Q-sequence.
300
400
ms
2.3 Dual Processor
The AD2CP uses a two-processor (DSP) design; one dedicated to Doppler processing (BBP) and the
other to Interface (SEC). The primary interface is Ethernet, so the Interface processor is only powered
when external power is applied. Note that powering through the Ethernet cable will also power the rest of
the electronics.
Figure: Power distribution relating to the two-processor design.

Integrator's Guide8
© 2017 Nortek AS
3 Interfaces
In addition to the traditional serial port interface for real time data output there are several
options for communication over Ethernet. The Ethernet communication is handled by a dedicated
processor in the instrument. This network processor runs a Linux operating system, which makes
it possible to connect to the instrument via telnet, raw connections and FTP. The network
processor mainly provides Ethernet connectivity. The other processor in the instrument, called
the Doppler processor, is where the commands end up and where they are used to perform the
measurements as specified.
The concept of a telemetry file has also been introduced which can be utilized in several ways
depending on the chosen interface. Below are some details:
3.1 Command interface
The command interface makes it possible to communicate with a Signature instrument using
terminal software, the serial port and a set of commands. The interface is also available over
Telnet. Some highlights:
ASCII based and line oriented. Commands are terminated with CR/LF
Optional capsulation of commands using NMEA style prefix and checksum to ensure data
integrity
NMEA style commands will return argument names in their response
Argument limits can be retrieved through commands
Comprehensive validation and error handling is implemented.
Invalid configurations return the erroneous argument with limits directly, so that each
subsequent error can be handled until a valid configuration is achieved
A single command can be used to retrieve the complete configuration of the instrument with
optional output to file
Commands to set default parameters
External controllers can use commands to store data in the raw data file (e.g. GPS position)
3.2 Telemetry
Our use of the telemetry term implies a "subset transfer system", that is, storing a subset of data
for transfer over low-bandwidth links (for example over iridium links, acoustic modems, etc). The
telemetry file is typically used in cases where the integrator either does not have the processing
power or bandwidth (if only a low data rate serial port is available) to do the processing
themselves.
For online data transmission a versatile scheme for telemetry options is available. The telemetry
file can be read out over the serial interface either in chunks or as acomplete file while checksum
or CRC on the downloaded data can be applied in a configurable manner. This enables external
controllers to configure separate handling of all, or a subset, of the measured data. That means
the file can be output directly as they are ready, or the data can be stored to a telemetry file for
later retrieval. The data format can be selected from a number of formats, including both binary

Interfaces 9
© 2017 Nortek AS
and ASCII data formats.
Since the instruments store individual ping data to file, the telemetry option can also be used to
average velocity data within the instrument. This averaged data can be immediately output via
serial line or stored for later retrieval in telemetry files. System integrators are able to
regularly offload subsets of data using FTP and telemetry files can be deleted after
download.
Since the telemetry file can be retrieved also in data retrieval mode, the instrument will continue
measuring after a timeout delay if the data transfer was interrupted. Erasing the telemetry file
after data retrieval will ensure that no data is lost if the transfer is interrupted.
The raw data, by design, is not supposed to be deleted from the disk. The raw data is collected
and saved continuously throughout the deployment and the configuration is supposed to be set
up in such a way that there is sufficient disk space to last for the whole deployment period (that is
one of the factors that the deployment software takes into account). The raw data is then taken
off the disk after the deployment and post-processed as required.
To FTP
The telemetry option implemented in the Doppler processor enables system integrators to
regularly offload subsets of the data by using FTP. When the network processor receives an
incoming FTP request, it will interrupt the Doppler processor by entering data retrieval mode and
mount the file system of the recorder. The data files on the recorder can then be accessed over
FTP. The telemetry file can be deleted after it has been downloaded, which is particularly
suitable for event driven data downloads. If the instrument was started with the DEPLOY
command, it will resynchronize to its measurement time base after the FTP session has ended.
For an example on how to configure the instrument to output a telemetry file and download the
file to FTP, check out this section.
3.3 Ethernet Operation
The AD2CP uses TCP (transmission control protocol) for both command processing and data
transmission. The Internet Protocol uses a combination of the IP address and port to uniquely
identify a communications channel between two computers. For the AD2CP, different ports
represent different means of communicating with the instrument. TCP ports 9001, 2002, 9004are
assigned for the following uses:
Port 9000 is a telnet-protocol ASCII interface (require username / password authentication)
port 9001is a raw (binary) interface (requires username / password authentication)
port 9002is a data only channel (no input accepted)
port 9004 is an ASCII data only channel (no input accepted).
The password entry is ignored if password authentication, as shown in the web page
configuration, is disabled (so any input, including an empty password, is accepted). The

Integrator's Guide10
© 2017 Nortek AS
command and data record formats for the interfaces are the same as for the serial port.
Commands available in measurement mode should be preceded by the command BBPWAKEUP.
This ensures that the BBP is ready to process the command when it is received (see Checking
instrument state over Ethernet). In measurement mode, another BBPWAKEUP must be sent when
more than 2seconds has elapsed since the previous command.
If uncertain of the active mode it is good practice to send BBPWAKEUP before sending GETSTATE
or INQ.
3.3.1 Telnet Connection
The telnet interface (TCP/IP port 9000) is used for user interaction with the instrument. This
dedicated port can be used for entering commands and getting human readable responses
(ASCII). The supported command set is available in the Commands section. The Windows telnet
client can be used to connect into the instrument using the command line telnet ip_address 9000.
You will get prompted for a username (nortek) and password (hit Enter if password protection
hasn’t been enabled via the Web interface).
Signature Username: nortek
Password:
Nortek Signature Command Interface
The interface is very similar to the direct serial interface over RS232/RS422 but some additions are
made to simplify the interfacing. Most notable is the ability to send a<break> to the Doppler
processor just by using Ctrl-C (ASCII 0x03). The internal application takes care of waking up the
Doppler DSP and timing the delivery of the break string.
The telnet server is not configured to echo characters, so users wishing to see and/or edit
commands before sending them to the instrument should enable local echo and local line
editing. If those features are desired, a telnet client capable of supporting local echo and local
line editing must be used (e.g. PuTTY).
Port 9000 is dedicated for ASCII only communication whereas the ports described in the next
section provide the complete set of data, including binary output of the measurements. A telnet
client should not be used to access these ports. Read more about this in the next section.
To terminate the telnet connection, enter Ctrl-X (ASCII 0x18).

Interfaces 11
© 2017 Nortek AS
3.3.2 Raw Connections
A port can be understood as a address point between two communicating parts. When first
connecting to a data listening port, the string "\r\nNortek name Data Interface\r\n" ( name is
replaced by the instrument host name) is sent to identify the instrument that has responded to
the connection request. TCP ports 9001, 9002and 9004are assigned for the following uses:
Port 9001 is used for machine driven control. This port requires username/password. The serial
port data is translated directly into TCP/ IP over Ethernet. Binary data generated in
measurement mode is visible on this port. Standard streaming record delineation techniques
must be used in order to make sure that the received data is properly synchronized for
decoding. A break can be sent by sending the string K1W%!Q<CR><LF> to the instrument or a
Ctrl-C character (ASCII 0x03) (Ctrl-C has to be sent on its own and not embedded in any
command). The internal application takes care of the appropriate timing of the break sent over
the internal serial port. This port require username / password authentication. Refer to
previous section for example. The password entry is ignored if password authentication, as
shown in the web page configuration, is disabled (so any input, including an empty password, is
accepted). The command and data record formats for the interfaces are the same as for the
serial port.
Port 9002 is a data only channel which will output all data that is configured for serial output.
This can,for example,be used by display only software while configuration is done by another
application.
Port 9004outputs ASCII data (no binary) that is configured for serial output.
A telnet client should not be used to access these ports. Telnet incorporates its own binary
protocol which is neither interpreted nor sent via the raw connection. Using a telnet client on
these ports will result in extraneous characters being sent and certain binary characters being
interpreted by the client.
3.3.3 FTP
The internal data recorder is accessed over Ethernet using a standard FTP (File Transfer Protocol)
client. Together with the various telemetry options, the FTP data download serves as a simple
way to download measured data at regular intervals if true real time operation is not required.
Only the telemetry file can be deleted using FTP.
When an FTP connection is active, the internal state of the machine is changed so that commands
are no longer processed (and an error is returned when commands are entered). Terminating the
FTP connection or sending a BREAK followed by the CO command will switch the instrument back
to the mode it was in before the FTP session began. If a break command is sent while an FTP
transaction is in progress, the FTP connection will be forcibly terminated.
If an FTP connection is done when the instrument is in measurement mode (see Figure 1), the FTP
connection is made through data retrieval mode. When the FTP connection is terminated, the
instrument will then return to measurement mode. If there is no data transferred or FTP

Integrator's Guide12
© 2017 Nortek AS
commands sent for 120 seconds, the FTP connection will terminate and the instrument will return
to measurement mode.
For an example on how to configure the instrument to output a telemetry file and download the
file to FTP, check out the next section.
3.3.4 HTTP
HTTP (Hypertext transfer protocol) can also be used for data transmission. For organizations with
strong security / firewall restrictions, FTP access to the instrument may not be permitted. For that
reason, a web page allowing individual data files to be downloaded has been implemented in the
Ethernet processor. The web page can be accessed by clicking on the “Data Download (HTTP)” link
from the main web page.
3.3.5 UDP
UDP (user datagram protocol) can also be used for data transmission. When using UDP, the data
collection software simply waits for data to be sent from the instrument without having to
establish a connection first. This may be useful for cases in which instrument power is
intermittently interrupted and re-connecting to the instrument is not desirable. One downside
to UDP communications is that transmission of the data is not guaranteed. On a noisy / error-
prone connection, it is possible that the occasional datagram may be dropped. If every data
record must be received, then TCP is recommended.
In order to use UDP in a power-safe configuration, the IP address of the data collection software
and port must first be configured using the web interface. The IP address identifies the client to
which the data is to be sent and the port may be used to uniquely identify the instrument to the
application. The same port may be used for all instruments if the data collection software
examines the IP address of the received datagram to identify the instrument. Once this
information has been configured, the Ethernet processor will automatically send real-time data
records to the configured address / port. An instrument in measurement mode re-enters
measurement mode shortly after a power-cycle, so the data collection software will immediately
receive new data without having to re-establish a connection.
3.3.6 PTP
Precision Time Protocol (IEEE-1588) is a standard used for distributing a high-resolution absolute
time throughout an Ethernet network. The Signature series instrument can be configured to act
as a slave to an existing PTP master clock (customer supplied) located in the same Ethernet LAN.
The instrument contains a high-resolution clock which is synchronized and conditioned using PTP
when enabled. The timestamps contained within the data records are then generated from this
clock. When synchronized, these timestamps are typically aligned to within ~10 microseconds.
The PTP master clock must use UDP (layer three) and be configured for two-step operation with
an end-to-end delay mode in order to be compatible with the Signature series PTP
implementation. Using PTP does not affect the choice of UDP or TCP for the transport of data.

Interfaces 13
© 2017 Nortek AS
4 User Cases
Note that the Nortek Signature Series products command interface are ASCII based and line
oriented (commands terminated with CR/LF). All commands should be set explicitly. The .deploy
file created by the Deployment software is command-based and can be read directly into the
command interface. Entering the .deploy file into the command interface can be a good starting
point before modifying certain parameters using individual commands. Alternatively, use the
Deployment software's "Customize..." function to create a .deploy file and input commands in
the #CustomCommands section.
Comprehensive validation and error handling is implemented. The setup is verified when
sending the SAVE command. If there is anything wrong with the deployment plan, i.e. some of
the parameters are entered with values outside their specific range, an ERROR will be returned.
The GETERROR command will describe why. If SAVE is not used, the deployment plan will be
validated when sending the START or DEPLOYcommand. Note the difference between DEPLOY
and START, the latter will immediately start a measurement any time the instrument state returns
to Measurement mode such as by applying power or timeout from Data Retrieval Mode. If DEPLOY
is used, be aware that if the deployment time has passed when the battery is connected, the
instrument will resynchronize its data sampling according to the deployment time and the
instrument configuration. This means you may have to wait for one average measurement
interval or one burst measurement interval before the instrument starts to ping.
Invalid configurations return the ERROR with limits directly, so that each subsequent error can be
handled until a valid configuration is achieved. Argument limits can be retrieved through
commands. For example, if entering SETPLAN,MIAVG=5000, you will receive an OK. But when
saving or deploying, you will receive an ERROR. When using GETERROR: 134,"Invalid setting: Plan
Profile Interval","GETPLANLIM,MIAVG=([1;3600])" OK. The measurement interval must be within
1:3600seconds. The valid range for the various arguments can also be verified by using the
GETPLANLIMand GETAVGLIMcommands.
Below you will find four examples illustrating the format and how to use the telemetry file.
4.1 Average velocity data and NMEA, Signature 55
Either use the Deployment wizard to create a .deploy file which can be uploaded via the Terminal
Emulator, or set the configuration through commands (seen below). The .deploy file can also be
uploaded then customized via commands once in the Terminal Emulator.
In this example: Signature55, configured to alternate between fine and coarse current profiles
(3:1). In this case the user wanted to download the averaged fine profile upon request.
Configuration example:
%Recommended starting point for configuration file
SETDEFAULT,ALL
OK
%Setting plan for "Fine" profile

Integrator's Guide14
© 2017 Nortek AS
SETPLAN,MIAVG=600,AVG=1,DIAVG=0,VD=0,MV=10,SA=35,BURST=0,
MIBURST=120,DIBURST=0,SV=0,FN="Data.ad2cp",SO=0,FREQ=75
OK
SETAVG,NC=109,CS=5,BD=2,CY="ENU",PL=-6,AI=180,VR=1,DF=3,NPING=137,
NB=3,CH=0,MUX=0,BW="BROAD",ALTI=0,BT=0,ICE=0
OK
%Setting plan for "Coarse" profile
SETPLAN1,MIAVG=1800,AVG=1,DIAVG=0,VD=0,MV=10,SA=35,BURST=0,
MIBURST=120,DIBURST=0,SV=0,FN="Data.ad2cp",SO=0,FREQ=55
OK
SETAVG1,NC=54,CS=20,BD=2,CY="ENU",PL=-2,AI=180,VR=1,DF=3,NPING=60,
NB=3,CH=0,MUX=1,BW="NARROW",ALTI=0,BT=0,ICE=0
OK
%Setting the alternating measurement intervals and ratios of "Fine"
and "Coarse"
SETALTERNATE,EN=1,PLAN=1380,IDLE=10,PLAN1=180,IDLE1=230
OK
%Setting the telemetry file to average the "Fine" profile over the
averaging interval
SETTMAVG,EN=1,CD=1,PD=1,AVG=180,TV=1,TA=1,TC=1,CY="ENU",FO=1,SO=0,
DF=100
OK
SAVE,ALL
ERROR
%Finding where the error in the configuration is
GETERROR
"Invalid setting: Avg Average Interval too low for the configured
number of pings and profiling distance",LIM="GETAVG1LIM,AI=
([360;1800])"
OK
%Number of pings too high compared to desired averaging interval
with multiplex enabled.
SETAVG1,NPING=30
OK
SAVE,ALL
OK
Note that SETTMAVG,AVGmust equal the AI set by SETAVG,AI. To set telemetry averaging for the
alternate plan use SETTMAVG1, note that these will be recorded to the same telemetryfile.bin
file.
Enter START or DEPLOY,TIME to begin the deployment.

User Cases 15
© 2017 Nortek AS
4.2 Download telemetry file via FTP
In this example, a Signature1000 is set up to measure currents for 2minutes every 10minutes and
waves every hour (4096 samples at 4 Hz). The raw current data are processed and a subset is saved
as a telemetry file and made available on FTP.
Configuration example:
%Recommended starting point for configuration file
SETDEFAULT,ALL
OK
%Configuration for instrument:
SETPLAN,MIAVG=600,AVG=1,DIAVG=0,VD=0,MV=10,SA=35,BURST=1,
MIBURST=3600,DIBURST=0,SV=0,FN="Ex3.ad2cp",SO=0,FREQ=1000
OK
SETAVG,NC=21,CS=1,BD=0.2,CY="ENU",PL=0,AI=120,VR=2.5,DF=3,NPING=13,
NB=4,CH=0,MUX=0,BW="BROAD",ALTI=0,BT=0,ICE=0,ALTISTART=1,ALTIEND=30
OK
SETBURST,NC=13,NB=4,CS=1,BD=9.5,CY="BEAM",PL=0,SR=4,NS=4096,VR=2.5,
DF=3,NPING=1,CH=0,VR5=2.5,ALTI=1,BT=0,DISV=0,RAWALTI=1,
ALTISTART=4.8,ALTIEND=33.1
OK
%Configuration for telemetry file:
SETTMAVG,EN=1,CD=2,PD=1,AVG=120,TV=1,TA=1,TC=1,CY="ENU",FO=1,SO=0,
DF=100
OK
SAVE,ALL
OK
DEPLOY,TIME="2014-11-12 14:40:00"
OK
Go to ftp://your-IP-address to find the telemetry file (telemetryfile.bin). Here is part of the result
from the above configuration. Note that the data were collected in air.
$PNORC,091715,142440,1,0.24,-1.35,-2.21,-1.69,1.37,169.7,C,79,84,67,102,11,13,8,11*2B
$PNORC,091715,142440,3,0.64,-0.28,-1.91,-1.32,0.70,113.9,C,79,84,66,96,12,14,7,20*13
$PNORC,091715,142440,5,0.08,-0.50,-1.76,-1.48,0.51,171.2,C,78,84,66,92,11,13,7,24*1D
$PNORC,091715,142440,7,-0.37,0.97,-1.02,-1.07,1.04,339.0,C,78,84,66,67,11,14,10,10*21
$PNORC,091715,142440,9,-0.94,0.57,-0.76,-1.11,1.10,301.1,C,78,83,65,69,12,15,9,10*10
$PNORC,091715,142440,11,-0.37,0.76,-0.95,-1.06,0.85,334.0,C,78,83,65,66,13,15,8,8*14
$PNORC,091715,142440,13,0.05,-0.25,-1.64,-1.36,0.26,168.4,C,78,84,66,82,11,14,9,33*2F
$PNORC,091715,142440,15,-0.20,0.20,-1.36,-1.32,0.28,314.6,C,78,84,66,67,11,13,9,7*16
$PNORC,091715,142440,17,0.19,0.17,-1.47,-1.13,0.25,48.0,C,78,84,65,69,12,16,9,2*0D
$PNORC,091715,142440,19,-0.91,0.45,-0.90,-1.19,1.02,296.5,C,78,84,65,66,12,14,10,8*27
$PNORC,091715,142440,21,-0.49,0.66,-1.00,-1.11,0.82,323.1,C,78,84,65,67,12,14,11,10*13
$PNORI,4,Signature1000900002,4,11,0.20,1.00,0*1B
$PNORS,091715,143440,00000000,2A4C0000,14.3,1300.0,278.3,15.7,-33.0,0.000,-262.45,0,0*65

Integrator's Guide16
© 2017 Nortek AS
$PNORC,091715,143440,1,0.76,-1.62,-2.45,-1.73,1.79,154.8,C,78,83,67,102,12,13,5,12*26
$PNORC,091715,143440,3,0.30,-0.77,-1.94,-1.50,0.83,158.6,C,78,83,66,97,12,14,9,17*19
$PNORC,091715,143440,5,-0.22,-1.19,-1.83,-1.66,1.21,190.4,C,78,84,66,91,11,13,8,22*36
$PNORC,091715,143440,7,-0.20,0.71,-1.09,-1.15,0.74,344.0,C,78,84,66,67,12,13,7,9*20
$PNORC,091715,143440,9,-0.30,0.94,-0.96,-0.97,0.99,342.0,C,78,84,65,66,11,15,9,8*25
$PNORC,091715,143440,11,0.20,0.82,-1.23,-1.09,0.85,13.3,C,78,84,66,67,13,14,6,8*09
$PNORC,091715,143440,13,0.11,0.46,-1.44,-1.19,0.48,13.5,C,78,84,65,75,11,13,8,1*04
$PNORC,091715,143440,15,-0.42,0.77,-1.05,-1.12,0.88,331.0,C,78,83,65,66,11,14,8,10*2D
$PNORC,091715,143440,17,-0.15,0.34,-1.29,-1.17,0.37,336.4,C,78,83,65,66,13,15,8,1*15
$PNORC,091715,143440,19,-0.79,0.50,-0.93,-1.13,0.93,302.5,C,78,84,65,66,12,15,10,10*10
$PNORC,091715,143440,21,-0.30,0.83,-1.08,-1.12,0.89,340.1,C,78,84,65,67,12,13,8,9*15
$PNORI,4,Signature1000900002,4,11,0.20,1.00,0*1B
After downloading the telemetry file, erase it either via FTP or commands. Only the telemetry
file can be deleted using FTP.
%Erasing telemetry file
ERASETM,9999
OK
%Continuing the configured deployment plan
CO
OK
Note that the instrument does not process wave data internally (read more about this in the
Operation Manual, if interested) thus only current data will be output in the telemetry file.
For use with external controller it can be interesting to note the following: If the instrument is
started at e.g. 12:00, the first current profile is finished at 12:02(120seconds) and the next starts
about 12:10. That leaves us with 8 minutes to download the telemetry file to FTP before next
current profile starts. The clock drifts with about 1 sec/week. Since DEPLOY was used the
measurement intervals will resynchronize according to the deployment time and the instrument
configuration (see DEPLOY for more information), thus is should be easier to schedule automatic
data download as the window 12:02to 12:10 remains.

User Cases 17
© 2017 Nortek AS
4.3 Download telemetry file over serial port
In this example the user wishes to download the telemetry file in 4096 byte chunks.
Connect via Terminal Emulator while the instrument is measuring
Send Break
CONFIRM
OK
%Going into Data Retrieval Mode
RM
NORTEK AS.
Version 2176 (Sep 17 2015 18:58:53)
DATA RETRIEVAL MODE
OK
%Checking the size of the telemetry file. Return in bytes
TMSTAT
95558
OK
%Outputting the telemetry file over serial port in 4096 byte chunks
DOWNLOADTM,0,4096,CKS=1
OUTPUT...
OK
%Next 4096 byte chunk, etc
DOWNLOADTM,4097,4096,CKS=1
OUTPUT...
OK
%Erasing telemetry file
ERASETM,9999
OK
%Continuing the configured deployment plan
CO
OK
Copy the returned text and paste to file. Or check "Record to file", the file will appearby default
in: C:\Users\xxxx\Documents\Nortek\Deployment\Online
Parameters can be added to the DOWNLOADTMcommand to set start address, length of file, etc
(see section DOWNLOADTM)

Integrator's Guide18
© 2017 Nortek AS
4.4 Erase telemetry file
In this example, the user wishes to erase the telemetry file after some period of time.
Send Break
CONFIRM
OK
%Going into Data Retrieval Mode
RM
NORTEK AS.
Version 2176 (Sep 17 2015 18:58:53)
DATA RETRIEVAL MODE
OK
%Checking the size of the telemetry file. Return in bytes
TMSTAT
34768
OK
%Erasing the telemetry file
ERASETM,9999
OK
%Continuing the configured deployment plan
CO
OK
The telemetry file can also be erased over FTP.

User Cases 19
© 2017 Nortek AS
4.5 Checking instrument state over Ethernet
In this example a user connects to and powers the Ethernet port, but is unsure of the current
operational state. If power is applied while in measurement mode, it will continue the
measurement but not wake the Ethernet processor (BBP). If power is applied while in
deployment state a re-synch will occur and resume sleep mode. Hence it is necessary to use
BBPWAKEUP in both cases.
A typical sequence starts by wanting to know the state of the instrument before proceeding with
either a new measurement or data retrieval.
%Waking up the BBP to make sure commands are received
BBPWAKEUP
OK
%Inquiring the state the of the instrument
GETSTATE
GETSTATE,MODE=0010,DEPTIME=27521,MEASTIME=27521,CURRTIME="2015-09-
28 11:21:16",WAKEUP=2
OK
This indicates the instrument has been configured to deploy and has started its scheduled
deployment for 27521 seconds. See GETSTATE for more information.
Depending on the desired action, send Break usually followed by; either MC to enter command
mode, RMfor data retrieval or START/DEPLOY/CO to start/schedule/continue a deployment.

Integrator's Guide20
© 2017 Nortek AS
5 Commands
Valid Range: The valid range for the following commands are not listed because some of them
depend on the actual instrument in use. However, the minimum and maximum values can be
retrieved through the appropriate GETxxxxLIMcommand.
Example: send GETAVGLIM,CS to read the valid range of cell sizes.
Default values are not listed for all commands in this document as some of them depend on the
actual instrument in use. Default parameters can be retrieved be setting default configuration
(SETDEFAULT,ALL) and reading out the desired parameter through the appropriate GET command.
The same is the case for some of the minimum and maximum values that depend on the actual
instrument in use. The parameter range for the various arguments can be retrieved through the
appropriate GETxxxLIMcommand, e.g. GETAVGLIM,CS to read the valid range of cell sizes.
All command parameters should be set explicitly, e.g.
SETAVG,NC=10,BD=0.7
OK
A configuration of the instrument should always start with setting the default configuration, e.g.
SETDEFAULT,ALL
OK