Section 10. Troubleshooting
Warning Message Examples
Message Meaning
Warning: COM310 word list
cannot be a variable.
The Phrases parameter of the VoicePhrases() instruction was assigned a
variable name instead of the required string of comma-separated words
from the Voice.TXT file.
Warning: EndIf never reached at
runtime.
Program will never execute the EndIf instruction. In this case, the cause is
a Scan() with a Count parameter of 0, which creates an infinite loop within
the program logic.
Warning: Internal Data Storage
Memory was re-initialized.
Sending a new program has caused final-memory to be re-allocated.
Previous data are no longer accessible.
Warning: Machine self-
calibration failed.
Indicates a problem with the analog measurement hardware during the auto
self-calibration. An invalid external sensor signal applying a voltage
beyond the internal ±8 Vdc supplies on a voltage input can induce this
error. Removing the offending signal and powering up the logger will
initiate a new auto self-calibration. If the error does not occur on power-up,
the problem is corrected. If no invalid external signals are present and / or
auto self-calibration fails again on power-up, the CR800 should be repaired
by a qualified technician.
Warning: Slow Seq 1, Scan 1,
will skip scans if running with
Scan 1
SlowSequence scan rate is <= main scan rate. This will cause skipped
scans on the SlowSequence.
Warning: Table [tablename] is
declared but never called.
No data will be stored in [tablename] because there is no CallTable()
instruction in the program that references that table.
Warning: Units:
a_units_name_that_is_more_than
_38_chara... too long will be
truncated to 38 chars.
The label assigned with the Units argument is too long and will be
truncated to the maximum allowed length.
Warning: Voice word TEH is not
in Voice.TXT file
The misspelled word TEH in the VoiceSpeak() instruction is not found in
Voice.TXT file and will not be spoken by the voice modem.
Voltage calibration failure!
Loose wire probably of a bridge sensor such as a wind vane or pressure
transducer
10.5.4.2 SkippedScan
Skipped scans are caused by long programs with short scan intervals, multiple
Scan() / NextScan instructions outside a SubScan() or SlowSequence, frame
errors, or by other operations that occupy the processor at scan start time.
Occasional skipped scans may be acceptable but should be avoided. Skipped
scans may compromise frequency measurements made on terminals configured
for pulse input. The error occurs because counts from a scan and subsequent
To Next Page
Loading...
