07.01.2015 Views

CR200/CR200X Series Dataloggers - Campbell Scientific

CR200/CR200X Series Dataloggers - Campbell Scientific

CR200/CR200X Series Dataloggers - Campbell Scientific

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix B. Status Table and Settings<br />

Table 26. Status Table Fields and Descriptions<br />

RfRXPakBusCnt<br />

Status<br />

VarOutOfBounds<br />

Number of times an array<br />

was accessed out of<br />

bounds 2<br />

Integer 0 0 Can Reset =<br />

0<br />

Error<br />

SkipScan<br />

Number of skipped scans<br />

that have occurred<br />

because the datalogger<br />

was not finished with the<br />

previous scan<br />

Integer 0 _ Can Reset =<br />

0<br />

Error<br />

TrapCode<br />

Indicates a problem with<br />

datalogger memory<br />

Integer 0 0 or 16 _ Error<br />

WatchDogCnt<br />

Number of Watchdog<br />

errors that have occurred<br />

while running this<br />

program 3<br />

Integer 0 0 Can Reset =<br />

0<br />

Error<br />

ResetTables<br />

Resets all the data tables<br />

in the datalogger when<br />

changed to 8888<br />

Integer 0 _0 Can Reset =<br />

8888<br />

Status<br />

BattVoltage<br />

Current value of the<br />

battery voltage.<br />

Measurement is made in<br />

the background<br />

calibration.<br />

Float _ 7-16 Volts _ Measure<br />

ProgSignature<br />

Signature of the current<br />

running program file<br />

including comments. Does<br />

not change with operating<br />

system changes.<br />

Integer _ _ _ Status<br />

1. Pak Bus Addresses 1 to 4094 are valid. Addresses >= 4000 are<br />

generally used for a PC by PC200W, RTDAQ, PC400, or LoggerNet.<br />

2. Watchdog errors are automatically reset upon compiling a new<br />

program.<br />

3. The Variable Out-of-Bounds error occurs when a program tries to write<br />

to an array variable outside of its declared size. A programming error<br />

causes this, so it should not be ignored. When the datalogger detects<br />

that a write outside of an array is being attempted it does not perform<br />

the write and increments the VOOB in the status table. The compiler<br />

and pre-compiler can only catch things like reps too large for an array<br />

etc. If an array is used in a loop or expression the pre-compiler does not<br />

(in most cases cannot) check to see if an array is accessed out of<br />

bounds (i.e. accessing an array with a variable index such as arr(index)<br />

= arr(index-1), where index is a variable).<br />

17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!