Campbell Scientific CR6 CR6 Measurement and Control System - Page 475
SkippedSlowScan, 5.1.4 SkippedRecord, 5.1.5 ProgErrors, 5.1.6 MemoryFree, 5.1.7 VarOutOfBounds
![]() |
View all Campbell Scientific CR6 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 475 highlights
Section 10. Troubleshooting the CR6 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 on-line processing may be necessary. Skipped scans in Pipeline Mode indicate an increase in the maximum buffer depth is needed. Try increasing the number of scan buffers (third parameter of the Scan() instruction) to a value greater than that shown in the MaxBuffDepth register in the Status table. 10.5.1.3 SkippedSlowScan The CR6 automatically runs a slow sequence to update the calibration table. When the calibration slow sequence skips, the CR6 will try to repeat that step of the calibration process next time around. This simply extends calibration time. 10.5.1.4 SkippedRecord SkippedRecord is normally incremented when a write-to-data-table event is skipped, which usually occurs because a scan is skipped. SkippedRecord is not incremented by all events that leave gaps in data, including cycling power to the CR6. 10.5.1.5 ProgErrors If not zero, investigate. 10.5.1.6 MemoryFree A number less than 4 kB is too small and may lead to memory buffer-related errors. 10.5.1.7 VarOutOfBounds When programming with variable arrays, care must be taken to match the array size to the demands of the program. For example, if an operation attempts to write to 16 elements in array ExArray(), but ExArray() was declared with 15 elements (for example, Public ExArray(15)), the VarOutOfBound runtime error counter is incremented in the Status table each time the absence of a sixteenth element is encountered. The CR6 attempts to catch VarOutOfBound errors at compile time (not to be confused with the CRBasic Editor pre-compiler, which does not). When a VarOutOfBound error is detected at compile time, the CR6 attempts to document which variable is out of bounds at the end of the CompileResults message in the Status table. For example, the CR6 may detect that ExArray() is not large enough and write Warning:Variable ExArray out of bounds to the Status table. The CR6 does not catch all out-of-bounds errors. 10.5.1.8 Watchdog Errors Watchdog errors indicate the CR6 has crashed and reset itself. A few watchdogs indicate the CR6 is working as designed and are not a concern. 475
![](/manual_guide/products/campbell-scientific-cr6-cr6-measurement-control-a476969/475.png)