Setting The Name Of The Event; Enable The Event; Triggering A Condition; Querying The Condition Counter - Lightware RAP-B511-EU User Manual

   
7. LW3 Programmers' Reference
Example 1 (simple delay)
ç SET /EVENTS/E1.ConditionTimeout=10
æ pw /EVENTS/E1.ConditionTimeout=10
If the Condition is detected (the ConditionDetect property becomes true), the ConditionTimeoutPending property
becomes true. 10 seconds later the ConditionTimeoutPending property becomes false and the set Action is
launched.
Example 2 ('still true after' delay type)
ç SET /EVENTS/E1.ConditionTimeout=10
æ pw /EVENTS/E1.ConditionTimeout=10
ç SET /EVENTS/E1.ConditionTimeoutPending=true
æ pw /EVENTS/E1.ConditionTimeoutPending=true
If the Condition is detected (the ConditionDetect property becomes true) the ConditionTimeoutPending property
becomes true. 10 seconds later the Condition is checked again (the ConditionTimeoutPending property
becomes false). If the Condition can be detected again (the ConditionDetect property becomes true again), the
Condition is fulfilled and the set Action is launched.
Example 3 ('continuously true' delay type)
ç SET /EVENTS/E1.ConditionTimeout=10
æ pw /EVENTS/E1.ConditionTimeout=10
ç SET /EVENTS/E1.ConditionTimeoutContinuous=true
æ pw /EVENTS/E1.ConditionTimeoutContinuous=true
If the Condition is detected (the ConditionDetect property becomes true), the ConditionTimeoutPending property
becomes true. If the Condition can be detected in the following 10 seconds continuously (the ConditionDetect
property stays true), the Condition is fulfilled, the ConditionTimeoutPending property becomes false, and the set
Action is launched.
7.12.2. Setting the Name of the Event
Command and Response
SET·/EVENTS/E<loc>.Name=<string>
ç
pw·/EVENTS/E<loc>.Name=<string>
æ
Parameters
The <string> may contain letters (A-Z) and (a-z), numbers (0-9), special characters: hyphen ( - ), underscore
( _ ), and space ( ) up to 20 characters. Longer string results an error, unaccepted characters are skipped.
Example
ç SET /EVENTS/E1.Name=Projector_ON
æ pw /EVENTS/E1.Name=Projector_ON
RAP-B511 series – User's Manual
7.12.3. Enable the Event
Command and Response
ç
æ
Parameters
When the property value is true (or 1), the Action will be launched if the Condition is detected. If the property
is false (or 0), the Action will not run, however, the Condition counter will be increased when detected.
Example
ç SET /EVENTS/E1.Enabled=true
æ pw /EVENTS/E1.Enabled=true
7.12.4. Triggering a Condition
DIFFERENCE:

This feature works like a condition is fulfilled. When a complex control system is built, a Condition may
trigger numerous Actions. A typical example is when a system is powered on and the 'ready-to-use' state
has to be loaded. In this case, there could be many actions which are based on the same condition. In order
to reduce the number of the commands, you can trigger one 'key' condition, which starts the whole process.
Command and Response
ç CALL·/EVENTS/E<loc>:triggerCondition(1)
æ mO·/EVENTS/E<loc>:triggerCondition
Example
ç CALL /EVENTS/E1:triggerCondition(1)
æ mo /EVENTS/E1:triggerCondition
The Condition of Event1 is fulfilled, the set Action will be launched (after the delay if set).
7.12.5. Querying the Condition Counter
This property shows how many times the Condition has been detected and triggered altogether. The counter
is reset at boot.
Command and Response
ç GET·/EVENTS/E<loc>.ConditionCount
æ
Example
ç GET /EVENTS/E1.ConditionCount
æ pw /EVENTS/E1>.ConditionCount=5
Applied firmware package: v1.1.0b3b3 | LDC software: v2.5.1b5
SET·/EVENTS/E<loc>.Enabled=<true/false>
pw·/EVENTS/E<loc>.Enabled=<true/false>
This command is available from FW package v1.1.0b3.
pw·/EVENTS/E<loc>.ConditionCount=<num_value>
82
#new