Event Manager Basics; How To Arrange An Event; Setting A Condition By Specifying A Direct Path; Setting A Condition By Linking Another Condition - Lightware RAP-B511-EU User Manual

   
7. LW3 Programmers' Reference
7.11. Event Manager Basics
The graphical interface of the Event Manager can be found in the LDC which allows creating any kind of
Events. In certain cases, the Events have to be arranged or modified by LW3 commands from another device.
These commands are detailed in the coming sections.
7.11.1. How to Arrange an Event?
The following are necessary to have a successful event:
▪ Defining the Condition
▪ Defining the Action
▪ Setting the Delay (optional)
▪ Name the Event and set to Enabled
INFO:
Setting the Event to Enabled as the last step is recommended.
7.11.2. Setting a Condition by Specifying a Direct Path
Command and Response
SET·/EVENTS/E<loc>.Condition=<expression>
ç
pw·/EVENTS/E<loc>.Condition=<expression>
æ
Parameters
The structure of the <expression>
Example 1
ç SET /EVENTS/E1.Condition=/MEDIA/UART/RECOGNIZER.Rx=ON
æ pw /EVENTS/E1.Condition=/MEDIA/UART/RECOGNIZER.Rx=ON
The Condition is fulfilled if the SignalPresent property changes to '1'.
Example 2
In some cases, the opposite is necessary: when the property does not equal with the value. If you need so,
the ConditionInverted property must be set to true:
ç SET /EVENTS/E2.Condition=/MEDIA/UART/RECOGNIZER.Rx=ON
æ pw /EVENTS/E2.Condition=/MEDIA/UART/RECOGNIZER.Rx=ON
ç SET /EVENTS/E2.ConditionInverted=true
æ pw /EVENTS/E2.ConditionInverted=true
The Condition is fulfilled if the ConnectedSource property does not equal with 'I1' (in other words: if other input
port is connected to O1 than I1).
Example 3
Sometimes, it is enough if the value of a property changes to anything. In this case, just put a ? to the end
of the property:
ç SET /EVENTS/E3.Condition=/MEDIA/UART/RECOGNIZER.Rx?
æ pw /EVENTS/E2.Condition=/MEDIA/UART/RECOGNIZER.Rx?
is: <node_path>.<property>=<value>.
Applied firmware package: v1.1.0b3b3 | LDC software: v2.5.1b5
RAP-B511 series – User's Manual
7.11.3. Setting a Condition by Linking Another Condition
Command and Response
SET·/EVENTS/E<loc>.Condition=<event_nr>
ç
pw·/EVENTS/E<loc>.Condition=<event_nr>
æ
Parameters
The <event_nr> means the number (location) of the linked event without letter 'E'.
Example
ç SET /EVENTS/E2.Condition=1
æ pw /EVENTS/E2.Condition=1
The Condition of the E2 Event is set to be the same as set at E1 Event.
7.11.4. Setting a Condition by Linking More Conditions

DIFFERENCE: This command is available from FW package v1.1.0b3.
The first generation of the Event Manager is able to sense a change (one condition) but in some cases that
is not enough. The practical experience has shown there is a need to examine more conditions (up to four)
as follows: if one of the set conditions becomes true (while the other conditions are fulfilled), then the set
Action is launched.
Command and Response
SET·/EVENTS/E<loc>.Condition=<event_nr>&<event_nr>&<event_nr>&<event_nr>
ç
pw·/EVENTS/E<loc>.Condition=<event_nr>&<event_nr>&<event_nr>&<event_nr>
æ
Parameters
The <event_nr> parameters mean the numbers (locations) of the linked Events without letter 'E'. Up to four
event number can be set
Example
ç SET /EVENTS/E4.Condition=1&2&3
æ pw /EVENTS/E4.Condition=1&2&3
If two Conditions exist and the third is detected (changes to true), the Condition of E4 will be fulfilled and the
Action of E4 will be launched.

TIPS AND TRICKS: You do not have to define Actions for E1, E2 and E3 Events and you can leave those
Disabled.
80