Thank You for choosing Lightware’s MMX6x2-HT200 device. In the first chapter we would like to introduce the device, highlighting the most important features in the sections listed below:
1.1. Description
Thank you for choosing Lightware MMX6x2-HT, our HDCP- and HDBaseTTM -compatible HDMI/TPS multiport standalone matrix switcher.
The MMX6x2-HT family responds to a need of a practical standalone matrix switcher specifically designed for meeting room and classroom environments. The flagship of the series is the MMX6x2-HT220 matrix with 6 video inputs and 2 video outputs (4x HDMI 1.4 and 2x TPS inputs, and 2x independent video outputs: 2x HDMI ports, which are both mirrored to TPS ports). The unit handles 4K video formats and 3D signals, while it’s fully HDCP compliant. The device has 4 audio input connectors for audio insertion and 2 audio outputs for de-embedding purposes. These features make this standalone matrix unique on the market. Thanks to its integrated PoE power injectors, the MMX6x2-HT is able to remote power TPS (HDBaseT) extenders on all its TPS input and output ports. The matrix receives and transmits digital video, audio, and control up to 170 m distance over a single CATx cable. Using the factory, custom or transparent EDID emulation, the user can fix and lock EDID data on each input connector. Advanced EDID Management forces the required resolution from any video source and fixes the output format conforming to the system requirements. The unit offers IR and RS-232 command injection capabilities, allowing to send any IR or RS-232 control command directly from the LAN connection.
Model Denomination
About the Serial Number
Lightware devices contain a label indicating the unique serial number of the product. The structure is the following:
1.2. Compatible Devices
The matrix switchers are compatible with other Lightware TPS devices, matrix boards, third-party HDBaseT- extenders, displays, but not compatible with the phased out TPS-90 extenders.
WARNING!The remote power feature of TPS-95 extenders is not PoE-compatible. Thus, TPS-95 series cannot be powered remotely by the MMX6x2 matrix switchers (but the video signal is transmitted to/from the extenders). If an RX95 or TX95 is connected to the matrix, make sure that the remote power jumper of the extender is removed or set to 'Remote power disabled' position.
1.3. Model Comparison
|
Model |
HDMI input |
TPS input |
Analog audio input |
HDMI output |
TPS output |
Analog audio output |
|
MMX6x2-HT200 |
4x |
2x |
4x |
2x |
- |
2x |
|
MMX6x2-HT210 |
4x |
2x |
4x |
2x |
1x |
2x |
|
MMX6x2-HT220 |
4x |
2x |
4x |
2x |
2x |
2x |
1.4. Box Contents
|
Supplied Accessories |
|||||
|
|
.png)
|
|
|
|
|
MMX6x2 Matrix Router |
Safety and Warranty Info, QSG |
IEC Power Cable |
Phoenix® Combicon 3-pole Connector |
Phoenix® Combicon 5-pole Connector |
|
|
MMX6x2-HT200 |
|
|
|
3x |
2x |
|
MMX6x2-HT210 |
|
|
|
3x |
4x |
|
MMX6x2-HT220 |
|
|
|
2x |
6x |
INFO:The matrix is supplied with 2 pcs of rack ears, which are mounted on the device.
1.5. Features of the Device
|
3D and 4K Support |
|
High bandwidth allows extension of resolutions of up to 4K, and even 3D sources and displays are supported. |
|
|
Signal Transmission up to 170 m |
|
Video and audio signal transmission (DVI, HDMI, Ethernet, RS-232 and Infra-Red over a single CAT5e…CAT7e cable. |
|
|
HDCP Compliant |
|
MMX6x2-HT family fulfills the HDCP standard. HDCP capability on the digital video inputs can be disabled when non-protected content is extended. |
|
|
Built-in Event Manager |
|
The Event Manager tool takes care of all the necessary control in a smaller configuration by performing predefined actions in response to device status changes. Hence, in a less complex environment there is no need to invest in additional control solutions, which makes the MMX6x2-HT series device series the best choice for numerous applications. |
|
|
Advanced EDID Management |
|
The user can emulate any EDID on the inputs independently, read out and store any attached monitor's EDID in 100 internal memory locations, upload and download EDID files using Lightware Device Controller software. |
|
|
Pixel Accurate Reclocking |
|
Each output has a clean, jitter free signal, eliminating signal instability and distortion caused by long cables or connector reflections. |
|
|
Frame Detector and Signal Analysis |
|
The exact video and audio signal format can be determined such as timing, frequencies, scan mode, HDCP encryption, color range, color space and audio sample rate. |
1.6. Typical Application
The chapter is about the installation of the device and connecting to other appliances, presenting also the mounting options and further assembly steps:
2.1. Mounting Options
The matrix can be mounted in several ways by the supplied two rack ears. Allen head screws fix them to the housing:
WARNING!Never block the ventilation holes on any side of the matrix! Ensure the proper ventilation by letting the air flow freely.
ATTENTION!M4x8 size is the longest allowed screw for fixing the ears to the housing. Longer screws may touch internal parts.
More details about the accessories and the mounting can be found in the Mounting Assembly Guide.
2.1.1. Standard Rack Installation (Default)
Two rack ears are supplied with the product, which are fixed on left and right side as shown in the picture. The default position allows mounting the device as a standard rack unit installation.
ATTENTION!Always use all the four screws for fixing the rack shelf ears to the rack rail. Choose properly sized screws for mounting. Keep a minimum of two threads left after the nut screw.
Mounting the device to the rack rail
2.1.2. Mounting with Front and Rear Rack Ears
ATTENTION!Two rack ears are assembled on the matrix as default, thus you will need two more rack ears for this kind of installation, which can be purchased separately.
The matrix can easily be mounted under the desk by rack ears. This mounting option means the top of the matrix is parallel with the base surface.
Please do the following steps:
Step 1.Release and remove the fixing screws of the rack ears on the matrix (both sides).
Step 2.Rotate the rack ears by 90° to the desired direction.
Step 3.Insert the screws into the holes and fix the front ears to the matrix.
Step 4.Fix the two additional rear ears (not supplied with the product) by the screws on both sides of the matrix.
Step 5.Fix the matrix through the holes of the rack ears to the desired surface (screws are not supplied).
INFO:The method is the same when the matrix has to be mounted to a wall.
2.1.3. Mounting with Mounting Bracket V2
ATTENTION!Two pieces of Mounting bracket V2 will be necessary for this kind of installation, which can be purchased separately.
The matrix can be easily mounted under the desk with Mounting bracket V2. This mounting option means that the front panel of the matrix is parallel with the surface. Please do the following steps:
Step 1.Prepare the desk and cut the necessary hole in the furniture. The frame size is 44.2 × 43.9 mm without rack ears.
Step 2.Release and remove the fixing screws of the rack ears on the matrix (both sides) and remove the ears, too.
Step 3.Insert the screws into the holes and fix the mounting bracket to the matrix. Pay attention to the thickness of the desk and leave enough space in the front when fixing the brackets.
Step 4.Insert the matrix in the hole and fix the brackets by the screws to the furniture.
2.2. Connecting Steps
|
Connect the desired sources (e.g. laptop) to the HDMI input ports. |
|
|
Optionally connect an audio source (e.g. media player) to the Audio input port, which is located above the connected HDMI input port. |
|
Optionally connect the PoE-compatible transmitter to the TPS input ports. |
|
|
Connect the sink devices (e.g. projector) to the HDMI output ports. |
|
|
Optionally connect an audio device (e.g. audio amplifier) to the Phoenix Audio output port, which is located above the connected HDMI output port. |
|
Optionally connect the PoE-compatible receiver to the TPS output ports. |
|
In order to control the matrix via Ethernet, connect the device to a LAN switch/router, and connect a controller (e.g. a Touch panel). |
|
Optionally connect the serial device (e.g. projector) to the RS-232 port. |
|
Connect the power cord to the AC power socket and to the matrix. |
INFO:It is recommended to power on the devices as the final step.
The following sections are about the physical structure of the device, input/output ports and connectors:
|
|
Control Lock |
Disables or enables front panel operation. When it shines red, switching operations on the front panel are prohibited and function buttons are disabled. |
|
|
Output Lock |
Locks and protects one (or more) outputs. It inhibits accidental input changing on protected outputs. |
|
|
Sources |
Source buttons have three functions: to select an input, to select a preset number, and to view the status of the selected input (Take mode). |
|
|
Destinations |
Destination buttons have two functions: to select an output, or to view the selected output’s state. |
|
|
Function Buttons |
Switching between working modes (Take / Autotake), Preset operations are available with the function buttons. See the Take/Autotake Mode section for more information. |
|
|
USB Control |
USB mini B-type connection for local control functions (e.g. with Lightware Device Controller software). |
|
|
Display |
2x16-character LCD display with backlight for menu operations and settings. |
|
|
Navigation Buttons |
(UP, DOWN, LEFT, RIGHT, ENTER, ESCAPE) buttons for menu navigation. |
|
|
Status LEDs |
Blinking CPU LIVE LED indicates normal operation; DC voltage indicator LEDs are for internal DC power voltages. |
|
|
Reset |
Reset button reboots the matrix. This is the same as disconnecting it from the power source and reconnecting it again. |
INFO:All three models have the same look and controls on the front panel.
3.2.1. MMX6x2-HT200
3.2.2. MMX6x2-HT210
3.2.3. MMX6x2-HT220
|
|
AC Connector |
Standard IEC power connector. Accepts 100 to 240 Volts, 50 or 60 Hz power sources. |
|
|
On/Off |
The matrix can be switched on/off by the power switch. |
|
|
RS-232 Port |
3-pole Phoenix connector for RS-232 serial port. Pin assignment can be found in the RS-232 Port section. |
|
|
LAN |
Locking RJ45 connector to control the matrix via LAN/Ethernet – it can be separated from TPS Ethernet communication. Not PoE-compliant. Pin assignment can be found in the RJ45 Ports section. |
|
|
TPS Ethernet |
Locking RJ45 connector to supply Ethernet communication for the TPS lines – it can be separated from the LAN communication (controlling functions) of the matrix. Not PoE-compliant. Pin assignment can be found in the RJ45 Ports section. |
|
|
TPS Inputs |
Locking RJ45 connector for incoming TPS signal. PoE-compliant. Pin assignment can be found in the RJ45 Ports section. |
|
|
Audio Inputs |
5-pole Phoenix connector for balanced analog audio input. Pin assignment can be found in the Analog Audio Inputs and Outputs section. |
|
|
HDMI Inputs |
Connect an HDMI cable between the source and the matrix. The applied cable shall be no longer than 20 m (22AWG) when the resolution of the signal is 4K. Pin assignment can be found in the HDMI Input and Output Ports section. |
|
|
TPS Outputs |
Locking RJ45 connector for outgoing TPS signal. PoE-compliant. The Audio/Video content on the two given HDMI and TPS output ports are mirrored. Two outputs are available on HT220, one output is available on H210. No TPS output is on HT200. Pin assignment can be found in the RJ45 Ports section. |
|
|
Audio Outputs |
5-pole Phoenix connector for balanced analog audio output; the signal is mirrored from the TPS/HDMI output port. Pin assignment can be found in the Analog Audio Inputs and Outputs section. |
|
|
HDMI Outputs |
Connect an HDMI cable between the sink and the matrix. HDMI and TPS output ports are mirrored: the same Audio/Video content is switched on the given two ports. |
3.3.1. HDMI Input and Output Ports
The matrix switchers are assembled with standard 19-pole HDMI connectors for inputs and outputs.
3.3.2. Analog Audio Inputs and Outputs
5-pole Phoenix connector is used for balanced analog audio (line in/out). Some I/O boards use this connector as a configurable input or output. Unbalanced audio signals can be connected as well. For asymmetrical output, connect only + and ground. For asymmetrical input, connect + and ground to the source, and connect – to the ground.
Compatible Plug Type
Phoenix® Combicon series (3.5mm pitch), type: MC 1.5/5-ST-3.5.
See more information about the most common audio cable wiring modes in the Audio Cable Wiring Guide section.
The 3-pole Phoenix connector is used for the local RS-232 serial connection.
Compatible Plug Type
Phoenix® Combicon series (3.5mm pitch, 3-pole), type: MC 1.5/3-ST-3.5.
See more information about the most common serial data cable wiring modes in the Cable Wiring Guide for Serial Data Transmission section.
The matrix provides standard RJ45 connectors for Ethernet and TPS input and output ports.
Wiring of TPS and LAN Cables
Lightware recommends the termination of LAN cables on the basis of TIA/EIA T 568 A or TIA/EIA T 568 B standards.
When a standard Ethernet device is connected to the TPS connector for some reason, the port is switched to Ethernet fallback mode automatically.
|
LED1 green |
|
off |
0 Mbit/s |
|
on |
100 Mbit/s |
||
|
LED2 amber |
|
off |
not linked |
|
|
on |
no activity |
||
|
blinking |
activity |
TPS Ethernet Port
The matrix contains two RJ-45 connectors for Ethernet/LAN connection: one for local control functions and one for the TPS lines. The two interfaces are connected (default) but can be separated. The connector with LAN display is for local controlling functions – the matrix can be configured and controlled via local Ethernet through this port. The connector with TPS Ethernet display is to supply Ethernet to the TPS ports.
The Ethernet ports can be connected to a LAN hub, switch or router by a CATx cable. Even though both cable types (straight or cross) are supported and handled by the device, the pin assignment of the TIA/EA T568 A cables is recommended.
|
TPS LEDs |
REAR |
||||
|
PoE LED |
|||||
|
|
off |
Remote power (PoE) is inactive, device is powered locally. |
||
|
amber |
on |
Remote power is active. |
||
|
TPS link LED |
|||||
|
|
off |
No TPS link between the devices. |
||
|
green |
blinking (1x) |
Only RS-232 (@ 9600 baud) and Ethernet communication is transmitted. |
||
|
green |
blinking (2x) |
Only RS-232 communication is transmitted (@ 9600 baud). |
||
|
|
green |
blinking (5x) |
Device is in Ethernet fallback mode. |
||
|
green |
on |
TPS signal is present. |
||
3.4. TPS Matrix Concept
MMX6x2-HT is the first stand-alone matrix switcher with HDBaseTTM (TPS) technology in Lightware’s product range. The matrix offers the possibility of routing many kinds of signal formats, including TPS and other available interfaces. In this chapter, we present the features and limitations of these interfaces.
Summary of the Interfaces
The TPS working mode between the transmitter and the receiver parties is determined by the mode set in them. Both parties influence on the setting that determines the final TPS transmission mode.
The following TPS modes are defined in the matrix:
▪Auto: The TPS mode is determined automatically.
▪HDBaseT: Ideal for high resolution signals up to 4K but with a shorter cable.
▪Long reach: Ideal for big distances up to 1080p@60Hz.
▪LPPF1*: Only RS-232 communication is transmitted (@ 9600 baud)
▪LPPF2*: Only RS-232 (@ 9600 baud) and Ethernet communication are transmitted.
* LPPF: Low Power Partial Functionality
The settings above refer to the matrix. The table below details the system's state with regard to mode selection behavior for all possible combinations for both ends of the link:
|
Selected mode on RX side |
||||||
|
LPPF1 |
LPPF2 |
HDBaseT |
Long reach |
Auto |
||
|
Selected mode on TX side |
LPPF1 |
LPPF1 |
LPPF1 |
LPPF1 |
LPPF1 |
LPPF1 |
|
LPPF2 |
LPPF1 |
LPPF2 |
LPPF2 |
LPPF2 |
LPPF2 |
|
|
HDBaseT |
LPPF1 |
LPPF2 |
HDBaseT |
Long reach |
HDBaseT |
|
|
Long reach |
LPPF1 |
LPPF2 |
Long reach |
Long reach |
Long reach |
|
|
Auto |
LPPF1 |
LPPF2 |
HDBaseT |
Long reach |
HDBaseT ** |
|
** If there is valid HDMI/DVI signal on the TX side, the TPS mode will be HDBaseT on both side. If the transmitter does not transmit HDMI/DVI signal, the TPS mode will be changed to LPPF2 automatically. Long reach mode is not available when both sides are set to Auto mode.
When using automatic operation mode selection, the device uses built-in sensors to determine the mode of operation. If both parties are set to Auto mode, the source side is the initiator. It will negotiate each state transition with its sink-side partner.
When one of the devices is configured to manual operation mode selection, the other device may be placed in automatic mode. In this case, the mode transition negotiation is initiated by the host-managed device and the auto-mode device follows through. The allowed cable lengths and resolutions are listed in the Maximum Twisted Pair Distances section.
TPS input and output ports are able to supply other HDBase-T compliant devices over the TPS lines, which are PoE-compliant as well. In this case, the connected transmitter or receiver does not require a local power supply.
ATTENTION!The Ethernet ports do not support PoE. Only the TPS ports support PoE function.
WARNING!The remote power feature of TPS 95 series extenders is not PoE-compatible. Thus, TPS 95 series cannot be powered remotely by the MMX6x2 matrix switchers (but the video signal is transmitted to/from the extenders). If a TPS 95 extender is connected to the matrix, make sure that the remote power jumper of the extender is removed or set to 'Remote power disabled' position.
The PoE feature in the practice
The TPS ports of the matrix are in accordance with IEEE 802.3af (PoE) standard. The feature is demonstrated on the figure below:
Extenders Supplied without Local Power
The concept
Supply the connected extenders through the CATx (TPS) cables without local adapters.
Settings
▪Extenders: the device must be PoE-compatible, or else the feature will not work.
▪Matrix: make sure the PoE option on the TPS port is enabled (which is the default setting) via LDC in the port properties window; see the Preset Settings section.
INFO:PoE-compatible and not PoE-compatible devices can be connected simultaneously, as the feature can be set individually on each port.
The matrix can receive audio from two type of sources:
▪Embedded (4x HDMI and 2x HDBaseT in) and
▪Analog balanced stereo audio sources (4x).
The audio coming from the analog inputs can be assigned to any video input or output. The volume/gain levels of the analog audio input/output ports are adjustable.
Input audio modes
ATTENTION!Input audio modes are valid if the output audio mode is set to Pass-through mode.
▪Embedded: The original audio of the HDMI signal is embedded in the video stream.
▪AUX1...AUX4: Auxiliary audio is embedded in the video stream.
Output audio modes
ATTENTION!The output audio modes can override the input audio mode when it is Aux1...Aux4.
▪Pass-through: This mode allows the input to set the audio source.
▪AUX1...AUX4: In this mode Aux1...Aux4 is locked to the output. The input cannot modify this audio source. This source will be selected always.
▪Copy from other output: the same audio is used that is present on the other output.
Audio options – example
Audio selection
The concept
The same audio is present on the TPS and Audio outputs. The desired source can be switched to the outputs: the MP3 player or the Blu-ray player. In both cases, the video signal is coming from the Blu-ray player.
Settings (matrix)
If the HDMI audio (Blu-ray) is switched to the outputs:
▪HDMI input properties: Signal source set to Embedded.
▪HDMI output properties: Signal source set to Pass-through.
If the Mp3 player is switched to the outputs:
▪HDMI input properties: Signal source set to AUXn.
▪HDMI output properties: Signal source set to Pass-through or AUXn.
See the settings in the Audio Options section.
INFO:The input audio modes are valid if the output audio mode is set to Pass-through mode.
3.7. Video Interface
The video crosspoint settings can be controlled in any of the following ways:
▪Pressing the Source and Destination buttons on the front panel,
▪Using Lightware Device Controller,
▪Sending LW2 or LW3 protocol command, or
▪Using the Autoselect function.
3.7.1. Mirrored Outputs
The matrix has 4 HDMI and 2 HDBaseT input ports. One or two input ports can be routed to the output ports at the same time. Optionally, each TPS output port can have a mirrored HDMI output port, which means the same video stream is transmitted over the HDMI output port and the TPS output port. Three variants are available, the difference between the versions is the number of the mirrored output ports:
▪MMX6x2-HT200: 2x HDMI out
▪MMX6x2-HT210: 2x HDMI out, 1x TPS out (HDMI out1 mirrored)
▪MMX6x2-HT220: 2x HDMI out, 2x TPS out (HDMI out1 and out2 mirrored)
MMX6x2-HT port diagram
* Not available on MMX6x2-HT200.
** Available on output 1 on MMX6x2-HT210 and on output 1 & 2 on MMX6x2-HT220.
There are three types of Autoselect as follows:
First detect mode: Selected input port is kept connected to the output while it has an active signal.
Priority detect mode: It is always the highest priority active input that is selected to be transmitted.
Last detect mode: It is always the last attached input that is selected to be transmitted.
INFO:The input ports where the priority is set to 31 will not be scanned. See more details about this setting in the Querying the Input Port Priority section.
INFO:An input port is active if there is a valid signal on it.
Input selection automatically – example
The concept
If a video signal of the Blu-ray player is present on the HDMI input of the matrix, the source will be automatically switched to the TPS output. If the video signal of the PC is also present on the other HDMI input of the matrix, it will be switched to the TPS output. If the Laptop is connected, the TPS input will be switched to the TPS output – independently of the presence of the other video signals.
Settings
TPS output: Set the Autoselect to Enabled. The Autoselect mode is Priority detect. The priorities are the followings:
|
Port |
Priority |
|
|
Laptop |
(I1, TPS IN) |
0 |
|
PC |
(I3, HDMI IN) |
1 |
|
Blu-ray |
(I4, HDMI IN) |
2 |
The other inputs can be disabled. See the settings in the Autoselect Settings section.
3.8. Control Features (Matrix Control and Third-Party Devices)
The interfaces of the MMX6x2-HT can be used to install the matrix at any place of a complex AV system. In addition, the matrix is capable of control functions as well. In this chapter, we present the possibilities through three simple layout examples.
System control via local Ethernet (example)
The following ways are available for controlling the devices:
▪The System controller can communicate with LW2/LW3 protocol commands via the local IP:port address of the Matrix, see the settings in the Factory Default Settings section).
▪The System controller can communicate directly with the Projector or an Extender via their IP:port address.
▪The System controller can communicate directly with the RS-232 relay box connected to the Matrix. In this case, Command Injection mode has to be enabled on the local RS-232 port.
▪The matrix can send a command (e.g. as an action by the Event Manager) to the IP:port address of the Projector or an Extender using LW3 protocol methods; for details, see the Infrared Port Configuration section.
System control via local RS-232 (example)
The following ways are available for controlling the devices:
▪The System controller can communicate with LW2/LW3 protocol commands via the local RS-232 port of the Matrix (see the default RS-232 port settings in the Factory Default Settings section).
▪The System controller can send TCP or UDP messages to the IP:port address of the Matrix or the Extender, using LW3 protocol methods, see the Infrared Port Configuration section.
▪The Matrix can send TCP or UDP message commands to the HDTV or the Extender by using LW3 protocol methods, see the Infrared Port Configuration section.
System control via extended Ethernet (example)
Current setup allows the following:
▪The System controller can communicate with LW2/LW3 commands to the IP:port address of the Matrix or the Extender.
Technical background
The Infrared signal transmission is similar to the serial data communication. Even though the matrix does not contain dedicated IR I/O connection, the TPS interface can transmit/receive IR signal in pronto HEX format.
IR interface block diagram
|
|
IR input of the TPS port. |
|
|
IR output of the TPS port. |
When the data transmission is enabled, the input/output port works in Command injection mode. The IR data (in pronto HEX format) is transferred between the TPS port and the LAN port. Separate user-configurable TCP/IP port numbers are defined for TPS IR input and IR output ports for this purpose, see the Factory Default Settings section. The settings are available in the LDC software, see the Infra Tab section.
ATTENTION!The IR signal cannot be routed from an IR port to another IR port.
IR signal transmission – example
IR Signal Transmission
The concept
When a certain button is pressed on the remote controller, the crosspoint is changed in the matrix. The IR code is sent through the TPS cable and recognized by the matrix. The recognized code is a condition that triggers the action (crosspoint change).
Settings
Matrix: The matrix has to learn the IR code in advance to recognize it, see the Infra Tab section. Then create a new event, where the stored IR (hash) code is the condition, see the Create or Modify an Event section. The action is the desired crosspoint setting.
Technical background
Serial data communication can be established via the local RS-232 port (Phoenix connector) or via the TPS lines. The RS-232 ports – which are connected to the microcontroller – can be configured separately (e.g. if the Baud rates are different, the microcontroller does the conversion automatically between the ports). The RS-232 port can be switched to Control mode, Command Injection mode, or can be Disconnected; see the figure below.
The block diagram of the Serial interface
All settings are available in the LDC software, see the RS-232 Tab section.
The following settings are defined:
|
|
The TPS serial link port is in Control mode. |
|
|
The TPS serial link port is in Command Injection mode. |
|
|
The TPS serial link port is Disconnected. |
|
|
The Local serial port is in Control mode. |
|
|
The Local serial port is in Command Injection mode. |
|
|
The Local serial port is Disconnected. |
Control mode 
The incoming data from the given port is processed and interpreted by the Microcontroller. The mode allows to control the matrix directly. LW2 or LW3 protocol commands are accepted – depending on the current port setting.
Command injection mode 
In this mode, the matrix works as an RS-232–Ethernet bidirectional converter. The Ethernet packets are converted to RS-232 data and vice versa. Unique TCP/IP port numbers are defined for the serial ports (TPS and local) for this purpose. E.g. the default Command Injection port number of the local RS 232 port is 8001. If a command is coming from the LAN interface that is addressed to the port no. 8001, it will be transmitted to the Tx pin of the local RS-232 port. It also works in the opposite direction, and the method is the same on the serial interface of the TPS ports. See the RS 232 settings in the Factory Default Settings section.
ATTENTION!The serial data cannot be routed from an RS-232 port to another RS-232 port.
RS-232 signal transmission – example
RS-232 signal transmission
The concept
The Touch controller can send commands (input/output switching, control functions, etc.) to the matrix and is able to remote control the projector via RS-232.
Settings
▪Touch controller: Wireless IP connection to the same Ethernet as the matrix is connected to. Use a dedicated software tool (e.g. a terminal) that is suitable for sending commands via TCP/IP to a certain IP:port address.
▪Matrix: The RS-232 interface of the TPS OUTPUT 1 (P4) is in Command Injection (CI) mode. Set the further parameters (Baud rate, Data bits, etc.) in accordance with the specifications of the projector. See the RS-232 Tab section.
▪Receiver: Set the RS-232 switch to Normal position. The receiver will transmit the RS 232 data between the TPS input port and the RS-232 port.
▪Projector: Note the RS-232 port setting that is specified by the Manufacturer. Connect a suitable serial cable with the proper wiring.
Command sending
▪You can send LW3 protocol commands to the 192.168.0.100:6107 port to control the matrix.
▪You can send LW2 protocol commands to the 192.168.0.100:10001 port to control the matrix.
▪You can send commands to the 192.168.0.100:8004 port to control the projector. This port number means the RS-232 interface of the TPS output port (TPS O1).
INFO:The values above are examples and are based on factory default settings.
3.8.3. USB Control Interface
The device can be controlled over a front panel USB mini B-type connector. This interface only supports LW3 protocol. The interface can be used to establish a connection to the Lightware Device Controller software.
3.9. Further Built-in Features
3.9.1. Automatically Launched Actions – the Event Manager
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 the creation of Events by defining a Condition and an Action.
Event manager example
See more information about the settings in the Event Manager section.
Matrix Cloning – Backup and Restore the Configuration
The matrix (configuration) cloning of MMX6x2-HT devices is a simple method that eliminates the need to repeatedly configure certain devices to have identical (non-factory) settings. If the devices are installed in the same type of system multiple times, then it is enough to set up only one device to fit the user’s needs, and then copy those settings to the others, thus saving time and resources.
See the details of the process in the Configuration Cloning (Backup Tab) section.
3.9.2. Remote Firmware Upgrade of Connected Lightware Devices
The firmware of the Lightware TPS devices can be updated individually by the Lightware Device Updater (LDU) software. MMX6x2 HT series contains a new feature that allows having a faster and more comfortable firmware update process. When the firmware of the connected extenders has to be updated, the TPS connection is necessary towards the extenders – nothing else. The LDU can find the connected devices and update them.
The update process is almost the same as the usual update process.
ATTENTION!The feature is supported by firmware v1.1.0 or above.
4. Operation of MMX6x2-HT Family
This chapter is about the powering and operating of the device, and describing the functions that are available by the front/rear controls:
4.1. Powering on
Connect the power cord to the IEC standard power input connector. Switch on the matrix by the power switch on the rear panel.
During the initial self-test and loading of the latest settings, ‘Booting…’ appears on the LCD screen. After the self-test, the router reloads its last configuration and it is ready for use. In case of hardware failure, an error message is displayed.
ATTENTION!After switching ON, the router reloads the latest settings that were used before it was turned off. The router has an internal emergency memory that stores all current settings and tie configurations. This memory is independent of presets and invisible for the user. This built-in feature helps the system to be ready immediately in case of power failure or accidental power down.
Control Lock #buttonlock #lockbutton
When the Control lock button shines red, the device is in control locked mode, which means front panel operations are disabled. Front panel operations are enabled if the Control lock button is not lit.
Press and hold the Control lock button for three seconds to toggle control lock state. Front panel button operations can be enabled or disabled using the Control lock button, while remote control (RS-232, USB or Ethernet) is still available.
The router has two different switching modes: Take and Autotake. If the Take button is unlit, Take mode is active. When the Take button continuously shines green, Autotake mode is selected. Press and hold the Take button for two seconds to change between Take and Autotake modes. #autotakemode
Take mode allows the user to connect or disconnect multiple outputs to an input at once. This mode is useful when time delay is not allowed between multiple switching. The commands are only realized when the Take button is pressed.
ATTENTION!If no button is pressed for three seconds, all preselected actions (which were not realized by pressing TAKE) will be ignored, and the router returns to its idle state.
Autotake mode is useful when immediate actions must be done or fast switching is needed between sources on a particular destination. In this mode switching occurs immediately upon pressing one of the input selector buttons.
The current switching status can be checked on the front panel by using the front panel buttons. The crosspoint state is displayed slightly differently in Take or Autotake modes because of the different switching methods. #portstatus
INFO:View mode does not mean that the router has to be switched in different modes, viewing and switching can be done after each other, without pressing any special buttons.
View Current State in Take Mode
If the router is in Take mode, the user can verify both input and output connections. In Take mode no accidental change can be done unless the Take button is pressed.
Press and release a source button. Now the selected source button and all destination buttons that are currently connected to the selected source will light up. This informative display will remain active for three seconds, then all buttons turn dark.
The sample drawing shows that Input 1 is currently connected to the Output 2 port.
If every source, destination, and the Take button are unlit (the unit is in Take mode, and no input was selected in the last 3 seconds), press and release a destination button to see its current state. Now the source button that is connected to the selected destination will light up.
The sample drawing shows that Output 2 is connected to the Input 1 port.
View Current State in Autotake Mode
In Autotake mode only states of destinations can be viewed.
Press and release the required destination button. Now the source button that is connected to the selected destination will light up.
4.2.2. Switching Operations
Switching in Take Mode #switch
Take mode allows the user to connect or disconnect multiple outputs to an input at once. This mode is useful when time delay is not allowed between multiple switching. The commands are only realized when the Take button is pressed.
Step 1.First, press and release the desired source button. The pressed source button and all destination buttons that are currently connected to the source light up.
Step 2.Press and release the desired destination buttons that have to be (dis)connected to/from the selected source. The preselected destination buttons will blink. If no button is pressed for three seconds, the buttons will turn dark.
Step 3.Press and release the Take button; the selected input is switched to the selected output(s).
Switching in Autotake Mode
Autotake mode is useful when immediate actions must be done or fast switching is needed between sources on a particular destination. In this mode switching occurs immediately upon pressing one of the input selector buttons.
Step 1.Press and release the desired destination button. The pressed destination button and the currently connected source button light up green. If no source is connected (the output is muted), no source button will light up.
Step 2.Press and release the desired source button. The switch action will be executed immediately. Switching between sources to the selected destination can be done directly.
4.2.3. Output Lock
ATTENTION!While the front panel buttons only allow locking the output ports, the input ports can also be locked by using the Lightware Device Controller software (see the Video Port and Crosspoint Settings section) or by sending LW3 protocol commands (see the Locking the Input Port section).
Using Lightware routers, it is possible to lock a destination. This feature prevents an accidental switching to the locked destination in case of an important signal. Locking a destination means that no input selection or muting action can be executed on that particular destination.
Destinations can be independently locked or unlocked. Locking a destination does not affect other destinations.
Output Lock in Take Mode
Step 1.Press and release the Output Lock button; it starts blinking and all the buttons of any locked destinations light up (view state).
Step 2.Press and release a destination button; it starts blinking (more destinations can be selected sequentially).
Step 3.Press and release the Take button. The selected destinations are now locked.
Output Lock in Autotake Mode
Step 1.Press and release the required destination button. Now the selected destination button and the currently configured source button light up (view mode).
Step 2.Press and release the Output Lock button; it lights up in red, and lock function is activated at once. No source can be changed at the locked destination.
Front panel button operation can be enabled or disabled using the Control Lock button, while the remote control is still enabled. If the button is unlit, front panel button operation is enabled. If the button continuously shines red, the front panel operations are not possible. Press and keep the Control Lock button pressed for three seconds to toggle between the control lock states. #buttonlock #lockbutton
The matrix can store user-programmable presets. Each preset stores a configuration regarding all input connections for all outputs. All presets are stored in a non-volatile memory; the router keeps the presets even in the case of a power down. Please note, that preset operations can be followed on the LCD during front panel preset operations.
ATTENTION!Eight of the memory slots are available by the Source buttons; see the Preset Settings for the details.
Saving a Preset in Take Mode
Step 1.Press and release the Save Preset button.
Step 2.Press and release the desired source (memory address) button (source 1 to 6).
Step 3.Press and release the Take button. Now the current configuration is stored in the selected memory.
ATTENTION!The preset save action always stores the current configuration for all outputs.
Loading a Preset in Take Mode
Step 1.Press and release the Load preset button.
Step 2.Press and release the desired source (memory address) button (source 1 to 6).
Step 3.Press and release the Take button. Now the selected preset is loaded.
Saving a Preset in Autotake Mode
Step 1.Press and release the Save Preset button.
Step 2.Press and release the desired source (memory address) button (source 1 to 6). Now the current configuration is stored in the selected memory.
ATTENTION!The preset save action always stores the current configuration for all outputs.
Loading a Preset in Autotake Mode
Step 1.Press and release Load Preset button.
Step 2.Press and release the desired source (memory address) button (source 1 to 6). Now the selected preset is loaded.
4.3. Front Panel Operations – Quick Summary
Take mode
View input connections
View output connections
Change connections
Save a preset
Load a preset
View locked outputs
Lock/unlock an output
Autotake mode
View current state
Create a connection
Save a preset
Load a preset
View locked state of an output
Lock/unlock an output
4.4. Front Panel LCD Menu Operation
The matrix has an LCD menu and navigation buttons, which offer the possibility of changing certain settings and displaying basic information via the front panel.
Navigation
Front panel LCD has 2 lines and 16 characters in each line. The name of the menu item is always displayed in the first line. If no button is pressed for 5 minutes, the LCD returns to its idle state and Device information is shown.
|
Buttons |
Functions |
|
|
|
up |
Toggle between menu items |
|
|
down |
|
|
« |
left |
Move the cursor or step back to the previous menu |
|
» |
right |
Move the cursor |
|
|
enter |
Execute changes or enter submenu |
|
• |
escape |
Step back to the previous menu; cancel the operation |
Display mode / Edit mode
The parameters are displayed in two modes on the LCD as follows:
|
Display mode |
Edit mode |
|
|
In Display mode, the value cannot be changed; the 
up and 
down buttons can be used to step between the submenu items (e.g. IP address – Subnet mask – Static gateway, etc.). In Edit mode, the values can be changed with the up and down buttons.
Display mode is the default; select the desired parameter and press enter to select Edit mode.
Idle state (Device information)
If no button is pressed for 5 minutes or the user navigates out from the menu by the escape • and/or the left « button, LCD gets into idle state. Front panel menu displays the following information in idle state:
Control RS-232 settings #rs232 #rs-232
The local RS-232 port settings are available in the front panel menu.
Baud rate
Step 1.Navigate to the Settings / Control RS232 / Baudrate submenu and press the enter button.
Step 2.To change the setting, press the enter button and use the up and down buttons to select the desired value.
Step 3.Press the enter button to save changes.
Data Bits
Step 1.Navigate to the Settings / Control RS232 / Data Bits submenu and press the enter button.
Step 2.To change the setting, press the enter button and use the up and down buttons to select the desired value.
Step 3.Press the enter button to save changes.
Stop Bits
Step 1.Navigate to the Settings / Control RS232 / Stop Bits submenu and press the enter button.
Step 2.To change the setting, press the enter button and use the up and down buttons to select the desired value.
Step 3.Press the enter button to save changes.
Parity
Step 1.Navigate to the Settings / Control RS232 / Parity submenu and press the enter button.
Step 2.To change the setting, press the enter button and use the up and down buttons to select the desired setting.
Step 3.Press the enter button to save changes.
Loading factory default settings #factory
Step 1.Navigate to the Settings / Fact. defaults submenu and press the enter button.
Step 2.Press the enter button to load factory defaults or the escape • button to cancel.
Step 3.The device is restarted; factory default settings and parameters are set. See the list of the details in the Factory Default Settings section.
The firmware of the device can be upgraded in Bootload mode. If the working mode of the device is not switched to bootload mode automatically, the mode can be also switched manually.
Step 1.Navigate to the Settings / Enter Bootload Mode submenu and press the enter button.
Step 2.Press the enter button to switch to Bootload mode.
Step 3.LCD will display the IP address of the Bootloader. (The device can be switched to normal operation mode by pressing the reset button or turning the matrix off and on again.)
Resetting the device #reboot #restart
Step 1.Navigate to the Settings / Reset submenu and press the enter button.
Step 2.Press the enter button to restart the device or the escape • button to cancel.
Step 3.The matrix is restarted immediately.
DHCP setting #dhcp
Step 1.Navigate to the Network Settings / DHCP submenu and press the enter button.
Step 2.To change the setting, press the enter button and use the up and down buttons to toggle between Enabled and Disabled settings.
Step 3.Press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
Setting the IP address #ipaddress
Step 1.Navigate to the Network Settings / IP Address submenu and press the enter button.
Step 2.To change the numbers, press the enter button and use the left « and right » buttons to place the cursor to the desired number.
Step 3.Set the numbers by the up and down buttons and press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
Setting the Subnet mask
Step 1.Navigate to the Network Settings / Subnet mask submenu and press the enter button.
Step 2.To change the numbers, press the enter button and use left « and right » buttons to place the cursor to the desired number.
Step 3.Set the numbers by the up and down buttons and press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
Setting the Static gateway
Step 1.Navigate to the Network Settings / Static gateway submenu, press the enter button.
Step 2.To change the numbers, press the enter button and use left « and right » buttons to place the cursor to the desired number.
Step 3.Set the numbers by the up and down buttons and press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
LW2 port setting
Step 1.Navigate to the Network Settings / Lw2 Port submenu and press the enter button.
Step 2.To change the numbers, press the enter button and use left « and right » buttons to place the cursor to the desired number.
Step 3.Set the numbers by the up and down buttons and press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
LW3 port setting
Step 1.Navigate to the Network Settings / Lw3 Port submenu and press the enter button.
Step 2.To change the numbers, press the enter button and use left « and right » buttons to place the cursor to the desired number.
Step 3.Set the numbers by the up and down buttons and press the enter button to save changes.
Step 4.Press the escape • button twice to navigate out from the submenu. You will be prompted to apply settings – press the enter button.
Apply settings
Step 1.Navigate to the Network Settings / Apply Settings submenu and press the enter or the right » button.
Step 2.Press the enter button to confirm.
INFO:The MAC address is also available in the Network settings submenu (read-only).
4.4.3. Health Status
INFO:The following values are stored in a non-volatile memory and will not be erased during firmware upgrade.
Voltages
The voltage values are listed are measured internally in the matrix.
Temperatures
The temperature values listed are measured internally in the matrix.
Operational time
The following time values are measured during operation:
▪Up Time: The time elapsed from the last boot.
▪Total Up Time: The total operational time (updated every 5 minutes).
▪Total high temperature Up Time: The total operational time when the measured internal temperature was above 70°C (the first 60 seconds are ignored).
ATTENTION!If the measured internal temperature is above 80°C (defined as Very High Temperature) for more than 60 seconds, the matrix is shut down automatically to avoid any damage.
TPS inputs (TPSIN1 and TPSIN2)
▪HDCP Enable: Enabled / Disabled
▪Audio Mode: Embedded / Aux1 / Aux2 / Aux3 / Aux4. The setting allows to pre-select the desired audio to the video on the given TPS input. The setting will be valid on all TPS/HDMI outputs where the audio mode is set to Pass-through.
▪PoE Enable: Enabled / Disabled
▪PoE Status: ON / OFF
▪TPS Mode: Auto / HDBaseT / Long reach / LPPF1 / LPPF2
▪TPS Status: Connected / Disconnected
HDMI inputs (HDMIIN3 – HDMIIN6)
▪HDCP Enable: Enabled / Disabled
▪Audio Mode: Embedded / Aux1 / Aux2 / Aux3 / Aux4. The setting allows to pre-select the desired audio to the video on the given HDMI input. The setting will be valid on all TPS/HDMI outputs where the audio mode is set to Pass-through.
Analog audio inputs (AUXIN1 – AUXIN4)
▪Volume: from -95 to 0 dB, step = 0.375 dB
▪Balance: from 0 to 100, step = 1 (50 = center)
▪Gain: from 0 to 21 dB, step = 0.75 dB
HDMI outputs (HDMIOUT1 and HDMIOUT2)
▪HDMI Mode: Auto / DVI / HDMI. The setting determines the output signal type.
▪HDCP Mode: Auto / Always
▪Audio Mode: Pass-through / AUX1 / AUX2 / AUX3 / AUX4. The desired audio can be selected to the video on the given HDMI output, thus the setting will override the input setting. In Pass-through mode, the setting on the input port will be valid.
▪Pwr5V Mode: Auto / Always on / Always off. The setting lets the source and the sink devices be connected – independently of the transmitted signal.
▪TPG Mode: Disabled / Enabled. The test pattern generator can be switched on/off.
TPS outputs (TPSOUT3 and TPSOUT4)
▪HDMI Mode: Auto / DVI / HDMI. The setting determines the output signal type.
▪HDCP Mode: Auto / Always
▪Pwr5V Mode: Auto / Always on / Always off. The setting lets the source and the sink devices be connected – independently of the transmitted signal.
▪TPG Mode: Disabled / Enabled. The test pattern generator can be switched on/off.
▪PoE Enable: Enabled / Disabled
▪PoE Status: ON / OFF. If power is sent via the current TPS output, the status is ON.
▪TPS Mode: Auto / HDBaseT / Long reach / LPPF1 / LPPF2
▪TPS Status: Disconnected / Connected (Read-only parameter)
Analog audio outputs (AUXOUT1 and AUXOUT2)
▪Volume: from -57 to 0 dB, step = 1 dB
▪Balance: from 0 to 100, step = 1 (50 = center)
▪Gain: from 0 to 3 dB, step = 1 dB
4.4.6. Signal Info Menu
Basic information is displayed about the transmitted audio and video in the submenus: image resolution, refresh rate, color depth and audio type.
4.4.7. EDID Settings
The currently emulated EDIDs are shown on each video input and the EDID can be also changed on the input. #edid
INFO:The same settings are available for the HDMI and TPS video inputs.
Changing the emulated EDID
Step 1.Select the desired input, e.g. navigate to the EDID settings / Switch submenu and press the enter button. The submenu is now in Display mode.
The upper line shows the memory place of the currently emulated EDID, e.g. Out1 means the (dynamic) EDID on the HDMI input 1 port. The second line is scrolled automatically to display the manufacturer code, the resolution with the refresh rate and the sink type.
Step 2.Press the enter button to Edit mode:
▪Use the left « and right » buttons to select the EDID memory group (Factory, User, Dynamic).
▪Use the up and down buttons to toggle between the memory places (e.g. D1..D4).
Step 3.Press the enter button to store the desired combination.
INFO:See the EDID memory structure in the Factory EDID List section.
4.4.8. Device Presets Menu
The matrix has 4 user programmable presets. Each preset stores the full configuration of the matrix. All presets are stored in a non-volatile memory; the matrix keeps presets even in case of a power down. This is the same as using the backup-restore feature of the Lightware Device Controller software (see the Matrix Cloning – Backup and Restore the Configuration section), but in this case the settings are stored in the matrix.
The list of the stored parameters and values can be found in the Content of the Backup File section
Run a preset
Step 1.Navigate to the Device Presets / Run Preset submenu and press the enter button.
Step 2.Press the enter button to activate the Run Preset submenu. Use the up and down buttons to toggle between the preset memories.
Step 3.Press the enter button to run the Preset. The configuration is restored.
Save a preset
Step 1.Navigate to the Device Presets / Save Preset submenu and press the enter button.
Step 2.Press the enter button to activate the Save Preset submenu. Use the up and down buttons to toggle between the preset memories.
Step 3.Press the enter button to save the Preset. The configuration is stored.
Delete a preset
Step 1.Navigate to the Device Presets / Delete Preset submenu and press the enter button.
Step 2.Press the enter button to activate the Delete Preset submenu. Use the up and down buttons to toggle between the preset memories.
Step 3.Press the enter button to delete the Preset. The preset memory is erased.
4.4.9. Info Menu
The Info menu displays basic information: the serial number and part number of the matrix; details about the firmware of the CPU and other controllers.
5. Software Control – Lightware Device Controller
The extender can be controlled by a computer through the LAN, RS-232, and USB ports using Lightware Device Controller (LDC). The software can be installed on a Windows PC or macOS. The application can be downloaded from www.lightware.com. The Windows and the Mac versions have the same look and functionality.
5.1. Install and Update
INFO:After the installation, the Windows and the macOS applications have the same look and functionality.
Minimum System Requirements
OS: Windows 10 (64 bit) or macOS 11.0
CPU: Single core 2.0 GHz
RAM: 512 MB
HDD: 400 MB
Minimum display resolution: 1280x720
Installation for Windows OS
Run the installer. If the User Account Control drops a pop-up message, click Yes.
During the installation you will be prompted to select the type of the installation: normal and the snapshot install:
|
Normal install |
Snapshot install |
|
Available for Windows and macOS |
Available for Windows |
|
The installer can update only this instance |
Cannot be updated |
|
Only one updateable instance can exist for all users |
More than one different version can be installed for all users |
Comparison of Installation Types
ATTENTION!Using the Normal install as the default choice is highly recommended.
Installation for macOS
ATTENTION!Please check the firewall settings on the macOS device. LDC needs to be added to the exeptions of the blocked softwares for proper operation.
Mount the DMG file by double clicking on it, and drag the LDC icon over the Applications icon to copy the program into the Applications folder. If you want to copy the LDC into another location, just drag the icon over the desired folder.
Updating the LDC
Step 1.Run the application.
The Device Discovery window appears automatically, and the program checks the available updates on Lightware’s website and opens the update window if LDC updates are found.
The current and the update version number can be seen at the top of the window and they are shown in this window even with the snapshot install.
The Update window can also be opened by clicking on the About icon and the Update button.
Set the desired update setting in the Options section.
▪If you do not want to check for updates automatically, uncheck the circle that contains the green tick.
▪If you want to postpone the update, a reminder can be set with different delays from the drop down list.
▪If the proxy settings traverse the update process, set the proper values, then click on the OK button.
Step 2.Click on the Download update button to start the upgrading.
The updates can be checked manually by clicking on the Check now button.
5.2. Running the LDC
The common way to start the software is to double-click on the LDC icon. But the LDC can be run by command line parameters as follows:
Connecting to a Device with Static IP Address
Format: LightwareDeviceController -i <IP_address>:<port>
Example: LightwareDeviceController -i 192.168.0.20:10001
The LDC is connected to a device with the indicated static IP address directly; the Device Discovery window is not displayed. When the port number is not set, the default port is used: 10001 (LW2 protocol). For LW3 devices, use the 6107 port number.
Adjusting the Zoom
The window can be zoomed to a specific value to fit to the resolution of the desktop (higher/lower). '1' is the default value (100%).
Format: LightwareDeviceController -z <magnifying_value>
Example: LightwareDeviceController -z 1.2
ATTENTION!The last set value is stored and applied when LDC is started without a parameter.
5.3. Establishing the Connection
Step 1.Connect the device to a computer via Ethernet, USB, or RS-232.
Step 2.Run the controller software; device discovery window appears automatically.
Ethernet Connection in Device Discovery Window
Step 3.Select the unit from the discovered Ethernet devices or under USB devices; when the device is connected through RS-232, click on the Query button next to the desired serial port to display the device’s name and serial number. Double click on the matrix, or select the device and click on the Connect button.
ATTENTION!When the device is connected via the local RS-232 port, make sure that Control mode and LW3 protocol are set on the serial port.
Change IP Address #ipaddress
To modify IP address settings quickly, it is not necessary to enter the device's settings/network menu, you can set them by clicking on the pencil icon beside the IP address. You can see the new settings only in this window.
Identifying the Device
Clicking on the icon results in the blinking of the LDC screen for 10 seconds. The feature helps to identify the device itself in the rack shelf.
When LDC finds the hardware, it determines the product type, and the LDC starts with the default page, showing the Crosspoint menu. #crosspoint #switch
|
1 |
Main menu |
The available menu items are displayed. The active one is shown with dark grey background color. |
|
2 |
Information ribbon |
The label shows the Device label of the connected device. Device discovery window can be displayed by clicking on this ribbon. When you hover the cursor over it, the Product name and the IP address of the device are displayed in a hint box. |
|
3 |
Submenu selector |
The available submenu items are displayed; in the Crosspoint menu, the Video and the Presets submenus are defined. |
|
4 |
Input ports |
HDMI and TPS input ports; click on the port to open the port properties window. |
|
5 |
Connections |
A light grey square means the port is available, but there is no connection between the input and the output. A white square means there is a connection between the input and the output port. |
|
6 |
Output ports |
TPS and HDMI output ports; since HDMIOUT1 and TPSOUT1 carry the same AV signal (such as HDMIOUT2 and TPSOUT2), the selected input will be switched to both output ports. |
|
7 |
Advanced view |
Displaying Advanced view page, showing the Terminal window and the LW3 protocol tree. |
Port Tiles
The colors of the port tiles and the displayed icons represent different states and information:
The following icons display different states of the port/signal:
|
Icon |
Icon is grey |
Icon is black |
|
Signal is not encrypted with HDCP |
Signal is encrypted with HDCP |
|
Port is unlocked |
Port is locked |
|
Port is unmuted |
Port is muted |
|
A |
Autoselect is disabled |
Autoselect is enabled* |
* Displayed only on output ports; when Autoselect is enabled, the icon is displayed in green.
5.5. Port Properties and Settings
Click on a port to display its properties; Signal status information and the most important parameters are displayed. Special functions (e.g. frame detector, test pattern generator) are also available on the panel. The look and the content are port-dependent.
5.5.1. Port Name
The name of a port can be changed by typing the new name and clicking on the Set button. The following characters are allowed when naming:
Letters (A-Z) and (a-z), hyphen (-), underscore (_), numbers (0-9) and dot (.).
The incoming/outgoing signal can be muted on the input and output ports. If the output is muted, button text is Muted. When the port is muted, no signal is present on the output.
INFO:The mute/unmute setting can be set on the output ports independently from each other, e.g. if HDMIOUT1 is muted, TPSOUT1 may be unmuted.
5.5.3. Lock/Unlock
The output ports can be locked by clicking on the button Unlocked. If the output is locked, button text is Locked. If the port is locked, its mute state cannot be changed either by the button or by loading a preset.
ATTENTION!Since the output ports are mirrored, the lock/unlock setting is valid on both outputs; e.g. if HDMIOUT1 is locked, TPSOUT1 is also locked.
The autoselect feature can be set on TPS out or HDMI out properties panel. #autoselect
See more information about the Autoselect modes in the The Autoselect Feature section.
Input priorities
The available input ports are listed; each one has its own priority number (equal numbers are allowed). If you want to disable a port from the priority list, uncheck the setting next to the priority number and the priority number will be emptied and disabled. A smaller number means higher priority, as usual. Priority 31 is the lowest priority, in this case, the port will not be checked and cannot be selected.
Always press the Set priorities button after a modification to store the settings.
5.5.5. TPS Mode Settings (TPSIN, TPSOUT)
The TPS working mode between the transmitter and the receiver parties is determined by the mode set in them. Both parties influence the setting that determines the final TPS transmission mode. The TPS settings mode selection is available on the TPS port properties panel. #tpsmode
See more information about TPS modes in the TPS Interface section.
5.5.6. PoE Setting (TPSIN, TPSOUT)
The matrix is able to supply (send remote power) devices through the TPS input and output ports that are compatible with the PoE standard. The PoE feature can be also enabled or disabled in the port properties window.
See more information about PoE feature in the Power over Ethernet (PoE) section.
The audio coming from the analog inputs can be assigned to any video input or any video output in a drop-down menu. The input audio modes are valid if the output audio mode is set to Pass-through mode. The output audio modes can override the input audio mode when it is Aux1...Aux4.
See more information about the audio options in the Audio Interface section.
The audio output is determined by the setting of both the input and the output port. The following table shows the possible combinations:
|
Output |
||||
|
Pass-through |
AUXm |
Copy from other output |
||
|
Input |
Embedded |
Embedded |
AUXm |
Copy from other output |
|
AUXn |
AUXn |
AUXm |
Copy from other output |
|
Audio Source Settings
Always Keep Audio Alive Option
Keeps HDMI and analog audio output alive to maintain audio transmission even when video is not available at the output. If video signal is not present, a 480p black screen will be transmitted automatically.
INFO:When enabled, no signal mode is not available in test pattern generator.
5.5.8. Further Settings (HDMIOUT, TPSOUT)
HDMI mode: Auto / DVI / HDMI
The outgoing signal format can be selected from a drop-down menu.
HDCP: Auto / Always
The matrix forces the source to send the signal without encryption if the content allows when Auto mode is selected.
Power 5V: Auto / Always on / Always off
The setting lets the source and the sink devices be connected – independently from the transmitted signal.
5.6. Diagnostic Tools
The cable diagnostics is a useful tool to determine any cable related issues in case of TPS connection. The estimated cable length and the quality of the link are measured periodically and the diagnostic window shows the values in real-time. If the green bars hit the first line in the middle, they turn red. It means the number of the errors during the extension is higher than what is generally deemed acceptable. The link might be alive, but recovery of the received data is not guaranteed. #diagnostic #cablediagnostics
INFO:Each bar represents a differential line in the CATx cable. The inappropriate termination of the cable usually causes high error rates. Check the cable terminations or change the cable.
Reference Values
|
Value |
Explanation |
|
10-10-10-9 |
Excellent image quality |
|
10-8 |
Minor error, not recognizable by eyes |
|
10-7 |
Sometimes recognizable flash on a special test pattern |
|
10-6 |
Small noise can be seen |
|
10-5 |
Easy to recognize image error |
|
10-4 |
Bad image quality |
The Video Bit Error Ratio (BER) displayed above means that on average there is 1 bad pixel after 1010 pixels, which means the number of the bit errors is about 1 pixel in every 80 seconds at 1080p60 video signal.
INFO:You can find more details about maximum twisted pair cable distances in the Maximum Twisted Pair Distances section.
Table and Chart Views
Cable diagnostics can be displayed in advanced modes as well. Two ways are available: table view and chart view. Data can be exported to a file by clicking on the Export data button.
Table view of cable diagnostics
Chart view of cable diagnostics
The ports can show detailed information about the signal like full size and active video resolution. This feature is a good troubleshooter if compatibility problems occur during system installation. To access this function, open the port properties window and click on the Frame detector button. #framedetector
Frame detector window
Lightware’s Frame Detector function works like a signal analyzer and makes it possible to determine the exact video format that is present on the port, thus helps to identify many problems. E.g. actual timing parameters may differ from the expected and this may cause some displays to drop the picture.
Frame Detector measures detailed timings on the video signals just like a built-in oscilloscope, but it is much more easy to use. Actual display area shows the active video size (light grey). Dark grey area of the full frame is the blanking interval which can contain the info frames and embedded audio data for HDMI signals. Shown values are measured directly on the signal and not retrieved only from the HDMI info frames.
5.6.3. No Sync Screen (Test Pattern)
No sync screen options in the port properties window of TPS output
The No sync screen feature generates an image that can be displayed when there is no incoming signal on the port. The following settings can be set for the Test Pattern function: #nosyncscreen #testpattern
Mode
▪On: the video output port always transmits the test pattern.
▪No signal: the video output port transmits the test pattern if there is no incoming signal on the selected input port.
▪Off: the test pattern function is disabled, the video output port transmits the video signal of the selected input port.
Clock Source
▪480p
▪576p
▪Original video signal
Pattern
▪Red / Green / Blue / Black / White / Ramp / Chess / Bar / Cycle. Cycle pattern means all the patterns are changed sequentially approx. every 2 seconds.
ATTENTION!Even though the mode of the Test pattern can be set at each port separately, the clock source and the pattern settings are common.
The matrix has six user-programmable presets. Each preset stores a configuration regarding the crosspoint and mute state for all inputs/outputs. All presets are stored in a non-volatile memory; the router keeps presets even in case of a power down. The presets can be run from the front panel or by sending protocol commands, too.
Preset settings
Loading a Preset
Step 1.Select the Presets tab from the Crosspoint menu.
Step 2.Select the desired preset; check the Preview panel and press the Load button. Press Yes in the confirmation window.
INFO:Presets that were saved by the front panel buttons previously are listed with names Preset1..Preset6 as default. See the corresponding Save or Load a Preset section.
Saving a Preset
Step 1.Arrange the desired crosspoint connections.
Step 2.Select the Presets tab from the Crosspoint menu and choose a target preset slot from Preset 1.. Preset 6. Type the desired Preset name in the indicated text field, up to 16 characters. The following are allowed when naming: letters (A-Z and a-z), hyphen (-)underscore (_), and numbers (0-9).
Confirm it with the Rename Preset button.
Step 3.Press the Save button and Yes to confirm storing the configuration.
Renaming a Preset
Step 1.Select the desired preset you want to rename.
Step 2.Type the desired name and press the Rename Preset button.
Deleting a Preset
Step 1.Select the desired preset you want to delete.
Step 2.Press the Clear button and Yes to confirm.
Auto Load Mode
When the Auto Load button is highlighted in green, the mode is active. In this case, confirmation is not required: the selected preset is loaded immediately when the button is pressed.
Advanced EDID Management can be accessed by selecting the EDID menu. There are two panels: the left one contains Source EDIDs, the right one contains Destination places where the EDIDs can be emulated or copied. #edid
EDID Menu
Control buttons
|
|
Exporting an EDID (save to a file) |
|
Executing EDID emulation or copying (Transfer button) |
|
|
Importing an EDID (load from a file) |
|
Deleting EDID (from User memory) |
|
|
Display EDID Summary window |
|
Selecting all memory places in the right panel |
|
|
Opening Advanced EDID Editor with the selected EDID |
|
Selecting none of the memory places in the right panel |
|
|
Opening Easy EDID Creator |
5.8.1. Sources and Destinations
The EDID memory consists of four parts:
▪Factory EDID list shows the pre-programmed EDIDs (F1-F120).
▪Dynamic EDID list shows the EDID of the display device connected to the device's outputs. The unit stores the last display devices’ EDID on either output, so there is an EDID shown even if there is no display device attached to the output port at the moment.
▪User memory locations (U1 – U12) can be used to save custom EDIDs.
▪Emulated EDID list shows the currently emulated EDID for the inputs. The source column displays the memory location that the current EDID was routed from.
The source reads the EDID from the Emulated EDID memory on the INPUT port. Any EDID from any of the User/Factory/Dynamic EDID lists can be copied to the user memory.
There are two types of emulation: static and dynamic.
▪Static EDID emulation: an EDID from the Factory or User EDID list is selected. Thus, the Emulated EDID remains the same until the user emulates another EDID.
▪Dynamic EDID emulation: it can be enabled by selecting D1 or D2 EDID memory. The attached monitor’s EDID is copied to the input; if a new monitor is attached to the output, the emulated EDID changes automatically.
5.8.2. EDID Operations
Changing Emulated EDID
Step 1.Choose the desired EDID list on the source panel and select an EDID.
Step 2.Press the Emulated button on the top of the Destination panel.
Step 3.Select the desired port on the right panel (one or more ports can be selected); the EDID(s) will be highlighted with a yellow cursor.
Step 4.Press the Transfer button to change the emulated EDID.
Learning an EDID
The process is the same as changing the emulated EDID; the only difference is the Destination panel: press the User button. Thus, one or more EDIDs can be copied into the user memory either from the factory memory or from a connected sink (Dynamic).
Exporting an EDID
ATTENTION!This function is working on Windows and Mac OS X operating systems and under Firefox or Chrome web browsers only.
Source EDID can be downloaded as a file (*.bin, *.dat or *.edid) to the computer.
Step 1.Select the desired EDID from the Source panel (highlighted with a yellow cursor).
Step 2.Press the Export button to open the dialog box and save the file to the computer.
Importing an EDID
Previously saved EDID (*.bin, *.dat or *.edid file) can be uploaded to the user memory:
Step 1.Select the User tab in the left panel and select a memory slot.
Step 2.Press the Import button below the Source panel.
Step 3.Browse the file in the opening window, then press the Open button. The browsed EDID is imported into the selected User memory.
ATTENTION!The imported EDID overwrites the selected memory place even if it is not empty.
Deleting EDID(s)
The EDID(s) from User memory can be deleted as follows:
Step 1.Select the User tab in the left panel.
Step 2.Select the desired memory slot(s); one or more can be selected (Select all and Select None buttons can be used). The EDID(s) will be highlighted in yellow.
Step 3.Press the Delete selected button to delete the EDID(s).
5.8.3. EDID Summary Window
Select an EDID from the Source panel and press the Info button to display EDID summary.
5.8.4. Editing an EDID
Select an EDID from the left panel and press the Edit button to display the Advanced EDID Editor window. The editor can read and write all descriptors that are defined in the standards, including the additional CEA extension. Any EDID from the device’s memory or a saved EDID file can be loaded into the editor. The software resolves the raw EDID and displays it as readable information to the user. All descriptors can be edited and saved in an EDID file, or uploaded to the User memory. For more details about EDID Editor, please download the EDID Editor Application Notes.
Since the Advanced EDID Editor mentioned above needs more complex knowledge about EDID, Lightware introduced a wizard-like interface for fast and easy EDID creation. With Easy EDID Creator it is possible to create custom EDIDs in four simple steps. By clicking on the Create button below the left panel, Easy EDID Creator is opened in a new window.
Easy EDID Creator Wizard
5.9. Control Menu
The menu gives the opportunity to set the interfaces that can be used to connect or control third party devices.
Control Menu, RS-232 Tab
The following settings and functions are available (both on local and TPS serial ports): #rs232 #rs-232
▪Operation mode: Control, Command Injection, or Disconnect (for more details about serial interface modes see the Serial Interface section);
▪Baud rate: 4800, 7200, 9600, 14400, 19200, 38400, 57600, 115200;
▪Data bits: 8 or 9;
▪Parity: None, Odd, or Even;
▪Stop bits: 1, 1.5, or 2;
▪Command injection: enable or disable; port number;
▪Control protocol: LW2 or LW3;
▪Message sending via serial port;
▪Reloading factory defaults (see factory default settings in the Factory Default Settings section).
5.9.2. Ethernet Tab
Basic information is shown about the network communication; the port names can be changed, and each Ethernet port can be enabled/disabled except the Control Ethernet port.
Ethernet Tab
ATTENTION!The device has no built-in Infrared receiver and transmitter. For the complete usage, attach an IR emitter unit to the IR OUT and an IR detector unit to the IR IN connectors of an extender, and connect the extender to the matrix via TPS..
Infrared (IR) receiver and transmitter options can be found on this tab. There are three submenus available under it: IR codes, Ports, and Clear all IR codes. #infra #infrared
IR Codes
The user can set the name of the IR code, the fingerprint (hash), and the repeat timeout in ms, and actions can be ordered to each IR code as well.
IR codes window in Control menu
|
Description |
Function |
|
ID |
Code number. |
|
Name |
You can give an unique name for the desired code. |
|
Fingerprint (hash) |
Fingerprint code in pronto HEX format. |
|
Detected |
Indicator gives feedback whether the given IR code is detected currently. |
|
Repeat timeout (ms) |
You can set a timeout to avoid the involuntary code recurrence. |
|
Actions |
Action buttons for the desired IR code: |
|
Detected IR fingerprints |
You can check the detected IR codes in this panel. Pushing the Clear button deletes all current fingerprints, and you can switch the automatic scrolling on or off with the Autoscroll option. |
80 fingerprints can be stored in the device at the same time. Each of them can be ordered to an action in Event Manager. For more details about events, see the Event Manager section.
Learning IR Codes
Step 1.Connect the IR detector unit to the IR IN port of the extender.
Step 2.Connect the extender to the TPS IN port of the matrix using a CATx cable.
Step 3.Click on the Learn button.
Step 4.Turn the remote controller to the IR detector. A pop-up window appears in LDC - press your remote button to learn.
Step 5.Once the code is received, a new window pops up in LDC - learning completed. Click on OK to continue.
Step 6.Optionally type a unique name for the code in the Name text box. The default name is code#, e.g. code0.
INFO:The setting depends on the device, as the port numbers are different. Port numbers are listed in section Input and Output Port Numbering.
Ports
The user can set the name and command injection port to each source and destination. For more details about IR interface, see the IR Interface section.
Infra tab - Ports window
Clear all IR codes
Clicking on the button deletes all stored IR fingerprints.
The feature means that the device can sense changes on its ports and is able to react according to the pre-defined settings. The development idea of the Event manager is based on users’ feedbacks. In many cases internal events (such as signal being present) are necessary to display, but it is not easy when the device is hard to access (e.g. built under the desk). #eventmanager
INFO:For tips and tricks and detailed description about the application of Event Manager, please download the Event Manager User's Guide from the Download section on the www.lightware.com.
The Event manager can be configured to perform an action if a condition has been detected. E.g. the desired setup is that after a certain type of signal has been detected on I1 port, the port has to be switched to O1. The settings can be done via the LDC in the Control/Events tab, or by LW3 protocol commands. The number of configurable events depends on the device that you are using actually.
Numerous new ideas and requests have been received in connection with the features and settings of the Event manager since the first release. Therefore, the user interface has been re-designed and many new functions have been implemented. The Event editor can be opened by pressing the Edit button at each Event.
There is a grey bar on the left of the Event panel in each line. If a condition and an action are set and the Event is enabled, the bar is displayed in green.
Control menu, Event Manager tab
Press the Edit button in the desired Event line to open the Event editor window.
|
1 |
Event header |
The name of the Event is displayed. Type the desired name and press the Set name button. The Event can be cleared by the Clear button. Use the tick mark to enable/disable the Event. |
|
2 |
Condition header |
If the condition is set, the description (white colored text) and the exact LW3 protocol expression (yellow colored text) can be seen. If the advanced mode was used, the description is Custom condition. |
|
3 |
Condition panel |
Different tools are available at the tabs to set the desired Condition. The parameters and settings are displayed below the buttons.. |
|
4 |
Condition counter |
If the set Condition is detected (or triggered), the indicator turns green for two seconds, and the counter is increased. The counter is reset at boot. |
|
5 |
Delay settings |
The action can be scheduled to follow the condition after the set time value. |
|
6 |
Action header |
If the action is set, the description (white colored text) and the exact LW3 protocol expression (yellow colored text) can be seen. If the advanced mode was used, the description is Custom action. |
|
7 |
Action panel |
Different tools are available at the tabs to set the Action. The parameters and settings are displayed below the buttons. |
|
8 |
Action test |
The set action can be tested to see the working method in the practice. |
5.10.2. Create or Modify an Event
Wizard Mode
The wizard mode lists the most common conditions and actions, so the user does not have to look for LW3 nodes and properties.
Step 1.Click on the Edit button of the desired Event; the Event editor is displayed.
Step 2.The wizard mode is displayed by default. Select the desired Category first (e.g. Audio or Video).
Step 3.Select the desired Expression from the drop-down menu. If any other parameter is necessary to be set, it is going to be displayed.
Step 4.Press the Apply button to store the settings of the Condition.
Advanced Mode
The goal of this mode is the same as that of the wizard: set the properties and methods for conditions and actions. The difference is the number of the available and usable properties and methods of the LW3 protocol. Advanced mode allows almost all of it.
Step 1.Click on the Edit button of the desired Event; the Event editor is displayed.
Step 2.The wizard mode is the default, press the Advanced button. The LW3 protocol tree is displayed, showing the list of the properties in the drop-down menu. Navigate to the desired node.
Step 3.Select the desired Property from the menu. The manual of the property is displayed below to help select the necessary property and to set the value.
Step 4.Set the desired value and operator, then press the Apply button to store settings.
The Link Tool
The new interface allows creating more actions for the same condition. In that case, a condition can trigger more actions. To set such an Event, the Link tool has been introduced.
Step 1.Click on the Edit button of the desired Event; the Event editor is displayed.
Step 2.The wizard mode is displayed by default, press the Link button.
Step 3.All the saved Events are analyzed and the conditions are listed (it takes a few seconds to finish). The Show advanced expressions option allows showing the exact path and set the value of the given property.
Step 4.Select the desired Condition and press the Apply button to store the settings.
5.10.3. Special Tools and Accessories
The Name of the Event
The name of a port can be changed by typing the new name and clicking on the Set name button. The following characters are allowed when naming:
Letters (A-Z) and (a-z), numbers (0-9), special characters: hyphen ( - ), underscore ( _ ), and space ( ).
Enable or Disable an Event
The set Event can be enabled or disabled in the Event list, or directly in the Event editor window by setting a tick mark beside the name.
Testing the Condition
When the desired Condition is arranged, the setting can be tested. The Event list and the Event editor contains a small panel that shows whether the set condition is detected and if so, how many times. The Counter can be reset by a button in the Event editor. If the Condition is true, the detected mark turns green for two seconds and the Counter is increased.
Testing the Action
The method is the same as testing the Condition, but in this case, the Action can be triggered manually by pressing the Test button.
TIPS AND TRICKS:The Test button is also placed on the Action panel in the Event list. Thus, you can check the Actions without opening the Event editor.
Delay the Action
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. Therefore, the new Event manager contains the Delay panel, which allows that feature with the settings below:
▪No delay: when the Condition is detected, the Action is launched.
▪Simple delay: when the Condition is detected, the Action is launched after the set time interval.
▪Still true after: when the Condition is detected, the Action is launched after the set time interval only if the Condition still exists.
▪Continuously true: when the Condition is detected, the Action is launched after the set time interval only if the Condition has been existing continuously.
TIPS AND TRICKS:The Show advanced expressions option is a useful tool when you look for the path or value of a property, but just the expression is displayed. The option is available in the Event list window or when Link tool is used.
5.10.4. Clear One or More Event(s)
Clear an Event
Press the Clear button in the Event list or in the header section in the Event editor.
Clear all Events
When all the Events must be cleared, press the Load factory defaults button above the Event list. You will be prompted to confirm the process.
ATTENTION!Clicking on the Load factory defaults button means the configuration of the buttons are also deleted, because the conditions and the actions of the buttons are saved as events.
5.10.5. Export and Import Events
The feature allows saving all the Events. The backup file can be uploaded to the same device type.
Export all the Events
Step 1.Press the Export button above the Event list.
Step 2.The Save as dialog box will appear. Set the desired folder and file name, then press the Save button.
The generated file is a simple text file, which contains LW3 protocol commands. The file can be viewed by a simple text editor, e.g. Notepad.
ATTENTION!Editing the file is recommended only for expert users.
Import all the Events
Step 1.Press the Import button above the Event list.
Step 2.The Open dialog box will appear. Select the desired folder and file, then press the Open button.
5.10.6. Event Creating - Example
The following example shows you on a real-life situation how to set up an Event.
The Concept
The MMX6x2-HT220 matrix is connected to a projector by the HDMI out 1 port. The matrix is also connected to the projector by the RS-232 port, and can send commands via the serial line.
The task is to turn on the projector when signal is detected on the HDMI out 1 port.
RS-232 Settings
Make sure that the serial line is established between the matrix and the projector. Check that the RS-232 settings of the matrix are set exactly the same as required for the projector: baud rate, data bits, parity, stop bits. The matrix needs to be set to: Control protocol: LW3; and RS-232 mode: Control. See the relevant LDC settings in the RS-232 Tab section.
Setting the Event
You can create the Event in the Wizard mode in a few simple steps:
Step 1.Set the condition.
Select the required parameters to set the condition:
▪Category: Video;
▪Expression: Signal is detected on a port;
▪Port: O1.
Click on the Apply button to complete the procedure. When it is done, the condition appears on the upper side in textual and LW3 command format as well.
Step 2.Set the action.
If the condition is fulfilled, the following action needs to be launched: the receiver sends a command to the projector over the serial line:
▪Power on - the required command that is accepted by the projector: PWR0<CR><LF>
For this instance the command has to be closed with the <CR><LF> characters, so they need to be escaped. You can use the following format for escaping:
<command1><\x0d\x0a><command2><\x0d\x0a>...
...<commandn><\x0d\x0a>
In the current case the command is: PWR0\x0d\x0a
Select the required parameters to set the action:
▪Category: RS-232;
▪Expression: Send RS-232 message;
▪Port: P1;
▪Message: PWR0\x0d\x0a
Step 3.Enable the Event.
Select the E1 enabled option in the upper left corner to set the Event as launched.
INFO:If you do not find the required category/expression/etc that you need, choose the Advanced moderather than the Wizard mode, where the entire LW3 structure tree is available. For example, instead of signal detection, you can set a specified resolution or color range too as a condition.
5.11. Settings Menu
5.11.1. Status
General information is shown on this tab, such as device label, part number, serial number and hardware health, voltage and temperature values.
Status Tab
Network-related settings are available on the tab #network.
Network Tab
When dynamic IP address is used, the DHCP option is ticked; the IP settings of the matrix are shown in the first three lines. When static IP address is used, the DHCP option shall be unticked and the three lines below can be used to define the IP settings. The device is able to communicate via LW2 and LW3 protocols, the ports can be set in the displayed lines.
ATTENTION!Connecting to the matrix via Ethernet and using LW2 port no. (default is 10001), the device will accept LW2 protocol commands. Using LW3 port no. (default is 6107), the device will accept LW3 protocol commands.
5.11.3. Backup
Details about this function can be found in the Configuration Cloning (Backup Tab) section.
System tab
System log button #systemlog #log
Logged events can be collected and saved into a file, which is useful when troubleshooting or in other special cases to be analyzed. Data collecting may take a few minutes. You will be asked about generating a log before starting. When the collection is done, the Save as window appears; select the desired location and press the Save button.
Factory defaults button
Factory default values can be restored by pressing the button; you will be asked to confirm. The connection will be terminated and the device is rebooted. Factory default values are listed in the Factory Default Settings section.
Reboot button
The device can be restarted; the connection will be terminated.
5.12. Configuration Cloning (Backup Tab)
Backup Tab
The configuration cloning of Lightware LW3 devices is a simple method that eliminates the need to repeatedly configure certain devices to have identical (non-factory) settings. If the devices are installed in the same type of system multiple times, then it is enough to set up only one device to fit the user’s needs and then copy those settings to the others, thus saving time and resources. #backup #configurationcloning
5.12.1. Cloning Steps in a Nutshell
Installing multiple devices with the same customized configuration settings can be done in a few easy steps:
Step 1.Configure one device with all your desired settings with the LDC software.
Step 2.Backup the full configuration file to your computer.
Step 3.If needed, make some modifications to the configuration file using a text editor (e.g. Notepad). E.g. modifying the static IP address is needed when DHCP is not used.
Step 4.Connect to the other device that has to be configured and upload (restore) your configuration file.
Step 5.Done! You can have as many totally identical, customized devices as you like.
5.12.2. Save the Settings of the Device (Backup)
Step 1.Apply the desired settings in the transmitter (port parameters, crosspoint, etc.)
Step 2.Select the Settings / Backup tab from the menu.
Step 3.Write a short description in the text box on the left (optional).
Step 4.Press the Create a full backup button. You will be prompted to save the file to the computer. The default file name is the following:
|
BACKUP_<DEVICE TYPE>_SN<SERIAL NUMBER>.LW3 |
Step 5.Set the desired file name, select the folder and save the file.
TIPS AND TRICKS:Using the exact product type in the filename is recommended, since it makes the file usage more comfortable.
About the Backup File
The backup file is a simple text file, which contains LW3 protocol commands. The first line is the description, and the further lines are the commands that will be executed during the restore process. The file can be viewed (and/or edited) by a simple text editor, e.g. Notepad.
ATTENTION!Editing the command lines is only recommended for expert users.
See the entire list of saved data in the Content of the Backup File section.
5.12.3. Upload the Settings to a Device (Restore)
WARNING!Please note that the settings will be permanently overwritten with the restored parameters in the device. Withdrawal is not possible.
ATTENTION!The cloning is successful when the backup file is downloaded from the same type of source device as the destination device.
The Restoring Process
Step 1.Select the Settings / Backup tab from the menu.
Step 2.Click on the Choose file button on the right panel and browse the desired file.
Step 3.The file is checked and the result will be displayed in the textbox below. If the file is correct, the settings can be restored.
Step 4.Choose the IP settings that you want to use after backup. You can apply settings from the backup file, keep actual settings, set it manually in a dialog box or apply DHCP.
Step 5.Press the Start restore process button and click on the Yes button when asked.
Step 6.Reboot the device to apply the network settings after finishing.
5.12.4. Create and Restore Backups from the Device Memory
MMX6x2-HT series matrix is able to store backups in its own memory and can be recalled from there, so the user does not need to save backup files to the local computer. Four slots are available for this purpose.
You can save the configuration to the desired slot:
▪without protection: it can be easily applied/deleted, or
▪with protection: it can be protected by a password to apply or delete the configuration.
|
Loading the selected configuration |
|
Deleting the selected configuration |
|
Saving the current configuration to the selected slot without protection |
|
Loading a configuration from a file to the selected slot |
|
Saving the current configuration to the selected slot with a password |
|
Saving the selected configuration as a file |
WARNING!Loading factory default settings will erase all presets that have been saved in the device memory!
LDC - Advanced view window
|
1 |
LW3 protocol help |
Pushing the button results in a help window opening, which describes the most important information about LW3 protocol commands in HTML format. |
|
|
2 |
Edit mode |
The default appearance is the read-only mode. If you want to modify the values or parameters, tick the option. You will be prompted to confirm your selection. |
|
|
3 |
Warning mode |
If this option is checked in, a warning window pops up when you enable Edit mode. |
|
|
4 |
Terminal window |
Commands and responses with time and date are listed in this window. Sent command starts with ‘>’ character, received response starts with ‘<’ character. The color of each item depends on the type of the command and response. The content of the window can be emptied by the Clear button. If the Autoscroll option is ticked, the list is scrolled automatically when a new line is added. |
|
|
5 |
Command line |
Type the desired command and execute it by the Send button. Clear all current commands and responses in the Terminal window with the Clear button. The commands typed in this line are not escaped automatically. |
|
|
6 |
Protocol tree |
LW3 protocol tree; select an item to see its content. |
|
|
7 |
Node list |
Correspondent parameters and nodes are shown that are connected to the selected item in the protocol tree. The commands typed into these fields are escaped automatically. |
|
|
Manual button: |
Manual (short description) of the node can be called and displayed in the terminal window. |
||
|
Set button: |
Saves the value/parameter typed in the textbox. |
||
|
Call button: |
Calls the method, e.g. reloads factory default settings. |
||
#advancedview #terminal
Lightware MMX6x2-HT family can be controlled with external devices that can communicate according to the extender protocol. The supported LW2 commands are described in this chapter.
6.1. LW2 Protocol Description
The protocol description hereinafter stands for Lightware protocol. The commands can be sent to the device in RAW format via the TCP/IP port no. 10001.
The receiver accepts commands surrounded by curly brackets - { } - and responds data surrounded by round brackets - ( ) - only if a command was successfully executed. All input commands are converted to uppercase, but respond commands can contain upper and lower case letters as well.
Legend for Control Commands
|
Format |
Explanation |
|
<in> |
Input number in 1- or 2-digit ASCII format (01, 5, 07, 16, etc.) |
|
<out> |
Output number in 1- or 2-digit ASCII format |
|
<in/out> |
input or output port number in 1- or 2-digit ASCII format * |
|
<in2> |
Input number in 2-digit ASCII format (01, 02, 10, 12 etc.) |
|
<out2> |
Output number in 2-digit ASCII format (01, 02, 10, 12 etc.) |
|
<in2/out2> |
input or output number in 2-digit ASCII format* |
|
<loc> |
Location number in 1-, 2- or 3-digit ASCII format |
|
<id> |
id number in 1- or 2-digit ASCII format |
|
<id2> |
id number in 2-digit ASCII format |
|
CrLf |
Carriage return, Line feed (0x0D, 0x0A) |
|
· |
Space character (0x20) |
|
→ |
Each command issued by the controller |
|
← |
Each response received from the router |
* The command has the same arguments on the input ports and the output port, as well.
6.2. Instructions for the Terminal Application Usage
Terminal Application
The LW2 protocol commands can be applied to the receiver using a terminal application. You need to install one of them on your control device, for example Putty or CLI. #terminal
Establishing Connection
Follow the steps to establish connection to the receiver:
Step 1.Connect the receiver to a LAN over Ethernet.
Step 2.Open the terminal application (e.g. Putty).
Step 3.Add the IP address of the device (default: 192.168.0.100) and the port number (10001).
Step 4.Select the Raw connection type, and open the connection.
Once the terminal window is opened, you can enter the LW2 protocol commands, which are listed in the following sections.
LW2 protocol command communication in a terminal window
6.3. General LW2 Commands
The device responds its name. #producttype
Command and Response
»{I}
«(<PRODUCT_TYPE>)CrLf
Example
»{i}
«(I:MMX6x2-HT220)
Explanation: The connected device is an MMX6x2-HT220.
Legend: <PRODUCT_TYPE> shows type.
The device responds its 8-digit serial number. #serialnumber
Command and Response
»{s}
«(SN:<SERIAL_N>)CrLf
Example
»{s}
«(SN:7A000941)
6.3.3. Querying Control Protocol
The device can be controlled with different control protocols. This command queries the active protocol of the currently used control interface.
Command and Response
»{P_?}
«(CURRENT•PROTOCOL•=•#<protocol>)CrLf
Example
»{p_?}
«(CURRENT PROTOCOL = #1)
Explanation: The device communicates with LW2 protocol.
6.3.4. Viewing Firmware Version of the CPU
View the CPU firmware revision. #firmwareversion
Command and Response
»{f}
«(FW:<FW_VER><s>)CrLf
Example
»{f}
«(FW:1.1.3b1 r9)
Legend: <FW_VER> is the firmware version. It is followed by <s> string, which may indicate special versions. <s>=r indicates standard version.
INFO:The version number of the firmware package and the CPU firmware can be different. The firmware package contains several different firmware components, the CPU firmware is a part of those.
Simple test to see if the connection is established successfully.
Command and Response
»{PING}
«(PONG!)CrLf
Example
»{ping}
«(PONG!)
Returns the date when the microcontroller firmware was compiled.
Command and Response
»{CT}
«(Compiled: <DATE&TIME>)CrLf
Example
»{ct}
«(Compiled: Oct 10 2017 16:33:59)
6.3.7. Viewing Installed Board(s)
Shows the hardware name and revision of the installed boards.
Command and Response
»{is}
«(SL#•0•<MB_DESC>)CrLf
«(SL•END)CrLf
Example
»{is}
«(SL# 0 MMX6x2-HT220 V12_AAA0)
«(SL END)
Explanation: The device reports its motherboard (slot 0).
6.3.8. Viewing Firmware for all Controllers’
Shows the firmware versions of all installed controllers. #firmwareversion
Command and Response
»{FC}
«(CF•<DESC>)CrLf
«(CF•<DESC>)CrLf
...
«(CF•END)CrLf
Example
»{fc}
«(CF MMX6x2-HT220 1.1.3b1 r9)
...
«(CF END)
Explanation: The device has one control panel.
6.3.9. Restarting the Matrix Router
The device can be restarted without unplugging power. #reboot #restart
Command
»{RST}
Example
»{RST}
Explanation: The device reboots; no response is sent in this case.
6.3.10. Querying Health Status
Internal voltages and measured temperature values are shown.
Command and Response
»{ST}
«(ST•<DESC>)CrLf
Example
»{st}
«(ST CPU 1.03V 1.03V 1.03V 1.81V 1.34V 1.34V 3.31V 5.07V 48.00V 35.40C 35.42C 0.00C 31.62C 35.38C)
6.3.11. Restoring Factory Default Settings
Settings can be reset to factory default values as follows: #factory
Command and Response
»{FACTORY=ALL}
«(FACTORY ALL...)CrLf
Example
»{factory=all}
«(FACTORY ALL...)
Explanation: All settings and parameters are reset to factory default, see the table in the Factory Default Settings section.
6.3.12. Listing All Commands
A list of all available LW2 commands and their descriptions can be queried.
Command and Response
»{LCMD}
«(LCMD#•I:•Device•name)CrLf
«(LCMD#•P_?:•Current•protocol)CrLf
...
«(LCMD•END)CrLf
Example
»{lcmd}
«(LCMD# I: Device name)CrLf
«(LCMD# P_?: Current protocol)CrLf
...
«(LCMD END)CrLf
6.4. Port and Crosspoint Settings
6.4.1. Switching One Input to One Output
Switch input <in> to output <out>. #crosspoint
Command and Response
»{<in>@<out>}
«(O<out2>•I<in2>)CrLf
Example
»{2@1}
«(O01 I02)
Explanation: Input 1 is switched to output 2.
ATTENTION!The response of this command does not show if the output is muted. To check the mute status, a separate query has to be used, like {VC}. See the Viewing Connection State on the Output section. To achieve multiple switches executed together, see the Batch Switching Outputs section.
6.4.2. Switching One Input to All Outputs
Switch input <in> to all outputs.
Command and Response
»{<in>@O}
«(I<in2>•ALL)CrLf
Example
»{2@O}
«(I02 ALL)
6.4.3. Disconnecting an Input
An input can be disconnected from all outputs.
Command and Response
»{0@<out>}
«(0<out2>•I00)CrLf
Example
»{0@3}
«(O03 I00)CrLf
Explanation: When using 0 (zero) value as an input, the input will be disconnected and no signal will appear on the output.
6.4.4. Muting Specified Output
Mute output <out>. The output signal is turned off. #mute
Command and Response
»{#<out>}
«(1MT<out2>)CrLf
Example
»{#01}
«(1MT01)
Explanation: O1 port is muted.
ATTENTION!Muting does not change the state of the crosspoint, but disables the output itself. This way the last connection can be easily restored with an unmute command. Switching a muted output does not unmute the output.
6.4.5. Unmuting Specified Output
Unmute output <out>. #unmute
Command and Response
»{+<out>}
«(0MT<out2>)CrLf
Example
»{+01}
«(0MT01)
Explanation: O1 port is unmuted.
INFO:Unmuting an output makes the previous connection active, as the state of the crosspoint has not been changed with the muting command, only the output was disabled.
Lock output <out>. Output’s state cannot be changed until unlocking. #lock
Command and Response
»{#><out>}
«(1LO<out2>)CrLf
Example
»{#>01}
«(1LO01)
Explanation: O1 port is locked.
Unlock output <out>. The connection on output can be changed. #unlock
Command and Response
»{+<<out>}
«(0LO<out2>)CrLf
Example
»{+<01}
«(0LO01)
Explanation: Output 1 is unlocked.
INFO:The device issues the response above regardless of the previous state of the output (whether it was locked or unlocked).
6.4.8. Viewing Connection State on the Output
Viewing the output’s connection results in different response length, because it depends on the device. The response below refers to an MMX6x2-HT220.
Command and Response
»{VC}
«(ALL•<O1>•<O2>•<O3>•<O4>)CrLf
Example
»{vc}
«(ALL 03 04 03 04)
Legend: All <Ox> indexes show the corresponding output’s connection state. If value <O1> equals 03, it means that output 1 is connected to input 3. All <Ox> indexes are two digit ASCII characters (01, 02, 04, etc.)
State letters
|
Letter |
State |
Example |
|
L |
Output is locked |
L01 |
|
M |
Output is muted |
M01 |
|
U |
Output is locked and muted |
U01 |
Explanation: I3 is switched to O1 and O3. I4 is switched to O2 and O4.
INFO:As the output ports are mirrored: O1 and O3 transmit the same input, such as O2 and O4.
6.4.9. Viewing Crosspoint Size
Shows the physical crosspoint size.
Command and Response
»{getsize}
«(SIZE=<size>)CrLf
Example
»{getsize}
«(SIZE=6x4)
Explanation: The device reports that it has a video crosspoint with 6 inputs and 4 outputs.
6.4.10. Batch Switching Outputs
The device is capable of switching multiple outputs exactly at the same time. To do this, the normal switch commands have to be used. If the switch commands arrive at the device with less than 10 milliseconds delay, the commands are collected and the output connections are changed together.
Required circumstances:
▪Switch commands have this format: {<in>@<out>}{<in>@<out>}
▪The delay between two ‘}’ characters must be below 10 milliseconds
▪No other command or junk character is allowed between switch commands
▪Affected outputs must not be locked
If any of the above circumstances fail, then the commands will be processed separately and the output connections will change one by one.
ATTENTION!The delay timeout applies for the receiving time of characters. Please note that if LAN connection is used, then the network may cause additional delays. This could resultin batch switching failure. The example below shows a command that resulted in batch switching:
One By One Commands
»{02@01 V}
«(O01 I02 V)CrLf
»{01@01 A}
«(O01 I01 A)CrLf
Batch Commands
»{02@01 V}{01@01 A}
«(O01 I02 V)CrLf
«(O01 I01 A)CrLf
6.4.11. Changing the Autoselect Mode
The autoselect mode of the video outputs can be changed.
Command and Response
»{AS_V<out>=<state>;<mode>}
«(AS_V<out>=<state>;<mode>)CrLf
Example
»{as_v1=E;P}
«(AS_V1=E;P)
Legend: The output numbers are listed in the Input and Output Port Numbering section.
|
Letter |
State |
|
F |
First detect mode |
|
P |
Priority detect mode |
|
L |
Las |
Explanation: The Autoselect mode of video output1 (and output 3) is enabled and set to Priority mode.
INFO:The Autoselect mode can be queried by typing the “as_v<out>=?” command.
6.4.12. Changing the Video Input Priorities
The settings of video input priority can be changed as follows.
Command and Response
»{PRIO_V<out>=<in1_prio>;<in2_prio>;...;<inn_prio>}
«(PRIO_V<out>=<in1_prio>;<in2_prio>;...;<inn_prio>)CrLf
Example
»{prio_v1=1;0;2;3;4;5}
«(PRIO_V1=1;0;2;3;4;5)
Legend:
|
Identifier |
Parameter description |
|
<out> |
The output port number: V1/V3 and V2/V4. |
|
<in1_prio>...<inn_prio> |
Input ports’ priority number. See more details about port numbering in the Input and Output Port Numbering section. |
Explanation: Input 2 has the highest priority (0), Input 1 has the second highest (1). Input 6 has the lowest priority (5).
ATTENTION!Always set all the ports’ priority when changing, otherwise the change will not be executed and the response will be the current setting (like querying the priority setting).
6.5. Network Configuration
6.5.1. Querying the Current IP Status
IP status can be queried as follows: #network
Command and Response
»{IP_STAT=?}
«(IP_STAT=<type>;<ip_address>;<subnet_mask>;<gateway_addr>)CrLf
Example
»{ip_stat=?}
«(IP_STAT=0;192.168.0.95;255.255.255.0;192.168.0.1)
Legend:
|
Identifier |
Parameter description |
|
<type> |
0= static |
|
1= DHCP |
|
|
<ip_addr> |
IP address (four decimal octets separated by dots). |
|
<subnet_mask> |
Subnet mask (four decimal octets separated by dots). |
|
<gateway_addr> |
Gateway address (four decimal octets separated by dots). |
Explanation: The device has a static (fix) IP address: 192.168.0.95; the subnet mask is 255.255.255.0, the gateway address is 192.168.0.1.
6.5.2. Querying the IP Address
IP address can be queried as follows:
Command and Response
»{IP_ADDRESS=?}
«(IP_ADDRESS=<type>;<ip_address>)CrLf
Example
»{ip_address=?}
«(IP_ADDRESS=0;192.168.0.110)
Legend:
|
Identifier |
Parameter description |
|
<type> |
0= static |
|
1= DHCP |
|
|
<ip_addr> |
IP address (four decimal octets separated by dots). |
INFO:The response contains the fix IP address that is stored in the device even if DHCP is enabled; in this case, this IP address is not valid.
IP address can be set as follows: #ipaddress
Command and Response
»{IP_ADDRESS=<type>;<ip_address>}
«(IP_ADDRESS=<type>;<ip_address>)CrLf
Example
»{ip_address=0;192.168.0.110}
«(IP_ADDRESS=0;192.168.0.110)
Legend:
|
Identifier |
Parameter description |
|
<type> |
0= static |
|
1= DHCP |
6.5.4. Querying the Subnet Mask
Subnet mask can be queried as follows.
Command and Response
»{IP_NETMASK=?}
«(IP_NETMASK=<subnet_mask>)CrLf
Example
»{ip_netmask=?}
«(IP_NETMASK=255.255.255.0)
Legend:
|
Identifier |
Parameter description |
|
<subnet_mask> |
Four decimal octets separated by dots. |
INFO:The response contains the fix IP subnet mask value that is stored in the device even if DHCP is enabled; in this case, this IP subnet mask is not valid.
6.5.5. Setting the Subnet Mask
Subnet mask can be set as follows.
Command and Response
»{IP_NETMASK=<subnet_mask>}
«(IP_NETMASK=<subnet_mask>)CrLf
Example
»{ip_netmask=255.255.255.0}
«(IP_NETMASK=255.255.255.0)
Legend:
|
Identifier |
Parameter description |
|
<subnet_mask> |
Four decimal octets separated by dots. |
6.5.6. Querying the Gateway Address
Gateway address can be set as follows.
Command and Response
»{IP_GATEWAY=?}
«(IP_GATEWAY=<gateway_addr>)CrLf
Example
»{ip_gateway=?}
«(IP_GATEWAY=192.168.0.50)
Legend:
|
Identifier |
Parameter description |
|
<gateway_addr> |
Four decimal octets separated by dots. |
INFO:The response contains the static IP gateway address that is stored in the device even if DHCP is enabled. In that case, the latest valid gateway address (for static IP) is stored.
6.5.7. Setting the Gateway Address
Gateway address can be set as follows.
Command and Response
»{IP_GATEWAY=<gateway_addr>}
«(IP_GATEWAY=<getaway_addr>)CrLf
Example
»{ip_gateway=192.168.0.50}
«(IP_GATEWAY=192.168.0.50)
Legend:
|
Identifier |
Parameter description |
|
<gatway_addr> |
Four decimal octets separated by dots. |
6.5.8. Applying the Network Settings
The network settings are applied and the network interface is restarted.
Command and response
»{IP_APPLY}
«(IP_APPLY)CrLf
Example
»{ip_apply}
«(ip_apply)
6.5.9. Querying the TCP/IP Port
TCP/IP port setting can be queried as follows.
Command and Response
»{LW2_PORT=?}
«(LW2_PORT=<port_nr>)CrLf
Example
»{lw2_port=?}
«(LW2_PORT=10001)
Explanation: The port number for LW2 protocol is set to 10001 (default value).
Command and Response
»{LW3_PORT=?}
«(LW3_PORT=<port_nr>)CrLf
Example
»{lw3_port=?}
«(LW3_PORT=6107)
Explanation: The port number for LW3 protocol is set to 6107 (default value).
6.5.10. Setting the TCP/IP Port
TCP/IP port setting can be set as follows.
Command and Response
»{LW2_PORT=<port_nr>}
«(LW2_PORT=<port_nr>)CrLf
Example
»{lw2_port=10001}
«(LW2_PORT=10001)
Explanation: The port number for LW2 protocol is set to 10001 (default value).
Command and Response
»{LW3_PORT=<port_nr>}
«(LW3_PORT=<port_nr>)CrLf
Example
»{lw3_port=6107}
«(LW3_PORT=6107)
Explanation: The port number for LW3 protocol is set to 6107 (default value).
6.5.11. Querying the Status of Ethernet Ports
The Ethernet can be enabled (1) or disabled (0) on each port individually.
Command and Response
»{ETH_ENABLE=?}
«(ETH_ENABLE=<cpu>;<ctrl_tps_link>;<ctrl_lan>;<tps_eth>;<tpsin1_eth>;<tpsin2_eth>;
<tpsout1_eth>;<tpsout2_eth>)CrLf
Example
»{eth_enable=?}
«(ETH_ENABLE=1;1;1;1;1;1;1;1)
6.5.12. Setting the Status of Ethernet Ports
The Ethernet can be enabled (1) or disabled (0) on each port as follows:
Command and Response
»{ETH_ENABLE=<cpu>;<ctrl_tps_link>;<ctrl_lan>;<tps_eth>;<tpsin1_eth>;<tpsin2_eth>;
<tpsout1_eth>;<tpsout2_eth>}
«(ETH_ENABLE=<cpu>;<ctrl_tps_link>;<ctrl_lan>;<tps_eth>;<tpsin1_eth>;<tpsin2_eth>;
<tpsout1_eth>;<tpsout2_eth>)CrLf
Example
»{eth_enable=1;1;1;1;1;1;0;0}
«(ETH_ENABLE=1;1;1;1;1;1;0;0)
ATTENTION!All ports’ status must be defined in the command.
6.6. Serial Port Configuration
6.6.1. Setting the Control Protocol
See more information about the RS-232 modes in the Serial Interface section. #rs232 #serial
Command and Response
»{RS232=<mode>}
«(RS232=<mode>)CrLf
Parameters
|
Parameter |
Parameter description |
Value |
Value description |
|
<mode> |
The serial port working mode |
PASS |
Pass-through mode |
|
CONTROL |
Control mode |
||
|
CI |
Command Injection mode |
The current setting can be queried by the {RS232=?} command.
Example
»{RS232=CONTROL}
«(RS232=CONTROL)
6.6.2. Serial Port Format Setting (Local port)
This command sets the format of the local RS-232 port (Phoenix).
Command and Response
»{RS232_LOCAL_FORMAT=<baud_rate>;<data_bit>;<parity>;<stop_bit>}
«(RS232_LOCAL_FORMAT=<baud_rate>;<data_bit>;<parity>;<stop_bit>)CrLf
Parameters
|
Parameter |
Parameter description |
Value |
Value description |
|
<baud_rate> |
Baud rate setting (optional) |
4800; 7200; 9600; 14400; 19200; 38400; 57600; 115200 |
|
|
<data_bit> |
Databit setting (optional) |
8; 9 |
|
|
<parity> |
Parity setting (optional) |
N; E; O |
|
|
<stop_bit> |
Stop bit setting (optional) |
1; 1.5; 2 |
The current setting can be queried by the {RS232_LOCAL_FORMAT=?} command. Any parameter can be skipped by using 'X' as a value, see the example.
Example
»{RS232_LOCAL_FORMAT=57600;X;X;1}
«(RS232_LOCAL_FORMAT=57600;8;N;1)
The databit and parity settings have not been changed.
6.6.3. Serial Port Format Setting (Link port)
DIFFERENCE:This command is available for MMX4x2-HT200 model only.
This command sets the format of the link RS-232 port (TPS port).
Command and Response
»{RS232_LINK_FORMAT=<baud_rate>;<data_bit>;<parity>;<stop_bit>}
«(RS232_LINK_FORMAT=<baud_rate>;<data_bit>;<parity>;<stop_bit>)CrLf
Parameters
See the previous section.
Example
»{RS232_LINK_FORMAT=38400;X;X;1}
«(RS232_LINK_FORMAT=38400;8;N;1)
The databit and parity settings have not been changed.
6.6.4. Serial Port Protocol Setting (Local port)
Command and Response
»{RS232_LOCAL_PROT=<protocol>}
«(RS232_LOCAL_PROT=<protocol>)CrLf
Parameters
|
Parameter |
Parameter description |
Value |
Value description |
|
<protocol> |
The applied protocol in the communication |
LW2 |
Lightware 2 Protocol is active |
|
LW3 |
Lightware 3 Protocol is active |
The current setting can be queried by the {RS232_LOCAL_PROT=?} command. #protocol
Example
»{RS232_LOCAL_PROT=LW2}
«(RS232_LOCAL_PROT=LW2)
6.6.5. Serial Port Protocol Setting (Link port)
DIFFERENCE:This command is available for MMX4x2-HT200 model only.
This command sets the communication protocol of the link RS-232 port (TPS port).
Command and Response
»{RS232_LINK_PROT=<protocol>}
«(RS232_LINK_PROT=<protocol>)CrLf
Parameters
See the previous section.
Example
»{RS232_LINK_PROT=LW2}
«(RS232_LINK_PROT=LW2)
6.7. LW2 Commands – Quick Summary
The device can be controlled through Lightware 3 (LW3) protocol commands to ensure the compatibility with other Lightware products. The supported LW3 commands are described in this chapter.
7.1. Overview
The Lightware Protocol #3 (LW3) is implemented in almost all new Lightware devices (matrix switchers, signal extenders and distribution amplifiers) since 2012. The protocol is ASCII-based and all commands are terminated with a carriage return (Cr, ‘\r’) and line feed (Lf, ‘\n’) pair. It is organized as a tree structure that provides outstanding flexibility and user-friendly handling with ‘nodes’, ‘properties’ and ‘methods’. The Advanced View of the Lightware Device Controller software is the perfect tool for browsing and learning how the LW3 protocol can be used in practice.
7.2. Instructions for the Terminal Application Usage
Terminal Application
The LW3 protocol commands can be applied to the receiver using a terminal application. You need to install one of them to your control device, for example Putty or CLI. #terminal
Establishing Connection
Follow the steps for establishing connection to the receiver:
Step 1.Connect the receiver to a LAN over Ethernet.
Step 2.Open the terminal application (e.g. Putty).
Step 3.Add the IP address of the device (default: 192.168.0.100) and the port number (6107).
Step 4.Select the Raw connection type, and open the connection.
Once the terminal window is opened, you can enter the LW3 protocol commands which are listed in the following sections.
LW3 protocol command communication in a terminal window
7.3. Protocol Rules
7.3.1. LW3 Tree Structure and Command Structure (Examples)
7.3.2. General Rules
▪All names and parameters are case-sensitive.
▪The nodes are separated by a slash (‘/’) character.
▪The node names are comprised of the elements of the English alphabet and numbers.
▪Use the TCP port no. 6107 when using LW3 protocol over Ethernet.
▪Node paths describe the exact location of the node, listing each parent node up to the root.
▪The length of a line (command/response, command type / prefix, path, method/property and parameters together) can be max. 800 bytes.
7.3.3. Command Types
GET command
The GET command can be used to get the child nodes, properties and methods of a specific node. It can also be used to get the value of a property. Use the dot character (.) when addressing a property:
»GET /.SerialNumber
«pr /.SerialNumber=87654321
GETALL command
The GETALL command can be used to get all child nodes, properties and methods of a node with one command.
»GETALL /EDID
«n- /EDID/F
«n- /EDID/D
«n- /EDID/U
«n- /EDID/E
«pr /EDID.EdidStatus=F47:E1;F47:E2;F23:E3;F47:E4;F17:E5;F47:E6
«m- /EDID:copy
«m- /EDID:delete
«m- /EDID:reset
«m- /EDID:switch
«m- /EDID:switchAll
SET command
The SET command can be used to modify the value of a property. Use the dot character (.) when addressing the property:
»SET /MEDIA/VIDEO/O1.HdcpModeSetting=1
«pw /MEDIA/VIDEO/O1.HdcpModeSetting=1
CALL command
A method can be invoked by the CALL command. Use the colon character (:) when addressing the method:
»CALL /MEDIA/VIDEO/XP:switch(I1:O1)
«mO /MEDIA/VIDEO/XP:switch
MAN command
The manual is a human readable text that describes the syntax and provides a hint for how to use the primitives. For every node, property and method in the tree there is a manual; type the MAN command to get the manual:
»MAN /MEDIA/VIDEO/O1.Pwr5vMode
«pm /MEDIA/VIDEO/O1.Pwr5vMode ["0" | "1" | "2"] 0 - Auto, 1 - Always On, 2 - Always Off]
7.3.4. Prefix Summary
DEFINITION:The prefix is a 2-character long code that describes the type of the response.
The following prefixes are defined in the LW3 protocol:
|
Prefix |
Description |
|
n- |
a node |
|
nE |
an error for a node |
|
nm |
a manual for a node |
|
ns |
a child node of a node |
|
pr |
a read-only property |
|
pw |
read-write property |
|
pE |
an error for the property |
|
pm |
a manual for the property |
|
m- |
a method |
|
mO |
a response after a successful method execution |
|
mF |
a response after a failed method execution |
|
mE |
an error for a method |
|
mm |
a manual for a method |
7.3.5. Error Messages
There are several error messages defined in the LW3 protocol, all of them have a unique error number.
»CALL /MEDIA/VIDEO/XP:switch(IA:O1)
«mE /MEDIA/VIDEO/XP:switch %E004:Invalid value
DEFINITION:An escape sequence is a sequence of characters that does not represent itself when used inside a character or string literal, but is translated into another character or a sequence of characters.
Property values and method parameters can contain characters that are used as control characters in the protocol. They must be escaped. The escape character is the backslash (‘\’) and escaping means injecting a backslash before the given character (like in C language).
Control characters are the following: \ { } # % ( ) \r \n \t
A typical usage is when a message is sent, and it contains such a character that must be escaped.
Example
The original message: CALL /MEDIA/UART/P1:sendMessage(Set(01))
The escaped message: CALL /MEDIA/UART/P1:sendMessage(Set\(01\))
The above case is a typical example: the Lightware device is directed to send out a message over one of its ports. The round brackets in the message are escaped.
7.3.7. Signature
DEFINITION:The signature is a four-digit-long hexadecimal value that can be optionally placed before every command to keep a command and the corresponding responses together as a group.
Each line is terminated with carriage return (Cr, ‘\r’) and line feed (Lf, ‘\n’) characters. In several cases the number of the lines in the response cannot be determined in advance, e.g. the client intends to receive the whole response and also wants to be sure that the received lines belong together and to the same command. In these cases, a special feature, the ‘signature’ can be used. The response to that particular command will also be preceded by the signature, and the corresponding lines will be between brackets:
»1700#GET /EDID.*
«{1700
«pr /EDID.EdidStatus=F47:E1;F47:E2;F23:E3;F47:E4;F17:E5;F47:E6
«m- /EDID:copy
«m- /EDID:delete
«m- /EDID:reset
«m- /EDID:switch
«m- /EDID:switchAll
«}
INFO:The lines of the signature are also Cr and Lf terminated.
7.3.8. Subscription
DEFINITION:Subscription to a node means that the user will get a notification if a property of the node changes.
A user can subscribe to any node. These notifications are asynchronous messages and are useful to keep the client application up to date, without having to periodically poll the node to detect a changed property. When the user does not want to be informed about the changes anymore, he can simply unsubscribe from the node.
ATTENTION!The subscriptions are handled separately for connections. Hence, if the connection is terminated, all registered subscriptions are deleted. After reopening a connection all subscribe commands have to be sent in order to get the notifications of the changes on that connection.
Subscribe to a Node
»OPEN /MEDIA/VIDEO
«o- /MEDIA/VIDEO
Get the Active Subscriptions
»OPEN
«o- /MEDIA/VIDEO
«o- /EDID
«o- /DISCOVERY
Subscribe to Multiple Nodes
»OPEN /MEDIA/VIDEO/*
«o- /MEDIA/VIDEO/*
Unsubscribe from a Node
»CLOSE /MEDIA/VIDEO
«c- /MEDIA/VIDEO
Unsubscribe from Multiple Nodes
»CLOSE /MEDIA/VIDEO/*
«c- /MEDIA/VIDEO/*
7.3.9. Notifications about the Changes of the Properties
When the value of a property is changed and the user is subscribed to the node that the property belongs to, an asynchronous notification is generated. This is notification is called the ‘change message’. The format of such a message is very similar to the response for the GET command:
«CHG /EDID.EdidStatus=F48:E1
A Short Example of How to Use the Subscription
There are two independent users controlling the device through two independent connections (Connection #1 and Connection #2). The events in the rows occur after each other.
|
»OPEN /MEDIA/VIDEO/I1 «o- /MEDIA/VIDEO/I1 »GET /MEDIA/VIDEO/I1.HdcpEnable «pm /MEDIA/VIDEO/I1.HdcpEnable=false |
connection #1 |
|
»GET /MEDIA/VIDEO/I1.HdcpEnable «pm /MEDIA/VIDEO/I1/HdcpEnable=false »SET /MEDIA/VIDEO/I1.HdcpEnable=true «pw /MEDIA/VIDEO/I1/HdcpEnable=true |
connection #2 |
|
«CHG /MEDIA/VIDEO/I1/HdcpEnable=true |
connection #1 |
Explanation: The first user (Connection #1) set a subscription to a node. Later the other user (Connection #2) made a change, and thanks to the subscription, the first user got a notification about the change.
Legend for the Control Commands
|
Format |
Description |
|
<in> |
Input port number |
|
<out> |
Output port number |
|
<port> |
Input or output port number |
|
<parameter> |
Specific property that is defined and described in the command. |
|
<expression> |
Batched parameters: the underline means that more expressions or parameters can be placed by using a semicolon, e.g. I2;I4;I5 or F27:E1;F47:E2 |
|
» |
Sent command |
|
« |
Received response |
|
• |
Space character |
|
| |
Separator line ("or" character) |
7.4. System Commands
7.4.1. Querying the Product Name
ATTENTION!The name of the product is a read-only parameter and cannot be modified.
Command and Response
»GET•/.ProductName
«pr•/.ProductName=<product_name>
Example
»GET /.ProductName
«pr /.ProductName=MMX6x2-HT220
7.4.2. Setting the Device Label
ATTENTION!The device label can be changed to a custom text, which is displayed in many windows of the LDC. This writable parameter is not the same as the ProductName parameter. The default format of the device label is the following: LW_<product_name>_<serial_no>.
The Device Label can be 39 characters long and ASCII characters are allowed. Longer names are truncated. #label #devicelabel
Command and Response
»SET•/MANAGEMENT/UID/DeviceLabel=<custom_name>
«pw•/MANAGEMENT/UID/DeviceLabel=<custom_name>
Example
»SET /MANAGEMENT/UID.DeviceLabel=MMX_Control_room
«pw /MANAGEMENT/UID.DeviceLabel=MMX_Control_room
7.4.3. Querying the Serial Number
Command and Response #serialnumber
»GET•/.SerialNumber
«pr•/.SerialNumber=<serial_nr>
Example
»GET /.SerialNumber
«pr /.SerialNumber=87654321
7.4.4. Setting the Background Light of the LCD Screen
Command and Response
»SET•/MANAGEMENT/UI.LcdMenuBackLightMode=<parameter>
«pw•/MANAGEMENT/UI.LcdMenuBackLightMode=<parameter>
Example
»SET /MANAGEMENT/UI.LcdMenuBackLightMode=0
«pw /MANAGEMENT/UI.LcdMenuBackLightMode=0
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<parameter> |
LCD screen background light mode |
0 |
Off |
|
1 |
On |
7.4.5. Setting the Displayed Text on the LCD Screen
Two-line long message can be displayed on the LCD screen.
Command and Response
»CALL•/MANAGEMENT/UI:LcdMenuMessage(<time>; <1stline_text>;<2ndline_text>)
«mO•/MANAGEMENT/UI:LcdMenuMessage
Example
»CALL /MANAGEMENT/UI:LcdMenuMessage(100;first line; second line)
«mO /MANAGEMENT/UI:LcdMenuMessage
Parameters
|
Identifier |
Parameter description |
Explanation |
|
<time> |
Time |
The displayed text shows a definite time (100 means 1 second.) |
|
<1stline_text> <2ndline_text> |
Custom text |
The displayed text can be 19 characters long and ASCII characters are allowed. Longer names are truncated. |
Calling the method results in the blinking of the front panel status LEDs for 10 seconds. This feature can be used to help to identify the device itself in the rack shelf.
Command and Response
»CALL•/MANAGEMENT/UI:identifyMe()
«mO•/MANAGEMENT/UI:identifyMe
Example
»CALL /MANAGEMENT/UI:identifyMe()
«mO /MANAGEMENT/UI:identifyMe
7.4.7. Resetting the Matrix
The matrix can be restarted – the current connections (LAN, RS-232) will be terminated. #reboot #restart
Command and Response
»CALL•/SYS:Reset()
«mO•/SYS:Reset=
Example
»CALL /SYS:reset()
«mO /SYS:reset=
7.4.8. Restoring the Factory Default Settings
Command and Response
»CALL•/SYS:factoryDefaults()
«mO•/SYS:factoryDefaults=
Example
»CALL /SYS:factoryDefaults()
«mO /SYS:factoryDefaults=
Explanation
The device is restarted, current connections are terminated, and the default settings are restored. See the complete list in the Factory Default Settings section. #factory
7.5. Video Port and Crosspoint Settings
7.5.1. Querying the Status of Source Port
Command and Response #portstatus #crosspoint #switch
»GET•/MEDIA/VIDEO/XP.SourcePortStatus
«pr•/MEDIA/VIDEO/XP.SourcePortStatus=<I1_state>;<I2_state>;...;<I6_state>
The response contains 5 ASCII characters for each port. The first character indicates the mute/lock state, the next four characters represent a 2-byte HEX code showing the current state of the input ports.
Example
»GET /MEDIA/VIDEO/XP.SourcePortStatus
«pr /MEDIA/VIDEO/XP.SourcePortStatus=T00AF;T00AA;T00BF;T00EF;T000A;M00FF
Legend
Example and Explanation (for input 1, T00AF)
|
Byte 1 |
Byte 2 |
|||||||
|
Character 2 |
Character 3 |
Character 4 |
Character 5 |
|||||
|
BIT 7-6 |
BIT 5-4 |
BIT 3-2 |
BIT 1-0 |
BIT 7-6 |
BIT 5-4 |
BIT 3-2 |
BIT 1-0 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
Embedded audio status |
HDCP status |
Signal present status |
Connection status |
|
|
0 0 |
Reserved |
Reserved |
Reserved |
Reserved |
Unknown |
|||
|
0 1 |
Reserved |
|||||||
|
1 0 |
No embedded audio |
Not encrypted |
No signal |
Not connected |
||||
|
1 1 |
Embedded audio presents |
Encrypted |
Signal presents |
Connected |
||||
|
T |
0 |
0 |
A |
F |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 0 |
1 0 |
1 1 |
1 1 |
|
Reserved |
Reserved |
Reserved |
Reserved |
No embedded audio |
Not encrypted |
Signal presents |
Connected |
|
The Most Common Received Port Status Responses
|
T00AA |
T |
0 |
0 |
A |
A |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 0 |
1 0 |
1 0 |
1 0 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
No embedded audio |
Not encrypted |
No signal |
Not connected |
||
|
T00AB |
T |
0 |
0 |
A |
B |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 0 |
1 0 |
1 0 |
1 1 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
No embedded audio |
Not encrypted |
No signal |
Connected |
||
|
T00AF |
T |
0 |
0 |
A |
F |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 0 |
1 0 |
1 1 |
1 1 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
No embedded audio |
Not encrypted |
Signal presents |
Connected |
||
|
T00EF |
T |
0 |
0 |
E |
F |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 1 |
1 0 |
1 1 |
1 1 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
Embedded audio presents |
Not encrypted |
Signal presents |
Connected |
||
|
T00BF |
T |
0 |
0 |
B |
F |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 0 |
1 1 |
1 1 |
1 1 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
No embedded audio |
Encrypted |
Signal presents |
Connected |
||
|
T00FF |
T |
0 |
0 |
F |
F |
||||
|
Reserved |
0 0 |
0 0 |
0 0 |
0 0 |
1 1 |
1 1 |
1 1 |
1 1 |
|
|
Reserved |
Reserved |
Reserved |
Reserved |
Embedded audio presents |
Encrypted |
Signal presents |
Connected |
||
INFO:The settings described in the coming sections depend on the device as the output port numbers are different. Port numbers are listed in section Input and Output Port Numbering.
INFO:The settings of the mirrored outputs are common in most cases. E.g. if the autoselect setting is changed on Output 1, it will be changed on Output 3 as well.
7.5.2. Querying the Status of Destination Port
Command and Response
»GET•/MEDIA/XP/VIDEO.DestinationPortStatus
«pr•/MEDIA/XP/VIDEO.DestinationPortStatus=<O1_state>;<O2_state>;...;<O4_state>
The response contains 5 ASCII characters for each port. The first character indicates the mute/lock state, the next four characters represent a 2-byte HEX code showing the current state of the input ports.
Example
»GET /MEDIA/VIDEO/XP.DestinationPortStatus
«pr /MEDIA/VIDEO/XP.DestionationPortStatus=M00AA;T00AA;T000A;T000A
Legend
See the Legend in the Querying the Status of Source Port section.
7.5.3. Querying the Video Crosspoint Setting
Command and Response
»GET•/MEDIA/VIDEO/XP.DestinationConnectionList
«pr•/MEDIA/VIDEO/XP.DestinationConnectionList=<out_connection>
Example
»GET /MEDIA/VIDEO/XP.DestinationConnectionList
«pr /MEDIA/VIDEO/XP.DestinationConnectionList=I1;I3;I1;I3
Explanation
I1 port is connected to O1 and O3, I3 is connected to O2 and O4.
Command and Response
»CALL•/MEDIA/VIDEO/XP:switch(<in>:<out>)
«mO•/MEDIA/VIDEO/XP:switch
Example 1
»CALL /MEDIA/VIDEO/XP:switch(I4:O1)
«mO /MEDIA/VIDEO/XP:switch
Explanation
I4 port is connected to O1 port.
7.5.5. Switching an Input to All Outputs
Command and Response
»CALL•/MEDIA/VIDEO/XP:switchAll(<in>)
«mO•/MEDIA/VIDEO/XP:switchAll
Example 1
»CALL /MEDIA/VIDEO/XP:switchAll(I4)
«mO /MEDIA/VIDEO/XP:switchAll
Explanation
I4 port is connected to all output ports.
7.5.6. Disconnecting a Video Input
Command and Response
»CALL•/MEDIA/VIDEO/XP:switch(0:<out>)
«mO•/MEDIA/VIDEO/XP:switch
Example 1
»CALL /MEDIA/VIDEO/XP:switch(0:O1)
«mO /MEDIA/VIDEO/XP:switch
Explanation
When using 0 (zero) value as an input, the input will be disconnected and no signal will appear on the output.
7.5.7. Disconnecting an Input from All Outputs
Command and Response
»CALL•/MEDIA/VIDEO/XP:switchAll(0)
«mO•/MEDIA/VIDEO/XP:switchAll
Example 1
»CALL /MEDIA/VIDEO/XP:switchAll(0)
«mO /MEDIA/VIDEO/XP:switchAll
Explanation
All output ports are disconnected.
7.5.8. Setting the HDCP (Input Port)
HDCP capability can be enabled/disabled on the input ports, thus non-encrypted content can be seen on a non-HDCP compliant display. See more information in the HDCP Management section. #hdcp
Command and Response
»SET•/MEDIA/VIDEO/<In>.HdcpEnable=<logical_value>
«pw•/MEDIA/VIDEO/<In>.HdcpEnable=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
HDCP setting |
true |
HDCP capability is enabled. |
|
false |
HDCP capability is disabled. |
The <logical_value> can be set to true or false.
Example
»SET /MEDIA/VIDEO/I1.HdcpEnable=false
«pw /MEDIA/VIDEO/I1.HdcpEnable=false
7.5.9. Setting the HDCP (Output Port)
HDCP capability can be set to Auto/Always on the output ports, thus non-encrypted content can be transmitted to a non-HDCP compliant display. See more information in the HDCP Management section.
Command and Response
»SET•/MEDIA/VIDEO/<out>.HdcpModeSetting=<parameter>
«pw•/MEDIA/VIDEO/<out>.HdcpModeSetting=<parameter>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<parameter> |
HDCP mode |
0 |
Auto |
|
1 |
Always |
Example
»SET /MEDIA/VIDEO/O1.HdcpModeSetting=0
«pw /MEDIA/VIDEO/O1.HdcpModeSetting=0
7.5.10. Querying the Video Autoselect Settings
Command and Response
»GET•/MEDIA/VIDEO/XP.DestinationPortAutoselect
«pr•/MEDIA/VIDEO/XP.DestinationPortAutoselect=<out_set>
The response shows the settings of each output one by one.
Legend
<out_set> Two-letter code of the Autoselect settings.
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<out_set> - 1st letter |
Autoselect enabling/disabling |
E |
Autoselect is enabled. |
|
D |
Autoselect is disabled. |
||
|
<out_set> - 2nd letter |
Autoselect mode |
F |
First detect mode: the first active video input is selected. |
|
P |
Priority detect: it is always the highest priority active video input that will be selected. |
||
|
L |
Last detect: it is always the last attached input that is automatically switched to the output. |
Example
»GET /MEDIA/VIDEO/XP.DestinationPortAutoselect
«pr /MEDIA/VIDEO/XP.DestinationPortAutoselect=EL;DP;EL;DP
Explanation
EL: the Autoselect is Enabled on output 1 and output 3, selected mode is Last detect.
DP: the Autoselect is Disabled on output 2 and output 4.
INFO:For more information, see the The Autoselect Feature section. #autoselect
7.5.11. Changing the Autoselect Mode
Command and Response
»CALL•/MEDIA/VIDEO/XP:setDestinationPortAutoselect(<On>:<On_set>)
«mO•/MEDIA/VIDEO/XP:setDestinationPortAutoselect
Legend
See the previous section.
Example
»CALL /MEDIA/VIDEO/XP:setDestinationPortAutoselect(O1:EF)
«mO /MEDIA/VIDEO/XP:setDestinationPortAutoselect
Explanation
The Autoselect mode is Enabled on Output 1 in First detect mode.
7.5.12. Querying the Input Port Priority
Command and Response
»GET•/MEDIA/VIDEO/XP.PortPriorityList
«pr•/MEDIA/VIDEO/XP.PortPrioirtyList=<out_list>
The response shows the priority of each output one after another. The priority number can be from 0 to 31; 0 is the highest- and 30 is the lowest priority. 31 means that the port will be skipped in the priority list.
Legend
<out_list>: The input port priority order of the given output port: <I1>,I2>,…,<Im>
Example
»GET /MEDIA/VIDEO/XP.PortPriorityList
«pr /MEDIA/VIDEO/XP.PortPriorityList= 5,4,3,2,1,0;0,1,2,3,4,5; 5,4,3,2,1,0;0,1,2,3,4,5
Explanation
There are four outputs, so there are four groups listed in the response (divided by semicolons) and each group (list) contains six priority numbers. The priority list of O1 and O3 is common, such as the list of O2 and O4.
The response: 5,4,3,2,1,0;0,1,2,3,4,5;5,4,3,2,1,0;0,1,2,3,4,5. Those values show the priority order of the video input ports:
|
Output 1 |
Output 2 |
Output 3 |
Output 4 |
||||||||||||||||||||
|
I1 |
I2 |
I3 |
I4 |
I5 |
I6 |
I1 |
I2 |
I3 |
I4 |
I5 |
I6 |
I1 |
I2 |
I3 |
I4 |
I5 |
I6 |
I1 |
I2 |
I3 |
I4 |
I5 |
I6 |
|
5 |
4 |
3 |
2 |
1 |
0 |
0 |
1 |
2 |
3 |
4 |
5 |
5 |
4 |
3 |
2 |
1 |
0 |
0 |
1 |
2 |
3 |
4 |
5 |
In the example above, the Input 6 has the highest priority on O1 and O3 output ports and Input 1 has the lowest priority. On O2 and O4 ports the setting is the opposite.
ATTENTION!The same priority number can be set to different input ports. When the priority numbers match, the input port with the lowest port number will have the highest priority.
7.5.13. Changing the Input Port Priority
Command and Response
»CALL•/MEDIA/VIDEO/XP:setAutoselectionPriority(<in>(<out>):<prio>)
«mO•/MEDIA/VIDEO/XP:setAutoselectionPrioirty
Legend
|
Identifier |
Parameter description |
|
<prio> |
Priority number from 0 to 31, equal numbers are allowed (31 means that the port will be skipped in the priority list). |
An input port priority can be set on an output port. Many settings can be executed by separating a semicolon (no space), see the example below.
Example
»CALL /MEDIA/VIDEO/XP:setAutoselectionPriority (I1(O1):31;I2(O1):1;I3(O1):2;I4(O1):3;I5(O1):4;I6(O1):5)
«mO /MEDIA/VIDEO/XP:setAutoselectionPriority
Explanation
The Input 1 is ignored from the autoselection, priority order of the inputs are: I2, I3, I4, I5, I6.
Command and Response #mute
»CALL•/MEDIA/VIDEO/XP:muteSource(<in>)
«mO•/MEDIA/VIDEO/XP:muteSource
Example
»CALL /MEDIA/VIDEO/XP:muteSource(I1)
«mO /MEDIA/VIDEO/XP:muteSource
7.5.15. Unmuting the Input Port
Command and Response #unmute
»CALL•/MEDIA/VIDEO/XP:unmuteSource(<in>)
«mO•/MEDIA/VIDEO/XP:unmuteSource
Example
»CALL /MEDIA/VIDEO/XP:unmuteSource(I1)
«mO /MEDIA/VIDEO/XP:unmuteSource
7.5.16. Locking the Input Port
Command and Response #lock
»CALL•/MEDIA/VIDEO/XP:lockSource(<in>)
«mO•/MEDIA/VIDEO/XP:lockSource
Example
»CALL /MEDIA/VIDEO/XP:lockSource(I1)
«mO /MEDIA/VIDEO/XP:lockSource
7.5.17. Unlocking the Input Port
Command and Response #unlock
»CALL•/MEDIA/VIDEO/XP:unlockSource(<in>)
«mO•/MEDIA/VIDEO/XP:unlockSource
Example
»CALL /MEDIA/VIDEO/XP:unlockSource(I1)
«mO /MEDIA/VIDEO/XP:unlockSource
7.5.18. Muting the Output Port
Command and Response
»CALL•/MEDIA/VIDEO/XP:muteDestination(<out>)
«mO•/MEDIA/VIDEO/XP:muteDestination
Example
»CALL /MEDIA/VIDEO/XP:muteDestination(O1)
«mO /MEDIA/VIDEO/XP:muteDestination
7.5.19. Unmuting the Output Port
Command and Response
»CALL•/MEDIA/VIDEO/XP:unmuteDestination(<out>)
«mO•/MEDIA/VIDEO/XP:unmuteDestination
Example
»CALL /MEDIA/VIDEO/XP:unmuteDestination(O1)
«mO /MEDIA/VIDEO/XP:unmuteDestination
7.5.20. Locking the Output Port
Command and Response
»CALL•/MEDIA/VIDEO/XP:lockDestination(<out>)
«mO•/MEDIA/VIDEO/XP:lockDestination
Example
»CALL /MEDIA/VIDEO/XP:lockDestination(O1)
«mO /MEDIA/VIDEO/XP:lockDestination
7.5.21. Unlocking the Input Port
Command and Response
»CALL•/MEDIA/VIDEO/XP:unlockDestination(<out>)
«mO•/MEDIA/VIDEO/XP:unlockDestination
Example
»CALL /MEDIA/VIDEO/XP:unlockDestination(O1)
«mO /MEDIA/VIDEO/XP:unlockDestination
7.5.22. Test Pattern Generator - Mode
The output ports can send a special image towards the sink devices for testing purposes. The setting is available on output ports with the parameters listed below. #testpattern
ATTENTION!The Mode can be set individually on each port, but the Clock source and the Pattern settings are common on the mirrored output ports (e.g. on O1 and O3 output ports).
Command and Response
»SET•/MEDIA/VIDEO/<out>.TpgMode=<mode>
«pw•/MEDIA/VIDEO/<out>. TpgMode=<mode>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<mode> |
Test pattern mode setting |
0 |
The test pattern is not displayed on the output. |
|
1 |
The test pattern is displayed if there is no video is received on the output port. |
||
|
2 |
The test pattern is displayed on the output even there is an incoming signal. |
Example
»SET /MEDIA/VIDEO/O1.TpgMode=2
«pw /MEDIA/VIDEO/O1.TpgMode=2
7.5.23. Test Pattern Generator - Clock Source
Command and Response
»SET•/MEDIA/VIDEO/<On>.TpgClockSource=<clock_source>
«pw•/MEDIA/VIDEO/<On>.TpgClockSource=<clock_source>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<clock_source> |
Test pattern clock source frequency |
480 |
480p |
|
576 |
576p |
||
|
EXT |
External clock (from actual TMDS source) |
Example
»SET /MEDIA/VIDEO/O1.TpgClockSource=576
«pw /MEDIA/VIDEO/O1.TpgClockSource=576
7.5.24. Test Pattern Generator - Pattern setting
Command and Response
»SET•/MEDIA/VIDEO/<On>.TpgPattern=<pattern>
«pw•/MEDIA/VIDEO/<On>.TpgPattern=<pattern>
Parameters
|
Identifier |
Parameter description |
Parameter values |
|
<pattern> |
Selectable test image |
RED / GREEN / BLUE / BLACK / WHITE / RAMP / CHESS / BAR / CYCLE |
Cycle setting means all the patterns are changed sequentially approx. every 2 seconds.
Example
»SET /MEDIA/VIDEO/O1.TpgPattern=GREEN
«pw /MEDIA/VIDEO/O1.TpgPattern=GREEN
7.5.25. Querying the Current TPS Mode
Command and Response
»GET•/REMOTE/<source>|<destination>.tpsMode
«pr•/REMOTE/<source>|<destination>.tpsMode=<TPS_mode>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<source> |
TPS input ports |
S1 |
TPS in 1 |
|
S2 |
TPS in 2 |
||
|
<destination> |
TPS output ports |
D1 |
TPS out 1 |
|
D2 |
TPS out 2 |
||
|
<TPS_mode> |
HDBaseT working mode |
A |
Auto |
|
H |
HDBaseT |
||
|
L |
Long reach |
||
|
1 |
LPPF1 |
||
|
2 |
LPPF2 |
For more information about TPS modes, see the TPS Working Modes section. #tpsmode
Example
»GET /REMOTE/S1.tpsMode
«pr /REMOTE/S1.tpsMode=A
7.5.26. Setting the TPS Mode on TPS Ports
Command and Response
»SET•/REMOTE/<source>|<destination>.tpsModeSetting=<TPS_mode>
«pw•/REMOTE/<source>|<destination>.tpsModeSetting=<TPS_mode>
Example
»SET /REMOTE/S1.tpsModeSetting=L
«pw /REMOTE/S1.tpsModeSetting=L
Parameters
See the previous section.
7.5.27. Setting the HDMI Mode (Output Ports)
Command and Response #signaltype
»SET•/MEDIA/VIDEO/<out>.HdmiModeSetting=<HDMI_mode>
«pw•/MEDIA/VIDEO/<out>.HdmiModeSetting=<HDMI_mode>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<HDMI_mode> |
HDMI mode |
0 |
Auto |
|
1 |
DVI |
||
|
2 |
HDMI |
Example
»SET /MEDIA/VIDEO/O1.HdmiModeSetting=2
«pw /MEDIA/VIDEO/O1.HdmiModeSetting=2
7.6.1. Selecting the Signal Source
Command and Response
»SET•/MEDIA/VIDEO/<in>|<out>.AudioMode=<audio_mode>
«pw•/MEDIA/VIDEO/<in>|<out>.AudioMode=<audio_mode>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<audio_mode> |
Audio signal source mode |
0 |
Embedded |
|
1 |
AUX1 |
||
|
2 |
AUX2 |
||
|
3 |
AUX3 |
||
|
4 |
AUX4 |
INFO:For more information about the audio capabilities, see the Audio Inputs and Modes section
INFO:The setting is common with the mirrored outputs and available on the HDMI output ports.
Example
»SET /MEDIA/VIDEO/I1.AudioMode=1
«pw /MEDIA/VIDEO/I1.AudioMode=1
7.6.2. Setting the Analog Audio Input Level - Volume
INFO:The following setting is valid only for analog audio input ports. #volume
Command and Response
»SET•/MEDIA/AUDIO/<in>.Volume=<volume>
«pw•/MEDIA/AUDIO/<in>.Volume=<volume>
Parameters
|
Identifier |
Parameter description |
|
<volume> |
Sets the input volume (attenuation) between -95.625 dB and 0 dB in step of -0.375 dB. The value is rounded up if necessary, to match with the step value. |
Example
»SET /MEDIA/AUDIO/I7.Volume=-15
«pw /MEDIA/AUDIO/I7.Volume=-15.000
7.6.3. Setting the Analog Audio Input Level - Balance
INFO:The following setting is valid only for analog audio input ports. #balance
Command and Response
»SET•/MEDIA/AUDIO/<in>.Balance=<balance>
«pw•/MEDIA/AUDIO/<in>.Balance=<balance>
Parameters
|
Identifier |
Parameter description |
|
<balance> |
Sets the balance; 0 means left balance, 100 means right balance, step is 1. Center is 50 (default). |
Example
»SET /MEDIA/AUDIO/I7.Balance=25
«pw /MEDIA/AUDIO/I7.Balance=25
7.6.4. Setting the Analog Audio Input Level - Gain
INFO:The following setting is valid only for analog audio input ports.
Command and Response
»SET•/MEDIA/AUDIO/<in>.Gain=<gain>
«pw•/MEDIA/AUDIO/<in>.Gain=<gain>
Parameters
|
Identifier |
Parameter description |
|
<gain> |
Sets the input gain between 0 dB and 21 dB in step of 0.75 dB. The value is rounded down if necessary, to match the step value. |
Example
»SET /MEDIA/AUDIO/I7.Gain=4
«pw /MEDIA/AUDIO/I7.Gain=3.75
7.6.5. Setting the Analog Audio Output Level - Volume
INFO:The following setting is valid only for analog audio output ports. #volume
Command and Response
»SET•/MEDIA/AUDIO/<out>.Volume=<volume>
«pw•/MEDIA/AUDIO/<out>.Volume=<volume>
Parameters
|
Identifier |
Parameter description |
|
<volume> |
Sets the output volume (attenuation) between 0dB and -57 dB in step of -1 dB. The value is rounded up if necessary, to match with the step value. |
Example
»SET /MEDIA/AUDIO/I7.Volume=-8
«pw /MEDIA/AUDIO/I7.Volume=-8
7.6.6. Setting the Analog Audio Output Level - Balance
INFO:The following setting is valid only for analog audio output ports. #balance
Command and Response
»SET•/MEDIA/AUDIO/<in>.Balance=<balance>
«pw•/MEDIA/AUDIO/<in>.Balance=<balance>
Parameters
|
Identifier |
Parameter description |
|
<balance> |
Sets the balance; 0 means left balance, 100 means right balance, step is 1. Center is 50 (default). |
Example
»SET /MEDIA/AUDIO/O5.Balance=0
«pw /MEDIA/AUDIO/O5.Balance=0
7.6.7. Setting the Analog Audio Output Level - Gain
INFO:The following setting is valid only for analog audio output ports.
Command and Response
»SET•/MEDIA/AUDIO/<out>.Gain=<gain>
«pw•/MEDIA/AUDIO/<out>.Gain=<gain>
Parameters
|
Identifier |
Parameter description |
|
<gain> |
Sets the output gain which can be 0, 1, 2 or 3 dB. The value is rounded down if necessary, to match with the step value. |
Example
»SET /MEDIA/AUDIO/O5.Gain=2
«pw /MEDIA/AUDIO/O5.Gain=2
7.6.8. Muting/Unmuting the Analog Audio Output Level
INFO:The following setting is valid only for analog audio output ports. #mute #unmute
Command and Response
»SET•/MEDIA/AUDIO/<out>.MuteSetting=<logical_value>
«pw•/MEDIA/AUDIO/<out>.MuteSetting=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
Mute setting |
true |
The port is muted. |
|
false |
The port is unmuted. |
Example
»SET /MEDIA/AUDIO/O5.MuteSetting=true
«pw /MEDIA/AUDIO/O5.MuteSetting=true
7.7. RS-232 Port Configuration
ATTENTION!MMX6x2 handles many serial ports. The following parameters can be set individually on each port; the exact port numbering is listed in section Factory Default Settings. #rs232 #serial
Command and Response #protocol
»SET•/MEDIA/UART/<port>.ControlProtocol=<number>
«pw•/MEDIA/UART/<port>.ControlProtocol=<number>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<number> |
Control protocol |
0 |
LW2 |
|
1 |
LW3 |
Example
»SET /MEDIA/UART/P1.ControlProtocol=1
«pw /MEDIA/UART/P1.ControlProtocol=1
7.7.2. Setting the BAUD Rate
Command and Response
»SET•/MEDIA/UART/<port>.Baudrate=<number>
«pw•/MEDIA/UART/<port>.Baudrate=<number>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<number> |
Baud rate value |
0 |
4800 |
|
1 |
7200 |
||
|
2 |
9600 |
||
|
3 |
14400 |
||
|
4 |
19200 |
||
|
5 |
38400 |
||
|
6 |
57600 |
||
|
7 |
115200 |
Example
»SET /MEDIA/UART/P1.Baudrate=2
«pw /MEDIA/UART/P1.Baudrate=2
Command and Response
»SET•/MEDIA/UART/<port>.DataBits=<databits>
«pw•/MEDIA/UART/<port>.DataBits=<databits>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<databits> |
Data bits value |
8 |
8 data bits |
|
9 |
9 data bits |
Example
»SET /MEDIA/UART/P1.DataBits=8
«pw /MEDIA/UART/P1.DataBits=8
7.7.4. Setting the Stopbits
Command and Response
»SET•/MEDIA/UART/<port>.StopBits=<number>
«pw•/MEDIA/UART/<port>.StopBits=<number>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<number> |
Stop bits value |
0 |
1 |
|
1 |
1,5 |
||
|
2 |
2 |
Example
»SET /MEDIA/UART/P1.StopBits=0
«pw /MEDIA/UART/P1.StopBits=0
Command and Response
»SET•/MEDIA/UART/<port>.Parity=<number>
«pw•/MEDIA/UART/<port>.Parity=<number>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<number> |
Parity value |
0 |
None |
|
1 |
Odd |
||
|
2 |
Even |
Example
»SET /MEDIA/UART/P1.Parity=0
«pw /MEDIA/UART/P1.Parity=0
7.7.6. Setting the RS-232 Operation Mode
Command and Response
»SET•/MEDIA/UART/<port>.Rs232Mode=<number>
«pw•/MEDIA/UART/<port>.Rs232Mode=<number>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<number> |
RS-232 operation mode |
0 |
Disconnect |
|
1 |
Control |
||
|
2 |
Command injection |
Example
»SET /MEDIA/UART/P2.Rs232Mode=1
«pw /MEDIA/UART/P2.Rs232Mode=1
7.7.7. Setting the Command Injection Mode
Command and Response #commandinjection
»SET•/MEDIA/UART/<port>.CommandInjectionEnable=<logical_value>
«pw•/MEDIA/UART/<port>.CommandInjectionEnable=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
Command injection status |
true |
Command injection is enabled on the port. |
|
false |
Command injection is disabled on the port. |
Example
»SET /MEDIA/UART/P2.CommandInjectionEnable=true
«pw /MEDIA/UART/P2.CommandInjectionEnable=true
ATTENTION!The Command injection status is stored in another read-only property, which is True if both above mentioned properties are set to the proper state; if so, Command injection mode is active:
/MEDIA/UART/<Pn>.CommandInjectionStatus.
ATTENTION!Do not forget to set the TCP/IP port setting, which works individually for each RS-232 port and is stored in the /MEDIA/UART/<Pn>.CommandInjectionPort parameter.
7.8. Message Sending via Ethernet Port
7.8.1. Sending a TCP Message (ASCII-format) via Ethernet
The command is for sending a command message in ASCII-format. This method allows escaping the control characters, see the Escaping section. #message
Command and Response
»CALL•/MEDIA/ETHERNET:tcpMessage(<IP_address>:<port_no>=<message>)
«mO•/MEDIA/ETHERNET:tcpMessage
Example
»CALL /MEDIA/ETHERNET:tcpMessage(192.168.0.20:5555=C00)
«mO /MEDIA/ETHERNET:tcpMessage
The 'C00' message is sent to the indicated IP:port address.
Example with HEX codes
»CALL /MEDIA/ETHERNET:tcpMessage(192.168.0.20:5555=C00\x0a\x0d)
«mO /MEDIA/ETHERNET:tcpMessage
The 'C00' message with CrLf (Carriage return and Line feed) is sent to the indicated IP:port address. The \x sequence indicates the HEXA code.
Escaping in the Message
When commands need to be separated by <CR><LF> characters to be recognized by the controlled device, then they need to be escaped. You can use the following format for escaping:
<command1><\x0d\x0a><command2><\x0d\x0a>...<commandn><\x0d\x0a>
7.8.2. Sending a TCP Text (ASCII-format) via Ethernet
The command is for sending a text message in ASCII-format. This method does not allow sending messages with control and non-printable characters.
Command and Response
»CALL•/MEDIA/ETHERNET:tcpText(<IP_address>:<port_no>=<text>)
«mO•/MEDIA/ETHERNET:tcpText
Example
»CALL /MEDIA/ETHERNET:tcpText(192.168.0.20:5555=open)
«mO /MEDIA/ETHERNET:tcpText
The 'open' text is sent to the indicated IP:port address.
7.8.3. Sending a TCP Binary Message (HEX-format) via Ethernet
The command is for sending a binary message in Hexadecimal format. This method does not allow sending messages with control and non-printable characters.
Command and Response
»CALL•/MEDIA/ETHERNET:tcpBinary(<IP_address>:<port_no>=<HEX_message>)
«mO•/MEDIA/ETHERNET:tcpBinary
Example
»CALL /MEDIA/ETHERNET:tcpBinary(192.168.0.20:5555=433030)
«mO /MEDIA/ETHERNET:tcpBinary
The '433030' message is sent to the indicated IP:port address.
INFO:There is no need to insert a space or other separator character between the binary messages.
7.8.4. Sending a UDP Message (ASCII-format) via Ethernet
The command is for sending a UDP message in ASCII-format. This method allows escaping the control characters, see the Escaping section.
Command and Response
»CALL•/MEDIA/ETHERNET:udpMessage(<IP_address>:<port_no>=<message>)
«mO•/MEDIA/ETHERNET:udpMessage
Example
»CALL /MEDIA/ETHERNET:udpMessage(192.168.0.20:9988=C00)
«mO /MEDIA/ETHERNET:udpMessage
The 'C00' message is sent to the indicated IP:port address.
Example with HEX codes
»CALL /MEDIA/ETHERNET:udpMessage(192.168.0.20:9988=C00\x0a\x0d)
«mO /MEDIA/ETHERNET:udpMessage
The 'C00' message with CrLf (Carriage return and Line feed) is sent to the indicated IP:port address. The \x sequence indicates the HEXA code.
Escaping in the Message
When commands need to be separated by <CR><LF> characters to be recognized by the controlled device, then they need to be escaped. You can use the following format for escaping:
<command1><\x0d\x0a><command2><\x0d\x0a>...<commandn><\x0d\x0a>
7.8.5. Sending a TCP Text (ASCII-format) via Ethernet
The command is for sending a text message in ASCII-format via UDP-protocol. This method does not allow sending messages with control and non-printable characters.
Command and Response
»CALL•/MEDIA/ETHERNET:udpText(<IP_address>:<port_no>=<text>)
«mO•/MEDIA/ETHERNET:udpText
Example
»CALL /MEDIA/ETHERNET:udpText(192.168.0.20:9988=open)
«mO /MEDIA/ETHERNET:udpText
The 'open' text is sent to the indicated IP:port address.
7.8.6. Sending a UDP Binary Message (HEX-format) via Ethernet
The command is for sending a binary message in Hexadecimal format via UDP protocol. This method does not allow sending messages with control and non-printable characters.
Command and Response
»CALL•/MEDIA/ETHERNET:udpBinary(<IP_address>:<port_no>=<HEX_message>)
«mO•/MEDIA/ETHERNET:udpBinary
Example
»CALL /MEDIA/ETHERNET:udpBinary(192.168.0.20:9988=433030)
«mO /MEDIA/ETHERNET:udpBinary
The '433030' message is sent to the indicated IP:port address.
INFO:There is no need to insert a space or other separator character between the binary messages.
7.9. Message Sending via RS-232 Serial Port
7.9.1. Sending a Text (ASCII-format) via Serial Port
The command is for sending a command message in ASCII-format. This method does not allow sending messages with control and non-printable characters.
Command and Response
»CALL•/MEDIA/UART/<port>:sendText(<message>)
«mO•/MEDIA/UART/<port>:sendText
Example
»CALL /MEDIA/UART/P1:sendText(open)
«mO /MEDIA/UART/P1:sendText
The 'open' text is sent out via the P1 serial port.
7.9.2. Sending a Binary Message (HEX-format) via Serial Port
The command is for sending a command message in Hexadecimal-format. This method does not require escaping the control and non-printable characters.
Command and Response
»CALL•/MEDIA/UART/<port>:sendBinaryMessage(<message>)
«mO•/MEDIA/UART/<port>:sendBinaryMessage
Example
»CALL /MEDIA/UART/P1:sendBinaryMessage(433030)
«mO /MEDIA/UART/P1:sendBinaryMessage
The '433030' message is sent out via the P1 serial port.
7.9.3. Sending a Message (ASCII-format) via Serial Port
The command is for sending a command message in ASCII-format. This method allows escaping the control characters, see the Escaping section.
Command and Response
»CALL•/MEDIA/UART/<port>:sendMessage(<message>)
«mO•/MEDIA/UART/<port>:sendMessage
Example
»CALL /MEDIA/UART/P1:sendMessage(PWR0)
«mO /MEDIA/UART/P1:sendMessage
The 'PWR0' message is sent out via the P1 serial port.
Escaping in the Message
When commands need to be separated by <CR><LF> characters to be recognized by the controlled device, then they need to be escaped. You can use the following format for escaping:
<command1><\x0d\x0a><command2><\x0d\x0a>...<commandn><\x0d\x0a>
7.10. Infrared Port Configuration
INFO:Infrared port numbering can be found in the Input and Output Port Numbering section.
7.10.1. Enabling/Disabling Command Injection Mode
Command and Response
»SET•/MEDIA/IR/<source>|<destination>.CommandInjectionEnable=<logical_value>
«pw•/MEDIA/IR/<source>|<destination>.CommandInjectionEnable=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<source> |
Infrared TPS input ports |
S1 - S4 |
Infrared TPS input ports |
|
<destination> |
Infrared TPS output ports |
D1 - D4 |
Infrared TPS output ports |
|
<logical_value> |
Command injection status |
true |
Command injection is enabled on the port. |
|
false |
Command injection is disabled on the port. |
Example
»SET /MEDIA/IR/S1.CommandInjectionEnable=true
«pw /MEDIA/IR/S1.CommandInjectionEnable=true
7.10.2. Enabling/Disabling Output Signal Modulation
Command and Response
»SET•/MEDIA/IR/<destination>.EnableModulation=<logical_value>
«pw•/MEDIA/IR/<destination>.EnableModulation=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
Signal modulation status |
true |
Signal modulation is enabled on the port. |
|
false |
Signal modulation is disabled on the port. |
Example
»SET /MEDIA/IR/D2.EnableModulation=false
«pw /MEDIA/IR/D2.EnableModulation=false
INFO:The default setting value is "true" (enabled).
7.10.3. Changing Command Injection Port Number
Command and Response
»SET•/MEDIA/IR/<source>|<destination>.CommandInjectionPort=<port_no>
«pw•/MEDIA/IR/<source>|<destination>.CommandInjectionPort=<port_no>
Example
»SET /MEDIA/IR/S1.CommandInjectionPort=9001
«pw /MEDIA/IR/S1.CommandInjectionPort=9001
7.11.1. Querying the DHCP State
Command and Response #dhcp
»GET•/MANAGEMENT/NETWORK.DhcpEnabled
«pw•/MANAGEMENT/NETWORK.DhcpEnabled=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
Dynamic IP address (DHCP) status |
true |
DHCP is enabled. |
|
false |
DHCP is disabled. |
Example
»GET /MANAGEMENT/NETWORK.DhcpEnabled
«pw /MANAGEMENT/NETWORK.DhcpEnabled=true
7.11.2. Changing the DHCP State
#dhcp
Command and Response
»SET•/MANAGEMENT/NETWORK.DhcpEnabled=<logical_value>
«pw•/MANAGEMENT/NETWORK.DhcpEnabled=<logical_value>
Parameters
See the previous section.
Example
»SET /MANAGEMENT/NETWORK.DhcpEnabled=true
«pw /MANAGEMENT/NETWORK.DhcpEnabled=true
7.11.3. Querying the IP Address
Command and Response
»GET•/MANAGEMENT/NETWORK.IpAddress
«pr•/MANAGEMENT/NETWORK.IpAddress=<IP_address>
Example
»GET /MANAGEMENT/NETWORK.IpAddress
«pr /MANAGEMENT/NETWORK.IpAddress=192.168.0.102
7.11.4. Changing the IP Address (Static)
Command and Response #ipaddress
»SET•/MANAGEMENT/NETWORK.StaticIpAddress=<IP_address>
«pw•/MANAGEMENT/NETWORK.StaticIpAddress=<IP_address>
Example
»SET /MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.105
«pw /MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.105
7.11.5. Querying the Subnet Mask
Command and Response
»GET•/MANAGEMENT/NETWORK.NetworkMask
«pr•/MANAGEMENT/NETWORK.NetworkMask=<netmask>
Example
»GET /MANAGEMENT/NETWORK.NetworkMask
«pr /MANAGEMENT/NETWORK.NetworkMask=255.255.255.0
7.11.6. Changing the Subnet Mask (Static)
Command and Response
»SET•/MANAGEMENT/NETWORK.StaticNetworkMask=<netmask>
«pw•/MANAGEMENT/NETWORK.StaticNetworkMask=<netmask>
Example
»SET /MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0
«pw /MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0
7.11.7. Querying the Gateway Address
Command and Response
»GET•/MANAGEMENT/NETWORK.GatewayAddress
«pr•/MANAGEMENT/NETWORK.GatewayAddress=<gw_address>
Example
»GET /MANAGEMENT/NETWORK.GatewayAddress
«pr /MANAGEMENT/NETWORK.GatewayAddress=192.168.0.1
7.11.8. Changing the Gateway Address (Static)
Command and Response
»SET•/MANAGEMENT/NETWORK.StaticGatewayAddress=<gw_address>
«pw•/MANAGEMENT/NETWORK.StaticGatewayAddress=<gw_address>
Example
»SET /MANAGEMENT/NETWORK.StaticGatewayAddress=172.0.0.1
«pw /MANAGEMENT/NETWORK.StaticGatewayAddress=172.0.0.1
7.12.1. Querying the Emulated EDIDs
Command and Response #edid
»GET•/EDID.EdidStatus
«pr•/EDID.EdidStatus=<E_loc>:<En>
Example
»GET /EDID.EdidStatus
«pr EDID.EdidStatus=F46:E1;F47:E2;F47:E3;F47:E4;F47:E5;F47:E6
Explanation
All emulated EDID memories (inputs) are listed with the EDID number that is currently emulated on the input, separated by semicolons. The example above shows that F46 EDID (46th Factory EDID) is emulated on I1 (E1) port, and F47 is emulated on all other input ports. Port numbers are listed in section Input and Output Port Numbering.
7.12.2. Querying the Validity of a Dynamic EDID
Command and Response
»GET•/EDID/D/<Dn>.Validity
«pr•/EDID/D/<Dn>.Validity=<logical_value>
Parameters
|
Identifier |
Parameter description |
Value |
Explanation |
|
<logical_value> |
EDID validity status |
true |
The selected EDID is valid. |
|
false |
The selected EDID is invalid. |
Example
»GET /EDID/D/D1.Validity
«pr /EDID/D/D1.Validity=true
7.12.3. Emulating an EDID to an Input Port
Command and Response
»CALL•/EDID:switch(<source>:<destination>)
«mO•/EDID:switch
Parameters
|
Identifier |
Parameter description |
|
<source> |
Source EDID memory place: Factory / User / Dynamic. |
|
<destination> |
The emulated EDID memory of the desired input port. |
Example
»CALL /EDID:switch(F49:E2)
«mO /EDID:switch
7.12.4. Copying an EDID to User Memory
Command and Response
»CALL•/EDID:copy(<Dn>|<En>|<Fn>|<Un>:<Um>)
«mO•/EDID:copy
Example
»CALL /EDID:copy(D1:U1)
«mO /EDID:copy
Explanation
The EDID of the last connected sink of D1 (Output 1) has been copied to U1.
7.12.5. Deleting an EDID from User Memory
Command and Response
»CALL•/EDID:delete(<Un>)
«mO•/EDID:delete
Example
»CALL /EDID:delete(U1)
«mO /EDID:delete
7.12.6. Resetting the Emulated EDIDs
Command and Response
»CALL•/EDID:reset(1)
«mO•/EDID:reset
Example
»CALL /EDID:reset(1)
«mO /EDID:reset
Explanation
Calling this method switches all emulated EDIDs to a factory default one. See the table in the Factory Default Settings section.
This chapter is meant to help customers perform firmware updates on our products by giving a few tips on how to start, and by explaining the features of the Lightware Device Updater (LDU2) software over LAN. The latest software and firmware pack can be downloaded from www.lightware.com.
8.1. Introduction
Lightware Device Updater v2 (LDU2) software is the second generation of the LFP-based (Lightware Firmware Package) firmware update process.
DIFFERENCE:The software can be used for uploading the packages with LFP2 extension only. LDU2 is not suitable for using LFP files, please use the LDU software for that firmware update.
8.2. Preparation
Most Lightware devices can be controlled over several interfaces (e.g. Ethernet, USB, RS-232). But the firmware can be updated usually over one dedicated interface, which is the Ethernet in most cases.
If you want to update the firmware of one or more devices, you need the following:
▪LFP2 file,
▪LDU2 software installed on your PC or Mac.
Both can be downloaded from www.lightware.com/downloads.
Optionally, you can download the release notes file in HTML format.
8.2.1. About the Firmware Package (LFP2 File)
All the necessary tools and binary files are packed into the LFP2 package file. You only need this file to do the update on your device.
▪This allows the use of the same LFP2 package for different devices.
▪The package contains all necessary components, binary and other files.
▪The release notes is included in the LFP2 file, which is displayed in the window where you select the firmware package file in LDU2.
8.2.2. LDU2 Installation
ATTENTION!Minimum system requirement: 2 GB RAM.
INFO:The Windows and the Mac applications have the same look and functionality.
Download the software from www.lightware.com/downloads.
Installation Modes
|
Normal install |
Snapshot install |
|
Available for Windows, macOS and Linux |
Available for Windows only |
|
The installer can update only this instance |
Cannot be updated |
|
One updateable instance may exist for all users |
Many different versions can be installed for all users |
ATTENTION!Using the default Normal install is highly recommended.
INFO:If you have a previously installed version, you will be prompted to remove the old version before installing the new one.
Installation in case of Windows OS
Run the installer. If the User Account Control displays a pop-up message, click Yes.
Using the Normal install (default setting) is highly recommended.
Installation in case of macOS
Mount the DMG file by double clicking on it, and drag the LDU2 icon over the Applications icon to copy the program into the Applications folder. If you want to copy LDU2 into another location, just drag the icon over the desired folder.
INFO:This type of installer is equal to the Normal install of Windows.
ATTENTION!Please check the firewall settings on the macOS device. LDU2 needs to be added to the exeptions of the blocked softwares for proper operation.
Installation in case of Linux
Step 1.Download the archive file (tar.gz) from www.lightware.com and unpack it to a temp folder.
Step 2.Run the install_ldu2.sh file in the temp folder. The script will install LDU2 into the following folder: HOME/.local/share/lightware/ldu2.
Step 3.Above folder will contain this file: LightwareDeviceUpdaterV2.sh that can be used to start LDU2.
8.3. Running the Software
ATTENTION!The computer that runs LDU2 and the target device (that will be updated) must be in the same subnet. The update cannot be performed behind a firewall or gateway.
You have two options:
▪Starting the LDU2 by double-clicking on the shortcut/program file, or
▪Double-clicking on an LFP2 file.
LDU2 Auto-Update
At startup, the software checks whether a newer version is available on the web.
Main Screen
When the software is started by the shortcut, the device discovery screen appears. Press the Search for devices button to start finding the Lightware devices:
Devices may also be added manually by typing the IP address in the box near the bottom of the screen. From LDU2 version v2.16.1, manual addition of the devices can also be done using the host name.
ATTENTION!If the device cannot be added by the host name, please use the IP address.
If you start the software by double-clicking on the LFP2 file, the firmware will be loaded. Press the Search for devices button; all the devices will be listed that are compatible with the selected firmware pack.
INFO:If you press the Select firmware package button, the release notes of the LFP2 file will be displayed in the right panel; see the Step 1. Select the Firmware Package. section.
Device List
When the discovery has completed, the devices available on the network are listed in the application.
Legend of the Icons
|
|
IP address editor |
The IP address of the device can be changed in the pop-up window. |
|
|
Identify me |
Clicking on the icon results in the front panel LEDs blink for 10 seconds, which helps to identify the device phisically. |
|
|
Favorite device |
The device has been marked, thus the IP address is stored. When a device is connected with that IP address, the star will be highlighted in that line. |
|
|
Further information available |
Device is unreachable. Change the IP address using the front panel LCD menu or the IP address editor of the LDU2. |
8.4. The Updating Steps
ATTENTION!While the firmware is being updated, the normal operation mode is suspended, as the device is switched to bootload mode. Signal processing is not performed. Do not interrupt the firmware update. If any problem occurs, reboot the unit and restart the process.
Keeping the Configuration Settings
By default, device configuration settings are restored when firmware update is finished. If factory reset has been chosen in the parameters window, all device settings will be erased. In the case of factory reset, you can save the settings of the device in the Lightware Device Controller software and restore it later.
The following flow chart demonstrates how this function works in the background.
Step 1.Create a backup
The current configuration of the device is being saved into a configuration backup file on your computer.
Step 2.Start the Update
The device reboots and starts in bootload mode (firmware update mode).
Step 3.Update
The CPU firmware is changed to the new one.
Step 4.Factory reset
All configuration settings are restored to the factory default values.
Step 5.Conversion / Restore
The firmware package checks the backup data before the restoration procedure, and if it is necessary, a conversion is applied to avoid incompatibility problems between the firmware versions. All configuration settings are restored to the device after the conversion.
If the factory default option is selected in the Parameters window, the conversion / restoration procedure will not be performed!
Step 6.Finish
Once the firmware update procedure is finished, the device reboots and is ready for use.
Step 1. Select the Firmware Package.
Click on the Select Firmware Package button and navigate to the location where the LFP2 file was saved. When you click on the name of package, the preview of the release notes is displayed in the right panel.
After the package file is loaded, the list is filtered to show the compatible devices only. The current firmware version of the device is highlighted in orange if it is different from the version of the package loaded.
INFO:If you start the update by double-clicking on the LFP file, the screen above will be loaded right away.
The Meaning of the Symbols
|
|
Show details |
The log about the updating process of the device can be displayed in a new window. |
|
|
Service mode |
The device is in bootload mode. Backup and restore cannot be performed in this case. |
Step 2. Select the desired devices for updating.
Select the devices for updating; the selected line will be highlighted in green.
If you are not sure which device to select, press the Identify me 
button. It makes the front panel LEDs blink for 10 seconds. The feature helps to find the device physically.
Step 3. Check the update parameters.
Clicking on the Parameters button, special settings will be available:
▪Creating a backup about current device configuration,
▪Restoring the configuration or reloading the factory default settings after the firmware update.
Please arrange the settings carefully.
Step 4. Start the update and wait until it is finished.
Click on the Start Update button to start the procedure. The status is shown in percent in the right side of the device line and the overall process in the bottom progress bar.
INFO:The device might reboot during the firmware update procedure.
When the progress bar reaches 100% (Done is displayed at all devices), the update of all devices is finished successfully and a message appears; you can close the software.
Step 5. Wait until the unit reboots with the new firmware.
Once the firmware update procedure is completed, the device is rebooted with the new firmware. Shutting down and restarting the device is recommended.
8.5. Command Line Interface (CLI)
DIFFERENCE:The Command Line Interface is available from LDU2 v2.9.0b9.
The CLI of the LDU2 software is a simple tool for creating scriptable device updates without needing human interactions. It allows batch updating with the same features that are available in case of GUI usage.
8.5.1. How to Run
Running under Windows® OS
The installer of LDU2 puts the following file into the installation folder:
LightwareDeviceUpdaterV2_CLI.cmd
CLI is available by this file, the exe is not suitable for this purpose. Open a command line window to execute or test the features directly.
Step 1.Open an Explorer window where the cmd file is located, the default is:
c:\Program Files (x86)\Lightware\Lightware Device Updater V2\LightwareDeviceUpdaterV2_CLI.cmd.
Step 2.Click on the address line (highlighed in blue in the picture), type cmd.exe and press enter. The command interpreter window of Windows is opened at the path of the LDU2 install folder.
Step 3.Now you can use the LightwareDeviceUpdaterV2_CLI.cmd file with the commands and options that are described in the coming sections:
Running under Linux
The Command Line Interface under Linux Operating Systems can be run by the following:
LightwareDeviceUpdaterV2.sh.
Running an update:
bash LightwareDeviceUpdaterV2.sh update --ip 172.24.5.27 --package ~/Downloads/mmx6x2-ht_v1.1.5b11.lfp2
The commands and options are the same under both Windows® and Linux. The following sections contain examples with LightwareDeviceUpdaterV2_CLI.cmd.
8.5.2. How to Use
Command Structure
The commands can be run over CLI in the following way:
LightwareDeviceUpdaterV2_CLI.cmd [command] [options]
[Command]: a certain command described in the coming sections; only one command can be run at a time
[Options]: mandatory and/or optional parameters of the command, if any. Optional parameters have a default value, which can be found at each affected command. You only have to define the parameter if you want to apply a different value. The order of the options is arbitrary.
Important Notes
▪CLI is case-sensitive (including commands, options and other parameters).
▪There is no limit regarding the number of the devices to update. At most, 20 devices are updated simoultaneously; when one of them is finished, the following (21st) will be started automatically.
▪If an update is failed, the IP address of the affected device(s) are listed at the end.
8.6. CLI Commands
INFO:The commands and options described in the following sections are the same under both Windows® and Linux. The examples contain LightwareDeviceUpdaterV2_CLI.cmd.
About the Examples
▪Sent command is in blue, response is in grey.
▪If the response in practice is longer than listed in the example, this symbol can be seen: [...].
8.6.1. Help
The defined commands and options can be listed by the help command.
Command
LightwareDeviceUpdaterV2_CLI.cmd help
Example
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd help
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar help
Command line usage:
Win: LightwareDeviceUpdaterV2_CLI.cmd [command] [options]
Linux: LightwareDeviceUpdaterV2.sh [command] [options]
Commands:
* help
* version
* update
* deviceInfo
* restore
* packageOptions
[...]
8.6.2. LDU2 Version
The response shows the version of the LDU2 and the version of the Script API (the Application Programming Interface that is used by the LDU2 and the script).
Command
LightwareDeviceUpdaterV2_CLI.cmd version
Example
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd version
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar version
LDU2 version: 2.13.1b2
Script API version: 1.3.12
8.6.3. Check For New LDU2 Version
The following command can be used to check if an update of LDU2 is available. This is just a request, since the CLI is not suitable for handling the complete installer of the software.
Command
LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates
Example 1
c:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar checkForUpdates
Current LDU2 version: 2.13.1b2
LDU2 is up-to-date
Example 2
c:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates
c:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar checkForUpdates
Current LDU2 version: 2.13.0b1
New version is available online: v2.13.1b2
Download URL: http://update.lightware.hu/ldu2/lwr/v2.13.1b2/install_LDU2_v2.13.1b2.exe
8.6.4. Device Info
The most important information about the selected device is displayed; see the example for more details.
Command
LightwareDeviceUpdaterV2_CLI.cmd deviceInfo [options]
Options
|
Option |
Description |
Required? |
|
-i or --ip |
List of IP addresses of devices to be updated |
one of them is mandatory |
|
-n or --hostName |
List of host names of devices to be updated |
|
|
-v or --packageVersion |
Shows installed package version only |
optional |
Example 1
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd deviceInfo --ip 192.168.0.111
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar deviceInfo --ip 192.168.0.111
Product name: MMX6x2-HT220
IP address: 192.168.0.111
Serial number: 00003188
MAC address: A8:D2:36:FF:31:88
Part number: 91310032
Device label: MMX6x2-HT220
Package version: v1.1.5b11
CPU FW version: v1.1.5b2
HW version: V11_BAA0
Operation mode: Application mode
Example 2
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd deviceInfo --ip 192.168.0.111 --packageVersion
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar deviceInfo --ip 192.168.0.111 --packageVersion
v1.1.5b11
8.6.5. Update
This command can be used to update the firmware of the devices.
Command
LightwareDeviceUpdaterV2_CLI.cmd update [options]
Options
|
Option |
Description |
Required? |
|
-p or --package |
The path of the firmware package file |
yes |
|
-i or --ip |
List of IP addresses of devices to be updated |
one of them is mandatory |
|
-n or --hostName |
List of host names of devices to be updated |
|
|
-b or --backupFolder |
Folder to create device configuration backup at. Default: USER_HOME/.ldu2/backup |
optional |
|
-f or --factoryDefault |
Apply factory reset during device update. Default: false |
optional |
|
-r or --reportProgress |
Report update progress in percentage form. Default: false |
optional |
|
Package-specific options |
Certain LFP2 packages have features which can be applied at this command; see the Package Options section. |
optional |
ATTENTION!The configuration is restored automatically if the factory default option is not applied in the update command.In that case, there is no need to run the restore command after the update.
Example
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip 192.168.0.111 --package C:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2 --reportProgress
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip 192.168.0.111 --package C:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2 --reportProgress
[2022-03-04 11:38:52.908] [ INFO] [ main] - Device IPs: [192.168.0.111]
[2022-03-04 11:38:55.870] [ INFO] [ main] - All the selected devices are accessible over the network.
[2022-03-04 11:38:56.102] [ INFO] [ main] - All the selected devices are compatible with the specified package.
[2022-03-04 11:38:56.556] [ INFO] [ 192.168.0.111] - Package version: 1.1.5b11
[2022-03-04 11:38:56.649] [ INFO] [ 192.168.0.111] - Creating backup of device settings...
[2022-03-04 11:38:56.683] [ INFO] [ 192.168.0.111] - Switching device into bootload mode...
[2022-03-04 11:39:00.343] [ INFO] [ 192.168.0.111] - Gathering UID information from device...
[2022-03-04 11:39:00.500] [ INFO] [ProgressReporter] - Progress: 5%
[2022-03-04 11:39:01.108] [ INFO] [ 192.168.0.111] - UID info - Device IP: 192.168.0.111 Product name: MMX6x2-HT220 Product part number: 91310032 Serial number: 00003188 Hardware version: V11_BAA0 MAC address: A8:D2:36:FF:31:88
[2022-03-04 11:39:03.121] [ INFO] [ 192.168.0.111] - Package version on device: 1.1.5b11 r29
[2022-03-04 11:39:03.128] [ INFO] [ 192.168.0.111] - Updating Firmware of the MCU...
[...]
The lines containing "ProgressReporter" can be enabled optionally. If it is enabled, the current state is displayed in every 5 seconds.
Restores device configuration from a backup file.
TIPS AND TRICKS:This command can be used for uploading a configuration to numerous devices (aka Configuration cloning by CLI).
Command
LightwareDeviceUpdaterV2_CLI.cmd restore [options]
Options
|
Option |
Description |
Required? |
|
-i or --ip |
List of IP addresses of devices to be updated |
one of them is mandatory |
|
-n or --hostName |
List of host names of devices to be updated |
|
|
-b or --backupFile |
The path of the configuration backup file |
yes |
|
-k or --keepOriginalIp |
Do not override the network settings of the device with the ones in the backup file. It comes in handy when multiple devices' configuration is being restored from a single backup file. Default: false |
optional |
ATTENTION!The configuration is restored automatically if the factory default option is not applied in the update command.In that case, there is no need to run the restore command after the update.
Example
c:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd restore --ip 192.168.0.111 --backupFile C:\mybackup.lw3 --keepOriginalIp
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar restore --ip 192.168.0.111 --backupFile C:\mybackup.lw3 --keepOriginalIp
[2022-03-04 13:42:28.754] [ INFO] [ main] - Executing configuration restore...
[2022-03-04 13:42:28.760] [ INFO] [ main] - Device IPs: [192.168.0.111]
INFO:The firmware package checks the backup data before the restore procedure and if it is necessary, a conversion is applied to avoid incompatibility problems between the firmware versions. In that case, two backup files are created: the original and a new one with "_converted" suffix. Using the last one for restoring is recommended.
Shows package-specific update options.
Command
LightwareDeviceUpdaterV2_CLI.cmd packageOptions [options]
Options
|
Option |
Description |
Required? |
|
-p or --package |
The path of the firmware package file |
yes |
Example
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd packageOptions --package c:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar packageOptions --package C:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2
Backup and restore options:
factoryDefault: if set to true device will reset to factory default settings after the upgrade process is finished, default: false
restoreFromBackup: if true, no device configuration is restored from the backup created at the begininning of upgrade process (default: true)
skipPresetsAtRestore: If true. Device presets will be skipped at restore. (default: false)
backupFolder: folder to create configuration backup into
Advanced backup and restore options:
forceNoBackup: if true, no backup file will be created (default: false)
INFO:There is a known bug in UMX-HDMI-140_v1.3.0b5.lfp2 package file: the double dashes of the options are not displayed in the description, however, above example shows correctly. The double dash is a must when applying a special parameter during update.
Package option example can be seen in the following section.
8.6.8. Complex Examples
Example 1
The following options applied:
▪Firmware is updated
▪Factory default settings restored
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip 192.168.0.111 --factoryDefault --package c:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip 192.168.0.111 --factoryDefault --package C:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2
[2022-03-04 13:24:22.333] [ INFO] [ main] - Device IPs: [192.168.0.111]
[2022-03-04 13:24:24.074] [ INFO] [ main] - All selected devices are available over the network.
[2022-03-04 13:24:24.204] [ INFO] [ main] - All the selected devices are compatible with the specified package.
[2022-03-04 13:24:24.563] [ INFO] [ 192.168.0.111] - Package version: 1.1.5b11
[2022-03-04 13:24:24.608] [ INFO] [ 192.168.0.111] - Creating backup of device settings...
[2022-03-04 13:24:25.329] [ INFO] [ 192.168.0.111] - Switching device into bootload mode...
[2022-03-04 13:24:26.415] [ INFO] [ 192.168.0.111] - Gathering UID information from device...
[2022-03-04 13:24:31.789] [ INFO] [ 192.168.0.111] - UID info - Device IP: 192.168.0.111 Product name: MMX6x2-HT220 Product part number: 91310032 Serial number: 00003188 Hardware version: V11_BAA0 MAC address: A8:D2:36:FF:31:88
[2022-03-04 13:24:32.034] [ INFO] [ 192.168.0.111] - Package version on device: 1.1.4b3 r29
[2022-03-04 13:24:32.070] [ INFO] [ 192.168.0.111] - Updating Firmware of the MCU...
[2022-03-04 13:24:32.311] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s current version on device: 1.1.4b3 r15
[2022-03-04 13:24:32.312] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s version in the package: 1.1.5b2 r15
[2022-03-04 13:24:54.008] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:24:54.012] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 RX1...
[2022-03-04 13:24:54.251] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:24:54.251] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:25:07.623] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:25:07.627] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 RX2...
[2022-03-04 13:25:07.867] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:25:07.868] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:25:21.289] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:25:21.294] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 TX1...
[2022-03-04 13:25:21.533] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:25:21.533] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:25:34.719] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:25:34.724] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 TX2...
[2022-03-04 13:25:34.962] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:25:34.962] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:25:48.448] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:25:54.226] [ INFO] [ 192.168.0.111] - Setting system information...
[2022-03-04 13:25:59.993] [ INFO] [ 192.168.0.111] - Starting application...
[2022-03-04 13:27:11.429] [ INFO] [ 192.168.0.111] - Done
All 1 update(s) finished successfully.
Example 2
The following options applied:
▪Custom backup folder is set
▪Current configuration is saved
▪Firmware is updated and saved configuration is restored
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip 192.168.0.111 --package c:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2 --backupFolder c:\My_backup
C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip 192.168.0.111 --package C:\Firmwares\mmx6x2-ht_v1.1.5b11.lfp2 --backupFolder C:\My_backup
[2022-03-04 13:06:37.586] [ INFO] [ main] - Device IPs: [192.168.0.111]
[2022-03-04 13:06:39.328] [ INFO] [ main] - All selected devices are available over the network.
[2022-03-04 13:06:39.469] [ INFO] [ main] - All the selected devices are compatible with the specified package.
[2022-03-04 13:06:39.828] [ INFO] [ 192.168.0.111] - Package version: 1.1.5b11
[2022-03-04 13:06:39.849] [ INFO] [ 192.168.0.111] - Creating backup of device settings...
[2022-03-04 13:06:40.646] [ INFO] [ 192.168.0.111] - Switching device into bootload mode...
[2022-03-04 13:06:41.739] [ INFO] [ 192.168.0.111] - Gathering UID information from device...
[2022-03-04 13:06:47.114] [ INFO] [ 192.168.0.111] - UID info - Device IP: 192.168.0.111 Product name: MMX6x2-HT220 Product part number: 91310032 Serial number: 00003188 Hardware version: V11_BAA0 MAC address: A8:D2:36:FF:31:88
[2022-03-04 13:06:47.357] [ INFO] [ 192.168.0.111] - Package version on device: 1.1.4b3 r29
[2022-03-04 13:06:47.906] [ INFO] [ 192.168.0.111] - Updating Firmware of the MCU...
[2022-03-04 13:06:48.145] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s current version on device: 1.1.4b3 r15
[2022-03-04 13:06:48.146] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s version in the package: 1.1.5b2 r15
[2022-03-04 13:07:09.972] [ INFO] [ 192.168.0.111] - [mmx_6x2_ht.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:07:09.980] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 RX1...
[2022-03-04 13:07:10.220] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:07:10.220] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:07:23.599] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:07:23.603] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 RX2...
[2022-03-04 13:07:23.842] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:07:23.842] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:07:36.969] [ INFO] [ 192.168.0.111] - [vs100_rx_cp0_cs5.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:07:36.973] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 TX1...
[2022-03-04 13:07:37.213] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:07:37.214] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:07:50.651] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:07:50.655] [ INFO] [ 192.168.0.111] - Updating Firmware of the VS100 TX2...
[2022-03-04 13:07:50.902] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0
[2022-03-04 13:07:50.902] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63
[2022-03-04 13:08:04.339] [ INFO] [ 192.168.0.111] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM.
[2022-03-04 13:08:10.107] [ INFO] [ 192.168.0.111] - Setting system information...
[2022-03-04 13:08:15.893] [ INFO] [ 192.168.0.111] - Starting application...
[2022-03-04 13:09:28.368] [ INFO] [ 192.168.0.111] - Restoring device settings from the following backup file: C:\My_backup\backup_91310032_00003188_2022-03-04_13-06-40_converted.lw3 ...
[2022-03-04 13:09:35.314] [ INFO] [ 192.168.0.111] - Device settings have been restored
[2022-03-04 13:09:40.533] [ INFO] [ 192.168.0.111] - Done
All 1 update(s) finished successfully.
8.6.9. Exit Codes
There is a return value in all cases, when a command run is finished. Currently, three codes are defined:
|
Code |
Displayed text |
Description |
|
0 |
N/A |
The update performed successfully |
|
1 |
Update error (ErrorCode:1) |
The error happened during the update |
|
2 |
CLI error (ErrorCode:2 |
The error happened before starting the update |
The error line contains further information about the error.
Querying the Exit Code under Windows®
c:\Program Files (x86)\Lightware\Lightware Device Updater V2\echo %errorlevel%
0
Querying the Exit Code under Linux
echo $?
0
So if this value is queried after the update and it is 0, the update performed successfully.
8.7. If the Update is not succesful
▪Restart the process and try the update again.
▪If the device cannot be switched to bootload (firmware update) mode, you can do that manually as written in the Enter bootload mode #bootload section. Please note that backup and restore cannot be performed in this case.
▪If the backup cannot be created for some reason, you will get a message to continue the process without backup or stop the upgrade. A root cause can be that the desired device is already in bootload (firmware update) mode, thus the normal operation mode is suspended and backup cannot be made.
▪If an update is not succesful, the Export log button becomes red. If you press the button, you can download the log file as a ZIP package, which can be sent to Lightware Support if needed. The log files contain useful information about the circumstances to find the root cause.
Usually, if the system seems not to transport the signal as expected, the best strategy for troubleshooting is to check signal integrity through the whole signal chain starting from source side and moving forward to receiver end.
At first, check front panel LEDs and take the necessary steps according to their states. For more information about front and rear panel LEDs of the matrix, refer to the Front View - All Models and the Rear View sections.
Pictogram Legend
|
Section to connections/cabling. |
|
Section to front panel operation. |
|
Section to LDC software. |
|
Section to LW2 protocol commands. |
|
Section to LW3 protocol commands. |
9.1. Use Case Studies
|
Symptom |
Root cause |
Action |
Refer to |
|
|
Video signal |
||||
|
No picture on the video output |
Device(s) not powered properly |
Check the matrix and the other devices if they are properly powered; try to unplug and reconnect them. |
|
|
|
Cable connection problem |
Cables must fit very well, check all the connectors. |
|
||
|
No incoming signal |
No video signal is present on the HDMI/TPS input ports. Check the source device and the HDMI/TPS cables. |
|
||
|
Not the proper video port is the active one |
Check the video crosspoint settings. |
|
||
|
||||
|
||||
|
||||
|
Not the proper interface is the active one |
If the source/display has more connectors, check if the proper interface is selected. |
|||
|
Output port is muted |
Check the mute state of output ports. |
|
||
|
||||
|
||||
|
Display is not able to receive the video format |
Check the emulated EDID and select another (e.g. emulate the display’s EDID on the input port). |
|
||
|
|
||||
|
Image is green or magenta colored |
Wrong colorspace was chosen |
The sink expects RGB color spaced signal, but receives YCbCr. Check if the proper signal type was set on the port properties window of the outputs (DVI / HDMI / Auto) or check the emulated EDIDs and select another one or check the colorspace settings on the sink device. |
|
|
|
|
||||
|
Autoselect doesn't choose the requested input |
Incorrect priority settings |
Check if the autoselect setting is enabled, priority detect mode is selected, needed input is active (not grey) and ticked, priority number text field is not empty, there is no two or more same priority numbers at input ports. Always verify the settings with the Set priorities button. |
|
|
|
|
||||
|
|
||||
|
Symptom |
Root cause |
Action |
Refer to |
|
|
Audio signal |
||||
|
No audio is present on output |
Other audio port is switched to the output |
Check the audio settings of both the input and output ports. |
|
|
|
|
||||
|
||||
|
Output port is muted |
Check the output port properties. |
|
||
|
||||
|
||||
|
Analog audio input/output: volume is set very low |
Check the Analog audio input/output port settings (Volume). |
|
||
|
||||
|
||||
|
Not the corresponding audio sounds |
Other audio port is switched to the output |
Check not only the audio settings of the output port, but the input ports', too. |
|
|
|
|
||||
|
|
||||
|
HDMI output signal contains no audio |
HDMI mode was set to DVI |
Check the properties of the output port and set to HDMI or Auto. |
|
|
|
||||
|
DVI EDID is emulated |
Check the EDID and select an HDMI EDID to be emulated. |
|
||
|
|
||||
|
RS-232 signal |
||||
|
Connected serial device cannot be controlled |
Cable connection problem |
Check the connectors to fit well; check the wiring of the plugs. |
|
|
|
Serial settings are different |
Check the port settings of the matrix and the connected serial device(s). Pay attention to link and/or local ports. |
|
||
|
||||
|
No RS-232 signal on output |
RS-232 data transmission is available between the local RS-232 port and the LAN port (not TPS port). |
Operation mode of the local RS-232 can be Command Injection, and enabling of the CI mode can be also applied. |
|
|
|
|
||||
|
Ethernet |
||||
|
No LAN connection can be established |
Incorrect IP address is set (direct connect) |
Restore the factory default settings (with fix IP). |
|
|
|
||||
|
|
||||
|
||||
|
IP address conflict |
Change the IP address to a not reserved one or enable DHCP if DHCP server exists in the network. |
|
||
|
||||
|
||||
|
Event Manager |
||||
|
Action does not start, although condition is completed |
Too much delay was set. |
Check the delay setting on the event Event Editor window. Try it again with zero delay (do not forget verify with Apply button). |
|
|
|
The event was not verified/ enabled. |
Both Condition and Action (and optionally the Delay) need to be verified by clicking on them. Check if the Event is Enabled on the Events tab. |
|
||
9.2. How to Speed Up the Troubleshooting Process
Lightware’s technical support team is always working hard to provide the fastest support possible. Our team’s response time is one of the best in the industry, and in the toughest of cases we can directly consult with the hardware or software engineer who designed the product to get the information from the most reliable source.
However, the troubleshooting process can be even faster… with your help.
There are certain pieces of information that push us in the right direction to find the root cause of the problem. If we receive most of this information in the first e-mail, or it is gathered at the time when you call us, then there is a pretty high chance that we will be able to respond with the final solution right away.
This information is the following:
▪Schematic (a pdf version is preferred, but a hand drawing is sufficient).
▪Serial number(s) of the device(s) (it is either printed somewhere on the box, or you can query it in the Device Controller software or on the built-in website).
▪Firmware versions of the devices (please note that there may be multiple CPUs or controllers in the device and we need to know all of their firmware versions, a screenshot is the best option).
▪Cable lengths and types (in our experience, it’s usually the cable).
▪Patch panels, gender changers or anything else in the signal path that can affect the transmission.
▪Signal type (resolution, refresh rate, color space, deep color).
▪Emulated EDID(s) (please save them as a file and send it to us).
▪Actions to take in order to re-create the problem (if we cannot reproduce the problem, it is hard for us to find the cause).
▪Photo or video about the problem (‘image noise’ can mean many different things, it’s better if we see it too).
▪Error logs from the Device Controller software.
▪In the case of an Event Manager issue, the event file and/or backup file from the Device Controller software.
The more of the information above you can give us, the better. Please send this information to the Lightware Support Team (support@lightware.com) to speed up the troubleshooting process.
The following sections contain descriptions and useful technical information how the devices work in the background. The content is based on experiences and cases we met in the practice. These sections help to understand features and technical standards like the followings:
10.1. EDID Management
10.1.1. Understanding the EDID
The Extended Display Identification Data (EDID) is the passport of display devices (monitors, TV sets, projectors). It contains information about the capabilities of the display, such as supported resolutions, refresh rates (these are called Detailed Timings), the type and manufacturer of the display device, etc.
After connecting a source to a display (DVI, HDMI, DP), the source reads out the EDID to determine the resolution and refresh rate of the image to be transmitted.
EDID Communication
Most DVI computer displays have a 128-byte-long EDID structure. However, Digital Televisions and HDMI capable displays may have another 128 bytes, which is called E-EDID and defined by CEA (Consumer Electronics Association). This extension contains information about additional Detailed Timings, audio capabilities, speaker allocation and HDMI capabilities. It is important to know that all HDMI capable devices must have CEA extension, but not all devices with CEA extension are HDMI capable.
Common Problems Related to EDID
Problem: “My system consists of the following: a computer, a Lightware device, a WUXGA (1920x1200) LCD monitor, and an SXGA (1280x1024) projector. I would like to see the same image on the monitor and the projector. What EDID should I choose on the Lightware device?”
Solution: If you want to see the image on both displays, you need to select the resolution of the smaller display (in this case SXGA), otherwise the smaller display may not show the higher resolution image.
Problem: “I have changed to a different EDID on an input port of the Lightware device to have a different resolution, but nothing happens.”
Solution: Some graphics cards and video sources read out the EDID only after power-up, and later they do not sense that the EDID has been changed. You need to restart your source to make it read out the EDID again.
Advanced EDID Management
Each DVI sink (e.g. monitors, projectors, plasma displays, etc...) must support the EDID data structure. Source BIOS and operating systems are likely to query the sink using DDC2B protocol to determine what pixel formats and interface are supported. DVI standard uses EDID data structure to identify the monitor type and capabilities. Most DVI sources (VGA cards, set top boxes, etc.) will output DVI signal after accepting the connected sink’s EDID information. In the case of EDID readout failure or missing EDID, the source will not send DVI video signal.
Lightware devices provide the Advanced EDID Management function that helps system integration. The built-in EDID Router can store and emulate factory pre-programmed- and User programmable EDIDs. The EDID of the attached monitors or projectors for each output are stored in a non-volatile memory. This way, the EDID of a monitor is available when the monitor is unplugged or switched off.
Any EDID can be emulated on any input. An emulated EDID can be copied from the EDID router’s memory (static EDID emulation), or from the last attached monitor’s memory (dynamic EDID emulation). For example, the Lightware device can be set up to emulate a sink device, which is connected to one of the outputs. In this case, the EDID automatically changes if the monitor is replaced with another display device (as long as it has a valid EDID).
The EDID is independently programmable for all inputs without affecting each other. All inputs have their own EDID circuit.
INFO:The user is not required to disconnect the video cable to change an EDID as opposed to other manufacturer’s products. The EDID can be changed even if a source is connected to the input and powered ON.
INFO:When the EDID has been changed, the router toggles the HOTPLUG signal for 2 seconds. Some sources do not sense this signal. In such cases, the source device must be restarted or powered OFF and ON again.
Lightware Visual Engineering is a legal HDCP adopter. Several functions have been developed that help solve HDCP related problems. Complex AV systems often have both HDCP and non-HDCP components. The matrix allows transmitting both HDCP encrypted and unencrypted signals. The devices will be still HDCP compliant, as they will never send an encrypted signal to a non-HDCP compliant display device. If an encrypted signal is switched to a non-compliant output, a red screen alert or muted screen will appear.
10.2.1. Protected and Unprotected Content
Many video sources send HDCP protected signal if they detect that the sink is HDCP capable – even if the content is not copyrighted. This can cause trouble if an HDCP capable device is connected between the source and the display. In this case, the content cannot be viewed on non-HDCP capable displays and interfaces like event controllers. Rental and staging technicians often complain about certain laptops, which are always sending HDCP encrypted signals if the receiver device (display, matrix router, etc.) reports HDCP compliancy. However, HDCP encryption is not required all the time (e.g. computer desktop image), certain laptops still do that.
To avoid unnecessary HDCP encryption, Lightware introduced the HDCP enabling/disabling function: the HDCP capability can be disabled in the Lightware device. If HDCP is disabled, the connected source will detect that the sink is not HDCP capable, and turn off authentication.
10.2.2. Disable Unnecessary Encryption
HDCP Compliant Sink
All the devices are HDCP-compliant, no manual setting is required, both protected and unprotected contents are transmitted and displayed on the sink.
Not HDCP-compliant Sink 1.
Non-HDCP compliant sink is connected to the matrix. Some sources (e.g. computers) always send HDCP encrypted signals if the receiver device reports HDCP compliancy, however, HDCP encryption is not required all the time (e.g. computer desktop image). If HDCP is enabled in the matrix, the image will not be displayed on the sink.
Setting the HDCP parameter to Auto on the output port and disable HDCP on the input port, the transmitted signal will not be encrypted if the content is not protected. Thus, non-HDCP compliant sinks will display non-encrypted signal.
Not HDCP-compliant Sink 2.
The layout is the same as in the previous case: non-HDCP compliant display device is connected to the matrix but the source would send protected content with encryption. If HDCP is enabled on the input port of the matrix, the source will send encrypted signal. The sink is not HDCP compliant, and thus it will not display the video signal (but blank/red/muted/etc. screen). If HDCP is disabled on the input port of the matrix, the source will not send the signal. The solution is to replace the display device with an HDCP-capable one.
10.3. Pixel Accurate Reclocking
Signal reclocking is an essential procedure in digital signal transmission. After passing the reclocking circuit, the signal becomes stable, jitter-free, and can be transmitted over more equipment like processors, or event controllers. Without reclocking, sparkles, noise, and jaggies appear on the image.
Lightware’s sophisticated Pixel Accurate Reclocking technology fixes more problems than general TMDS reclocking. It removes not only intra-pair skew, but inter-pair skew as well. The Pixel Accurate Reclocking circuit eliminates the following errors:
Intra-pair skew
Skew between the + and - wires within a differential wire pair (e.g. Data2- and Data2+). It’s caused by different wire lengths or slightly different wire construction (impedance mismatch) in the DVI cable. It results in jitter.
Inter-pair skew
Skew between two differential wire pairs in a cable. It is caused by different wire pair lengths or different number of twists in the DVI cable. Too much inter-pair skew results in color shift in the picture or sync loss.
Jitter
Signal instability in the time domain. The time difference between two signal transitions should be a fixed value, but noise and other effects cause variations.
Noise
Electromagnetic interference between other electronic devices such as mobile phones, motors, etc. and the DVI cable are coupled onto the signal. Too much noise results in increased jitter.
Tables, drawings, guides, technical details as follows:
11.1. Specifications
General
|
Compliance |
CE, UL, UKCA |
|
Electrical safety |
EN 60065:2002 + A1:2006 + A11:2008 + A2:2010 + A12:2011 |
|
EMC compliance (emission) |
EN 55032:2015+A1:2020 |
|
EMC compliance (immunity) |
EN 55035:2017+A11:2020 |
|
RoHS compliance |
EN 63000:2018 |
|
Warranty |
3 years |
|
Cooling |
Cooling fan, air flows from right to left (as viewed from front) |
|
Operating temperature |
0 to +55°C (+32 to +122°F) |
|
Operating humidity |
10% to 90%, non-condensing |
Power
|
Heat dissipation |
120 BTU/h (max.), 85 BTU/h (typ.) |
|
Power source |
100-240 V AC; 50~60 Hz |
|
Power consumption (max) |
120 W |
|
Power over TPS |
DC 48V (IEEE 802.3af) |
Enclosure
|
Front panel buttons |
Yes |
|
Display |
LCD, 2x16 characters |
|
Rack mountable |
Yes, 1U High (rack ears supplied) |
|
Material |
1 mm steel |
|
Dimensions in mm |
442 (482*) W x 43.9 H x 300 D |
|
Dimensions in inch |
17.4 (18.9*) W x 1.72 H x 11.8 D |
|
Weight |
4.8 kg |
* with rack-mounting ears
RS-232 control
|
Serial port connector |
3-pole Phoenix connector |
|
Available Baud rates |
between 4800 and 115200 |
|
Available Data bits |
8 or 9 |
|
Available Parity |
None / Odd / Even |
|
Available Stop bits |
1 / 1.5 / 2 |
Audio/Video ports
|
Crosspoint |
6x2 video – any input(s) to any output(s) |
|
HDCP compliant |
Yes |
TPS input and output ports
|
TPS port connector type |
RJ45 connector |
|
Compliance |
HDBaseT |
|
Transferred signals (TPS) |
Video, Audio, RS-232, Infra-red, Ethernet |
|
Max. video resolutions |
1920x1080@120 Hz, 24 bit; 1600x1200@60 Hz, 36 bit; 3840x2160@30 Hz, 24 bit |
|
Audio formats |
8 ch. PCM, Dolby TrueHD, DTS-HD Master Audio 7.1 |
|
Reclocking |
Pixel Accurate Reclocking |
HDMI input and output ports
|
HDMI port connector type |
19-pole HDMI Type A receptacle |
|
Standard |
DVI 1.0, HDMI 1.4 |
|
Max. video resolutions |
1920x1080@120 Hz, 24 bit; 1600x1200@60 Hz, 36 bit; 3840x2160@30 Hz, 24 bit |
|
Audio formats |
8 channel PCM, Dolby TrueHD, DTS-HD Master Audio 7.1 |
|
Reclocking |
Pixel Accurate Reclocking |
Analog audio input ports
|
Signal transmission |
Balanced and unbalanced audio |
|
Gain |
0 – 21 dB |
|
Volume |
-95 – 0 dB |
Analog audio output ports
|
Signal transmission |
Balanced and unbalanced audio |
|
Gain |
0 – 3 dB |
|
Volume |
-57 – 0 dB |
|
Nominal Differential Output Level |
+4 dBu @ 0 dB Gain |
|
Nominal Differential Output Level |
+7 dBu @ 3 dB Gain |
EDID management
|
EDID emulation |
Yes |
|
EDID memory |
119 factory presets, 12 user-programmable |
INFO:Specifications are subject to change without notice.
11.2. Cable Wiring Guide
11.2.1. Cable Wiring Guide for Serial Data Transmission
The matrix switcher is built with a 3-pole Phoenix connector. See the two examples below of the most common assembling cases.
|
Matrix and a DCE (Data Circuit-terminating Equipment) |
Matrix and a DTE (Data Terminal Equipment) |
|
D-SUB 9 and Phoenix |
D-SUB 9 and Phoenix |
|
|
11.2.2. Audio Cable Wiring Guide
Inputs and outputs of audio devices are symmetric or asymmetric. The main advantage of the symmetric lines is the better protection against the noise, therefore they are widely used in the professional audio industry. Symmetric audio is most often referred to as balanced audio, as opposed to asymmetric, which is referred to as unbalanced audio. Lightware products are usually built with 5-pole Phoenix connectors, so we would like to help users assemble their own audio cables. See the most common cases below.
ATTENTION!Symmetric and asymmetric lines can be linked with passive accessories (e.g. special cables), but in this case half of the line level is lost.
ATTENTION!There are numerous types of regularly used connector and cable types to connect audio devices. Please always make sure that a connector or cable fits your system before use.
ATTENTION!Never join the phase-inverted (negative, cold or -) poles (either right or left) to the ground or to each other on the output side, as this can damage the unit.
INFO:Use a galvanic isolation in case of a ground loop.
For more information about the cable wiring, see the Cable Wiring Guide on our website: www.lightware.com.
From Unbalanced Output to Balanced Input
|
2 x 6.3 (1/4") TS - Phoenix |
2 x RCA - Phoenix |
3.5 (1/8") TRS - Phoenix |
||
|
|
|
From Balanced Output to Unbalanced Input
|
Phoenix - 2 x 6.3 (1/4") TS |
Phoenix - 2 x RCA |
Phoenix - 3.5 (1/8") TRS |
||
|
|
|
From Balanced Output to Balanced Input
|
Phoenix - 2 x 6.3 (1/4") TRS |
Phoenix - 2 x XLR |
2 x 6.3 TRS (1/4") - Phoenix |
||
|
|
|
||
|
2 x XLR - Phoenix |
Phoenix - Phoenix |
|||
|
|
11.3. Mechanical Drawings
Dimensions are in mm.
11.4. Content of the Backup File
The backup file contains numerous settings and parameters saved from the device. When the file is uploaded to a device, the following will be overwritten:
|
Local serial port |
|
RS-232 mode, Control protocol, Baud rate, Data bits, Stop bits, Parity |
|
Port name and CI (Command Injection) port number |
|
Ethernet settings |
|
Enable/Disable on Local, and TPS Link lines |
|
HDMI input port |
|
Audio mode, HDCP setting, Port name |
|
Analog audio input port |
|
Volume, Balance, Gain, Port name |
|
TPS input port |
|
Port names, TPS mode, PoE (enabled / disabled), Ethernet (Enable / Disable) |
|
Audio mode (Embedded / AUX1-4), HDCP setting |
|
RS-232 mode, Control protocol, Baud rate, Data bits, Stop bits, Parity, CI port number |
|
IR input port status, code length, repetition code, CI mode, and CI port number |
|
IR output port status, code length, repetition code, CI mode, and CI port number |
|
HDMI output port |
|
Power +5V mode, Audio mode, HDCP mode, HDMI mode, Port name |
|
Test pattern mode, clock source, and type |
|
Analog audio output port |
|
Volume, Balance, Gain, Mute setting, Port name |
|
TPS output port |
|
Port names, TPS mode, PoE (enabled / disabled), Ethernet (Enable / Disable) |
|
Test pattern mode, clock source, and type |
|
HDCP mode, HDMI mode, Power +5V mode |
|
RS-232 mode, Control protocol, Baud rate, Data bits, Stop bits, Parity, CI port number |
|
IR input port status, code length, repetition code, CI mode, and CI port number |
|
IR output port status, code length, repetition code, CI mode, and CI port number |
|
Network settings |
|
DHCP status (enable / disable) |
|
LW2, LW3 and HTTP port numbers |
|
Static IP address, Network mask, Gateway address |
|
Further settings |
|
Emulated EDID list, User EDID data (U1-U12) |
|
Event manager: All Events’ settings (1-100) |
|
All Presets’ settings (1-6) |
11.5. Input and Output Port Numbering
|
Port name |
Video port no. (LW2) |
Video port no. (LW3) |
Audio port no. |
EDID memory |
RS-232 port no. |
IR port no. |
|
|
Input |
Output |
||||||
|
TPS input #1 |
1 |
I1 |
I1 |
E1 |
P2 |
S1 |
D1 |
|
TPS input #2 |
2 |
I2 |
I2 |
E2 |
P3 |
S2 |
D2 |
|
HDMI input #3 |
3 |
I3 |
I3 |
E3 |
- |
- |
- |
|
HDMI input #4 |
4 |
I4 |
I4 |
E4 |
- |
- |
- |
|
HDMI input #5 |
5 |
I5 |
I5 |
E5 |
- |
- |
- |
|
HDMI input #6 |
6 |
I6 |
I6 |
E6 |
- |
- |
- |
|
HDMI output #1 |
1 |
O1 |
O1 |
D1 |
- |
- |
- |
|
HDMI output #2 |
2 |
O2 |
O2 |
D2 |
- |
- |
- |
|
TPS output #1 * |
3 |
O3 |
O3 |
D3 |
P4 |
S3 |
D3 |
|
TPS output #2 ** |
4 |
O4 |
O4 |
D4 |
P5 |
S4 |
D4 |
|
Analog audio input #1 |
- |
- |
I7 |
- |
- |
- |
- |
|
Analog audio input #2 |
- |
- |
I8 |
- |
- |
- |
- |
|
Analog audio input #3 |
- |
- |
I9 |
- |
- |
- |
- |
|
Analog audio input #4 |
- |
- |
I10 |
- |
- |
- |
- |
|
Analog audio output #1 |
- |
- |
O5 |
- |
- |
- |
- |
|
Analog audio output #2 |
- |
- |
O6 |
- |
- |
- |
- |
|
Local RS-232 |
- |
- |
- |
- |
P1 |
- |
- |
Mirrored outputs: O1-O3 and O2-O4.
* Only on MMX6x2-HT210 and MMX6x2-HT220 devices.
** Only on MMX6x2-HT220 device.
11.6. Maximum Twisted Pair Distances
|
Resolution |
Pixel clock rate |
Cable lengths ( Auto / Longreach TPS mode) |
||
|
CAT5e AWG24 |
CAT7 AWG26** |
CAT7 AWG23 |
||
|
1024x768@60Hz |
65 MHz |
100 m / 130 m* |
90 m / 120 m* |
120 m / 170 m* |
|
1280x720p@60Hz |
73.8 MHz |
|||
|
1920x1080p@60Hz / 24bpp |
148.5 MHz |
|||
|
1920x1200@60Hz |
152.9 MHz |
100 m / NA |
90 m / NA |
120 m / NA |
|
1600x1200@60Hz |
162 MHz |
|||
|
1920x1080@60Hz / 36bpp |
223.6 MHz |
70 m / NA |
70 m / NA |
100 m / NA |
|
3840x2160@30Hz UHD |
297 MHz |
|||
|
4096x2160@30Hz 4K |
297 MHz |
|||
* With Long reach operation mode, which supports pixel clock frequencies up to 148.5 MHz.
** When remote powering is used with AWG26 cables, distances are 20% shorter.
11.7. Factory Default Settings
|
Parameter |
Setting/Value |
|
Network Settings |
|
|
IP address |
192.168.0.100 |
|
Subnet mask |
255.255.255.0 |
|
Static gateway |
192.168.0.1 |
|
LW2 Port number |
10001 |
|
LW3 Port number |
6107 |
|
HTTP Port number |
80 |
|
DHCP |
disabled |
|
TPS and HDMI Port Settings |
|
|
HDCP – on input ports |
Enabled |
|
HDCP – on output ports |
Auto |
|
Output TPS mode (on TPS output ports) |
Auto |
|
Output HDMI mode |
Auto |
|
Power 5V mode |
Auto |
|
No sync screen mode |
Off |
|
No sync screen color |
Bar |
|
No sync screen resolution |
480p |
|
Crosspoint state |
HDMI I3 @ O1 & O3; HDMI I4 @ O2 & O4 |
|
Audio source |
Embedded audio |
|
Autoselect |
Disabled |
|
Autoselect video priority (from 0 to 5) |
I1, I2, I3, I4, I5, I6 |
|
PoE feature |
Enabled |
|
Emulated EDID* |
F47 - Factory (1920x1080@60Hz HDMI) |
|
Analog Audio Port Settings |
|
|
Volume |
0.00 dB |
|
Balance |
50 (center) |
|
Gain |
0.00 dB |
|
RS-232 Settings |
|
|
Control protocol |
LW2 |
|
Baud rate |
57600 |
|
Databits / Parity / Stopbits |
8 / No / 1 |
|
Operation mode (local and link ports) |
CI (Command Injection) |
|
Command Injection port nr. (Local) |
8001 |
|
Command Injection port nr. (TPSIN1) |
8002 |
|
Command Injection port nr. (TPSIN2) |
8003 |
|
Command Injection port nr. (TPSOUT1) |
8004 |
|
Command Injection port nr. (TPSOUT2) |
8005 |
* The default EDID has been changed since firmware 1.1.0. The default EDID for firmware 1.0.0 is D1, dynamic.
|
Mem. |
Resolution |
Type |
|||
|
F1 |
640 x |
480 |
@ 60.00 |
Hz |
D |
|
F2 |
848 x |
480 |
@ 60.00 |
Hz |
D |
|
F3 |
800 x |
600 |
@ 60.32 |
Hz |
D |
|
F4 |
1024 x |
768 |
@ 60.00 |
Hz |
D |
|
F5 |
1280 x |
768 |
@ 50.00 |
Hz |
D |
|
F6 |
1280 x |
768 |
@ 59.94 |
Hz |
D |
|
F7 |
1280 x |
768 |
@ 75.00 |
Hz |
D |
|
F8 |
1360 x |
768 |
@ 60.02 |
Hz |
D |
|
F9 |
1280 x |
1024 |
@ 50.00 |
Hz |
D |
|
F10 |
1280 x |
1024 |
@ 60.02 |
Hz |
D |
|
F11 |
1280 x |
1024 |
@ 75.02 |
Hz |
D |
|
F12 |
1400 x |
1050 |
@ 50.00 |
Hz |
D |
|
F13 |
1400 x |
1050 |
@ 60.00 |
Hz |
D |
|
F14 |
1400 x |
1050 |
@ 75.00 |
Hz |
D |
|
F15 |
1680 x |
1050 |
@ 60.00 |
Hz |
D |
|
F16 |
1920 x |
1080 |
@ 50.00 |
Hz |
D |
|
F17 |
1920 x |
1080 |
@ 60.00 |
Hz |
D |
|
F18 |
2048 x |
1080 |
@ 50.00 |
Hz |
D |
|
F19 |
2048 x |
1080 |
@ 60.00 |
Hz |
D |
|
F20 |
1600 x |
1200 |
@ 50.00 |
Hz |
D |
|
F21 |
1600 x |
1200 |
@ 60.00 |
Hz |
D |
|
F22 |
1920 x |
1200 |
@ 50.00 |
Hz |
D |
|
F23 |
1920 x |
1200 |
@ 59.56 |
Hz |
D |
|
F24 |
2048 x |
1200 |
@ 59.96 |
Hz |
D |
|
F29 |
1920 x |
1080 |
@ 60.00 |
Hz |
Universal |
|
F30 |
1440 x |
480 |
@ 60.05 |
Hz |
H |
|
F31 |
1440 x |
576 |
@ 50.08 |
Hz |
H |
|
F32 |
640 x |
480 |
@ 59.95 |
Hz |
H |
|
F33 |
720 x |
480 |
@ 59.94 |
Hz |
H |
|
F34 |
720 x |
576 |
@ 50.00 |
Hz |
H |
|
F35 |
1280 x |
720 |
@ 50.00 |
Hz |
H |
|
F36 |
1280 x |
720 |
@ 60.00 |
Hz |
H |
|
F37 |
1920 x |
1080 |
@ 50.04 |
Hz |
H |
|
F38 |
1920 x |
1080 |
@ 50.00 |
Hz |
H |
|
F39 |
1920 x |
1080 |
@ 60.05 |
Hz |
H |
|
F40 |
1920 x |
1080 |
@ 60.05 |
Hz |
H |
|
F41 |
1920 x |
1080 |
@ 24.00 |
Hz |
H |
|
F42 |
1920 x |
1080 |
@ 25.00 |
Hz |
H |
|
F43 |
1920 x |
1080 |
@ 30.00 |
Hz |
H |
|
F44 |
1920 x |
1080 |
@ 50.00 |
Hz |
H |
|
F45 |
1920 x |
1080 |
@ 60.00 |
Hz |
H |
|
F46 |
1920 x |
1080 |
@ 60.00 |
Hz |
H |
|
F47 |
1920 x |
1080 |
@ 60.00 |
Hz |
Universal |
|
F48 |
1920 x |
1080 |
@ 60.00 |
Hz |
Universal |
|
F49 |
1920 x |
1080 |
@ 60.00 |
Hz |
Universal |
|
F90 |
1920 x |
2160 |
@ 59.99 |
Hz |
D |
|
F91 |
1024 x |
2400 |
@ 60.01 |
Hz |
D |
|
F92 |
1920 x |
2400 |
@ 59.97 |
Hz |
D |
|
F93 |
2048 x |
2400 |
@ 59.98 |
Hz |
D |
|
F94 |
2048 x |
1536 |
@ 60.00 |
Hz |
D |
|
F95 |
2048 x |
1536 |
@ 75.00 |
Hz |
D |
|
F96 |
2560 x |
1600 |
@ 59.86 |
Hz |
D |
|
F97 |
3840 x |
2400 |
@ 24.00 |
Hz |
D |
|
F98 |
1280 x |
720 |
@ 60.00 |
Hz |
H |
|
F99 |
1920 x |
1080 |
@ 60.00 |
Hz |
H |
|
F100 |
1024 x |
768 |
@ 60.00 |
Hz |
H |
|
F101 |
1280 x |
1024 |
@ 50.00 |
Hz |
H |
|
F102 |
1280 x |
1024 |
@ 60.02 |
Hz |
H |
|
F103 |
1280 x |
1024 |
@ 75.02 |
Hz |
H |
|
F104 |
1600 x |
1200 |
@ 50.00 |
Hz |
H |
|
F105 |
1600 x |
1200 |
@ 60.00 |
Hz |
H |
|
F106 |
1920 x |
1200 |
@ 59.56 |
Hz |
H |
|
F107 |
2560 x |
1440 |
@ 59.95 |
Hz |
H |
|
F108 |
2560 x |
1600 |
@ 59.86 |
Hz |
H |
|
F109 |
3840 x |
2400 |
@ 24.00 |
Hz |
H |
|
F110 |
3840 x |
2160 |
@ 24.00 |
Hz |
H |
|
F111 |
3840 x |
2160 |
@ 25.00 |
Hz |
H |
|
F112 |
3840 x |
2160 |
@ 30.00 |
Hz |
H |
|
F118 |
3840 x |
2160 |
@ 30.00 |
Hz |
Universal |
|
F119 |
3840 x |
2160 |
@ 30.00 |
Hz |
Universal |
|
F120 |
3840 x |
2160 |
@ 60.00 |
Hz |
H |
Legend
D: DVI EDID
H: HDMI EDID
H3D: HDMI EDID with 3D support
U: Universal EDID
Please note that minor changes in the factory EDID list may be applied in the later firmware versions.
11.9. Applied Ports (Network Settings)
The following ports are necessary to pass via a network switch/firewall for proper working between the device and the softwares:
|
Purpose/function |
Affected software |
Protocol |
Port nr. |
|
Firmware update TFTP |
LDU2 |
UDP |
69 |
|
UDP |
49990 |
||
|
UDP |
49995 |
||
|
Device Discovery |
LDC |
UDP |
224.0.0.251:5353 |
|
Remote IP |
LDC |
UDP |
230.76.87.82:37421 |
|
Find me (LMDMP) |
- |
UDP |
230.76.87.82:37422 |
|
LW2 protocol |
- |
TCP |
10001 |
|
LW3 protocol |
- |
TCP |
6107 |
|
HTTP port |
- |
TCP |
80 |
|
RS-232 command injection |
- |
TCP |
8001 |
|
IR command injection |
- |
TCP |
9001, 9002 |
The list below shows the released firmware packages with important notes.
v1.2.0b2
Release date: 2023-02-09
Bugfix:
▪Fixed a bug which prevented the LW3 "switch" method to disconnect an output from the input connected.
v1.1.5b11
Release date: 2020-02-19
Bugfix:
▪Manufacturing support.
v1.1.4b3
Release date: 2018-06-18
Bugfix:
▪RS-232 parity settings fixed.
v1.1.0b1
Release date: 2017-07-19
New feature:
▪Audio can be embedded from the analog audio ports and the embedded audio can be copied the output ports even if there is no signal on the output port.
Bugfix:
▪After factory reset The mmx6x2 booted too long, which caused that on the LCD screen there was nothing for a long time.
▪Minor bug fixes.
This user's manual contains keywords with hashtag (#) to help you to find the relevant information as quick as possible.
The format of the keywords is the following:
#<keyword>
The usage of the keywords: use the Search function (Ctrl+F / Cmd+F) of your PDF reader application, type the #(hashtag) character and the wished keyword.
The #new special keyword indicates a new feature/function that has just appeared in the latest firmware or software version.
Example
#dhcp
This keyword is placed at the DHCP (dynamic IP address) setting in the front panel operation, the Lightware Device Controller (LDC) and the LW3 programmer's reference section.
The following list contains all hashtag keywords placed in the document with a short description belonging to them. The list is in alphabetical order by the hashtag keywords.
|
Hashtag Keyword |
Description |
|
#advancedaudio |
Advanced audio settings |
|
#advancedview |
Advanced view / Terminal window |
|
#analogaudio |
Analog audio related settings |
|
#autoselect |
Autoselect feature settings |
|
#autotakemode |
Autotake mode |
|
#backup |
Configuration cloning (backup) |
|
#balance |
Balance (for analog audio) setting |
|
#bootload |
Bootload mode setting |
|
#buttonlock |
Front panel button lock setting |
|
#cablediagnostics |
Cable diagnostics tool in LDC |
|
#commandinjection |
RS-232 command injection settings |
|
#configurationcloning |
Configuration cloning (backup) |
|
#crosspoint |
Crosspoint switch setting |
|
#devicelabel |
Device label |
|
#dhcp |
Dynamic IP address (DHCP) setting |
|
#diagnostic |
Failure diagnostic related tool/information |
|
#edid |
EDID related settings |
|
#eventmanager |
Event manager |
|
#factory |
Factory default settings |
|
#firmwareversion |
Firmware version query |
|
#framedetector |
Frame detector in LDC |
|
#hdcp |
HDCP-encryption related setting |
|
#infra |
Infrared port related settings |
|
#infrared |
Infrared port related settings |
|
#ipaddress |
IP address related settings |
|
#label |
Device label |
|
#lock |
Port lock setting |
|
#lockbutton |
Front panel button lock setting |
|
#log |
System log |
|
#message |
Message sending via communication ports |
|
#mute |
Port mute setting |
|
#network |
Network (IP address) related settings |
|
#nosyncscreen |
Test pattern (no sync screen) settings |
|
#portstatus |
Source/destination port status query |
|
#producttype |
Product type query |
|
#protocol |
RS-232 protocol setting |
|
#reboot |
Restarting the device |
|
#restart |
Restarting the device |
|
#rs-232 |
RS-232 related settings |
|
#rs232 |
RS-232 related settings |
|
#serial |
RS-232 related settings |
|
#serialnumber |
Serial number query |
|
#signaltype |
HDMI/DVI signal type setting |
|
#switch |
Crosspoint switch setting |
|
#systemlog |
System log |
|
#terminal |
Advanced view / Terminal window |
|
#testpattern |
Test pattern (no sync screen) settings |
|
#tpsmode |
TPS (HDBaseT) mode setting |
|
#unlock |
Port unlock setting |
|
#unmute |
Port unmute setting |
|
#volume |
Volume (for analog audio) setting |
11.12. Further Information
Limited Warranty Statement
1. Lightware Visual Engineering PLC (Lightware) warrants to all trade and end user customers that any Lightware product purchased will be free from manufacturing defects in both material and workmanship for three (3) years from purchase unless stated otherwise below. The warranty period will begin on the latest possible date where proof of purchase/delivery can be provided by the customer. In the event that no proof can be provided (empty ‘Date of purchase’ field or a copy of invoice), the warranty period will begin from the point of delivery from Lightware.
1.1. 25G and MODEX product series will be subject to a seven (7) year warranty period under the same terms as outlined in this document.
1.2. If during the first three (3) months of purchase, the customer is unhappy with any aspect of a Lightware product, Lightware will accept a return for full credit.
1.3. Any product that fails in the first six (6) months of the warranty period will automatically be eligible for replacement and advanced replacement where available. Any replacements provided will be warranted for the remainder of the original unit’s warranty period.
1.4. Product failures from six (6) months to the end of the warranty period will either be repaired or replaced at the discretion of Lightware. If Lightware chooses to replace the product, then the replacement will be warranted for the remainder of the original unit’s warranty period.
2. The above-stated warranty and procedures will not apply to any product that has been:
2.1. Modified, repaired or altered by anyone other than a certified Lightware engineer unless expressly agreed beforehand.
2.2. Used in any application other than that for which it was intended.
2.3. Subjected to any mechanical or electrical abuse or accidental damage.
2.4. Any costs incurred for repair/replacement of goods that fall into the above categories (2.1., 2.2., 2.3.) will be borne by the customer at a pre-agreed figure.
3. All products to be returned to Lightware require a return material authorization number (RMA) prior to shipment, and this number must be clearly marked on the box. If an RMA number is not obtained or is not clearly marked on the box, Lightware will refuse the shipment.
3.1. The customer will be responsible for in-bound and Lightware will be responsible for out-bound shipping costs.
3.2. Newly repaired or replaced product's will be warranted to the end of the originally purchased product's warranty period.
Document Revision History
|
Rev. |
Release date |
Changes |
Editor |
|
1.0 |
12-11-2015 |
Initial version |
Laszlo Zsedenyi |
|
... |
|||
|
3.2 |
22-11-2018 |
General updates, updated LW3 programmer's reference chapter |
Tamas Forgacs |
|
3.3 |
13-03-2020 |
Firmware update process changed, LDU2 SW introduced. |
Laszlo Zsedenyi |
|
3.4 |
29-03-2022 |
TPS LED operation updated; infrared operation corrected; CLI update added; minor corrections |
Nikolett Keindl |
|
3.5 |
08-07-2022 |
Box contents information updated - CATx cross cable is no longer supplied |
Nikolett Keindl |
|
3.6 |
16-11-2022 |
Minor corrections for HTML export |
Nikolett Keindl |
|
3.7 |
05-12-2022 |
Minor correction of incorrect switching information using LW3 protocol |
Nikolett Keindl |
|
3.8 |
08-02-2023 |
Minor correction of incorrect switching information using LW3 protocol |
Nikolett Keindl |
|
3.9 |
08-06-2023 |
Minor corrections |
Nikolett Keindl |
|
3.10 |
12-12-2023 |
Specifications updated |
Nikolett Keindl |
Contact Us
+36 1 255 3800
+36 1 255 3810
Lightware Visual Engineering PLC.
Peterdy 15, Budapest H-1071, Hungary
©2024 Lightware Visual Engineering. All rights reserved. All trademarks mentioned are the property of their respective owners. Specifications subject to change without notice.