8. LW3 Programmers' Reference
8.21.5. 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>
are handled in the same way: dot (.) stands after the path in both cases, colon (:) is not used. The
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
8.21.6. 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.
8.21.7. Setting an Action by Linking a Macro
DIFFERENCE:
This command is available from FW package v1.3.0.
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
is: <node_path>.<property_or_method>=<value>. Properties and methods
command.
MMX8x4-HT series – User's Manual
<value>
Macros
section) or can
Applied firmware package: v1.3.0 | LDC software: v2.4.2
145