Page
215
of
248
GFR,status,totalbytes,start,numbytes,data
status will have one of the following values:
Value
Description
0
Ok.
1
File not found.
2
Get beyond file end.
6
Record not found.
7
Command format error
totalbytes will be set to the byte size of the whole file. It is not the number of bytes returned in this retry!
The client station should issue repeated GetFile commands until it has received totalbytes amount of data.
Retries are the responsibility of the client station. If totalbytes changes in the reply, the file has changed
and the get should be restarted. If a reply is missing, the client station must request the data again.
start should be the same value as startpos in the Get File command.
The numbytes value in the GFR response does not include the comma preceding the data
and refers to the number of data bytes from the file that are being returned, not the number
of packet bytes used to store the response (which would be twice the number of data bytes
when ASCII protocol is selected).
data is the data payload. It is the file data requested by the Get File command. There are numbytes bytes
of data.
Current data
Request the file "curdata.txt" and the station will reply with last measured sensor data. The reply is very
similar to what is found in LinkComm's Data tab. The format is
MM/DD/YYYY,HH:MM:SS,Label,Value,Units,Quality
Each line is terminated by a CR/LF. Date and Time are expressed as
in “01/31/2004” and “20:47:52”,
respectively. Quality is a single character defining the quality of the data where
“G” = Good and “B” = Bad
Below is an example:
M1 BATT, 12.190, 2017/03/16 17:11:10,
M2 TEMP, 24.00, 2017/03/16 17:11:10,
M3 MINO, 1032, 2017/03/16 17:11:10,
Note that if no measurements are enabled, GF commands for sensors.txt and curdata.txt will return
errors.
Summary of Contents for SUTRON XLINK 100
Page 230: ...Page 230 of 248...
Page 247: ...Page 247 of 248...
