System information

Section 4. The CR1000 Type Datalogger
4-3
settings for this and other operating systems by reviewing the included Device
Description File in Appendix C.
Setting ID Name
0 OS Version
1 Serial Number
2 Station Name
3 PakBus Address
4 Security
4.5 Getting and Setting the Clock
The CR1000 type datalogger contains a precise clock that drives the execution
interval of the running program. An application can either check or set the
datalogger clock with the Clock Transaction.
Before attempting to set the datalogger clock, the application should always
check the current time. Then, if necessary, the appropriate adjustment can be
made by either adding time to or subtracting time from the datalogger clock
with the Clock Command message. A hexadecimal example of this message
that is checking the clock for a datalogger with a PakBus address of 1 looks
like:
BD A0 01 4F FE 10 01 0F FE 17 17 00 00 00 00 00 00 00 00 00
00 B2 B3 BD
The response from the datalogger to the clock request comes in the form of the
Clock Response message. A hexadecimal example of a clock response packet
looks like:
BD AF FE 00 01 1F FE 00 01 97 17 00 1B FA 2A 61 C8 00 00 00
04 FA BD
4.6 The Program Structure
CR1000 type datalogger programs are written with a programming language
called CRBasic. This BASIC-like programming language facilitates the
creation of datalogger programs capable of precise measurement and data
analysis. Programs are sent to the CR1000 type datalogger as ASCII text
where the datalogger operating system compiles and runs them.
Datalogger programs execute on a precise interval to process data or store
measurements. Data are stored in tables that are defined by the datalogger
program. The CR1000 type datalogger includes the Status table and the Public
table by default. The number of additional tables that can be defined by the
datalogger program is only limited by the amount of memory available in the
datalogger.
The CR1000 type datalogger compiles the program and creates tables that are
stored in battery backed RAM. Therefore, when the datalogger is powered
down, the data remains. However, since the datalogger program creates the
tables, all data are erased when a new datalogger program is compiled and run
by the datalogger.