Lightware UMX-HDMI-140, User Manual

Page: 31 / 161

4. Device Concept UMX-HDMI-140 series– User's Manual 31
Applied firmware package: v1.3.0b5 | LDC software: v2.5.6b2
The Concept
An IR detector is attached to the Infrared input port of the switcher and IR signals are sent by the Remote
controller. The switcher has two A/V sources (a Blu-ray player and a MacBook) and an A/V sink device (an
HDTV).
UMX-HDMI-140 switcher's input can be routed by the remote controller the following way:
Step 1.
Make the
Switcher
learn the IR codes of the desired remote control buttons, see the Learning IR Code
(hash) section.
Step 2.
Arrange the events in
Event Manager
; if the set IR code is received from the IR input (condition), then
switch the input source between the
Blu-ray player
and the
MacBook
(action) in the
Switcher
. In this case
you can control the
HDTV
via the
Switcher
remotely. See the details about the Event Manager settings
in the Event Manager section.
Advanced IR functionality
DIFFERENCE: This feature is available only in UMX-HDMI-140-Plus model from FW package v1.2.0b12.
UMX-HDMI-140-Plus can send Little-endian pronto hex IR codes on its IR output port.
It is possible in the following ways:
▪ With Lightware Device Controller software (for more details see the Sending Pronto Hex Codes in
Little-endian Format via IR Port section)
▪ With Event Manager (for more details see the Sending Pronto Hex Codes in Little-endian Format via
IR Port and Event Manager sections)
▪ With LW3 protocol command (for more information see Sending Pronto Hex Codes in Little-endian
Format via IR Port )
Sending Bigger-endian pronto hex code is also available, see Sending Pronto Hex Codes in Big-endian
Format via IR Port .
4.12. The Event Manager Feature
The Event Manager feature means that the device can sense changes on its ports and is able to react
according to the pre-defined settings. Lightware Device Controller contains a user-friendly software tool and
allows to create Events by defining a Condition and an Action.
Event Manager example
See more information about the settings in the Event Manager section.
Event M
The AND Operator
DIFFERENCE: This feature is available from FW package v1.3.0b5 ..
The practical experience has shown that 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. For example, in a meeting room we have the following situation:
▪ Signal is present on an input port,
▪ A GPIO pin state becomes ’low’ (by an external device).
If the two
Conditions
are present at the same time, the
Action
is launched. Just create the two
Conditions
into
separate Events, then create a third Event, select the two
Conditions
and define the
Action
.
See the Combine Links section for the settings in LDC.
Event Manager Variables
DIFFERENCE: This feature is available only for UMX-HDMI-140-Plus from FW package v1.3.0b5.
A brand new area is opened by implementing the variables. You can create custom variables in number
or text format which can be used in the Event Manager. The variables can have the following properties/
methods:
▪ Numeric (integer) type with min/max value setting, or string-type (determined automatically)
▪ Increment/step the numeric value,
▪ Value-dependent case operations,
▪ Reading and storing the value of an LW3 property into a string or a numeric variable.
The defined variables are stored in a non-volatile memory and the value is kept in case of a reboot. The
new opportunities allow creating a monitoring/controlling system without connecting an additional control
processor.
See the
Variables section for the settings in LDC. #new
Condition Trigger
DIFFERENCE: This feature is available only for UMX-HDMI-140-Plus from FW package v1.3.0b5 ..
This improvement in the Event Manager works as if a condition is detected. 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
could start the whole process.
See the
Condition Triggering section for the settings in LDC.
  
