System information

Section 4. The CR1000 Type Datalogger
4-2
BD AF FE 00 01 5A 89 BD
The datalogger may not be aware that a connection has been established from
the PC when beginning the initial communication process. The application
should initiate communication to the CR1000 by sending a series of 0xbd
SerSyncBytes before the initial packet to wake up the datalogger, clear the
communication buffer, and determine the communication baud rate.
Since the CR1000 type datalogger supports automatic baud-rate
synchronization, the recommended procedure is to send at least six
SerSyncBytes before sending the Ring packet.
4.3 Getting the PakBus Address
Knowing the address of the CR1000 type datalogger is necessary for
communication. Every PakBus device needs a PakBus address to send and
receive packets. In addition all devices on the network need unique addresses.
The valid range for PakBus addresses is 1to 4094. The address range of 1 to
3999 is normally reserved for dataloggers while the address range of 4000 to
4094 is normally reserved for applications. The CR1000 type datalogger ships
with a default PakBus address of 1 but could have any address within the
allowable range.
If the address of the CR1000 type datalogger is unknown, it can be obtained
with a PakCtrl Hello Request Message. Since all PakBus dataloggers on the
network will respond to this broadcast type message, make sure you are
connected to a single datalogger before you send a PakCtrl Hello Request
Message in order to determine that specific datalogger’s address.
The DstPhyAddr and DstNodeId in the header of the Hello Request Message
should be specified as 4095 to indicate a broadcast packet. The datalogger will
respond to the application with a Hello Command transaction that contains its
PakBus address in the header.
4.4 Getting and Setting Datalogger Settings
The DevConfig protocol is used to get settings from and set setting on the
CR1000 type datalogger. The DevConfig Get Settings transaction is used to
request specific settings from the datalogger according to the setting ID.
Similarly the setting ID is used with the DevConfig Set Settings transaction
when attempting to change a particular setting on the datalogger.
In both of these cases, the setting ID used comes from the Device Description
File for the CR1000 datalogger found in Appendix C. This XML file contains
setting ID catalogs corresponding to specific operating system versions for the
CR1000 type datalogger. Since parsing this XML file may be difficult,
viewing the file and merely including the necessary settings with a
corresponding ID in the application is an acceptable method for getting settings
from and setting settings in a CR1000 type datalogger.
Settings are specific to the operating system of the CR1000 type datalogger.
An example of some common settings for CR1000 type datalogger operating
systems are taken from the Device Description File in Appendix C include but
are not limited to those described in the following table. Discover additional