System information

Section 2. Protocols and Packet Types
2-20
When a response comes in from this command, the fields after RespCode exist
only if the response indicates the transaction completed. If the response to the
Collect Data Command sets the parameter IsOffset equal to one, the client
must retrieve the remaining fragments of the record by using collect mode
0x08. The client should know the size of the record and therefore know when
the entire record has been collected.
Collect Data Response Body (MsgType 0x89):
Name Type Description
MsgType Byte Message type code (0x89)
TranNbr Byte Transaction number
RespCode Byte Response code:
0x00: Completed
0x01: Permission denied
0x02: Insufficient resources
0x07: Invalid table definition
{ { TableNbr UInt2 Table number
BegRecNbr UInt4 The first record number from the table
IsOffset bit 7 A flag that, if true, indicates this message
contains a fragment of a single record.
NbrOfRecs 15 or 31 bits Number of Records (15-bit value) in RecFrag
field or if IsOffset is true, it is the byte offset
(31-bit value) into the current record where this
fragment starts. The offset is based from the
beginning of the TimeOfRec field.
{ TimeOfRec } Sec, USec, or NSec Time of the first record relative to Jan 1, 1990.
This field only exists for interval data and also
only exists on the first fragment of a
fragmented record. The table definition
interval will be non-zero.
RecFrag } Byte [ ] Records as specified by the collection
parameters or if the IsOffset field is true, this is
a fragment of a record. Note: a time field
exists preceding each record on event driven
data, and the table definition interval is zero.
MoreRecsExist } Bool More records or fragments exist. Since the
datalogger may limit the response message size
to the larger of 512 bytes or one record,
sometimes not all of the requested records can
be returned in a single response. If more
records exist that meet the criteria of the
collection parameters than are returned from
the datalogger, this flag will be set.
2.3.4.4 One-Way Data Transaction (MsgType 0x20 & 0x14)
One-way data messages provide a way for a datalogger to send records to an
application when the underlying network has either limited or no support for
two-way communication. These one-way data messages may also be used to
emit data to an application during an event or on a regular schedule. One-way
data messages are initiated and controlled completely by the datalogger
program. The application must recognize these packets as they are received
from the datalogger and handle them appropriately.