Section 10. Troubleshooting
473
skipped scans are regarded by the CR800 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.4.3 SkippedSystemScan
The CR800 automatically runs a slow sequence to update the calibration table.
When the calibration slow sequence skips, the CR800 will try to repeat that step
of the calibration process next time around. This simply extends calibration time.
10.5.4.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
CR800.
10.5.4.5 ProgErrors
Should be
0
. If not, investigate.
10.5.4.6 MemoryFree
A number less than 4 kB is too small and may lead to memory-buffer related
errors.
10.5.4.7 VarOutOfBounds
Related Topics:
•
Declaring Arrays
(p. 134)
•
VarOutOfBounds
(p. 473)
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 CR800 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 CR800 attempts to
document which variable is out of bounds at the end of the
CompileResults
message in the
Status
table. For example, the CR800 may detect that
ExArray()
Summary of Contents for CR800 Series
Page 2: ......
Page 4: ......
Page 6: ......
Page 32: ......
Page 34: ......
Page 54: ......
Page 92: ......
Page 310: ......
Page 446: ...Section 8 Operation 446 8 11 2 Data Display FIGURE 100 CR1000KD Displaying Data ...
Page 448: ...Section 8 Operation 448 FIGURE 102 CR1000KD Real Time Custom ...
Page 449: ...Section 8 Operation 449 8 11 2 3 Final Storage Data FIGURE 103 CR1000KD Final Storage Data ...
Page 450: ...Section 8 Operation 450 8 11 3 Run Stop Program FIGURE 104 CR1000KD Run Stop Program ...
Page 452: ...Section 8 Operation 452 FIGURE 106 CR1000KD File Edit ...
Page 456: ......
Page 462: ......
Page 523: ...Section 11 Glossary 523 FIGURE 116 Relationships of Accuracy Precision and Resolution ...
Page 524: ......
Page 526: ......
Page 556: ......
Page 558: ......
Page 560: ......
Page 597: ......