events

Receive CyFlex events.

Enter:

events [t] [n]

Where:

t	Optional. Specify the maximum time, in milliseconds, to receive events.
n	Optional. Specify the maximum number of events to be receive.

Example:

events
The above command asks you to enter the names of the events that should be received. Once all the event names have been entered the program waits for the events. When one of the specified events is received, its name and the time it was received is displayed on the monitor. Enter ‘ctrl-c’ to terminate the program.

events t=3000
The above command monitors the specified events for 3 seconds. When the command is entered, respond to the prompt to enter the names of the events to monitor.  The timer begins after all desired events have been entered. When the time has expired, a report is displayed that lists all the events that were received in the order they were received.

events n=30
The above command monitors the specified events until a total of 30 events are received. When the command is entered, respond to the prompt  to enter the names of the events to monitor. After all desired events have been entered the program waits to receive events. When the specified number of events are received, a report is displayed that lists all the events that were received in the order that they were received.

If both of the optional arguments are entered, the ‘n=number’ option will have precedence and the ‘t=time’ argument will be ignored.

Notes:

When entering the events to monitor, it is now possible to get the contents of the event displayed. There are number a of selected events for which this capability exists. These events are

1. GLOBAL CONFIG EVENT
2. TRANSITION EVENT
3. ALARM EVENT
4. PROCESS DONE EVENT
5. ASC TTY EVENT
6. ASC CMD EVENT
7. ASC RSP EVENT
8. ASC XMT EVENT

If the event names of ‘config’, ‘done’, ???_tty, ???_rsp, ???_cmd or or ???_xmt are entered, the contents of the events are automatically printed. Since the other events do not have fixed names, there is a second entry that is required to identify the event. The second entry for each of the events are:

TRANSITION EVENT – transition ALARM EVENT – alarm

For example if the asc events ‘AEI’ and the fuel reading in progress events are to be monitored the following entries are required

FR_IP transition AEI_tty AEI_rsp AEI_cmd AEI_xmt

See Also: