rev1 ā Dec 2013 www.digitalcomtech.com 20
Actions
Once you have defined a trigger (and/or a set of triggers) the next step for configuring
the Syrus TM event machine, is to tell the unit what to do when a trigger goes off. There
are two types of actions the unit may take when a trigger goes off. These are the report
action and the user-defined action.
When the event machine detects that a trigger goes off it uses the configuration of the
report action to generate a report. A report action configuration includes routing options
and a type of report.
The routing options tell the unit where to report the occurrence of the specific event. The
report destinations may be IP addresses (or host names), cellular phone numbers or the
unit's serial port. It could also be a silent report which is not reported to any destination.
It is possible to send the same report to several destination at the same time by defining
a group of destinations using the DA command.
The type of report used by the unit is called "EV Event report". The information
contained in this type of report is described in the EV command. The EV report can
include extra information tags, called "Extended EV Tags". This tags are included in the
report by defining an event using the A, B or C Message IDs. The information that each
tag contains can be defined using the XAEF command.
A user-defined action is defined by a user-specified command (or set of commands)
that are appended at the end of a regular event definition using the "ACT=" or "XCT="
string. This enables the user to predefine commands that the unit will only process
whenever the trigger of a defined event goes off.
Events
Triggers and actions are bound together on a single configuration message called
event. An event is defined or consulted with the ED command. A single event holds a
trigger, a report action and optionally a user action. The following figure gives a global
description of the ED command.
The SyrusTM has 100 events available for the user to configure. They may be defined
all at once in a configuration script or they me be individually defined at any moment as
the user adds/removes functionality. Please refer to the ED command for more
information on each of the message's fields.
To Next Page
Loading...