Section 18. troubleshooting, 1 programming, 1 status table as debug resource – Campbell Scientific CR200/CR200X-series Dataloggers User Manual

Page 163: 2 skippedscan, 3 varoutofbounds, 4 watchdogerrors

Advertising
background image

Section 18. Troubleshooting

Note If any component needs to be returned to the factory for repair or

recalibration, remember that an RMA number is required. Contact a Campbell

Scientific applications engineer to receive the RMA number.

18.1 Programming

A properly deployed CR200(X) measures sensors accurately and stores all data

as instructed by its program. Experienced users analyze data soon after

deployment to ensure the CR200(X) is measuring and storing data as intended.

Most measurement and data storage problems are a result of one or more

instances of improper program code or "bugs."

18.1.1.1 Status Table as Debug Resource

Consult the CR200(X) Status Table when developing a program or when a

problem with a program is suspected.

Read More! See

APPENDIX. Status Table and Settings

p. 15 for a complete list

of Status Table registers and hints on using the Status Table.

18.1.1.2 SkippedScan

Skipped scans are caused by long programs with short scan intervals or when

other operations occupy the processor at a scan's start time. Occasional skipped

scans may be acceptable but should be avoided. Skipped scans may compromise

frequency measurements made with pulse channels. The error occurs because

counts from a scan and subsequent skipped scans are regarded by the CR200(X)

as having occurred during a single scan. The measured frequency can be much

higher than actual. Be careful that scans that store data are not skipped. If any

scan skips repeatedly, optimization of the datalogger program or reduction of

online processing may be necessary.

18.1.1.3 VarOutOfBounds

Indicates the number of variables that are out of bounds, meaning the

dimensioned array is not large enough to store the variable. When this value is

non-zero, edit the program and increase the array size.

18.1.1.4 WatchdogErrors

Non-zero indicates the CR200(X) has crashed, which can be caused by power or

transient voltage problems, or an operating system or hardware problem.

Watchdog errors may cause telecommunications disruptions, which can make

diagnosis and remediation difficult. Sometimes a TrapCode will accompany a

WatchDogCnt.

151

Advertising