Setting An Action By Specifying A Direct Path; Setting An Action By Linking Another Action; Setting An Action By Linking A Macro; Event Manager Tool Kit - Lightware UMX-TPS-TX120 User Manual

Hdbaset multimedia extender
Hide thumbs Also See for UMX-TPS-TX120:
Table of Contents

Advertisement

 
7. LW3 Programmers' Reference
7.9.4. Setting an Action by Specifying a Direct Path
Command and Response
SET·/EVENTS/E<loc>.Action=<expression>
ç
pw·/EVENTS/E<loc>.Action=<expression>
æ
Parameters
The structure of the
<expression>
is: <node_path>.<property_or_method>=<value>. Properties and methods
are handled in the same way: dot (.) stands after the path in both cases, colon (:) is not used. Do not use
brackets for methods. The
<value>
parameter is optional in case of certain methods.
Example
ç SET /EVENTS/E1.Action=/MEDIA/VIDEO/XP.switch=I4:O1
æ pw /EVENTS/E1.Action=/MEDIA/VIDEO/XP.switch=I4:O1
7.9.5. Setting an Action by Linking Another Action
Command and Response
SET·/EVENTS/E<loc>.Action=<event_nr>
ç
pw·/EVENTS/E<loc>.Action=<event_nr>
æ
Parameters
The
<event_nr>
means the number (location) of the linked event without letter 'E'.
Example
ç SET /EVENTS/E2.Action=1
æ pw /EVENTS/E2.Action=1
The Action of the E2 Event is set to be the same as set at E1 Event.
7.9.6. Setting an Action by Linking a Macro
DIFFERENCE:

This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW
package v1.5.0b4.
Command and Response
SET·/EVENTS/E<loc>.Action=<macro_name>
ç
pw·/EVENTS/E<loc>.Action=<macro_name>
æ
Parameters
The
<macro_name>
means the name of the macro that can be seen in LDC (see the
be queried by the GET
/CTRL/MACROS.<id>
Example
ç SET /EVENTS/E1.Action=Macro1
æ pw /EVENTS/E2.Action=Macro1
Macros
section) or can
command.
Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-UMX-TPS): v1.4.0b8 | (FP-UMX-TPS): v1.4.0b8 | LDC software: v2.5.6b2
UMX-TPS-TX100 series – User's Manual
7.10. Event Manager Tool Kit
7.10.1. Setting the Delay
In most cases, the Action is performed immediately after the Condition is detected. But sometimes a delay
is necessary between the Condition and the Action, thus, the following delay options are defined:
no delay
simple delay
still true after
continously
Command and Response (summary)
SET·/EVENTS/E<loc>.ConditionTimeout=<time>
ç
pw·/EVENTS/E<loc>.ConditionTimeout=<time>
æ
SET·/EVENTS/E<loc>.ConditionEndCheck=<true/false>
ç
pw·/EVENTS/E<loc>.ConditionEndCheck=<true/false>
æ
SET·/EVENTS/E<loc>.ConditionTimeoutContinuous=<true/false>
ç
pw·/EVENTS/E<loc>.ConditionTimeoutContinuous=<true/false>
æ
Parameters
The
<time>
parameter means seconds. Set the following properties for the desired delay type:
Delay type
no delay
/EVENTS/E<loc>.ConditionTimeout
simple delay
/EVENTS/E<loc>.ConditionTimeout
/EVENTS/E<loc>.ConditionTimeout
still true after
/EVENTS/E<loc>.ConditionEndCheck
/EVENTS/E<loc>.ConditionTimeout
continuously
true
/EVENTS/E<loc>.ConditionEndCheck
/EVENTS/E<loc>.ConditionTimeoutContinuous
Condition = true
Perform the action
Condition = true
Delay
Perform the action
Condition = true
Delay
Condition = true Perform the action
Condition = true
Perform the action
true
Delay
Properties to set
Value
0
The Action will be launched
after the Condition is detected.
<time>
If the Condition is detected, the
action will be launched after the
set time.
<time>
The Condition is fulfilled only
if is detected after the set time
true
again.
<time>
The Condition is fulfilled only if
it is existing continuously during
true
the set time.
true
117
Time
Result

Advertisement

Table of Contents
loading

This manual is also suitable for:

Umx-tps-tx130Umx-tps-tx140Umx-tps-tx140kUmx-tps-tx140-plusFp-umx-tps-tx120Fp-umx-tps-tx130 ... Show all

Table of Contents