rev1 ā Dec 2013 www.digitalcomtech.com 21
Signals
As described in the previous section, the event machine takes actions like reporting or
switching outputs whenever a user defined trigger goes off. This trigger is configured by
the user with the logical combination of situations.
Situations make reference to a vehicle state which is in fact represented by signals and
their state. SyrusTM signals are of boolean nature, meaning that they can only take one
of two possible values: true or false.
Signals and the logical operators AND, OR, NOT are used to create logical equations to
form event triggers.
By using the SS command a signal's state can be consulted, and depending on the
signal's type, this command can be used also to change the signal's state. Signals'
names always have three characters. Please refer to the Signal List section, for a list of
valid signals and their meanings.
Examples
Some examples about the use of the event machine are presented next.
Configuring two events on the Event Machine to generate an ignition report:
The ignition ON event may be defined as:
>SED18NV4;F00+<
And the Ignition OFF event:
>SED19NV4;F00-<
Both events' routing actions indicate that the destination of the report is the DA 4 and
that EV is the reporting message to generate. Both events use a simple trigger
consisting of a one-signal-only condition, F00 which is the vehicle's ignition signal.
Configuring an event that uses two signals:
For this example we will use signal S00, which is associated with a speed limit and
signal J00, which is associated with a heading delta. The event will be triggered when
both signals are true, meaning that the vehicle exceeded the speed limit while making a
turn greater than the heading delta defined:
>SED05NV0;S00J00&+<
To Next Page
Loading...