Campbell Scientific CR200X CR200/CR200X-series Dataloggers - Page 163

Troubleshooting

Page 163 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

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