User's Guide

The ID of a specific sensor can be found using the attr -s command, under the
section sensor ID (index), it is the value given in parenthesis. If there is only one
sensor configured in the RTU, then the ID is always 0.
Example
: dacq abort 0
4.2.6. dacq date
Description
Use to set/synchronise the date/time of a sensor/logger.
Usage
dacq date <sensor_IX> where <sensor_IX> is the ID of the sensor to synchronise.
Remarks
Not all sensors support a date command, in particular it is not supported in a
standard way by the SDI-12 sensors. Thies and Davis loggers support this
command.
The ID of a specific sensor can be found using the attr -s command, under the
section sensor ID (index), it is the value given in parenthesis. If there is only one
sensor configured in the RTU, then the ID is always 0.
Example
: dacq date 0
4.2.7. dacq interval
Description
Used to set the sampling interval of a sensor/logger.
Usage
dacq interval <sensor_IX> <interval> where <sensor_IX> is the ID of the sensor to
set the sampling interval to and <interval> is the new sampling interval, in
seconds.
Remarks
Not all sensors support an interval command, in particular it is not supported in a
standard way by the SDI-12 sensors. Thies and Davis loggers support this
command. The command determines the sampling and storage interval in the
logger themselves.
Do not confuse this setting with the interval defined by a sensors
acquisitionSchedule attribute; for SDI-12 sensors, this attribute defines the storage
interval in the RTU’s memory.
The ID of a specific sensor can be found using the attr -s command, under the
section sensor ID (index), it is the value given in parenthesis. If there is only one
sensor configured in the RTU, then the ID is always 0.
Example
: dacq interval 0 600
4.2.8. dacq direct
Description
Used to directly connect to a sensor.
Usage
dacq direct <sensor_IX> where <sensor_IX> is the ID of the sensor to connect to.
This command is interactive, to exit the command type <ctrl-X>.
Remarks
While this command allows connection to any sensor, not all sensors support an
interactive conversation. In particular SDI-12 sensors cannot be reached in this
way. Moreover, the sensor/logger commands must be known. Thies loggers and
24