Specifications

APPENDIX C: EVENT PROGRAMMING
Page 184 MRC-565 Packet Data Radio Operations & Maintenance
Action Definition
An "action" can be assigned to each event defined in the event table. When the event condition
is detected, the action is initiated. Available actions are defined in the following sections.
Multiple actions are supported by defining multiple events that test the same input, but take
different action, or multiple actions can be defined using a special "continue" event. The
“continue” event does not test the input condition again, but will trigger the action when the
event it is connected to detects the event.
Any action can be forced on a timed basis by several methods. One method is to use the MRC-
565 scheduler (SCHED command) to trigger the desired immediate action. For example, the
UPDT action can be specified by the insertion of the EVENT,UPDT, group-number command
into the MRC-565 scheduler to produce reports on a timed basis. See the SCHED command for
this capability. Another example would be to pulse an output line by placing two commands in
the scheduled event list that would first SET then CLR the signal. The duration of the pulse
would be controlled by the offset value in the SCHED command. Yet another method is to use
an event timer (counter) to facilitate scheduling of actions. Special timer registers are provided
for this purpose, and will automatically count down from a non-zero value to zero at a rate of
1/16 seconds per count. An event command can monitor the timer register, and when it reaches
zero, the action can be taken, and the timer reset to the next desired time count.
Programming in Real-Time
Events are programmed via operator commands, one event per command line. It is a multi-step
process. Because of this, each event being entered will be a fragment until all event definitions
are complete. If the event monitor is allowed to execute a fragment of an event, strange and
possibly adverse actions will occur. Therefore, the operator should stop the event monitor when
adding events and actions to the event table. The event monitor task can be stopped and started
by operator command. The best way to do this is to use a script file containing the stop
command, a command to delete all prior definitions, the desired event definitions, and a start
command.
Some examples are given below, following these, a detailed description of each event command
and action is given.