UM-0085-B09 DT80 Range User Manual Page 59
RG
The channels defined here will be sampled and reported in the following order:
12:00:00
S 2V -
12:00:01 S 2V * -
12:00:02
12:00:04
B 3V 3V
12:00:05
2V(AV) average of the 5 samples marked *
2V(SD) standard deviation of the 5 samples marked *
12:00:06
S 2V -
As can be seen in the above example, when multiple schedules are due at the same time, they execute in a fixed order
governed by their identifier (A, B, etc.) – regardless of the order in which they are specified in the job. Channels,
however, are sampled/reported in the order in which they appear within a schedule definition (e.g. 2V before 1V in the
above example).
Changing a Schedule Trigger
The schedule’s trigger can be changed at any time simply by sending a new schedule ID and trigger without any channel
definitions. For example, suppose a schedule had been defined as follows:
RA10M 1V 2DS
This will measure a voltage and a digital input every 10 minutes. If you then send:
RA10S
the schedule will then, from that point on, measure every 10 seconds.
Important : If any channel definitions are included on the same line (e.g. RA10S 2V) then this will be interpreted as a whole new job
being entered, which will replace the currently running job
.
Halting & Resuming Schedules
Schedules can be halted individually or as a group using the following commands:
Halt all schedules
Halt
…
schedule
Halt the statistical sub-schedule (see Statistical Sub-Schedule Halt/ Go (P57))
Schedules can then be resumed ("GOed") individually or as a group:
Command Function
Resume the statistical sub-schedule (see Statistical Sub-Schedule Halt/ Go (P57))
Executing Commands in Schedules
It is important to distinguish between commands and channel definitions. Commands (e.g. H, /S, P11=60, DIRJOB,
COPY etc.) are always executed once only, immediately they are received – even if they appear to be within a schedule
definition.
To Next Page
Loading...
