Specifications

Section 9. Program Control Instructions
9-17
FieldName Description
MaxProcTime The maximum amount of time that it has taken
to execute the program.
Messages A field that can be used to hold a string value in
the datalogger's Status table. The string must be
enclosed in quotes.
SkippedScan An error counter indicating the number of times
a Scan has been missed because the datalogger
was busy with another task (such as the previous
scan).
SkippedSlowScan An error counter indicating the number of times
a SlowScan has been missed.
SkippedRecord An error counter indicating the number of times
a record was supposed to be stored but wasn't.
StationName The name of the datalogger station.
VarOutOfBound An indication that a variable is not dimensioned
large enough to hold the values being returned.
WatchdogErrors An error counter indicating the number of times
the datalogger has had to reset its processor. Set
to 0 to reset counter.
For all Status table settings except Messages and StationName, setting the
value to 0 resets the error indicator. This can be useful for troubleshooting
purposes.
Slow Sequence
The SlowSequence instruction is used to mark the beginning of a section of
code that will run concurrently with the main program.
Syntax
SlowSequence
Remarks
The SlowSequence statement marks the end of the main program and begins a
separate sequence of instructions. The instructions for the slow sequence
program are executed when the main program is not running as time allows. It
is possible to have up to four slow sequences executing at a rate different than
that of the primary scan interval. Slow sequences can be declared with a
Scan/NextScan structure, or they can be placed within a Do/Loop to execute
whenever the datalogger is not busy with other tasks.
Because measurements in the main scan have priority over all other tasks, the
measurement instructions in a slow sequence are performed during the times
when the datalogger is not running the main scan. This can result in the
measurements of a slow sequence being performed over a longer period of
time than if they were placed in the main scan.
Priority of a slow sequence in the datalogger will vary, depending upon
whether the datalogger is executing its program in pipeline mode or sequential
mode. With the important exception of measurements, when running in
pipeline mode all sequences in the program have the same priority. When
running in sequential mode, the main scan has the highest priority for