Specifications

Section 13. PakBus Communication Instructions
13-2
TABLE 13.1-2. ResultCode Error Codes
1 Read Only or Permission denied
2 Out of Space in the remote
3 Syntax Error
16 Invalid Table Name or Field Name
17 Data type conversion not supported
18 Memory bounds violation
19
20 Out of memory in the host
21 Cannot route to remote (communication not attempted)
The Timeout parameter in these instructions is in units of .01 seconds. If 0 is
used, then the default timeout defined by the time of the best route is used.
PakBus “Hop Metrics” are used to calculate this time.
Presently there is not a number of tries parameter. It is easy to retry within
CRBasic: For I = 1 to 3: SetSettings(ResultCode,….): if ResultCode = 0 Exit
For
(If needed, we can add a retry parameter or default to more than one try.)
These communication instructions will by default wait for a response or
timeout before the program moves on to the next instruction. They of course
can be used in a SlowSequence Scan. Optionally the ComPort parameter can
be negated, which will cause the instruction not to wait for a response or
timeout. This will make the instruction execute faster but any data that it
retrieves and the ResultCode will be set asynchronously with the Scan, i.e.,
whenever the communication is complete.
ClockReport
The ClockReport instruction sends the datalogger's internal clock value to a
remote datalogger in the PakBus network.
Syntax
ClockReport ( ComPort, NeighborAddr, PakBusAddr )
Remarks
This instruction initiates a one-way transmission of the datalogger's clock value
to a remote datalogger. No response is returned from the remote datalogger. If
the remote datalogger has a PakBusClock instruction with this datalogger's
address, the remote will set its clock according to the transmitted time value.