Nortek Signature 100, Manual

Page: 13 / 85

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 DEPLOY command. 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:3600 seconds. The valid range for the various arguments can also be verified by using the
GETPLANLIM and GETAVGLIM commands.
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