Campbell Scientific CR1000 Measurement and Control System - Manual (Page 538)

Appendix B. Status Table and Settings
538
Table 121. Status-Table Fields and Descriptions
Fieldname Description Variable Type Default Range Edit? Info Type
CalSeOffSet 19
Calibration table of single-
ended offset values. Each
integration / range
combination has a single-
ended offset associated with
it. These numbers are
updated by the background
slow sequence if needed in
the program.
Integer array of 18 close to 0 Calib
CalDiffOffset
19
Calibration table of
differential offset values.
Each integration / range
combination has a
differential offset associated
with it. These numbers are
updated by the background
slow sequence if needed in
the program.
Integer array of 18 close to 0 Calib
1 The station name written to the header of data files by the datalogger support software (p. 77) is the
station name entered when the software was set up to communicate with the CR1000. In contrast, the
station name set in the
Status table (by typing it directly into the field, using the StationName()
instruction, or using the SetStatus() instruction), can be sampled into a data table using data table
access syntax. See the Program Access to Data Tables (p. 148) section for more information.
2 PakBus Addresses 1 to 4094 are valid. Addresses >= 4000 are generally reserved for a PC by the
datalogger support software (p. 77).
3 Watchdog errors are automatically reset upon compiling a new program.
4
Replace the lithium battery if <2.7 Vdc. See Replacing the Internal Battery (p. 417) for replacement
directions.
5
The 12 Vdc low comparator has some variation, but typically triggers at about 9.0 Vdc. The
minimum-specified input voltage of 9.6 Vdc will not cause a 12-Vdc low condition, but a 12-Vdc low
condition will stop the program execution before the CR1000 will give bad measurements on account
of low supply voltage.
6 A 1 indicates that the program was compiled due to the logger starting from a power-down condition.
A 0 indicates that the compile was caused by either a Program Send, a File Control transaction, or a
watchdog reset.
7 The VarOutOfBound error occurs when a program tries to write to an array variable outside of its
declared size. A programming error causes this, so it should not be ignored. When the datalogger
detects that a write outside of an array is being attempted, it does not perform the write and increments
the VarOutOfBound register. The compiler and pre-compiler can only catch things like reps too large
for an array, etc. If an array is used in a loop or expression, the pre-compiler does not (in most cases,
cannot) check to see if an array is accessed out of bounds (i.e. accessing an array with a variable index
such as arr(index) = arr(index-1), where index is a variable).
8
The background calibration runs automatically in a hidden SlowSequence scan. See the Self-
Calibration (p. 289) section.
9
If no user-entered SlowSequence scans are programmed, this variable is not listed in the table. If
multiple user-entered SlowSequence scans are programmed, this variable becomes an array with a
value for each scan.
10
The order of tables is the order in which they are declared.
11 CF card bytes free is set to -1 when no CF card is present.
12
Displays a large number until a SlowSequence scan runs.