User's Guide

4.2.3. dacq sample
Description
Used to sample and show sensor/logger data.
Usage
dacq sample <sensor_IX> [ date [ time ]] where <sensor_IX> is the ID of the sensor
to sample, while the optional date and time parameters can be used to specify a
point in time after which the data should be returned. Obviously, this is valid only
for loggers, i.e., devices having storage possibilities (e.g., Thies loggers or Vantage
Pro consoles); for SDI-12 sensors, these parameters are ignored.
Remarks
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.
The values in parenthesis represent the status bits: if 0, all is OK while status 1
means missing data.
Certain sensors may need longer time to return data, just be patient.
Example
: dacq sample 1
:
Mon Aug 3 18:27:45 2020
26.025999[0] 60.115002[0]
4.2.4. dacq retrieve
Description
Used to sample and store sensor/logger data.
Usage
dacq retrieve <sensor_IX> [ date [ time ]] where <sensor_IX> is the ID of the sensor
to sample, while the date and time parameters can be used to specify a point in
time after which the data should be returned, or in case of simple sensors (e.g.
SDI-12), the date/time stamp which will be associated to the retrieved values
when they are stored in the RTU’s memory. If no date is provided, the current date
and time will be used; for data loggers, the date of the last datapoint in the local
memory will be used for the request and the returned data point’s date will be
used as timestamp.
Remarks
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.
Note that this command, in contrast to the dacq sample command, stores the
retrieved data to the internal data base of the RTU. This data will then be pushed
on the M2M Gateway during the next session.
Certain sensors may need longer time to return data, just be patient.
Example
: dacq retrieve 0
4.2.5. dacq abort
Description
Aborts a running dacq sample or dacq retrieve transaction.
Usage
dacq abort <sensor_IX> where <sensor_IX> is the ID of the sensor to abort a
running transaction.
Remarks
Not all sensors support an abort operation.
23