Lightware HDMI-TPS-TX210, HDMI-TPS-TX220, DP-TPS-TX210, DP-TPS-TX220, DVI-HDCP-TPS-TX210 User Manual
...Page 1
HDMI-TPS-TX210
HDMI-TPS-TX220
DVI-HDCP-TPS-TX210
DVI-HDCP-TPS-TX220
DP-TPS-TX210
DP-TPS-TX220
SW4-TPS-TX240
User’s Manual
Page 2
Page 3
HDMI-TPS-TX200 series
User’s Manual
SAFETY INSTRUCTIONS
Class II apparatus construction.
The equipment should be operated only from the power source indicated on the product.
To disconnect the equipment safely from power, remove the power cord from the rear of the equipment,
or from the power source. The MAINS plug is used as the disconnect device, the disconnect device
shall remain readily operable.
There are no user-serviceable parts inside of the unit. Removal of the cover will expose dangerous
voltages. To avoid personal injury, do not remove the cover. Do not operate the unit without the cover
installed.
The apparatus shall not be exposed to dripping or splashing and that no objects filled with liquids, such
as vases, shall be placed on the apparatus. No naked flame sources, such as lighted candles, should
be placed on the apparatus.
The appliance must be safely connected to multimedia systems. Follow instructions described in this
manual.
Ventilation
For the correct ventilation and avoid overheating ensure enough free space around the appliance. Do
not cover the appliance, let the ventilation holes free and never block or bypass the ventilators (if any).
WARNING
To prevent injury, the apparatus is recommended to securely attach to the floor/wall or mount in
accordance with the installation instructions.
WEEE ( Waste Electrical & Electronic Equipment )
Correct Disposal of This Product
This marking shown on the product or its literature, indicates that it should not be
disposed with other household wastes at the end of its working life. To prevent possible
harm to the environment or human health from uncontrolled waste disposal, please
separate this from other types of wastes and recycle it responsibly to promote the
sustainable reuse of material resources.
Household users should contact either the retailer where they purchased this product,
or their local government office, for details of where and how they can take this item for
environmentally safe recycling.
Business users should contact their supplier and check the terms and conditions of the purchase
contract. This product should not be mixed with other commercial wastes for disposal.
Section 1. Introduction Page 3 / 122
Page 4
DECLARATION OF CONFORMITY
We,
Lightware Kft. 1071 Budapest Peterdy str. 15 HUNGARY
as manufacturer declare, that the products
HDMI-TPS-TX210
HDMI-TPS-TX220
DVI-HDCP-TPS-TX210
DVI-HDCP-TPS-TX220
DP-TPS-TX210
DP-TPS-TX220
SW4-TPS-TX240
( Computer Monitor Extender )
in accordance with the EMC Directive 2004/108/EC and the Low Voltage Directive
2006/95/EEC are in conformity with the following standards:
EMI/EMC ...................................... EN 55022 Class B
Safety ........... UL, CUL, GS, CR, RCM, PSE, Class II
Date: 04 March 2015
Name: Gergely Vida ( Managing Director )
Signed:
Page 4 / 122 Section 1. Introduction
Page 5
HDMI-TPS-TX200 series
TABLE OF CONTENTS
1. INTRODUCTION .................................................................................................................... 10
1.1. BOX CONTENTS................................................................................................................. 10
1.2. DESCRIPTION.................................................................................................................... 10
1.3. MODEL COMPARISON ........................................................................................................ 11
1.4. COMPATIBLE DEVICES ....................................................................................................... 11
1.5. TYPICAL APPLICATION ....................................................................................................... 11
1.6. FEATURES ........................................................................................................................ 12
2. CONTROLS AND CONNECTIONS ....................................................................................... 13
2.1. FRONT VIEW ..................................................................................................................... 13
2.2. FRONT VIEW LEGEND......................................................................................................... 15
2.3. REAR VIEW ....................................................................................................................... 16
2.4. REAR VIEW LEGEND .......................................................................................................... 18
2.5. ELECTRICAL CONNECTIONS ............................................................................................... 19
2.5.1. DVI inputs and outputs............................................................................................ 19
2.5.2. HDMI inputs and outputs ........................................................................................ 19
2.5.3. DisplayPort input ..................................................................................................... 20
2.5.4. TPS output connector ............................................................................................. 20
2.5.5. Ethernet port ........................................................................................................... 21
2.5.6. DC +12V connection ............................................................................................... 21
2.5.7. RS-232 connector ................................................................................................... 21
2.5.8. Audio input .............................................................................................................. 22
2.5.9. GPIO – General purpose input/output ports ........................................................... 22
2.5.10. IR connector ............................................................................................................ 22
User’s Manual
3. TECHNOLOGIES ................................................................................................................... 23
3.1. BASICS ............................................................................................................................. 23
3.1.1. Common problems related to EDID ........................................................................ 23
3.2. ADVANCED EDID MANAGEMENT ........................................................................................ 24
3.3. HDCP MANAGEMENT ........................................................................................................ 24
3.3.1. Protected and unprotected content ......................................................................... 24
3.3.2. Real life examples ................................................................................................... 25
4. INSTALLATION ..................................................................................................................... 26
4.1. MOUNTING ....................................................................................................................... 26
4.2. REMOTE POWERING (POE) ................................................................................................ 26
4.3. CONNECTING DEVICES ...................................................................................................... 26
4.3.1. Connecting steps – using local PSU ....................................................................... 26
4.3.2. Connecting steps – using power injector (TPS-PI-1P1) ......................................... 27
5. FRONT PANEL OPERATIONS ............................................................................................. 28
5.1. INPUT PORT SELECTION ..................................................................................................... 28
5.1.1. Direct selection on SW4-TPS-TX240 (video input port) ......................................... 28
5.1.2. Audio embedding – allowed connections ............................................................... 28
5.1.3. Autoselect – First detect mode ............................................................................... 29
5.1.4. Autoselect – Last detect mode ............................................................................... 30
5.1.5. Autoselect – Static mode (available only at Audio crosspoint) ............................... 30
5.1.6. Autoselect – Priority detect mode ........................................................................... 31
5.2. SPECIAL FUNCTIONS ......................................................................................................... 32
5.2.1. Control lock ............................................................................................................. 32
5.2.2. Programmable Show me button ............................................................................. 32
5.2.3. Reset to factory default settings ............................................................................. 32
5.2.4. Enable DHCP IP address ....................................................................................... 33
5.2.5. Entering bootload mode .......................................................................................... 33
5.3. IR INTERFACE ................................................................................................................... 33
5.4. GENERAL PURPOSE INPUT/OUTPUT PORTS ......................................................................... 33
5.5. RS-232 INTERFACE .......................................................................................................... 34
5.5.1. Control mode .......................................................................................................... 34
Section 1. Introduction Page 5 / 122
Page 6
5.5.2. Pass-through mode ................................................................................................. 35
5.5.3. Command injection mode ....................................................................................... 35
6. SOFTWARE CONTROL – USING LIGHTWARE DEVICE CONTROLLER (LDC) .............. 36
6.1. STEPS OF THE INSTALLATION IN CASE OF WINDOWS OS ...................................................... 36
6.2. STEPS OF THE INSTALLATION IN CASE OF MAC OS X ........................................................... 38
6.3. LDC UPGRADE ................................................................................................................. 38
6.4. ESTABLISHING THE CONNECTION ....................................................................................... 39
6.5. CROSSPOINT MENU ........................................................................................................... 40
6.6. PORT PROPERTIES AND SETTINGS ...................................................................................... 41
6.6.1. Frame detector (on video input ports) ..................................................................... 42
6.6.2. Analog audio port properties ................................................................................... 42
6.6.3. TPS output port properties and mode settings ....................................................... 43
6.7. EDID MENU ...................................................................................................................... 46
6.7.1. Sources and Destinations ....................................................................................... 46
6.7.2. Changing emulated EDID ....................................................................................... 47
6.7.3. Learning an EDID ................................................................................................... 47
6.7.4. Exporting an EDID .................................................................................................. 47
6.7.5. Importing an EDID .................................................................................................. 47
6.7.6. Deleting EDID(s) ..................................................................................................... 47
6.7.7. EDID info window .................................................................................................... 48
6.7.8. Editing an EDID ...................................................................................................... 48
6.7.9. Creating an EDID .................................................................................................... 49
6.8. CONTROL MENU ................................................................................................................ 50
6.8.1. RS-232 tab .............................................................................................................. 50
6.8.2. GPIO tab ................................................................................................................. 51
6.8.3. Ethernet tab ............................................................................................................ 51
6.9. EVENT MANAGER .............................................................................................................. 51
6.9.1. The event area ........................................................................................................ 52
6.9.2. Wizard mode ........................................................................................................... 53
6.9.3. Advanced mode ...................................................................................................... 56
6.9.4. Save, load or clear an event ................................................................................... 57
6.10. SETTINGS MENU ................................................................................................................ 58
6.10.1. Status tab ................................................................................................................ 58
6.10.2. Network tab ............................................................................................................. 58
6.10.3. Backup tab .............................................................................................................. 59
6.10.4. Function buttons ..................................................................................................... 60
6.11. ADVANCED VIEW ............................................................................................................... 60
7. LW2 PROGRAMMER’S REFERENCE ................................................................................. 61
7.1. LW2 PROTOCOL DESCRIPTION ........................................................................................... 61
7.2. GENERAL LW2 COMMANDS ............................................................................................... 61
7.2.1. View product type ................................................................................................... 61
7.2.2. Query control protocol............................................................................................. 61
7.2.3. View firmware version of the CPU .......................................................................... 62
7.2.4. Connection test ....................................................................................................... 62
7.2.5. View serial number ................................................................................................. 62
7.2.6. Compile time ........................................................................................................... 62
7.2.7. View installed board(s)............................................................................................ 62
7.2.8. View firmware for all controllers’ ............................................................................. 62
7.2.9. Restart the device ................................................................................................... 63
7.2.10. Query health status ................................................................................................. 63
7.2.11. Restore factory default settings .............................................................................. 63
7.3. PORT AND CROSSPOINT SETTINGS ..................................................................................... 63
7.3.1. Switch one input to one output ............................................................................... 63
7.3.2. Mute specified output .............................................................................................. 64
7.3.3. Unmute specified output ......................................................................................... 64
7.3.4. Lock the output ....................................................................................................... 64
7.3.5. Unlock the output .................................................................................................... 64
7.3.6. View connection state on the output ....................................................................... 65
7.3.7. View crosspoint size ............................................................................................... 65
Page 6 / 122 Section 1. Introduction
Page 7
HDMI-TPS-TX200 series
User’s Manual
7.3.8. Query video Autoselect mode ................................................................................. 65
7.3.9. Change video Autoselect mode .............................................................................. 66
7.3.10. Query audio Autoselect mode ................................................................................ 66
7.3.11. Change audio Autoselect mode .............................................................................. 66
7.3.12. Query the video input port priority ........................................................................... 67
7.3.13. Change video input priority ..................................................................................... 67
7.3.14. Query audio input port priority ................................................................................ 67
7.3.15. Change audio input priority ..................................................................................... 68
7.3.16. Batch switch outputs ............................................................................................... 68
7.4. RS-232 PORT CONFIGURATION .......................................................................................... 69
7.4.1. Query the RS-232 mode ......................................................................................... 69
7.4.2. Change RS-232 mode ............................................................................................ 69
7.4.3. Query the RS-232 port settings .............................................................................. 69
7.4.4. Change RS-232 port settings ................................................................................. 70
7.4.5. Query the RS-232 protocol ..................................................................................... 70
7.4.6. Change RS-232 protocol ........................................................................................ 71
7.5. NETWORK CONFIGURATION ............................................................................................... 71
7.5.1. Query the current IP status ..................................................................................... 71
7.5.2. Query the IP address .............................................................................................. 71
7.5.3. Set the IP address .................................................................................................. 72
7.5.4. Query the subnet mask ........................................................................................... 72
7.5.5. Set the subnet mask ............................................................................................... 72
7.5.6. Query the gateway address .................................................................................... 72
7.5.7. Set the gateway address ........................................................................................ 72
7.5.8. Query the TCP/IP port ............................................................................................ 73
7.5.9. Set the TCP/IP port ................................................................................................. 73
7.5.10. Query the status of Ethernet ports .......................................................................... 73
7.5.11. Set the status of Ethernet ports .............................................................................. 73
7.6. GPIO SETTINGS................................................................................................................ 74
7.6.1. Query the state of a GPIO pin ................................................................................ 74
7.6.2. Set the state of a GPIO pin ..................................................................................... 74
7.7. LW2 COMMANDS – QUICK SUMMARY ................................................................................. 75
8. LW3 PROGRAMMERS’ REFERENCE ................................................................................. 77
8.1. OVERVIEW ........................................................................................................................ 77
8.1.1. Elements of the tree structure ................................................................................. 77
8.1.2. Escaping ................................................................................................................. 79
8.1.3. Error messages ....................................................................................................... 80
8.1.4. Prefix summary ....................................................................................................... 80
8.2. THE TREE STRUCTURE OF THE TRANSMITTER ...................................................................... 80
8.3. LW3 COMMANDS .............................................................................................................. 81
8.3.1. Get command ......................................................................................................... 81
8.3.2. Set command .......................................................................................................... 83
8.3.3. Invocation ................................................................................................................ 83
8.3.4. Manual .................................................................................................................... 84
8.3.5. Signature ................................................................................................................. 84
8.3.6. Subscription ............................................................................................................ 85
8.3.7. Notifications about the changes of the properties .................................................. 86
8.4. MEDIA LAYER PROPERTIES ................................................................................................ 87
8.4.1. SublayerCount ........................................................................................................ 87
8.4.2. PortCount ................................................................................................................ 87
8.4.3. PortMap .................................................................................................................. 87
8.4.4. ActiveSublayerMask ............................................................................................... 87
8.4.5. P1-P7 – port numbers ............................................................................................. 87
8.5. VIDEO PORT AND CROSSPOINT SETTINGS ........................................................................... 87
8.5.1. Query the video crosspoint setting ......................................................................... 87
8.5.2. Query the status of source ports ............................................................................. 88
8.5.3. Switching video input .............................................................................................. 88
8.5.4. Query the video Autoselect settings ....................................................................... 89
8.5.5. Change the Autoselect mode ................................................................................. 89
8.5.6. Query the input port priority .................................................................................... 90
Section 1. Introduction Page 7 / 122
Page 8
8.5.7. Changing the input port priority ............................................................................... 90
8.5.8. Mute an input port ................................................................................................... 90
8.5.9. Unmute an input port .............................................................................................. 91
8.5.10. Lock an input port ................................................................................................... 91
8.5.11. Unlock an input port ................................................................................................ 91
8.5.12. Mute the output ....................................................................................................... 91
8.5.13. Unmute the output .................................................................................................. 91
8.5.14. Lock the output ....................................................................................................... 92
8.5.15. Unlock the output .................................................................................................... 92
8.6. AUDIO PORT AND CROSSPOINT SETTINGS ........................................................................... 92
8.6.1. Query the audio crosspoint setting ......................................................................... 92
8.6.2. Switching audio input .............................................................................................. 92
8.6.3. Query the audio Autoselect setting ......................................................................... 93
8.6.4. Change the audio Autoselect setting ...................................................................... 93
8.7. RS-232 PORT CONFIGURATION .......................................................................................... 94
8.7.1. Protocol setting ....................................................................................................... 94
8.7.2. BAUD rate setting ................................................................................................... 94
8.7.3. Databit setting ......................................................................................................... 95
8.7.4. Stopbits setting ....................................................................................................... 95
8.7.5. Parity setting ........................................................................................................... 95
8.7.6. RS-232 operation mode .......................................................................................... 95
8.8. NETWORK CONFIGURATION ............................................................................................... 96
8.8.1. Query the DHCP state ............................................................................................ 96
8.8.2. Change the DHCP state ......................................................................................... 96
8.8.3. Query the IP address .............................................................................................. 96
8.8.4. Change the IP address (static) ............................................................................... 96
8.8.5. Query the subnet mask ........................................................................................... 96
8.8.6. Change the subnet mask (static) ............................................................................ 97
8.8.7. Query the gateway address .................................................................................... 97
8.8.8. Change the gateway address (static) ..................................................................... 97
8.9. GPIO SETTINGS................................................................................................................ 97
8.9.1. Set the direction of a GPIO pin ............................................................................... 97
8.9.2. Set the output value of a GPIO pin ......................................................................... 97
8.9.3. Toggle the value of a GPIO pin .............................................................................. 98
8.10. EVENT SETTINGS (CONDITIONS AND ACTIONS) .................................................................... 98
8.10.1. Set the source node (condition) .............................................................................. 98
8.10.2. Set the source property (condition) ......................................................................... 98
8.10.3. Set the value of the source property (condition) ..................................................... 99
8.10.4. Set the target node (action) .................................................................................... 99
8.10.5. Set the target property (action) ............................................................................... 99
8.10.6. Set the value of the target property (action) ........................................................... 99
8.11. EDID MANAGEMENT ........................................................................................................ 100
8.11.1. Query the emulated EDIDs ................................................................................... 100
8.11.2. Query the validity of a dynamic EDID ................................................................... 100
8.11.3. Query a user EDID header ................................................................................... 100
8.11.4. Emulating an EDID to an input port ...................................................................... 100
8.11.5. Copy an EDID to user memory ............................................................................. 101
8.11.6. Deleting an EDID from user memory .................................................................... 101
8.11.7. Resetting emulated EDIDs ................................................................................... 101
8.12. LW3 COMMANDS – QUICK SUMMARY ............................................................................... 102
9. FIRMWARE UPGRADE – USING LIGHTWARE DEVICE UPDATER (LDU) .................... 104
9.1. ABOUT THE FIRMWARE PACKAGE (LFP FILE) ..................................................................... 104
9.2. SHORT INSTRUCTIONS ..................................................................................................... 104
9.3. INSTALLING LIGHTWARE DEVICE UPDATER (LDU)............................................................. 104
9.3.1. Windows install ..................................................................................................... 104
9.3.2. Mac OS X install ................................................................................................... 107
9.3.3. Upgrading the LDU ............................................................................................... 107
9.4. DETAILED INSTRUCTIONS ................................................................................................. 107
9.4.1. Establish the connection between the computer and the device(s) ..................... 107
9.4.2. Start the LDU and follow the instructions.............................................................. 108
Page 8 / 122 Section 1. Introduction
Page 9
HDMI-TPS-TX200 series
User’s Manual
10. TROUBLESHOOTING ......................................................................................................... 113
11. APPENDIX ........................................................................................................................... 115
11.1. SPECIFICATIONS ............................................................................................................. 115
11.2. MECHANICAL DRAWINGS.................................................................................................. 117
11.3. MAXIMUM TWISTED PAIR CABLE DISTANCES ...................................................................... 118
11.4. INPUT/OUTPUT PORT NUMBERING ..................................................................................... 118
11.5. FACTORY DEFAULT SETTINGS .......................................................................................... 120
11.6. FACTORY EDID LIST ....................................................................................................... 121
12. VERSION APPLICABILITY ................................................................................................. 122
13. WARRANTY ........................................................................................................................ 122
14. DOCUMENT REVISION HISTORY ..................................................................................... 122
Section 1. Introduction Page 9 / 122
Page 10
1. Introduction
Transmitter unit
+12V DC adaptor with
interchangeable plugs
Phoenix® Combicon
3-pole connector
Infrared transmitter with
3.5 mm TS male connector
Phoenix® Combicon
8-pole connector *
Thank You for choosing Lightware HDMI-TPS-TX200 series transmitter. The products have
HDBaseTTM integration with additional Lightware developments. HDMI-TPS devices
transmit digital video at a resolution up to 4K, audio and control up to 170 m distance over
a single CAT cable. The transmitters are compatible with Lightware TPS matrix boards and
other TPS products.
1.1. Box contents
* Only for the following models: HDMI-TPS-TX220, DVI-HDCP-TPS-TX220, DP-TPS-TX220,
SW4-TPS-TX240.
1.2. Description
This transmitter family was designed to extend digital video signals (e.g. HDMI 1.4 and
DP 1.1) and audio signals (analog stereo audio from local input or embedded 7.1 HBR
audio). Video signals with HDCP encryption are also supported. Many combination of the
audio/video signals are available to transmit.
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 bi-directional and transparent IR, RS-232 and Ethernet transmission.
Furthermore, the IR and RS-232 connection supports command injection, allowing them to
send any IR or RS-232 control command directly from the LAN connection.
PoE-compatible remote powering (Power over Ethernet) is available through a single CAT
cable, but local power supply can also be used. The device can be mounted on a rack shelf
or used standalone. HDMI-TPS-TX200 series is compatible with both the HDBaseTTM
extenders and matrix switchers.
Advanced models contain an 8-pole Phoenix® connector with user-configurable General
Purpose Input and Output pins. Using the built-in Event manager with the GPIO pins, many
controlling functions can be established in a simple way.
Page 10 / 122 Section 1. Introduction
Page 11
1.3. Model comparison
Video ports
Audio
port
Interface ports
HDMI
input
DVI-I
input
DP
input
HDMI
output
DVI-I
output
Jack
3.5 in
Ethernet
Infra
RS-232
GPIO
HDMI-TPS-TX210
-
- -
-
-
HDMI-TPS-TX220
-
-
-
DVI-HDCP-TPS-TX210
-
-
-
-
-
DVI-HDCP-TPS-TX220
-
-
-
DP-TPS-TX210
-
-
-
-
-
DP-TPS-TX220
-
-
-
SW4-TPS-TX240
-
The available models have different features depending on the design. Following table
contains the most important differences of the models:
HDMI-TPS-TX200 series
User’s Manual
1.4. Compatible devices
The transmitters are compatible with the following receivers and input boards:
MX modular matrix frames with MX-TPS-IB
HDMI-TPS-RX90
DVI-HDCP-TPS-RX95
HDMI-TPS-RX95
Info: The remote power feature of TPS-RX95 receivers differs from the HDMI-TPS-TX200 family
thus RX95 can be remote powered only by TX95 transmitter. HDMI-TPS-TX200 family
contains PoE-compatible remote power function, TX/RX95 family is not PoE-compatible.
1.5. Typical application
Table 1-1. Features of HDMI-TPS-TX200 series
Section 1. Introduction Page 11 / 122
Figure 1-1. A stand-alone application with an HDMI-TPS-RX95 receiver
Page 12
1.6. Features
Certain features depend on the configuration of the model. For more information about the
models see section 1.3 on page 11.
3D and 4K support – High bandwidth allows extension of resolutions up to 4K and
even 3D sources and displays are supported.
Signal transmission up to 170 m – Video and audio signal transmission (DVI,
HDMI or DisplayPort, and Ethernet + RS-232 + Infra-Red over a single
CAT5e…CAT7e cable.
Various audio and video connectors – DVI-I, HDMI, DisplayPort, Stereo jack.
GPIO control port – 7 GPIO pins operating at TTL digital signal levels and can be
controlled with both LW2 and LW3 commands.
HDCP compliant – HDMI-TPS-T200 series fulfils HDCP standard. HDCP
capability on the digital video inputs can be disabled when non-protected content
is extended.
Advanced EDID management – User can emulate any EDID on the input ports,
read out and store any monitor's EDID in the internal memory.
Pixel Accurate Reclocking – (removes jitter caused by long cables) The output
has a clean, jitter free signal, eliminating signal instability and distortion caused by
long cables or connector reflections.
Frame detector and signal analysis – Using Lightware Device Controller
software 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.
Deep Color support and conversion – It is possible to transmit the highest quality
36-bit video streams for perfect color reproduction.
DVI/HDMI, DP/DVI, DP/HDMI conversion – The transmitter is able to convert the
input video signal to another format so that you can watch the video on your local
display in another format.
Bi-directional RS-232 pass-through – AV systems can also contain serial port
controllers and controlled devices. Serial port pass-through supports any unit that
works with standard RS-232.
Remote power – The transmitters are PoE-compatible and can be powered locally
by the supplied power adaptor, or remotely via the TPS connection (through the
CATx cable) with a compatible Power Source Equipment.
Locking DC connector – Special plug of wall adaptor ensures safe power supply.
This type of connector prevents unwanted extractions.
Separate Audio and Video switching – Video and audio signals are separated
and can be switched independently.
Analog Audio conversion – Analog audio signal is converted to digital before
being sent to the output.
Input (video & audio) status LEDs – Front panel LEDs give feedback about state
of the unit and the video and audio signals.
Accepts analog and digital audio signals - Accepts analog stereo; 5.1 S/PDIF
and even 7.1 HDMI embedded audio signals. Analog signals are converted to
digital format and the digital or digitized analog audio can be embedded in the
video stream.
Auto-switch function for video and audio inputs – Autoselect mode with or
without priority can toggle between inputs. It helps the handling of the transmitter
and installation of new devices (SW4-TPS-TX240).
Page 12 / 122 Section 1. Introduction
Page 13
2. Controls and connections
1
HDCP
4
Show me
2
HDMI in
3
Reset
1
HDCP
7
Audio select
4
Show me
2
HDMI in
3
Reset
6
Audio in
5
Autoselect
1
HDCP
4
Show me
8
DVI-D in
3
Reset
1
HDCP
7
Audio select
4
Show me
6
Audio in
8
DVI-D in
3
Reset
5
Autoselect
2.1. Front view
HDMI-TPS-TX210
HDMI-TPS-TX220
HDMI-TPS-TX200 series
User’s Manual
DVI-HDCP-TPS-TX210
DVI-HDCP-TPS-TX220
Section 2. Controls and connections Page 13 / 122
Page 14
4
Show me
3
Reset
9
DP in
1
HDCP
4
Show me
6
Audio in
3
Reset
9
DP in
1
HDCP
5
Autoselect
7
Audio select
7
Audio select
4
Show me
8
DVI-D in
3
Reset
9
DP in
1
HDCP
5
Autoselect
2
HDMI in
2
HDMI in
10
Video select
6
Audio in
DP-TPS-TX210
DP-TPS-TX220
SW4-TPS-TX240
Info: The number before the port name is the port number used in LW3 protocol.
E.g. means the video port number for the DVI-D input port is P4.
Page 14 / 122 Section 2. Controls and connections
Page 15
2.2. Front view legend
1 2 3
4
6
7
8
9
10
5
HDCP LED
dark: video output signal is not encrypted with HDCP
lights: video output signal is encrypted with HDCP
HDMI in Connect a HDMI cable between the source and the transmitter. Applied
Reset Reset button reboots the extender. This is the same as disconnecting the
Show me Special functions are available with this button (switch to bootload mode,
Autoselect LED
dark: autoselect function is OFF
blinks: searching for signal (the video LEDs also blink)
lights: active video signal was found (the selected video LED also lights)
Audio in 3.5 mm Jack connector for asymmetric analog audio input signal. Pin
HDMI-TPS-TX200 series
User’s Manual
cable shall not be more, than 30 m (when signal is 1080p) and 15 m (when
signal is 4K). Pin assignment can be found in section 2.5.2 on page 19.
device from the power source and reconnecting it again.
enable DHCP, restore factory default settings). For details about the
special functions see the section 5.2 on page 32.
assignment can be found in section 2.5.8 on page 22.
Audio select Switching between audio inputs is available with this button.
DVI-D in 29-pole DVI-I connector for DVI-D signal. Applied cable shall not be more,
than 30 m (when signal is 1080p) and 15 m (when signal is 4K). Pin
assignment can be found in section 2.5.1 on page 19.
DP in DisplayPort input connector. Applied cable shall not be more, than 30 m
(at 2.7 Gbps data speed). Pin assignment can be found in section 2.5.3 on
page 20.
Video select Switching among video inputs is available with this button.
Audio and Video LEDs
The input ports have their own LEDs regarding the Audio and/or Video state. The functions
of these LEDs are the same and refer to the given input port.
Audio LEDs
dark: the audio source is not selected
blinks: the audio source is selected but not active, regardless of the output mode
(e.g. DVI EDID is emulated on the port with HDMI signal)
lights: (with short pause): audio source is selected, the port is active but audio is
not embedded to the video stream (e.g. the output mode is DVI).
(continuously): audio source is selected, active and the audio is embedded
to the output video stream.
Video LEDs:
dark: video source is not selected
blinks: video source is selected but not active
lights: video source is selected and the port is active
Info: When Autoselect is enabled and video signal is not present at all, video LEDs blink.
Info: A port is active if there is a valid signal on it.
Section 2. Controls and connections Page 15 / 122
Page 16
2.3. Rear view
7
RS-232
8
DC in
2
TPS out
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
1
HDMI out
7
RS-232
8
DC in
2
TPS out
9
GPIO
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
1
HDMI out
7
RS-232
8
DC in
2
TPS out
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
10
DVI-D out
7
RS-232
8
DC in
2
TPS out
9
GPIO
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
10
DVI-D out
HDMI-TPS-TX210
HDMI-TPS-TX220
DVI-HDCP-TPS-TX210
DVI-HDCP-TPS-TX220
Page 16 / 122 Section 2. Controls and connections
Page 17
HDMI-TPS-TX200 series
7
RS-232 8
DC in
2
TPS out
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
1
HDMI out
7
RS-232
8
DC in
2
TPS out
9
GPIO
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
1
HDMI out
7
RS-232
8
DC in
2
TPS out
9
GPIO
5
IR in
6
IR out
4
Status LEDs
3
Ethernet
1
HDMI out
User’s Manual
DP-TPS-TX210
DP-TPS-TX220
SW4-TPS-TX240
Section 2. Controls and connections Page 17 / 122
Page 18
2.4. Rear view legend
10
1
2
3
4
5
6
7
8
9
HDMI out Local HDMI output with the same A/V content as the TPS output.
TPS out Locking RJ45 connector. Connect a twisted pair cable between
Ethernet Locking RJ45 connector. Remote control port for connecting the
Status LEDs The LEDs give immediate feedback about device’s state, RS-232
IR in 3-pole TRS connector, also known as 3.5 mm (1/8”) jack plug for
IR out 3-pole TS connector, also known as 3.5 mm (1/8”) jack plug for
Pin assignment can be found in section 2.5.2 on page 19.
the transmitter and the receiver. Remote powering also happens
through this connector. Pin assignment can be found in section
2.5.4 on page 20. Maximum twisted pair cable distances can be
found in section 11.3 on page 118.
extender to a Local Area Network (LAN). Pin assignment can be
found in section 2.5.5 on page 21.
and TPS link state. For more information see the table below.
optional IR receiver only. Pin assignment can be found in section
2.5.10 on page 22.
optional IR transmitter only. Pin assignment can be found in
section 2.5.10 on page 22.
RS-232 3-pole Phoenix connector for RS-232 serial port. Pin assignment
can be found in section 2.5.6 on page 21.
DC in Local power in; connect the output of the supplied +12V DC
power adaptor or use Lightware’s rack mountable power supply
unit (PSUx10-200-12V or PSUx20-400-12V).
GPIO 8-pole Phoenix connector for configurable general purpose
input/output ports. Pin assignment can be found in section 2.5.8
on page 22.
DVI-D out 29-pole DVI-I connector for DVI-D signal with embedded audio;
local output with the same A/V content as the TPS output. Pin
assignment can be found in section 2.5.1 on page 19.
Status LEDs
LIVE LED
dark: device is not powered
blinks: (slow): device is powered and operational
(fast): device is in bootload mode
lights: device is powered but no operation
RS-232 LED
dark: RS-232 ports (Local and Link) are in Pass-through mode
blinks: command injection mode is active
lights: RS-232 ports (Local and Link) are in Control mode
SRVC LED
Reserved for future developments.
LINK LED
dark: no TPS link between transmitter and receiver
blinks: (slow): low power mode is active
(fast): Ethernet fallback mode is active
lights: TPS link is established, HDBaseT or Long Reach mode is active
Info: See more information about TPS link modes in section 0 on page 43.
Page 18 / 122 Section 2. Controls and connections
Page 19
2.5. Electrical connections
Pin
Signal
Pin
Signal
Pin
Signal
1
TMDS Data2-
9
TMDS Data1-
17
TMDS Data0-
2
TMDS Data2+
10
TMDS Data1+
18
TMDS Data0+
3
TMDS Data2 Shield
11
TMDS Data1 Shield
19
TMDS Data0 Shield
4
n.c.
12
n.c.
20
n.c. 5 n.c.
13
n.c.
21
n.c.
6
DDC Clock
14
+5V Power
22
TMDS Clock Shield
7
DDC Data
15
GND (for +5V)
23
TMDS Clock+
8
n.c.
16
Hot Plug Detect
24
TMDS Clock-
C1
n.c.
C2
n.c.
C3
n.c.
C4
n.c.
C5
GND
HDMI Type A receptacle
HDMI Type A Plug
Pin
Signal
Pin
Signal
1
TMDS Data2+
11
TMDS Clock Shield
2
TMDS Data2 Shield
12
TMDS Clock–
3
TMDS Data2–
13
CEC
4
TMDS Data1+
14
Reserved
5
TMDS Data1 Shield
15
SCL
6
TMDS Data1–
16
SDA
7
TMDS Data0+
17
DDC/CEC Ground
8
TMDS Data0 Shield
18
+5 V Power (max 50 mA)
9
TMDS Data0–
19
Hot Plug Detect
10
TMDS Clock+
1 2 3 4 5 6 7 8 9
10
11
12
13
14
15
16
17
18
19
19
18
17
16
15
14
13
12
11
10
9 8 7 6 5 4 3 2 1
C1
C2
C4
C3
1 2 3
4
5
6 7 8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
C5
2.5.1. DVI inputs and outputs
29-pole DVI-I connector, however only digital pins are connected. This way, user can plug
in any DVI connector, but keep in mind that analog signals (such as VGA or RGBHV) and
Dual-Link DVI signals are NOT processed. Always use high quality DVI cable for
connecting sources.
HDMI-TPS-TX200 series
User’s Manual
Table 2-1. DVI-D connector pin assignments
2.5.2. HDMI inputs and outputs
Section 2. Controls and connections Page 19 / 122
Table 2-2. HDMI connector pin assignments
Page 20
2.5.3. DisplayPort input
Pin
Signal
Pin
Signal
1
ML_Lane 3 (n)
11
GND
2
GND
12
ML_Lane 0 (p)
3
ML_Lane 3 (p)
13
Config1
4
ML_Lane 2 (n)
14
Config2
5
GND
15
AUX CH (p)
6
ML_Lane 2 (p)
16
GND
7
ML_Lane 1 (n)
17
AUX CH (n)
8
GND
18
Hot Plug
9
ML_Lane 1 (p)
19
Return
10
ML_Lane 0 (n)
20
DP_PWR
Pin
TIA/EIA T568 A
color and name
TIA/EIA T568 B
color and name
1
white/green stripe
white/orange stripe
2
green solid
orange solid
3
white/orange stripe
white/green stripe
4
blue solid
blue solid
5
white/blue stripe
white/blue stripe
6
orange solid
green solid
7
white/brown stripe
white/brown stripe
8
brown solid
brown solid
1
8
8
1
Figure 2-1. DisplayPort connector
Table 2-3. DisplayPort input connector pin assignments
2.5.4. TPS output connector
The transmitters provide standard RJ45 connectors for TPS Output.
RJ45 receptacle RJ45 plug
The recommended termination is based on TIA/EIA T 568 A or TIA/EIA T 568 B standards.
Page 20 / 122 Section 2. Controls and connections
Table 2-4. Recommended termination of TP cables
Info: When a standard Ethernet device is connected to the TPS connector for some reason, the
transmitter is switched to Ethernet fallback mode automatically. TPS port is changed to
work as an Ethernet port, but to operate the transmitter this way is not recommended.
Page 21
2.5.5. Ethernet port
LED1 (green)
LED2 (yellow)
Pin nr.
Name
Wire color
OFF
10 Mbit/s
not linked
1 TX +
Green stripe
Blink
-
activity
2 TX -
Green
ON
100 Mbit/s
no activity
3 RX +
Orange stripe
4 Not used
Blue
5 Not used
Blue stripe
6 Rx -
Orange
7 Not used
Brown stripe
8 Not used
Brown
Pin nr.
Signal
Ground
1
TX data
2
RX data
8
1
LED1
LED2
1
2
The Ethernet port can be connected to a LAN hub, switch or router by a CATx cable.
However both cable types (straight or cross) are supported and handled by the device,
below pin assignment is recommended.
Figure 2-2. RJ45 connector and pin assignments for Ethernet
2.5.6. DC +12V connection
HDMI-TPS-TX200 series
User’s Manual
The transmitters have a locking DC connector to establish robust and safe power
connection. After plugging it in, turn the plug clockwise as you can see in the picture below.
Do not forget to turn the plug counterclockwise before disconnecting the power adaptor.
Always use the supplied +12V power adaptor or Lightware’s rack mountable power supply.
Warranty void if damage occurs due to use of a different power source.
2.5.7. RS-232 connector
Most of the transmitters contain a 3-pole Phoenix connector, which is used for RS-232
serial connection. The transmitter has pass-through function, or can be remote controlled.
Figure 2-3. Locking DC connector
Figure 2-4. RS-232 connector pin assignments
Compatible plug type
Phoenix® Combicon series (3.5mm pitch, 3-pole)
Type: MC 1.5/3-ST-3.5, order nr.: 691361100003 (Würth)
Section 2. Controls and connections Page 21 / 122
Page 22
Pin nr.
Signal
1
Left
2
Right
3
Ground
Voltage [V]
Current, max. [mA]
Low level
0 - 0,8
30
High level
2 - 5
18
Pin nr.
Signal
1
Configurable
2 3 4 5 6 7 Ground
Receiver – 3-pole-TRS
Transmitter – 2-pole-TS
1 Tip
IR Input -
1 Tip
IR Output +
2 Ring
GND
2 Ring
IR Output -
3 Sleeve
IR Input +
3 Sleeve
IR Output -
2 3 4
5
6 7
1
1 2 3
1 3
1 2 3
2.5.8. Audio input
The connector is used for asymmetric analog audio input signal. It is also known as (3.5
mm or approx. 1/8”) audio jack, phone jack, phone plug and mini-jack plug.
Figure 2-5. 3.5 mm Jack audio plug pin assignments
2.5.9. GPIO – General purpose input/output ports
Advanced models have seven GPIO pins, which operate at TTL digital signal levels and
can be set to high or low level (Push-Pull). The direction of the pins can be input or output
(adjustable). The signal levels are the followings:
Table 2-5. Signal level of GPIO pins (values refer to each pin)
Info: The total available current of the controller is 180 mA.
Figure 2-6. GPIO connector and plug pin assignments
Compatible plug type
Phoenix® Combicon series (3.5mm pitch 8-pole), type: MC 1.5/8-ST-3.5, order #: 1840421.
2.5.10. IR connector
IR receiver and IR transmitter can be connected to the transmitter with TRS (Tip, Ring, and
Sleeve) connectors. They are also known as (3,5 mm or approx. 1/8”) audio jack, phone
jack, phone plug, and mini-jack plug.
Page 22 / 122 Section 2. Controls and connections
Table 2-6. TRS/TS connector pin assignment
Info: Transmitter’s Ring pole is optional. If your IR transmitter has three pole-TRS plug, then the
Ring and the Sleeve are the same signal (Output - ).
Page 23
3. Technologies
3.1. Basics
EDID stands for Extended Display Identification Data. Simply put, EDID is the passport of
display devices (monitors, TV sets, projectors). It contains information about the display’s
capabilities, such as supported resolutions, refresh rates (these are called Detailed
Timings), the type and manufacturer of the display device, etc.
After connecting a DVI source to a DVI display, the source reads out the EDID to determine
the resolution and refresh rate of the image to be transmitted.
HDMI-TPS-TX200 series
User’s Manual
Figure 3-1. EDID communication
Most DVI computer displays have 128-byte long EDID structure. However, Digital
Televisions and HDMI capable displays may have another 128 bytes, which is called EEDID and the most common extension is 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 are HDMI capable which
have the extension.
3.1.1. Common problems related to EDID
Problem: „I have changed to a different EDID on HDMI-TPS-TX210 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 don’t sense that EDID has been changed. You need to restart
your source to make it read out the EDID again.
Problem: „I have an HDMI-TPS-TX210 and I’m using a Lightware factory preset EDID. I
would like to be able to choose from different resolutions, but my source allows
only one resolution.”
Solution: Most Lightware factory preset EDIDs allow only one resolution, forcing the
sources to output only that particular signal. You need to select the Universal
EDID that supports all common VESA resolutions, see the factory EDID list.
Section 3. Technologies Page 23 / 122
Page 24
3.2. Advanced EDID management
Each DVI sink (e.g. monitors, projectors, plasma displays, and switcher inputs) 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 makes use of EDID data structure for the identification of 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 case of EDID readout failure or
missing EDID, the source will not output DVI video signal.
The transmitters provide Lightware’s Advanced EDID Management function that helps
system integration. The transmitter’s built-in memory stores and emulates pre-programmed
factory EDIDs, user’s EDID and the monitor's EDID that is connected to the receiver. The
transmitter stores the EDID of the attached monitor or projector in a non-volatile memory.
This way the EDID from a monitor is available when the monitor is unplugged, or switched
off.
The EDID emulated on the HDMI / DVI / DP input can be copied from the transmitter's
memory (static EDID emulation), or from the last attached monitor’s memory (dynamic
EDID emulation). For example, the transmitter can be set up to emulate a device, which is
connected to the receiver’s DVI output. In this case, the EDID is automatically changed, if
the monitor is replaced with another display device (as long as it has a valid EDID).
Advanced EDID management can be controlled via Lightware Device Controller.
Info: The user is not required to disconnect the HDMI / DVI / DP cable to change an EDID as
opposed to other manufacturer’s products. EDID can be changed even if source is
connected to the input and powered ON.
Info: When EDID has been changed, the transmitter toggles the HOTPLUG signal for 2 seconds.
Some sources do not observe this signal, so in this case the change is not recognized by
the source. In such cases, the source device must be restarted or powered OFF and ON
again.
3.3. HDCP management
Lightware Visual Engineering is a legal HDCP adopter. Several functions have been
developed which help to solve HDCP related problems. Complex AV systems often have
both HDCP and non-HDCP components. The extenders allow to transmit HDCP encrypted
and unencrypted signals. The devices will be still HDCP compliant, as they will never output
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 be shown.
3.3.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 a HDCP capable
device (e.g. an extender-pair) 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 always send
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 on the extenders. If
HDCP is disabled, the connected source will detect that the sink is not HDCP capable, and
turn off authentication.
Page 24 / 122 Section 3. Technologies
Page 25
3.3.2. Real life examples
HDCP-compliant sink
Figure 3-2. HDCP-compliant sink
All the devices are HDCP-compliant, no manual setting is required, both protected and
unprotected content is transmitted and displayed on the sink.
Non-HDCP-compliant sink (HDMI/DVI) 1.
Figure 3-3. Non-HDCP compliant sink displaying unprotected content
HDMI-TPS-TX200 series
User’s Manual
Non-HDCP compliant sink is connected to the receiver. 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 transmitter, 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, nonHDCP compliant sinks will display non-encrypted signal.
Non-HDCP-compliant sink (HDMI/DVI) 2.
Figure 3-4. Non-HDCP compliant sink and protected content
The layout is the same as in the previous case: non-HDCP compliant display device is
connected to the receiver but the source would send protected content with encryption. If
HDCP is enabled on the input port of the transmitter, the source will send encrypted signal.
The sink is not HDCP-compliant, thus it will not display the video signal (but
blank/red/muted/etc. screen). If HDCP is disabled on the input port of the transmitter, the
source will not send the signal to the transmitter. The solution is to replace the display
device to a HDCP-capable one.
Section 3. Technologies Page 25 / 122
Page 26
4. Installation
4.1. Mounting
To mount the transmitter Lightware supplies optional accessories for different usage. There
are two kinds of mounting kits with similar fixing method. The transmitters have two
mounting holes with inner thread on the bottom side; see the bottom view in section 11.2
on page 117. Fasten the device by the screws enclosed to the accessory.
Figure 4-1. Under-desk double mounting kit and 1U high Rack shelf
The Under-desk double mounting kit makes easy to mount a single device on any flat
surface, e.g. furniture. 1U high rack shelf provides mounting holes for fastening two halfrack or four quarter-rack sized units. Pocket-sized devices can also be fastened on the
shelf. To order mounting accessories please contact [email protected].
Info: The transmitters are half-rack sized.
4.2. Remote powering (PoE)
Remote powering of the transmitters was designed from a new approach as the devices
support PoE (Power over Ethernet) feature. The transmitter can be powered remotely
through TPS connector by using an external power injector module anywhere on the
transmission lane. The transmitter is compatible with IEEE 802.3af standard and able to
work as a Powered Device (PD) but cannot be used as a Power Sourcing Equipment
(PSE).
Important! The transmitters can receive the remote power only via their TPS output port. Using
Lightware’s remote power injector (TPS-PI-1P1) is highly recommended.
Info: If both remote and local power sources are connected, the remote power will be used.
4.3. Connecting devices
Info: When a standard Ethernet device is connected to the TPS connector for some reason, the
transmitter is switched to Ethernet fallback mode automatically. TPS port is changed to
work as an Ethernet port, but operating the transmitter this way is not recommended.
4.3.1. Connecting steps – using local PSU
Figure 4-2. SW4-TPS-TX240 – Powered by a local adaptor
Page 26 / 122 Section 4. Installation
Page 27
Step 1. Connect the transmitter and the receiver unit by a CATx cable via the TPS
connectors.
Step 2. Connect the desired video and audio source(s) to the input port(s) of the transmitter.
Step 3. Optionally connect the transmitter to a Local Area Network (LAN) in order to control
the device. More information about establishing the connection can be found in
section 6.4 on page 39.
Step 4. Optionally connect a serial device to the transmitter’s RS-232 port.
Step 5. Optionally for Infra-Red extension:
Connect the IR emitter to the IR OUT port of the transmitter.
Connect the IR detector to the IR IN port of the transmitter.
Step 6. Connect the power cord of the supplied adaptor to the transmitter or use
Lightware’s rack mountable power supply unit.
Step 7. Optionally connect a sink to the local HDMI output port.
Step 8. Power on the devices.
4.3.2. Connecting steps – using power injector (TPS-PI-1P1)
HDMI-TPS-TX200 series
User’s Manual
Figure 4-3. SW4-TPS-TX240 – Powered remotely
Step 1. Connect the “TPS OUT+PoE” port of the transmitter to the “TPS+PoE” output port
of the TPS-PI-1P1 by a CATx cable.
Step 2. Connect the receiver (or the Matrix input board) to the power injector by a CATx
cable via the TPS connector.
Step 3. Connect the desired video and audio source(s) to the input port(s) of the transmitter.
Step 4. Optionally connect the transmitter to a Local Area Network (LAN) in order to control
the device. More information about establishing the connection can be found in
section 6.4 on page 39.
Step 5. Optionally connect a serial device to the transmitter’s RS-232 port.
Step 6. Optionally for Infra-Red extension:
Connect the IR emitter to the IR OUT port of the transmitter.
Connect the IR detector to the IR IN port of the transmitter.
Step 7. Optionally connect a sink to the local HDMI output port.
Step 8. Power on the devices.
Info: If both remote and local power sources are connected, the remote power will be used.
Section 4. Installation Page 27 / 122
Page 28
5. Front panel operations
5.1. Input port selection
The transmitters accept many video and audio input signals depending on the model’s
capabilities. The audio/video input can be selected by any of the following ways:
Pressing the Audio select / Video select button,
Using the Autoselect function,
Using Lightware Device Controller,
Sending LW2 or LW3 protocol command.
The transmitter can receive LW2 or LW3 commands from Ethernet or RS-232 interface,
which can be either local or remote. It means that the input selection can also be controlled
remotely from a TPS receiver’s RS-232 or Ethernet port.
Only one video and audio can be selected to transmit; below figure shows the block
diagram of input/output selection.
Figure 5-1. Input port selection – summary of SW4-TPS-TX240 transmitter
Info: The audio/video signal on the local output port (HDMI/DVI) is always the same as on TPS
output port.
5.1.1. Direct selection on SW4-TPS-TX240 (video input port)
Desired video input can be selected by the Video select button, the order is the following:
5.1.2. Audio embedding – allowed connections
When the desired video signal is selected, the audio of the transmitted signal can be:
The audio of the original signal, or
The analog audio signal
Info: The audio of the HDMI2 input can be embedded only to the original video stream. The
audio of HDMI2 input cannot be mixed with the video of HDMI3 input and vica versa.
Page 28 / 122 Section 5. Front panel operations
Page 29
5.1.3. Autoselect – First detect mode
Meaning: Selected input port is switched to the output while it has active signal.
HDMI-TPS-TX200 series
User’s Manual
Figure 5-2. Autoselect – First detect mode
Info: The signal detection is handled on a different way in the case of analog audio input: if a 3.5
mm jack plug is connected to Audio in, the port is handled as it has an active signal.
Section 5. Front panel operations Page 29 / 122
Page 30
Priority
0 1 2
31
Input port
P2
HDMI2
P3
HDMI3
P4
DVI-D
P1
DP
Example (Video input ports on an SW4-TPS-TX240)
The priority values have to be assigned to each input port which are desired to be used.
The followings priority settings will be used during the explanation of this mode:
The port priority parameter can be set from 0 to 31. If the priority of a port is set to 31, the
port will not be on the priority list and will be skipped. In this case lowest priority (31) is
assigned to the DP input thus it cannot be selected.
The priority list is checked from 0 to 30. After an event the device always checks the
selected port. If there is a valid signal on it, the port remains selected. If there is no valid
signal on the port the device checks the port with priority 0, in this case P2 (HDMI2). If there
is a valid signal on that port, it will be selected. If there is no valid signal on that port the
device checks the port with priority 1, P3 (HDMI3). If there is a valid signal on that port, it
will be selected. If there is no valid signal on that port the device checks the port with priority
2, P4 (DVI-D). If there is a valid signal on that port, it will be selected. If there is no valid
video on any of the checked input ports, the No sync-screen state will be checked; if the
function is in On/Auto state, No sync-screen will be displayed. If the state is Off, there will
be no Audio/Video transmission.
Autoselect priority and crosspoint settings can be changed via the LDC surface, see section
0 on page 43, or by protocol commands.
Special features
If more than one input port is active (there is a valid signal on the input port) when the
device is powered on or autoselect is switched on, the priority order will be used to select
the input port. The same priority number can be set to different input ports. In this case the
input port with the lowest port number will have the highest priority among them. E.g. setting
the priority of P1 (DP) and P2 (HDMI2) to “0”, the DP input port will have higher priority
since P1 is lower than P2.
5.1.4. Autoselect – Last detect mode
This mode was introduced in Firmware 1.0.1. When the autoselect setting is enabled in this
mode, always the last attached input is the active one. If a user connects a signal to any of
the input ports, it becomes the transmitted input automatically.
5.1.5. Autoselect – Static mode (available only at Audio crosspoint)
In this mode the audio inputs are assigned to the video inputs statically:
Figure 5-3. Autoselect – Static mode
Page 30 / 122 Section 5. Front panel operations
Page 31
5.1.6. Autoselect – Priority detect mode
Meaning: The highest priority active input will be selected to transmit.
Info: An input port is active if there is a valid signal on it.
HDMI-TPS-TX200 series
User’s Manual
Figure 5-4. Autoselect – Priority detect mode
Info: The signal detection is handled on a different way in the case of analog audio input: if a 3.5
mm jack plug is connected to Audio in, the port is handled as it has an active signal.
Section 5. Front panel operations Page 31 / 122
Page 32
Priority
0 1 2
3
Input port
P2
HDMI2
P3
HDMI3
P4
DVI-D
P1
DP
Example (video input ports on an SW4-TPS-TX240)
The priority values have to be assigned to each input port which are desired to use. The
following priority settings will be used during the explanation of this mode:
After an event the device always checks the port with the highest priority, P2 (HDMI2). If
there is a valid signal on P2, it will be selected. If there is no valid signal on HDMI2 input
port the device checks the following port with priority 1, P3 (HDMI3). If there is a valid signal
on P3, it will be selected. If there is no valid signal on HDMI3 input port the device checks
the following port with priority 2, P4 (DVI-D). If there is a valid signal on P4, it will be
selected. If there is no valid signal on DVI-D input port the device checks the following port
with priority 3, P1 (DP). If there is a valid signal on it, P1 will be selected. If there is no valid
video on any of the checked input ports, the No sync-screen state will be checked; if the
function is in On/Auto state, No sync-screen will be displayed. If the state is Off, there will
be no Audio/Video transmission.
Port priority settings
Autoselect priority settings can be changed via the LDC surface, see section 0 on page 43,
or by protocol commands.
Special features
The same priority number can be set to different ports. In this case the input port with the
lowest port number will have the highest priority among them. E.g. setting the priority of P2
(HDMI2) and P3 (DP) to “0”, the HDMI2 input port will have higher priority since P2 is lower
than P3. Ports can be skipped from the priority list by giving the lowest value: priority 31.
5.2. Special functions
5.2.1. Control lock
Press the Audio select and Show Me buttons together (within 100 ms) to disable/enable
front panel buttons; front panel LEDs blink 4 times when locking/unlocking. If the control
lock is enabled and a button is pressed, front panel LEDs blink 3 times quickly.
5.2.2. Programmable Show me button
Action or an operation can be assigned to the Show me button. “Show me button pressed”
is a condition that can be selected in the Event manager. See more details in section 6.9
on page 51.
5.2.3. Reset to factory default settings
To restore factory default values, do the following steps:
Step 1. Make sure the device is powered on and operational (control is not locked).
Step 2. Press and keep pressed the Show me button for 10 seconds.
Step 3. After 5 seconds front panel LEDs start blinking but keep on pressing the button.
Step 4. After 10 seconds the blinking gets faster; release the button and press it 3 times
again quickly (within 3 seconds).
Step 5. The LEDs get dark, the device restores the factory default settings and reboots.
Factory default settings are listed in section 11.5 on page 120.
Page 32 / 122 Section 5. Front panel operations
Page 33
5.2.4. Enable DHCP IP address
The device gets a fix IP address as a factory default setting. If this setting does not fit to
the circumstances during install or usage, DHCP can be enabled from the front panel:
Step 1. Make sure the device is powered on and operational (control is not locked).
Step 2. Press and keep pressed the Show me button for 5 seconds.
Step 3. After 5 seconds front panel LEDs start blinking; release the button and press it 3
times again quickly (within 3 seconds).
Step 4. The LEDs get dark, DHCP gets enabled and the device reboots.
5.2.5. Entering bootload mode
It may happen that the firmware upgrade process is not successful as the device cannot
be switched to bootload mode automatically. In this case transmitter device can be forced
to switch to bootload mode as follows:
Step 1. Make sure the transmitter is powered off.
Step 2. Press and keep pressed the Show me button.
Step 3. Power on the transmitter. If the device is switched to bootload mode the LIVE LED
is blinking quickly (less than 500 ms duty cycle). The other LEDs are off.
HDMI-TPS-TX200 series
User’s Manual
Info: Device can be switched to normal operation mode by resetting or switching it off and on
again.
5.3. IR interface
IR receiver can sense IR light (e.g. emitted by a remote controller) and send electrical
signals to the IR transmitter. The transmitter unit processes the electrical signals and emits
IR light toward the controlled device (e.g. projector). IR OUT receptacle accepts only the
IR transmitter and IR IN receptacle accepts only the IR receiver. IR accessories are not
interchangeable.
IR signal from the IR input is transmitted to the receiver or input board and vica versa.
Info: Direct line of sight is required between IR transmitter and the controlled device (e.g. Blu-
Ray or DVD player) and the same is valid for the IR receiver and the controller device (e.g.
remote controller).
5.4. General purpose input/output ports
Certain models have 7 GPIO pins, which operate at TTL digital signal levels and can be
controlled by both LDC and LW2 / LW3 protocol commands.
Output pin state can be set with specific command.
Input pin state can be queried, and a notification is sent from the device, if the state
is changed.
As a special function, the GPIO pins would act the same way as video select, audio select
and show me buttons. Using the GPIO pins in conjunction with the Event manager gives
many functions. See more details in section 6.9 on page 51.
Info: GPIO control is available in Firmware v1.0.1 and above.
Section 5. Front panel operations Page 33 / 122
Page 34
5.5. RS-232 interface
The RS-232 interface supports three modes: Pass-through mode, Control mode and
Command injection mode. The RS-232 mode can be set by protocol commands or via the
Lightware Device Controller, see the section 6.8.1 on page 50.
Local and link lines
The transmitters have two lines for RS-232 serial communication:
Local: serial line between the CPU and the Phoenix connector,
Link: serial line between the CPU and the TPS interface.
Figure 5-5. Local and link serial lines
Both lines are connected to the microcontroller, so these can be configured separately (e.g.
the baud rate can be different; the microcontroller does the conversion automatically
between the two ports).
5.5.1. Control mode
In Control mode the transmitter’s CPU can receive commands and send responses to/from
its own serial port or to/from the serial port on the receiver through the CATx (TPS) cable.
The incoming data from both sides is processed and interpreted as LW2 or LW3 protocol
commands. Selecting the control protocol (LW2 or LW3) on the RS-232 interface can be
done either by using Lightware Device Controller or sending LW2/LW3 protocol
commands. The interface can be set for the Local and for the Link RS-232 line
independently from each other.
Example
Figure 5-6. Control mode
The transmitter is connected to a receiver. A touch panel is connected to the RS-232 port
of the receiver and it sends commands to the transmitter; this is called ROT v2 (RS-232
over TPS). ROT only supports a few commands, which answer length is less than 50 Bytes.
Page 34 / 122 Section 5. Front panel operations
Page 35
5.5.2. Pass-through mode
In pass-through mode the incoming data from the local and link sides is passed through to
the other side without processing it. The serial ports on the transmitter and on the receiver
are linked together through the CATx (TPS) cable. This allows direct communication
between a device connected to the receiver and a device connected to the transmitter.
Example
HDMI-TPS-TX200 series
User’s Manual
Figure 5-7. Pass-through mode
The transmitter is connected to a receiver. A button panel is connected to the RS-232 port
of the transmitter and a projector is connected to the RS-232 port of the receiver. The
commands sent by the button panel are passed through the extenders to the projector.
This layout allows to remote control the projector from a button panel.
5.5.3. Command injection mode
When the device is in RS-232 command injection mode, it works as an RS-232-Ethernet
converter (bidirectional). There are two separate TCP/IP ports for this purpose, one for the
link and one for the local side. On these ports the Ethernet packets are converted to RS-232
data and vica versa. The local and the link sides are not connected in this mode.
Figure 5-8. Command injection mode
Example
The transmitter is connected to a receiver. A monitor is connected to the receiver’s RS-232
port. The transmitter and a computer are connected to same Ethernet. In command
injection mode the computer can send commands to the monitor through the extenders, so
this layout allows to remote control the monitor from a computer.
Section 5. Front panel operations Page 35 / 122
Page 36
Normal install
Snapshot install
Available for Windows and MAC OS X
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 versions can be
installed for all users
Does not contain the version in its name
Version number is displayed in the name
6. Software control – using Lightware Device Controller (LDC)
The device can be controlled by a computer through the Ethernet port using Lightware
Device Controller. The software can be installed to a Windows PC or MAC OS X. The
application and the User’s manual can be downloaded from www.lightware.eu. The
Windows and the Mac versions have the same look and functionality.
6.1. Steps of the installation in case of Windows OS
Step 1. Run the installer; if User Account Control appears click Yes.
Step 2. A welcome window opens. Click Next.
Step 3. Select the type of the installation: normal or snapshot install. Select the optional
components then click Next. (Normal install is recommended.)
Step 4. Select the destination folder and click Next. (Default path is highly recommended.)
Page 36 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 37
HDMI-TPS-TX200 series
User’s Manual
Step 5. Select the Start Menu Folder and click Next. (Using the default folder is highly
recommended. If the Start menu entries was not checked in Step 3 this window will
be skipped.)
Step 6. Verify the settings and if they are correct click Install. (If not, click Back and change
the setting.)
Step 7. After the installation of the last component the Next button is activated. Click on it.
Step 8. If the installation is complete, click Finish. (Uncheck the box if you do not want to
run the software immediately.)
Section 6. Software control – using Lightware Device Controller (LDC) Page 37 / 122
Page 38
6.2. Steps of the installation in case of Mac OS X
Info: After the installation the Windows and the Mac application has the same looks and
functionality.
Step 1. Mount the DMG file with double clicking on it.
Step 2. 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.
Info: This type of the installer is equal with the Normal install in case of Windows. This is an
updateable version with the same attributes.
6.3. LDC Upgrade
Step 1. Run the application.
The Device Discovery window appears automatically and the software
checks the available updates on Lightware’s website and a new window
pops up if a new update is found.
The current and the update version number can be seen in the top of the window
and they are shown in this window even with the snapshot install.
Page 38 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 39
Step 2. Set the desired update setting in the option section.
a) If you do not want to check for the updates automatically, uncheck
the circle, which contains the green tick.
b) If you want to postpone the update, a reminder can
be set with different delays from the drop-down list.
c) If the proxy settings traverse the update process, set
the proper values then click the OK button.
HDMI-TPS-TX200 series
User’s Manual
Step 3. Click the Download update button to start the upgrading.
User can check updates manually by clicking the Check now button.
6.4. Establishing the connection
Step 1. Connect the device to a computer directly or via Ethernet. Cable type does
not matter, both patch and cross cable can be used.
Step 2. Run the controller software; device discovery window appears
automatically.
Figure 6-1. Ethernet connection in Device discovery window
Step 3. Double-click on the desired device or select it and click on the Connect button. If
you do not see your device in the list, you can add it by clicking on the Add button
and typing its IP address.
Section 6. Software control – using Lightware Device Controller (LDC) Page 39 / 122
Page 40
6.5. Crosspoint menu
2
3
4
1
5
6
9
7
8
1 2 3
4
5
6
7
9
8
When LDC finds the hardware, it determines the product type, and the LDC starts with the
default page, showing the Crosspoint menu.
Main menu The available menu items are displayed. The active one is
showed with dark grey background color.
Information ribbon The label shows the type of the connected device. Device
discovery window can be displayed by clicking on this ribbon.
Video input ports Each tile represents a video input port. The tile below the port
shows current crosspoint setting; if the port is switched to the
output, the color of the tile is white, otherwise grey.
Audio input ports Each tile represents an audio input port. The tile below the
port shows current crosspoint setting; if the port is switched to
the output, the color of the tile is white, otherwise grey. Dark
grey means the audio port is not allowed to embed in the
current video input port.
Audio output The audio output of the TPS and local outputs; the audio
signal is the same on those ports.
Video output The video output of the TPS and local outputs; the video
signal is the same on those ports.
Advanced view Displaying Advanced view page, showing the Terminal
window and the protocol tree.
Navigation buttons If the window is smaller than required, the ports may not fit in
the available area. Thus the arrows on this button get
activated and the ports can be scrolled. Clicking on the middle
icon restores the original layout (window is arranged to the left
top corner).
Properties Toggling right panel display, showing the properties of
Page 40 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
selected port. The panel is also displayed when clicking on a
port tile.
Page 41
HDMI-TPS-TX200 series
Port name
Port icon
State indicators
Signal present (green),
not present (grey)
Icon
Icon is not displayed
Icon is grey
Icon is black
HDCP is not supported
Signal is not encrypted
with HDCP
Signal is encrypted
with HDCP
-
Port is unmuted
Port is muted
-
Port is unlocked
Port is locked
-
Autoselect is disabled
Autoselect is enabled*
2 3
4 1 1
2 3 4
User’s Manual
Port tiles
The colors of the port tiles and the displayed icons represent different states and
information:
State indicators
Following icons display different states of the port/signal:
* When Autoselect is enabled the icon is displayed in green.
6.6. Port properties and settings
Left click on Properties button to display the
properties panel of selected port. Signal status
information and the most important
parameters are displayed on the panel.
Special functions (e.g. frame detector, port
naming) are also available on the panel. The
look and the content is port-dependent.
Port name
The name of a port can be changed by typing
the new name and clicking the Set button.
The following characters are allowed when
naming:
Letters (A-Z) and (a-z), hyphen (-), underscore
(_), numbers (0-9) and dot (.).
HDCP setting
The HDCP compliancy can be enabled or
disabled on the digital video input port. This
feature can force the source to send
non-encrypted signal if the encryption would
not be necessary and the content allows it.
Section 6. Software control – using Lightware Device Controller (LDC) Page 41 / 122
Page 42
Frame detector
6.6.1. Frame detector (on video input ports)
Input ports can show detailed information about the signal like blanking
intervals and active video resolution. This feature is a good
troubleshooter if compatibility problems occur during system
installation. To access this function, open Properties panel of the input port on which the
signal has to be checked. Click on Frame Detector button to show detailed timings.
Figure 6-2. Frame detector window
Lightware’s frame detector function works like an input signal analyzer and makes possible
to determine the exact video format that is sent by the source, 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 incoming 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 gray 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
actually on the signal and not retrieved only from the HDMI info frames.
6.6.2. Analog audio port properties
Certain parameters of analog audio input
signal can be adjusted as follows:
Volume:
from 0 dB to -52 dB (step 0.25 dB),
from -54 dB to -66 dB (step
2 dB); -69 dB; -72 dB; -78 dB (default
is 0 dB)
Balance:
from 0 to 100, step 1 (default is 50 =
center)
Gain:
0 dB / 3 dB / 6 dB
Page 42 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 43
6.6.3. TPS output port properties and mode settings
Muting/Locking
TPS output can be muted by clicking on the button Unmuted. If the output is muted, button
text is Muted. When the port is muted, no signal is present on the output.
TPS output 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.
No sync screen
When there is no incoming signal on the selected input port, a
static image can be sent on the output port(s).
Mode: No sync – No sync-screen signal is sent when
there is no incoming signal.
On – No sync-screen signal is sent always,
independently from the incoming signal.
Off – No sync-screen is disabled.
Clock source: Set the desired resolution: 480p / 576p /
External clock source (from actual TMDS
source).
HDMI-TPS-TX200 series
User’s Manual
Pattern: Select the desired color or the pre-defined
pattern from the list.
Autoselect
The autoselect feature can be set via the TPS
OUT properties panel as follows:
Settings
Enabled: The Autoselect mode is ON.
Disabled: The Autoselect mode is OFF.
Priority detects: Priority detect mode is
active (see section 5.1.6 on page 31).
First detect: First detect mode is active
(see section 5.1.3 on page 29).
Last detected: Last detect mode is
active (see section 5.1.4 on page 30).
Static: Static mode is active (see
section 5.1.5 on page 30). Available
only at TPS Audio out.
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. 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 the
modification to store the settings.
Section 6. Software control – using Lightware Device Controller (LDC) Page 43 / 122
Page 44
TPS mode
Explanation
Auto
The TPS mode is determined automatically
HDBaseT
Ideal for high resolution signals up to 4K but with shorter cable
Longreach
Ideal for big distances, but till 1080p@60Hz
Only RS232
Only RS-232 communication is transmitted
(Low Power mode)
Only RS232+Eth
Only RS-232 and Ethernet communication is transmitted
(Low power mode)
Mode selected on RX side
RS232
RS232+Eth.
HDBaseT
Longreach
Auto
Mode selected
on TX side
RS232
RS232
RS232
RS232
RS232
RS232
RS232+Eth.
RS232
RS232+Eth.
RS232+Eth.
RS232+Eth.
RS232+Eth.
HDBaseT
RS232
RS232+Eth.
HDBaseT
RS232
HDBaseT
Longreach
RS232
RS232+Eth.
RS232
Longreach
Longreach
Auto
RS232
RS232+Eth.
HDBaseT
Longreach
Auto
Settings (only on TPS Video output port)
Basic transmission parameters can be set on this panel as follows:
Info: If Low power mode is active and the Ethernet connector is plugged/unplugged, minor
temporary disturbance may arise in the transmission of RS-232 and/or IR signal.
Info: The allowed cable lengths and resolutions are listed in section 11.3 on page 118.
These settings refer to the transmitter. The TPS transmission mode between the transmitter
and the receiver depends on the settings of both units. Next table contains the details about
the system's state with regard to mode selection behavior for all possible combinations on
both ends of the link:
Figure 6-3. TPS mode determination between transmitter and receiver
Info: When a standard Ethernet device is connected to the TPS connector for some reason, the
transmitter is switched to Ethernet fallback mode automatically. TPS port is changed to
work as an Ethernet port, but to operate the transmitter this way is not recommended.
When using automatic operation mode selection, the device uses built-in sensors to
determine the mode of operation. If the transmitter and the receiver is in Auto mode, the
source side is the initiator. It will negotiate each state transition with its sink side partner.
Info: If the sink is switched off or disconnected on receiver’s side, the TPS link mode is changed
to “RS232+Eth” mode – when the devices are set to Auto. In this case signal is not present
on the output port of the transmitter.
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.
Further settings
HDMI mode: Auto / DVI / HDMI 24 bit / HDMI 30 bit / HDMI 36 bit
HDCP: Auto / Always
Power5V mode: Auto / Always on / Always off
Page 44 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 45
HDMI-TPS-TX200 series
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
User’s Manual
Cable diagnostics (only on TPS Video output port)
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 into red. It means the number of
the errors – during the extension – is higher than the
recommended one. The link might be alive but
recovering of the received data is not guaranteed.
Info: Each bar represents a differential line in the CATx cable.
The inappropriate termination of the cable usually
occurs high error rates. Check the cable terminations or
change the cable.
Info: The estimated length is valid for Cat5e AWG24 cables. Cat7 cable length is calculated from
the measurement of Cat5e AWG24 cable.
Video Bit Error Ratio
This feature works in conjunction with the TPS receiver’s side and is about to show the
average bit error numbers in the transmitted video signal. The value is displayed only if the
installed firmware on the RX side supports this feature.
Reference values
Above displayed “Video BER < 10
1010 pixels, which means the number of the bit errors is about 1 pixel in every 15 minutes.
-10
” value means that in average there is 1 bad pixel after
Section 6. Software control – using Lightware Device Controller (LDC) Page 45 / 122
Page 46
6.7. EDID menu
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
Save
Load
Clear selected
Info
Select All
Edit
Unselect All
EEC
Advanced EDID Management can be accessed by selecting the EDID menu. There are
two panels: left one contains Source EDIDs, right one contains Destination places where
the EDIDs can be emulated or copied.
Control buttons
6.7.1. Sources and Destinations
Figure 6-4. EDID menu
Page 46 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
The EDID memory consists of four parts:
Factory EDID list shows the pre-programmed EDIDs (F1-F119).
Dynamic EDID List shows 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 of the transmitter at the moment.
User memory shows the memory locations (U1 – U14) which can be used by the user 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.
Page 47
The DVI source reads the EDID from the Emulated EDID memory on the INPUT port. The
user can copy an EDID from any of the User/Factory/Dynamic EDID lists to the user
memory locations.
There are two types of emulation: static and dynamic.
Static EDID emulation happens, when an EDID from the Factory or User EDID
list is selected. In this case the Emulated EDID will remain the same until the user
emulates another EDID.
Dynamic EDID emulation 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.
6.7.2. Changing emulated EDID
Step 1. Select the desired EDID list from one of the three sources by pressing its button.
Step 2. Select an EDID from the Source panel to emulate.
Step 3. Press Emulated button on the top of the Destination panel.
Step 4. Select desired port on the right panel (more than one ports can also be selected);
the EDID(s) will be highlighted with yellow cursor.
HDMI-TPS-TX200 series
User’s Manual
Step 5. Press Transfer button to change the emulated EDID.
6.7.3. Learning an EDID
Info: The process is the same as changing the emulated EDID; the only difference is at 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).
6.7.4. Exporting an EDID
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 yellow cursor).
Step 2. Press the Save button to open the Save as dialog and download the file to the
computer.
6.7.5. Importing an EDID
Previously saved EDID (*.bin, *.dat or *.edid file) can be uploaded to the user memory:
Step 1. Press the User button on the top of the Source panel.
Step 2. Select a memory slot from the Source panel.
Step 3. Press the Upload button below the Source panel.
Step 4. Browse the file in the opening window then press the Open button. Browsed EDID
is imported into the selected User memory.
Info: The imported EDID overwrites the selected memory place even if it is not empty.
6.7.6. Deleting EDID(s)
The EDID(s) from User memory can be deleted as follows:
Step 1. Press User button on the top of the Destination panel.
Step 2. Select desired memory slot(s); more can be selected (Select All and Deselect All
buttons can be used). The EDID(s) will be highlighted with yellow cursor.
Step 3. Press the Clear selected button to delete the EDID(s).
Section 6. Software control – using Lightware Device Controller (LDC) Page 47 / 122
Page 48
6.7.7. EDID info window
Select an EDID from Source panel and press Info button to display the EDID info window.
Figure 6-5. EDID info window
6.7.8. Editing an EDID
Select an EDID from Source panel and press the Edit button to display Advanced EDID
Editor window. The editor can read and write all descriptors, which are defined in the
standards, including the additional CEA extensions. Any EDID from the device’s memory
can be loaded in the editor. The software resolves the raw EDID, and displays it as readable
information to the user. The modified EDID can be saved to the User memory.
Figure 6-6. Advanced EDID Editor
Page 48 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 49
6.7.9. Creating an 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
EEC button below Source panel, Easy EDID Creator is opened in a new window.
HDMI-TPS-TX200 series
User’s Manual
Figure 6-7. Easy EDID creator wizard
Step 1. Select resolution
The preferred resolution can be defined here. There are more ways to define the desired
format. You are able to select one from the drop-down list where the most common
resolutions are listed.
Step 2. Signal type
You have to decide whether you want to add HDMI support to your EDID or not. Please
note that the use of audio, non-RGB color spaces and deep color requires the HDMI mode.
Step 3. Select audio
If you have selected HDMI support in the previous step, specify the desired audio format.
The most common audio formats are listed, but the number of possible formats is greater.
If you don’t find your preferred audio, you are able to add it later by using EDID editor.
Step 4. Finish
You have to give a name to your new EDID as last step. This name will be fit into the display
product descriptor, so it can be up to 13 alphanumeric characters long. You also have to
select the desired operation: you are able to upload the new EDID to the actually used
Lightware product or/and save it to a file or/and open it in the EDID editor.
Info: For more information about creating and EDID by using EEC see the User’s manual of the
EDID Editor which is available at www.lightware.eu.
Section 6. Software control – using Lightware Device Controller (LDC) Page 49 / 122
Page 50
6.8. Control menu
The menu gives the opportunity to setup those channels which can be used to connect or
control third party devices.
6.8.1. RS-232 tab
General Settings
There are three RS-232 working modes: Passthrough-, Control- and Command Injection modes.
See more details in section 5.5 on page 34.
Port settings
Two lines are available:
Local: RS-232 connection between the
CPU and the 3-pole Phoenix connector
Link: RS-232 connection between the CPU
and the receiver unit (via TPS line)
The settings are the same but different parameters
can be set for Local and Link ports.
Command injection
If the RS-232 mode is set to Command injection,
this section is activated and the port number can be
set. Default values: 8001 (local) and 8002 (link).
Figure 6-8. Control menu (RS-232 tab)
Control protocol
The active protocol can be set by the drop-down
menu: LW2 or LW3 protocol.
Other
The terminal line can be used to send commands to the destination in pass-through mode.
Page 50 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 51
6.8.2. GPIO tab
GPIO pin name
GPIO port icon
Low level indicator*
High level indicator*
Pin direction: input (down
arrow) or output (up arrow)
2
1
5
4
3
1 2 3
4
5
The GPIO port has 7 pins, which operate at TTL digital signal levels and can be controlled
by LDC or protocol commands. Select a GPIO pin and under the Port settings section; the
settings (pin direction and input level) are displayed on the port tiles as well:
* The black colored symbol means the current setting.
Info: See more information about GPIO pins in section 2.5.8 on page 22.
6.8.3. Ethernet tab
Basic information is shown about the network communication.
HDMI-TPS-TX200 series
User’s Manual
6.9. Event manager
The feature means that device can sense changes on its ports and 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 present or HDCP active) are
necessary to display but it is not easy when the device is hard to access (e.g. built under
desk). When the Event manager is used in combination with the GPIO ports, many new
possibilities are opened.
Basically the Event manager can be configured to detect LW3 CHANGE messages, and if
the condition (the given change message) appears, the event will be fired. The device will
perform an action (send out a preprogrammed LW3 SET or CALL message to itself). E.g.
the desired setup is that after the input signal has been present on the VGA port, the level
of GPIO1 pin is changed. The settings can be done via the LDC in the Control/Events tab,
or by LW3 protocol commands, see chapter 8 on page 77.
Section 6. Software control – using Lightware Device Controller (LDC) Page 51 / 122
Figure 6-9. Event manager tab
20 events can be configured, which are available in Control/Events submenu. The user can
see all the 20 events here and modify them by the Wizard or the Advanced setting.
Page 52
6.9.1. The event area
9
5
8 7 6
10
3 1
2
4
11
6
4
2 3 1
5
7
8 9 11
10
Number of the event 20 events can be defined in the transmitter, the label shows
Condition If the condition was set, the description (white colored text)
Figure 6-10. First event (E1) settings
the number of them (E1-E20).
and the exact LW3 protocol expression (yellow colored text)
can be seen. If advanced mode was used the description is
“Custom condition”.
Name of the event Text as the name of the event can be stored. Click into the
text box and type desired name.
Action If the action was set, the description (white colored text) and
the exact LW3 protocol expression (yellow colored text) can
be seen. If advanced mode was used the description is
“Custom action”.
Set name button The device stores the name of the event if the Set name
button was pressed. The button is dark when the name is
already saved.
Set condition (wizard) Run the wizard to choose from the most common expressions
as a condition.
Set condition (advanced) Advanced setting contains a wide range of LW3 expressions,
which are displayed in a tree structure.
Set action (wizard) Run the wizard to choose from the most common expressions
as an action.
Set action (advanced) Advanced setting contains a wide range of LW3 expressions,
which are displayed in a tree structure.
Clear event button Unwanted events can be cleared with a single click on this
button. Confirmation is needed for deleting.
Check bar If the event is ready and syntactically correct the check bar
becomes green.
Page 52 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 53
6.9.2. Wizard mode
A simple wizard makes things easy for the user, because it lists the most common
conditions and actions. Conditions and actions also have their own buttons.
Step 1. Click on the Wizard button on the Condition side.
Step 2. Select the desired category from the drop-down menu.
HDMI-TPS-TX200 series
User’s Manual
Step 3. Select an Expression.
The expression determines the further possible parameters. E.g. if the Expression is a
video signal detection of an input, the port has to be defined in the following step.
Select the desired parameter and click on the OK to finish the wizard of the condition.
The action is the “reply” if the condition becomes true.
Info: The sequence does not matter: you may define the action first.
Section 6. Software control – using Lightware Device Controller (LDC) Page 53 / 122
Page 54
Step 4. To set the action, click on the wizard button on the action side.
The process is the same. Click on the down arrow of the drop-down menu than select the
desired item. The category and the expression can be set (the values are listed in the
“Action” column of the Actions table on page 56). If the expression requires further
parameter, select it. E.g. if the Expression is a switching on the video layer, the input and
the output port has to be selected in the next step.
Step 5. Click on the OK to finish the wizard of the action.
The window of the wizard is closed; the created action can be seen above the buttons. The
white text is the name of the selected action, the yellow is the accurate property (and its
value) or method name by LW3 protocol. You do not need to remember or note this text,
LDC shows it continuously. The system checks the validity of the event. If everything is
correct, a green line can be seen at the bottom of the event area.
Page 54 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 55
Conditions of the Event Manager Wizard
Layer
Event
Path and value in LW3 protocol tree*
Video
Input signal is detected on a port
/MEDIA/VIDEO/P1.SignalPresent=1
Input signal is not detected on a port
/MEDIA/VIDEO/P1.SignalPresent=0
Input signal type changes to DVI
/MEDIA/VIDEO/P2.SignalType=0
Input signal type changes to HDMI
/MEDIA/VIDEO/P2.SignalType=1
Input signal type changes to Undefined
(no signal)
/MEDIA/VIDEO/P2.SignalType=F
HDCP encryption state changes to
Unencrypted
/MEDIA/VIDEO/P5.HdcpActive=0
HDCP encryption state changes to
Encrypted
/MEDIA/VIDEO/P5.HdcpActive=1
HDCP encryption state changes to
Undefined (no signal)
/MEDIA/VIDEO/P5.HdcpActive=F
Audio
Input signal is detected on a port
/MEDIA/AUDIO/P2.SignalPresent=1
Input signal is not detected on a port
/MEDIA/AUDIO/P2.SignalPresent=0
Input signal type changes to PCM
/MEDIA/AUDIO/P2.SignalType=0
Input signal type changes to Compressed
/MEDIA/AUDIO/P2.SignalType=1
Input signal type changes to HBR
/MEDIA/AUDIO/P2.SignalType=3
Input signal type changes to Undefined
(no signal)
/MEDIA/AUDIO/P2.SignalType=F
GPIO
Input state changes to “High”
/MEDIA/GPIO/P1.Input=H
Input state changes to “Low”
/MEDIA/GPIO/P1.Input=L
General
TPS link state changes to Connected
/MEDIA/VIDEO/P5.LinkState=true
TPS link state changes to Disconnected
/MEDIA/VIDEO/P5.LinkState=false
Display connected to receiver side
/MEDIA/VIDEO/P5.ReceiverSense=true
Display disconnected from receiver side
/MEDIA/VIDEO/P5.ReceiverSense=false
Show me button pressed
/SYS/MB/BUTTONS.ShowMePressed=1
Below table lists the Conditions, which are grouped by layers in LDC:
HDMI-TPS-TX200 series
User’s Manual
* Referring to SW4-TPS-TX-240. The port numbers are only for references. Exact port numbers
can be found in section 11.4 on page 118.
Section 6. Software control – using Lightware Device Controller (LDC) Page 55 / 122
Table 6-1. Conditions of the Event Manager Wizard
Page 56
Layer
Action
Path and value in LW3 protocol tree*
Video
Switch output to input
/MEDIA/VIDEO/XP1:switch(P1:P5)
Switch output to next
input
/SYS/MB:SwitchToNextSource(V)
Enable autoselect on
output
/MEDIA/VIDEO/XP1:setDestinationPortAutoselect(P5:E)
Disable autoselect on
output
/MEDIA/VIDEO/XP1:setDestinationPortAutoselect(P5:D)
Audio
Switch output to input:
/MEDIA/AUDIO/XP1:switch(P1:P6)
Switch output to next
input
/SYS/MB:SwitchToNextSource(A)
Enable autoselect on
output
/MEDIA/AUDIO/XP1:setDestinationPortAutoselect(P6:E)
Disable autoselect on
output
/MEDIA/AUDIO/XP1:setDestinationPortAutoselect(P6:D)
GPIO
Set output state to “High”
/MEDIA/GPIO/P1.Output=H
Set output state to “Low”
/MEDIA/GPIO/P1.Output=L
Toggle output state
/MEDIA/GPIO/P1:toggle()
RS-232
Send RS232 message
/MEDIA/UART/P1:sendMessage(…)
Actions of the Event Manager Wizard
Below table lists the Actions, which are grouped by layers in LDC:
* Referring to SW4-TPS-TX-240. The port numbers are only for references. Exact port numbers
can be found in section 11.4 on page 118.
6.9.3. Advanced mode
The goal of this mode is the same as 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. The LW3 protocol tree allows almost all the methods and settings to select.
Step 1. Click on the Advanced button; a new window pops up.
Step 2. Select the desired node: click on the folder sign.
Table 6-2. Actions of the Event Manager Wizard
Page 56 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 57
HDMI-TPS-TX200 series
Export
Import
Clear
Load factory defaults
User’s Manual
The tree structure is opened and the available properties are listed in the drop-down box.
The manual of the selected property can be seen below it.
Step 3. Set the desired value in the field next to the list.
Step 4. Click on the OK button to save the settings.
If the condition is finished, set the action with the same method. In case of advanced mode,
the type of the condition and the action is custom (in red square).
The system checks the validity of the event. If everything is correct, a green line can be
seen at the bottom of the event area. Name the event and press the Set name button.
6.9.4. Save, load or clear an event
Save
Although the device stores the set events, – even after reboot or firmware
upgrade – in some cases event saving to the computer can be useful (e.g.
transfer to another TPS device). Events can be stored in a readable CSV
file (Comma Separated Values) which is a human readable file type and can be
imported/edited by many spreadsheet application.
Info: Events cannot be exported one by one. All events will be stored with the exportation.
To save all events click on “Export to CSV”, browse the desired folder, then click “Save”.
Load
Click on the “Import from CSV” button. A browse window comes up. Find
the .CSV file than click on the “Open” button.
Clear
Click on the “Clear” button, a confirmation window comes up. Click on the
OK button to clear the event. Clearing the events means setting them to
the factory default values. The names become Event1..20, the condition
and the action get empty value.
Section 6. Software control – using Lightware Device Controller (LDC) Page 57 / 122
Clear all events
All events can be cleared at the same time with the loading
factory default values. All the values will be cleared: names,
conditions, actions. Click on the “Load factory defaults” button. A warning message
appears. Confirm it by clicking on the OK button.
Page 58
6.10. Settings menu
Device status information and network settings are available in this menu, function buttons
help to do operations in connection with logs and device settings.
6.10.1. Status tab
General information is shown on this tab, such as device label, part number, serial number
and hardware health, voltage and temperature values.
6.10.2. Network tab
Network-related settings are available on the tab. The first three (two) lines are valid when
the device has a fix IP address. If dynamic IP address is used, the DHCP setting shall be
set to enabled and the IP parameters will be indicated below the drop-down menu.
Figure 6-11. Status tab
Figure 6-12. Network tab
Since the device is able to communicate with LW2 and LW3 protocols, the ports can also
be set here. Always press the Apply changes button after modification to store the settings;
you will be prompted to reboot the device to apply changes in practice.
Page 58 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 59
6.10.3. Backup tab
The transmitter’s settings can be saved and loaded to/from the computer. When creating a
backup, the following settings are stored:
All ports’ AND crosspoint settings (writeable properties’ values) of all layers,
All EDID data stored in the User memory,
All Control settings set on the Control tab,
All Events (from the Event manager) and
Network settings.
HDMI-TPS-TX200 series
User’s Manual
Figure 6-13. Backup tab
Create a full backup
Step 1. Arrange the desired settings in the transmitter.
Step 2. Navigate to Settings/Backup menu.
Step 3. Write a short description in the textbox on the left (optionally).
Step 4. Press the Create a full backup button. You will be prompted to save the file to the
computer (select the desired folder and save the file).
Restore a backup file
Previously saved backup file can be restored as follows:
Step 1. Navigate to the Settings/Backup 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. Press the Start restore process button. The process is displayed in a small window;
when finished, you can continue the work with the LDC.
Important: Please note that the settings will be overwritten with the restored parameters in the
transmitter permanently. Withdrawal is not possible.
Section 6. Software control – using Lightware Device Controller (LDC) Page 59 / 122
Page 60
6.10.4. Function buttons
2 1 4
3
1
2 3 4
System log button: Logged events can be collected and saved into a file which is
useful when troubleshooting or in other special case for analyzing. When the
collecting is done, the Save as window appears; select the desired location and
press the Save button.
Info: Please note that the data collecting may take some minutes. You will be prompted about
log generating before starting.
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 section 11.5 on page 120.
Reboot button: The device can be restarted; the connection will be terminated.
6.11. Advanced view
Advanced view is the surface for LW3 protocol tree with terminal window. Commands and
specific parameters (which are not available on the user interface) can be run and set.
Detailed information about the protocol, nodes, methods and parameters can be found in
chapter 8 on page 77. Click on Close button to hide the Advanced view.
Terminal window Commands and responses with time and date are listed in this
window. Sent command is displayed in red and starts with ‘>’
character, received response is displayed in blue and starts with ‘<’
character. 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.
Command line Type the desired command and execute it by the Send button.
Protocol tree LW3 protocol tree; select an item to see its content.
Node list Correspondent parameters and nodes are shown which are
connected to the selected item in the protocol tree.
Manual button: Manual (short description) of the node can be
called and displayed in the terminal window. See
more information about manuals in section 8.3.4
on page 84.
Set button: Saves the value/parameter typed in the textbox.
Call button: Calls the method, e.g. reloads factory default
settings.
Page 60 / 122 Section 6. Software control – using Lightware Device Controller (LDC)
Page 61
7. LW2 Programmer’s reference
Format
Example
Command
{i} → {i}
Response
(I:<PRODUCT_TYPE>)CrLf
←
(I:SW4-TPS-TX240)CrLf
Format
Example
Command
{P_?}
→
{P_?}
Response
(CURRENT●PROTOCOL●=
●#<protocol>)CrLf
←
(CURRENT PROTOCOL = #1)CrLf
The device can be controlled through a reduced command set of LW2 protocol commands
to ensure the compatibility with other Lightware products. The supported LW2 commands
are described in this chapter.
7.1. LW2 protocol description
The device accepts commands surrounded by curly brackets - { } - and responds data
surrounded by round brackets - ( ) - only if a command was successfully executed.
Legend for control commands:
<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²> = input number in 2 digit ASCII format (01, 02, 10, 12 etc.)
<out²> = output number in 2 digit ASCII format (01, 02, 10, 12 etc.)
<loc> = location number in 1, 2 or 3 digit ASCII format
<id> = id number in 1 or 2 digit ASCII format
HDMI-TPS-TX200 series
User’s Manual
<id²> = 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
7.2. General LW2 commands
7.2.1. View product type
Description: The transmitter responds its name.
Explanation: The connected device is an SW4-TPS-TX240 device.
Legend: <PRODUCT_TYPE> shows type.
7.2.2. Query control protocol
Description: The transmitter can be controlled with different control protocols. This
command queries the active protocol for the used control interface.
Explanation: The device communicates with LW2 protocol.
Section 7. LW2 Programmer’s reference Page 61 / 122
Page 62
Format
Example
Command
{f} → {f}
Response
(FW:<FW_VER><s>)CrLf
←
(FW:1.0.3b1 r1256)CrLf
Format
Example
Command
{PING}
→
{ping}
Response
(PONG!)CrLf
←
(PONG!)CrLf
Format
Example
Command
{s} → {s}
Response
(SN:<SERIAL_N>)CrLf
←
(SN:12345678)CrLf
Format
Example
Command
{CT}
→
{ct}
Response
(Complied: <DATE&TIME>)
CrLf
←
(Compiled: Mar 4 2015 19:41:43)
CrLf
Format
Example
Command
{is} → {is}
Response
(SL#●0●<MB_DESC>)CrLf
(SL●END)CrLf
←
←
(SL# 0 SW4-TPS-TX240 V10_2b)
CrLf
(SL END)CrLf
Format
Example
Command
{FC}
→
{fc}
Response
(CF●<DESC>)CrLf
(CF●<DESC>)CrLf
…
(CF END)CrLf
←
←
(CF SW4-TPS-TX240 1.0.3b1
r1256)CrLf
(CF END) CrLf
7.2.3. View firmware version of the CPU
Description: View the CPU firmware revision.
Legend: <FW_VER> is the firmware version. It is followed by <s> string which may indicate
special versions. <s>=r indicates standard version.
7.2.4. Connection test
Description: Simple test to see if the connection is established successfully.
7.2.5. View serial number
Description: The transmitter responds its 8-digit serial number.
7.2.6. Compile time
Description: Returns the date, when the microcontroller firmware was compiled.
7.2.7. View installed board(s)
Description: Shows the hardware name and revision of the installed cards.
Explanation: The device reports its motherboard (slot 0).
7.2.8. View firmware for all controllers’
Description: Shows the firmware versions of all installed controllers.
Explanation: The device has one control panel.
Page 62 / 122 Section 7. LW2 Programmer’s reference
Page 63
7.2.9. Restart the device
Format
Example
Command
{RST}
→
{RST}
Format
Example
Command
{ST}
→
{st}
Response
(ST●<12V>●<5V>●<1.8V>●
<1.2V>●<1V>●<Temp>)
CrLf
←
(ST CPU 11.96V N/A 1.83V N/A
1.02V 38.74C)CrLf
Format
Example
Command
{FACTORY=ALL}
→
{factory=all}
Response
(FACTORY ALL…)CrLf
←
(FACTORY ALL…)CrLf
Format
Example
Command
{<in>@<out>●<layer>}
→
{2@1 av}
Response
(O<out²>●I<in²>●<layer>)CrLf
←
(O01 I02 AV)CrLf
<layer>
Layer
A
Audio layer
V
Video layer
AV (or nothing)
Audio & Video layer
Description: The device can be restarted without unplugging power.
Explanation: The device reboots; no response is sent in this case.
7.2.10. Query health status
Description: Measured internal voltages and temperature values are shown.
7.2.11. Restore factory default settings
Description: Settings can be reset to factory default values as follows:
HDMI-TPS-TX200 series
User’s Manual
Explanation: All settings and parameters are reset to factory default, see the table in
section 11.5 on page 120.
7.3. Port and crosspoint settings
7.3.1. Switch one input to one output
Following commands with <A/V/AV> option can take effect in multiple layers, according to
their parameters. Depending on ‘A’ or ‘V’ it can change only the Audio, or only the Video
layer; or ‘AV’ changes both.
Info: <A/V/AV> option usually can be skipped for legacy purposes. In this case the devices
changes all (Video & Audio) layers, but using status commands it displays information
about only the Video layer. Please use AV option, when available.
Description: Switch input <in> to output <out>.
Explanation: I2 audio and I2 video ports are switched to O1 port.
Legend:
Info: The response of this command does not show if the output is muted. To check the mute
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Section 7. LW2 Programmer’s reference Page 63 / 122
<out>: O1 or O2 output port
<in>: Input port. The port numbering is different in the devices. See
the details in section 11.4 on page 118.
status a separate query has to be used like {VC}. See section 7.3.6 on page 65.
Page 64
Format
Example
Command
{#<out>●<layer>}
→
{#01 A}
Response
(1MT<out²>●<layer>)CrLf
←
(1MT01 A)CrLf
Format
Example
Command
{+<out>●<layer>}
→
{+01 A}
Response
(0MT<out²>●<layer>)CrLf
←
(0MT01 A)CrLf
Format
Example
Command
{#><out>●<layer>}
→
{#>01 A}
Response
(1LO<out²>●<layer>)CrLf
←
(1LO01 A)CrLf
Format
Example
Command
{+<<out>●<layer>}
→
{+<01 A}
Response
(0LO<out²>●<layer>)CrLf
←
(0LO01 A)CrLf
7.3.2. Mute specified output
Description: Mute output <out>. The output signal is turned off.
Explanation: The O1 audio port is muted.
Legend: See section 7.3.1 on page 63.
Info: Muting does not change the crosspoint state, but disables the output itself. This way the
last connection can be easily restored with an unmute command.
Info: Switching a muted output does not unmute the output.
7.3.3. Unmute specified output
Description: Unmute output <out>.
Explanation: The O1 audio port is unmuted.
Legend: See section 7.3.1 on page 63.
Info: Unmuting an output makes the previous connection active as the crosspoint state has not
been changed by the muting command, only the output was disabled.
7.3.4. Lock the output
Description: Lock an output port. Output’s state cannot be changed until unlocking.
Explanation: O1 audio output port is locked.
Legend: See section 7.3.1 on page 63.
7.3.5. Unlock the output
Description: Unlock an output port. The connection on output can be changed.
Explanation: O1 audio output port is unlocked.
Page 64 / 122 Section 7. LW2 Programmer’s reference
Legend: See section 7.3.1 on page 63.
Info: The device issues the above response regardless of the previous state of the output (either
it was locked or unlocked).
Page 65
7.3.6. View connection state on the output
Format
Example
Command
{VC●<layer>}
→
{vc av}
Response
(ALL<layer>●<O01>●<O02>)
CrLf
← ← (ALLV 02 02)CrLf
(ALLA 05 05)CrLf
<layer>
Layer
A
Audio layer
V
Video layer
AV*
Audio & Video layer
Format
Example
Command
{getsize●<layer>}
→
{getsize av}
Response
(SIZE=<size>●<layer>)CrLf
← ← (SIZE=5x2 V)CrLf
(SIZE=5x2 A)CrLf
Format
Example
Command
{AS_V<out>}
→
{as_v1}
Response
(AS_V<out>=<state>;
<mode>;<no_signal>)CrLf
←
(AS_V1=E;K;B)CrLf
Description: Viewing the crosspoint state of the device; showing the input port numbers
connected to the outputs. The response below refers to an SW4-TPS-TX240.
Legend: O01 and O02 show the corresponding output’s connection state. If value<O01>
equals 02 it means that output 1 is connected to input 2.
* AV is not used in the response. When AV is typed in the commands, the response will
result two lines, one for the Video and one for the Audio port states.
Explanation: I2 video input port is connected to the video output ports and I5 audio input
port is connected to the audio output ports.
HDMI-TPS-TX200 series
User’s Manual
Info: If an output is locked, muted, or both locked and muted, the response format changes. If
outputs are muted you get a letter 'M', if locked a letter 'L' and if muted and locked at the
same time 'U' before the 2 digit numbers.
7.3.7. View crosspoint size
Description: Shows the physical crosspoint size.
Legend: <size>: <number of inputs>x<number of outputs>
<layer>: See section 7.3.6 on page 65.
Explanation: The device reports that it has a video crosspoint with 5 inputs and 2 outputs,
and an audio crosspoint with 5 inputs and 2 outputs.
7.3.8. Query video Autoselect mode
Description: The autoselect mode of video outputs can be queried.
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Section 7. LW2 Programmer’s reference Page 65 / 122
Legend: <out>: The output port number. See more details about port
numbering in section 11.4 on page 118.
<state>: E = Autoselect is enabled; D = Autoselect is disabled
<mode>: P = Priority detect; K = First detect; L = Last detect
<no_signal>: B = Blank screen; M = Mute output
Explanation: The Autoselect mode is enabled in first detect mode, and if there is no
incoming signal at all, the crosspoint is not changed (blank screen is shown).
For more information about the autoselect modes see the section 5.1 on page 28.
Page 66
Format
Example
Command
{AS_V<out>=<state>;
<mode>;<no_signal>}
→
{as_v1=E;K;B}
Response
(AS_V<out>=<state>;
<mode>;<no_signal>)CrLf
←
(AS_V1=E;K;B)CrLf
Format
Example
Command
{AS_A<out>}
→
{as_a1}
Response
(AS_A<out>=<state>;
<mode>;<no_signal>)CrLf
←
(AS_A1=E;K;B)CrLf
Format
Example
Command
{AS_A<out>=<state>;
<mode>;<no_signal>}
→
{as_a1=E;K;B}
Response
(AS_A<out>=<state>;
<mode>;<no_signal>)CrLf
←
(AS_A1=E;K;B)CrLf
7.3.9. Change video Autoselect mode
Description: The autoselect mode of the video outputs can be changed.
Legend: See section 7.3.8 on page 65.
Explanation: The Autoselect mode is enabled in first detect mode, and if there is no
incoming signal at all, the crosspoint is not changed (blank screen is shown).
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
7.3.10. Query audio Autoselect mode
Description: The autoselect mode of audio outputs can be queried.
Legend: <out>: The output port number. See more details about port
numbering in section 11.4 on page 118.
<state>: E = Autoselect is enabled; D = Autoselect is disabled
<mode>: P = Priority detect; K = First detect; L = Last detect; S = Static
<no_signal>: B = Blank; M = Mute output
Explanation: The Autoselect mode is enabled in first detect mode, and if there is no
incoming signal at all, the crosspoint is not changed.
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
7.3.11. Change audio Autoselect mode
Description: The autoselect mode of audio output ports can be changed.
Legend: See section 7.3.8 on page 65.
Explanation: The Autoselect mode is enabled in first detect mode, and if there is no
incoming signal at all, the crosspoint is not changed.
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Page 66 / 122 Section 7. LW2 Programmer’s reference
Page 67
HDMI-TPS-TX200 series
Format
Example
Command
{PRIO_V<out>}
→
{prio_v1}
Response
(PRIO_V<out>=<in1_prio>;
<in2_prio>;..;<inn_prio>)CrLf
←
(PRIO_V1=1;0;2;3;31)CrLf
Format
Example1
Command
{PRIO_V<out>=<in1_prio>;
<in2_prio>;…;<inn_prio>}
→
{prio_v1=1;0;2;3;4}
Response
(PRIO_V<out>=<in1_prio>;
<in2_prio>;…;<inn_prio>)CrLf
←
(PRIO_V1=1;0;2;3;4)CrLf
Format
Example
Command
{PRIO_A<out>}
→
{prio_a1}
Response
(PRIO_A<out>=<in1_prio>;
<in2_prio>;..;<inn_prio>)CrLf
←
(PRIO_A1=1;0;2;3;31)CrLf
User’s Manual
7.3.12. Query the video input port priority
Description: The priority order of the input ports can be queried as follows.
Legend: <out>: The output port number.
<in1_prio>…<inn_prio>: Input ports’ priority number. See more details
about port numbering in section 11.4 on page 118.
Explanation: I2 has the highest priority (0), I1 has the second highest priority number (1).
I5 has priority 31 which is the lowest possible setting; it means I5 is disabled from the
priority list and will not be selected.
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
7.3.13. Change video input priority
Description: The priority order of video input ports can be changed as follows.
Legend: <out>: The output port number.
<in1_prio>…<inn_prio>: Input ports’ priority number. See more details about
port numbering in section 11.4 on page 118.
Explanation: I2 has the highest priority (0), I1 has the second highest (1). I5 has the lowest
priority (4).
Info: 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).
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
7.3.14. Query audio input port priority
Description: The settings of audio input priority can be queried as follows.
Legend: <out>: The output port number.
<in1_prio>…<inn_prio>: Input ports’ priority numbers. See more details
about port numbering in section 11.4 on page 118.
Explanation: I2 has the highest priority (0), I1 has the second highest priority number (1).
I5 has priority 31 which is the lowest possible setting; it means I5 is disabled from the
priority list and will not be selected.
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Section 7. LW2 Programmer’s reference Page 67 / 122
Page 68
Format
Example
Command
{PRIO_A<out>=<in1_prio>;
<in2_prio>;…;<in
n
_prio>}
→
{prio_a1=1;0;2;3;4}
Response
(PRIO_A<out>=<in1_prio>;
<in2_prio>;…;<in
n
_prio>)CrLf
←
(PRIO_A1=1;0;2;3;4)CrLf
One by one commands
Batch commands
→
{2@1 V}CrLf
→
{02@01 V}{05@01 A}CrLf
←
(O01 I02 V)CrLf
←
(O01 I02 V)CrLf
←
(O01 I02 A)CrLf
←
(O01 I02 A)CrLf
←
(O02 I02 V)CrLf
←
(O02 I02 V)CrLf
←
(O02 I02 A)CrLf
←
(O02 I02 A)CrLf
←
(O01 I05 A)CrLf
←
(O02 I05 A)CrLf
→
{5@1 A}CrLf
←
(O01 I05 A)CrLf
←
(O02 I05 A)CrLf
7.3.15. Change audio input priority
Description: The settings of audio input priority can be changed as follows.
Legend: <out>: The output port number.
<in1_prio>…<inn_prio>: Input ports’ priority number. See more details about
port numbering in section 11.4 on page 118.
Explanation: I2 has the highest priority (0), P1 has the second highest (2). P5 has the
lowest priority (5).
Info: 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).
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
7.3.16. Batch switch outputs
Description: 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
to the device with less than 10 milliseconds delay, the commands are collected and
changes the output connections 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 be unlocked
If any of the above circumstances fail, then the commands will be processed separately.
Info: 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 result that
batch switching does not occur.
The below example shows a command that resulted batch switching:
Page 68 / 122 Section 7. LW2 Programmer’s reference
Page 69
7.4. RS-232 port configuration
Format
Example
Command
{RS232=?}
→
{rs232=?}
Response
(RS232=<mode>)CrLf
←
(RS232=CONTROL)CrLf
Format
Example
Command
{RS232=<mode>}
→
{rs232=pass}
Response
(RS232=<mode>)CrLf
←
(RS232=PASS)CrLf
Format
Example1
Command
{RS232_LOCAL_FORMAT=?}
→
{rs232_local_format=?}
Response
(RS232_LOCAL_FORMAT=
<baud>;<data bits>; <parity>;
<stop bits>)CrLf
←
(RS232_LOCAL_FORMAT=57600;
8;N;1)CrLf
Format
Example2
Command
{RS232_LINK_FORMAT=?}
→
{rs232_link_format=?}
Response
(RS232_LINK_FORMAT=
<baud>;<data bits>;
<parity>; <stop bits>)CrLf
←
(RS232_LINK_FORMAT=9600;
8;N;1)CrLf
7.4.1. Query the RS-232 mode
Description: The RS-232 mode can be queried as follows:
Legend: <mode>: CONTROL = Control mode is enabled,
PASS = Pass mode is enabled,
CI = Command injection mode is enabled.
Explanation: Current RS-232 mode is Control mode.
7.4.2. Change RS-232 mode
Description: The RS-232 mode can be changed as follows:
HDMI-TPS-TX200 series
User’s Manual
Legend: See section 7.4.1 on page 69.
Explanation: The RS-232 mode is set to Pass mode.
7.4.3. Query the RS-232 port settings
Description: The RS-232 port settings can be queried as follows:
Legend: <baud>: Baud rate which can be 4800, 7200, 9600, 14400, 19200,
38400, 57600, 115200
<data bits>: 8 or 9
<parity>: N (none), O (odd), E (even)
<stop bits>: 1, 1.5, 2
Explanation1: Current RS-232 settings on local port: Baud rate is 57600, 8 data bits, no
parity, 1 stop bit.
Legend: Same as above.
Explanation2: Current RS-232 settings on link port: Baud rate is 9600, 8 data bits, no
parity, 1 stop bit.
Section 7. LW2 Programmer’s reference Page 69 / 122
Page 70
Format
Example1
Command
{RS232_LOCAL_FORMAT=
<baud>;<data bits>;
<parity>; <stop bits>}
→
{rs232_local_format=57600;9;N;1}
Response
(RS232_LOCAL_FORMAT=
<baud>;<data bits>;
<parity>; <stop bits>)CrLf
←
(RS232_LOCAL_FORMAT=57600;
9;N;1)CrLf
Format
Example2
Command
{RS232_LINK_FORMAT=
<baud>;<data bits>;
<parity>; <stop bits>}
→
{rs232_link_format=9600;9;N;1}
Response
(RS232_LINK_FORMAT=
<baud>;<data bits>;
<parity>; <stop bits>)CrLf
←
(RS232_LINK_FORMAT=9600;
9;N;1)CrLf
Format
Example1
Command
{RS232_LOCAL_PROT=?}
→
{rs232_local_prot=?}
Response
(RS232_LOCAL_PROT=
<protocol>)CrLf
←
(RS232_LOCAL_PROT=
LW2)CrLf
Format
Example2
Command
{RS232_LINK_PROT=?}
→
{rs232_link_prot=?}
Response
(RS232_LINK_PROT=
<protocol>)CrLf
←
(RS232_LINK_PROT=
LW2)CrLf
7.4.4. Change RS-232 port settings
Description: The RS-232 port settings can be set as follows:
Legend: See section 7.4.3 on page 69.
Explanation1: RS-232 settings on the local port have been set as follows: Baud rate is
57600, 9 data bits, no parity, 1 stop bit.
Legend: See section 7.4.3 on page 69.
Explanation2: RS-232 settings on the link port have been set as follows: Baud rate is
9600, 9 data bits, no parity, 1 stop bit.
Info: If the device is connected to an MX-TPS-IB, the port settings (Baud rate, databits, stop bits,
parity) are ignored, since the followings pre-defined values are valid: 115200 8N1.
7.4.5. Query the RS-232 protocol
Description: The RS-232 protocol can be queried as follows:
Legend: <protocol>: LW2 or LW3.
Explanation1: Current protocol on local RS-232 port is LW2.
Legend: <protocol>: LW2 or LW3
Explanation2: Current protocol on link RS-232 port is LW2.
Page 70 / 122 Section 7. LW2 Programmer’s reference
Page 71
HDMI-TPS-TX200 series
Format
Example1
Command
{RS232_LOCAL_PROT=
<protocol>}
→
{rs232_local_prot=LW3}
Response
(RS232_LOCAL_PROT=
<protocol>)CrLf
←
(RS232_LOCAL_PROT=LW3)CrLf
Format
Example2
Command
{RS232_LINK_PROT=
<protocol>}
→
{rs232_link_prot=LW3}
Response
(RS232_LINK_PROT=
<protocol>)CrLf
←
(RS232_LINK_PROT=LW3)CrLf
Format
Example
Command
{IP_STAT=?}
→
{ip_stat=?}
Response
(IP_STAT=<type>;<ip_
address>;<subnet_mask>;
<gateway_addr>)CrLf
←
(IP_STAT=1;192.168.0.102;
255.255.255.0;192.168.0.1)CrLf
Format
Example
Command
{IP_ADDRESS=?}
→
{ip_address=?}
Response
(IP_ADDRESS=<type>;
<ip_address>)CrLf
←
(IP_ADDRESS=0;192.168.0.100)
CrLf
User’s Manual
7.4.6. Change RS-232 protocol
Description: The RS-232 protocol can be set as follows:
Legend: <protocol>: LW2 or LW3
Explanation1: Current protocol on local RS-232 port is set to LW3.
Legend: <protocol>: LW2 or LW3
Explanation2: Current protocol on link RS-232 port is set to LW3.
Info: If the device is connected to an MX-TPS-IB board, the active protocol is always LW2 on
the link RS-232 port, LW3 is not supported through the link in this case. Besides the port
settings (Baud rate, databits, stop bits, parity) are ignored, since the followings pre-defined
values are valid: 115200, 8N1. The user can set the protocol to LW3, but this setting will
take effect only after connecting the transmitter to a TPS-RX-90/95 receiver.
7.5. Network configuration
7.5.1. Query the current IP status
Description: IP address settings can be queried as follows.
Legend: <type>: 0 = fix IP; 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 dynamic IP address: 192.168.0.102; subnet mask is
255.255.255.0, gateway address is 192.168.0.1.
7.5.2. Query the IP address
Description: IP address can be queried from the device with this command.
Legend: <type>: 0 = fix IP; 1 = DHCP
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.
Section 7. LW2 Programmer’s reference Page 71 / 122
Page 72
Format
Example
Command
{IP_ADDRESS=<type>;
<ip_address>}
→
{ip_address=0;192.168.0.100}
Response
(IP_ADDRESS=<type>;
<ip_address>)CrLf
←
(IP_ADDRESS=0;192.168.0.100)
CrLf
Format
Example
Command
{IP_NETMASK=?}
→
{ip_netmask=?}
Response
(IP_NETMASK=<subnet_
mask>)CrLf
←
(IP_NETMASK=255.255.255.0)CrLf
Format
Example
Command
{IP_NETMASK=<subnet_
mask>}
→
{ip_netmask=255.255.255.0}
Response
(IP_NETMASK=<subnet_
mask>)CrLf
←
(IP_NETMASK=255.255.255.0)CrLf
Format
Example
Command
{IP_GATEWAY=?}
→
{ip_gateway=?}
Response
(IP_GATEWAY=<gateway_
addr>)CrLf
←
(IP_GATEWAY=192.168.0.1)CrLf
Format
Example
Command
{IP_GATEWAY=<gateway_
addr>}
→
{ip_gateway=192.168.0.50}
Response
(IP_GATEWAY=<gateway_
addr>)CrLf
←
(IP_GATEWAY=192.168.0.50)CrLf
7.5.3. Set the IP address
Description: IP address can be set as follows.
Legend: <type>: 0 = fix IP; 1 = DHCP
Info: Restarting the transmitter is necessary to apply the changes after modification.
7.5.4. Query the subnet mask
Description: Subnet mask can be queried as follows.
Legend: <subnet_mask>: Four decimal octets separated by dots.
Info: The response contains the fix subnet mask that is stored in the device even if DHCP is
enabled; in this case this subnet mask is not valid.
7.5.5. Set the subnet mask
Description: Subnet mask can be set as follows.
Legend: <subnet_mask>: Four decimal octets separated by dots.
7.5.6. Query the gateway address
Description: Gateway address can be queried as follows.
Legend: <gateway_addr>: Four decimal octets separated by dots.
Info: The response contains the fix gateway address that is stored in the device even if DHCP
is enabled; in this case this gateway address is not valid.
7.5.7. Set the gateway address
Description: Gateway address can be set as follows.
Legend: <gateway_addr>: Four decimal octets separated by dots.
Page 72 / 122 Section 7. LW2 Programmer’s reference
Page 73
7.5.8. Query the TCP/IP port
Format
Example1
Command
{LW2_PORT=?}
→
{lw2_port=?}
Response
(LW2_PORT=<port_nr>)CrLf
←
(LW2_PORT=10001)CrLf
Format
Example2
Command
{LW3_PORT=?}
→
{lw3_port=?}
Response
(LW3_PORT=<port_nr>)CrLf
←
(LW3_PORT=6107)CrLf
Format
Example1
Command
{LW2_PORT=<port_nr>}
→
{lw2_port=10001}
Response
(LW2_PORT=<port_nr>)CrLf
←
(LW2_PORT=10001)CrLf
Format
Example2
Command
{LW3_PORT=<port_nr>}
→
{lw3_port=6107}
Response
(LW3_PORT=<port_nr>)CrLf
←
(LW3_PORT=6107)CrLf
Format
Example
Command
{ETH_ENABLE=?}
→
{eth_enable=?}
Response
(ETH_ENABLE=<cpu>;
<local>;<link>)CrLf
←
(ETH_ENABLE=1;1;1)CrLf
Format
Example
Command
{ETH_ENABLE=<cpu>;
<local>;<link>}
→
{eth_enable=X;X;0}
Response
(ETH_ENABLE=<cpu>;
<local>;<link>)CrLf
←
(ETH_ENABLE=1;1;0)CrLf
Description: TCP/IP port setting can be queried as follows.
Explanation1: The port number for LW2 protocol is 10001 (default value).
Explanation2: The port number for LW3 protocol is 6107 (default value).
7.5.9. Set the TCP/IP port
Description: TCP/IP port setting can be set as follows.
HDMI-TPS-TX200 series
User’s Manual
Explanation1: The port number for LW2 protocol is set to 10001 (default value).
Explanation2: The port number for LW3 protocol is set to 6107 (default value).
7.5.10. Query the status of Ethernet ports
Description: The link, the local Ethernet ports, and the TCP/IP connections to the CPU
can be queried with this command.
Legend: <cpu>: 0 = TCP/IP disabled, 1 = TCP/IP enabled
<local>: 0 = local Ethernet is disabled, 1 = local Ethernet is enabled
<link>: 0 = link Ethernet is disabled, 1 = link Ethernet is enabled
Explanation: The gateway address is set to 192.168.0.50.
7.5.11. Set the status of Ethernet ports
Section 7. LW2 Programmer’s reference Page 73 / 122
Description: Enable or disable the link, the local Ethernet ports, and the TCP/IP
connections to the CPU.
Legend: see section 7.5.10 on page 73.
“X” parameter can be used to prevent modifying a parameter.
Explanation: The link Ethernet port is set to disabled, the other ports are not modified.
Page 74
7.6. GPIO settings
Format
Example
Command
{GPIO<pin_nr>=?}
→
{gpio1=?}
Response
(GPIO<pin_nr>=<direction>;
<level>)CrLf
←
(GPIO1=I;H)CrLf
Format
Example
Command
{GPIO<pin_nr>=<direction>;
<level>}
→
{gpio1=i;l}
Response
(GPIO<pin_nr>=<direction>;
<level>)CrLf
←
(GPIO1=I;L)CrLf
7.6.1. Query the state of a GPIO pin
Description: The state of a GPIO pin can be queried as follows.
Legend: <pin_nr>: GPIO pin number (1-7).
<direction>: Direction of the pin: I = input, O = output
<level>: H = high level, L = low level.
Explanation: GPIO pin #1 is input, input level is high.
7.6.2. Set the state of a GPIO pin
Description: The state of a GPIO pin can be set as follows.
Legend: See section 7.6.1 on page 74.
Explanation: GPIO pin #1 is set as input, input level is low.
Page 74 / 122 Section 7. LW2 Programmer’s reference
Page 75
7.7. LW2 commands – Quick summary
Operation
See in
chapter
Command
View product type
7.2.1
{i}
Query control protocol
7.2.2
{P_?}
View firmware version of the CPU
7.2.3
{F}
Connection test
7.2.4
{PING}
View serial number
7.2.5
{S}
Compile time
7.2.6
{CT}
View installed board(s)
7.2.7
{IS}
View firmware for all controllers’
7.2.8
{FC}
Restart the device
7.2.9
{RST}
Query health status
7.2.10
{ST}
Restore factory default settings
7.2.11
{FACTORY=ALL}
Operation
See in
chapter
Command
Switch one input to one output
7.3.1
{<in>@<out>●<layer>}
Mute specified output
7.3.2
{#<out>●<layer>}
Unmute specified output
7.3.3
{+<out>●<layer>}
Lock the output
7.3.4
{#><out>●<layer>}
Unlock the output
7.3.5
{+<out>●<layer>}
View connection state on the output
7.3.6
{VC●<layer>}
View crosspoint size
7.3.7
{GETSIZE●<layer>}
Query video Autoselect mode
7.3.8
{AS_V<out>}
Change video Autoselect mode
7.3.9
{AS_V<out>=<state>;<mode>;<no_signal}>
Query audio Autoselect mode
7.3.10
{AS_A<out>}
Change audio Autoselect mode
7.3.11
{AS_A<out>=<state>;<mode>;<no_signal>}
Query the video input port priority
7.3.12
{PRIO_V<out>}
Change video input priority
7.3.13
{PRIO_V<out>=<in1_prio>;…;<inn_prio>}
Query audio input port priority
7.3.14
{PRIO_A<out>}
Change audio input priority
7.3.15
{PRIO_A<out>=<in1_prio>;…;<inn_prio>}
Batch switch outputs
7.3.16
{<in>@<out>●<layer>}{<in>@<out>●<layer>}
General LW2 commands
HDMI-TPS-TX200 series
User’s Manual
Port and crosspoint settings
Section 7. LW2 Programmer’s reference Page 75 / 122
Page 76
RS-232 port configuration
Operation
See in
chapter
Command
Query the RS-232 mode
7.4.1
{RS232=?}
Change RS-232 mode
7.4.2
{RS232=<mode>}
Query the RS-232 port settings
7.4.3
{RS232_LOCAL_FORMAT=?}
Change RS-232 port settings
7.4.4
{RS232_LOCAL_FORMAT=<baud>;
<data bits>; <parity>; <stop bits>}
Query the RS-232 protocol
7.4.5
{RS232_LOCAL_PROT=?}
Change RS-232 protocol
7.4.6
{RS232_LOCAL_PROT=<protocol>}
Operation
See in
chapter
Command
Query the current IP status
7.5.1
{IP_STAT=?}
Query the IP address
7.5.2
{IP_ADDRESS=?}
Set the IP address
7.5.3
{IP_ADDRESS=<type>;<ip_address>}
Query the subnet mask
7.5.4
{IP_NETMASK=?}
Set the subnet mask
7.5.5
{IP_NETMASK=<subnet_mask>}
Query the gateway address
7.5.6
{IP_GATEWAY=?}
Set the gateway address
7.5.7
{IP_GATEWAY=<gateway_addr>}
Query the TCP/IP port
7.5.8
{LW2_PORT=?}
Set the TCP/IP port
7.5.9
{LW2_PORT=<port_nr>}
Query the status of Ethernet ports
7.5.10
{ETH_ENABLE=?}
Set the status of Ethernet ports
7.5.11
{ETH_ENABLE=<cpu>;<local>;<link>}
Operation
See in
chapter
Command
Query the state of a GPIO pin
7.6.1
{GPIO<pin_nr>=?}
Set the state of a GPIO pin
7.6.2
{GPIO<pin_nr>=<direction>;<level>}
Network configuration
GPIO settings
Page 76 / 122 Section 7. LW2 Programmer’s reference
Page 77
HDMI-TPS-TX200 series
User’s Manual
8. LW3 Programmers’ reference
8.1. Overview
Lightware 3 (LW3) protocol is currently used by the UMX-TPS-TX100 series, HDMI-TPSTX200 series, the MODEX family, the 25G product line and will be the preferred protocol
in the new developments.
The protocol (LW3) 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 for implementing a human readable, but programmatically still ease
to parse, which is suitable for different products with different feature list.
In order to implement a flexible, easy-to-use protocol that is straightforward to adapt to new
devices and provides outstanding scalability and sustainability, we decided to organize all
settings, parameters and properties of the device to a tree structure with ‘nodes’,
‘properties’ and ‘methods’.
8.1.1. Elements of the tree structure
Important! All names and values are case sensitive. The space character is replaced by ‘●’ character
in the elements and commands descriptions.
Node
The basic building block of the tree structure is the ‘node’.
A node can have multiple child nodes, but only one parent.
The tree has only one root the ‘root node’.
The leaves of the tree are also nodes, which do not have child nodes.
The nodes are separated by a slash (‘/’) character.
All the slashes are ‘right slashes’, no backslash is used.
The identifier of the root node is a slash (‘/’)
Nodes’ name can contain the elements of the English alphabet and numbers.
Recommended convention for case sensitivity:
- Fix nodes (that cannot be altered) are capitalized.
- User created nodes can contain both lowercase and capital letters, no
restrictions.
The path of a node has to contain all parent nodes from the root node.
Format (the root node): nX●/
Path: nX●/[nodeName]/[nodeName]/[nodeName]
Legend: ‘n’: node
‘X’ can be:
‘-’: default for a node,
‘m’: this is a manual for the node,
‘E’: this is an error message for the node.
Info: All parent nodes must be listed in the path of a node.
Section 8. LW3 Programmers’ reference Page 77 / 122
Page 78
Following example presents the structure of the tree traversal:
Path of the nodes:
n-/node1
n-/node1/node11
n-/node1/node12
n-/node2
n-/node2/node21
n-/node2/node21/node211
n-/node3
Figure 8-1. Tree structure of nodes
Property
The ‘property’ in the LW3 protocol is basically a leaf, which has a well-defined value.
A property has a value.
A property cannot have child nodes or child properties. It is always a leaf.
A node can have any number of properties (may not have any).
A property is referenced with a dot (‘.’) after the node name.
The properties’ name can contain the elements of the English alphabet, numbers
and underscore (‘_’) character.
By convention, properties are beginning with capital letter, all other characters are
lowercase ones. In case of compound words, all words are beginning with a capital
letter (CamelCase).
The value of the property can contain any readable ASCII character.
A property can be read-only or read/write.
Format: pX●/[nodeName].[propertyName]=[propertyValue]
Legend: p: property
X can be:
‘r’: if the property is read-only.
‘w’: if the property is readable, writable.
‘m’: manual for the property.
‘E’: error message for the property.
Example:
The following two ones are read-only properties:
pr●/node1/node12.ReadOnlyProperty=value1
pr●/.DeviceName=25G Hybrid Device
The following two ones are read-write properties:
pw●/node1/node12.ReadWriteProperty=value2
pw●/.DeviceNickName=John
Page 78 / 122 Section 8. LW3 Programmers’ reference
Page 79
HDMI-TPS-TX200 series
User’s Manual
Method
The ‘method’ in the LW3 protocol is also a leaf. It cannot have a value, such as the
properties, but it can be invoked with a parameter with the help of a special ‘CALL’
command.
A method cannot have child nodes or child methods. It is always a leaf.
A node can have any number of methods (may not have any).
A method is referenced with a colon (‘:’) after the node.
The methods’ name can contain the elements of the English alphabet, numbers
and underscore (‘_’) character.
By convention, methods are beginning with lowercase letter. In case of compound
words, the very first letter is lowercase, and the first letter of each other words are
capitalized (lowerCamelCase).
The parameter of the method can contain any readable ASCII character.
The method always has a return ‘state’ if the method could be executed. The state
could be either ‘OK’ or ‘FAILED’.
The method not necessarily has a return ‘value’. If it does, it can contain additional
information, which is always specific for the current case (the return value can
specify why the execution failed).
When the method cannot be executed (e.g. the parameter list is illegal), there is an
error message.
Format: mX●/[nodeName]:[methodName]=[returnValue]
Legend: m: method
X can be:
‘O’: when the execution of the method was successful (OK),
‘F’: when the execution of the method failed,
‘m’: manual for the method,
‘E’: error message for the method.
Example:
mO●/node1/node12:method1
mO●/MEDIA/VIDEO/XP1:switch
mE●%E001:Syntax error
mm●/MEDIA/VIDEO/XP1:lockSource:Lock one or more source ports
8.1.2. Escaping
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 character that should be escaped
(like in C language).
Control characters are the followings: \ { } # % ( ) \r \n \t
Example:
The original text: John●(Doe).●#3:●5%2=1●node1\node11
The escaped text: John●\(Doe\).●\#3:●5\%2=1●node1\\node11
Section 8. LW3 Programmers’ reference Page 79 / 122
Page 80
8.1.3. Error messages
There are several error messages defined in the LW3 protocol, all of them have a unique
error number.
Format: XE●[primitive]●%EYYY:●[Error message]
Legend: X can be:
‘-’: syntax error. Cannot parse the command at all.
‘n’: node error.
‘p’: property error.
‘m’: method error.
YYY: error code, which can be one of the followings:
E001 Syntax error E010 Illegal parameter count
E002 Node not found E011 Item already exist
E003 EOL expected E012 Item does not exist
E004 Writing read-only property E013 Illegal operation
E005 Invalid value E014 Internal error
E006 Property does not exist E015 Access denied
E007 Syntax error E016 Write access denied
E008 Illegal method E017 Reserved
E009 Method does not exist E018 Waiting timeout
8.1.4. Prefix summary
The following prefixes are defined in the LW3 protocol:
‘n-’: a node,
‘nE’: an error for a node,
‘nm’: a manual for 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 success method execution,
‘mF’: a response after a failed method execution,
‘mE’: an error for a method,
‘mm’: a manual for a method.
8.2. The tree structure of the transmitter
The /MEDIA node is used by the LDC to connect input ports to output ports on different
layers. Each subnode of /MEDIA is representing a layer, e.g. video (/MEDIA/VIDEO), audio
(/MEDIA/AUDIO) or RS-232 (/MEDIA/UART). Each layer has a crosspoint to define
connections between the ports associated to the layer, all of them are represented by a
specific node. E.g. the video layer node is /MEDIA/VIDEO: under the video layer node, the
video crosspoint node (XP1) and the video ports (P1, P2, …) are located.
Page 80 / 122 Section 8. LW3 Programmers’ reference
Page 81
HDMI-TPS-TX200 series
User’s Manual
The tree structure is available in the Advanced view of LDC, see section 6.11 on page 60.
8.3. LW3 commands
8.3.1. 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.
The response format
The first two characters of a response are unambiguously identifies the type of the element
that the response line concerns. The first character is the type of the element (node,
property or method), the second is for miscellaneous information (e.g. read/write rights).
The defined prefixes are:
‘n-’: node
‘pr’: property - only readable
‘pw’: property - writable, readable
‘m-’: method executable
After the prefix the response contains the full path of the node, property or method after a
space character.
Get all children of a node
Get all of the child nodes of a parent node, with one GET command.
Command format: GET●[nodePath]
Response format: n-●[nodePath]
Example:
> GET●/MEDIA
< n-●/MEDIA/VIDEO
< n-●/MEDIA/AUDIO
< n-●/MEDIA/UART
< n-●/MEDIA/IR
< n-●/MEDIA/GPIO
< n-●/MEDIA/ETHERNET
Section 8. LW3 Programmers’ reference Page 81 / 122
Page 82
Get all properties and methods of a node
Get all properties and methods of a node, with one GET command and asterisk character.
Command format: GET●[nodePath].*
Response format: (for properties)
pX●[nodePath].[propertyName]=[parameter]
Legend: X can be:
‘r’: read-only
‘w’: read-write
Response format: (for methods)
m-●[nodePath]:[methodName]
Example:
> GET●/EDID.*
< pr●/EDID.EdidStatus=F48:E1;F49:E2;F48:E3;F48:E4;F48:E5
< m-●/EDID:switch
< m-●/EDID:switchAll
< m-●/EDID:copy
< m-●/EDID:delete
< m-●/EDID:reset
Get all child nodes, properties and methods of a node
Get all child nodes, properties and methods of a node with one command, without using a
wildchar.
Command format: GETALL●[nodePath]
Response format: (for nodes)
n-●[nodePath]
Response format: (for properties)
pX●[nodePath].[propertyName]=[parameter]
Legend: X can be:
‘r’: read-only
‘w’: read-write
Response format: (for methods)
m-●[nodePath]:[methodName]
Example:
> GETALL●/EDID
< n-●/EDID/F
< n-●/EDID/D
< n-●/EDID/U
< n-●/EDID/E
< pr●/EDID.EdidStatus=F48:E1;F49:E2;F48:E3;F48:E4;F48:E5
< m-●/EDID:switch
< m-●/EDID:switchAll
< m-●/EDID:copy
< m-●/EDID:delete
< m-●/EDID:reset
Page 82 / 122 Section 8. LW3 Programmers’ reference
Page 83
8.3.2. Set command
The setter command can be used to modify the value of a property.
Command format: SET●[nodePath].[propertyName]=[newPropertyValue]
Response format:
The response for setting a property to a new value is the same as the response for the
‘GET’ command. The value in the response is the new value if the execution of the ‘SET’
command was successful, otherwise the unmodified ‘old value’ with an error message.
pw●[nodePath].[propertyName]=[newPropertyValue]
Example:
> SET●/SYS/MB/RS232.Rs232Mode=1
< pw●/SYS/MB/RS232.Rs232Mode=1
Error response format:
If there were errors during setting a property, an error message follows the unmodified
property value.
pE●[nodePath].[propertyName]=[umodifiedValue]●%EXXX:Error message
Legend:
HDMI-TPS-TX200 series
User’s Manual
XXX: error number.
Examples:
> SET●/SYS/MB/RS232.Rs232Mode=11
< pE●/SYS/MB/RS232.Rs232Mode %E005:Invalid value
> SET●/SYS/MB/RS232/Local.ActiveProtocol=LW3
< pE●%E004:Writing read-only property
8.3.3. Invocation
A method can be invoked with the help of the ‘CALL’ command.
Command format: CALL●[nodePath]:[methodName]([parameter])
Response format:
The response for a method execution is a state and a value. The state is mandatory and
always defined, if the method could be executed. It can be either a success or a failure.
The value is optional and it can contain additional information, such as the reason why the
state is a failure or a specific value when the state is success that the client can process. It
is also possible to get an error message, when the method could not be executed – e.g.
the parameter was illegal - and hence not even the state of the execution could be
specified.
mX●[nodePath]:[methodName]=Y
Legend: X can be:
‘O’: if the execution is successful.
‘F’: if the execution is failed, but the method could be executed.
‘E’: if the method could not be executed: e.g. illegal parameter count.
Y can be:
The return value of the method if any.
It is valid that a method does not have any return value. In this case the
equal sign (‘=‘) can be omitted.
Section 8. LW3 Programmers’ reference Page 83 / 122
Page 84
Example:
Error response format:
If there were errors during the execution, an error message is received, which follows the
method name.
mE●[nodePath]:[methodName]●%EXXX:Error message
Example:
8.3.4. Manual
For every node, property and method in the tree there is a manual. The manual is a human
readable text that describes the syntax and provides a hint for how to use the primitives.
Command format:
for nodes: MAN●[nodePath]
for property: MAN●[nodePath].[propertyName]
> CALL●/EDID:switch(F48:E1)
< mO●/EDID:switch
> CALL●/EDID:switch(F48:R1)
< mE●%E001:Syntax error
for method: MAN●[nodePath]:[methodName]
Response format:
The human readable manual is separated by a space (‘ ‘) character from the primitives.
for nodes: nm●[nodePath]●Human readable manual
for properties: pm●[nodePath].[propertyName]●Human readable manual
for methods: mm●[nodePath]:[methodName]●Human readable manual
Example: (for a property)
> MAN●/SYS/MB/RS232/Local.ActiveProtocol
< pm●/SYS/MB/RS232/Local.ActiveProtocol ["LW2" | "LW3"]
Active Protocol
Example: (for a method)
> MAN●/SYS/MB/RS232/Local:factoryDefaults
< mm●/SYS/MB/RS232/Local:factoryDefaults [] Restore factory
default settings
8.3.5. Signature
For some command the response can contain multiple lines. Each line is terminated with a
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 is intended
waiting for 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 signature is a four digit long hexadecimal value that can be optionally placed before
every command. In that case, the response to that particular command will also be
preceded by the signature, and the corresponding lines will be between brackets.
Command format: XXXX#[command]
Legend: xxxx: 4-digit long hexadecimal value.
Page 84 / 122 Section 8. LW3 Programmers’ reference
Page 85
Response format:
{XXXX
[command lines]
}
Legend: xxxx: 4-digit long hexadecimal value.
Example:
> 1103#GET●/MEDIA/UART.*
< {1103
< pr●/MEDIA/UART.SublayerCount=1
< pr●/MEDIA/UART.PortCount=2
< pr●/MEDIA/UART.PortMap=P401;P401
< pr●/MEDIA/UART.PortStatus=0000;0000
< pr●/MEDIA/UART.ActiveSublayerMask=300;300
< pr●/MEDIA/UART.P1=Local
< pr●/MEDIA/UART.P2=Link
< }
Info: The lines of the signature are also Cr and Lf terminated.
HDMI-TPS-TX200 series
User’s Manual
8.3.6. Subscription
A user can subscribe to any node. Subscribe to a node means that the user will get a
notification if any of the properties of the node is changed. These notifications are
asynchronous messages - such as the ones described above - and hence they are useful
to keep the client application up-to-date, without receiving any unwanted information. When
the user does not want to be informed about the changes anymore, he can simply
unsubscribe from the node.
Info: The subscriptions are handled separately for connections and not to users. Hence, if the
connection is terminated all registered subscriptions are deleted. After closing a connection
the subscribe command has to be sent in order to get the notifications of the changes on
that connection.
Subscribe to a node
Command format: OPEN●[nodePath]
Response format: o-●[nodePath]
Example:
> OPEN●/MEDIA/VIDEO
< o-●/MEDIA/VIDEO
Subscribe to multiple nodes
In order to subscribe to multiple nodes, the asterisk wildchar can be used.
Command format: OPEN●[nodePath]/*
Response format: o-●[nodePath]/*
Example:
> OPEN●/MEDIA/VIDEO/*
< o-●/MEDIA/VIDEO/*
Get the active subscriptions
Issuing an ‘OPEN’ command without any parameters returns the active subscriptions
for the current connection.
Command format: OPEN
Response format: o-●[nodePath]
Section 8. LW3 Programmers’ reference Page 85 / 122
Page 86
CONNECTION
#1
> OPEN●/MEDIA/VIDEO/XP1
< o-●/MEDIA/VIDEO/XP1
> GET●/MEDIA/VIDEO/XP1.DestinationConnectionList
< pr●/MEDIA/VIDEO/XP1.DestinationConnectionList=P1:P7
CONNECTION
#2
> GET●/MEDIA/VIDEO/XP1.DestinationConnectionList
< pr●/MEDIA/VIDEO/XP1.DestinationConnectionList=P1:P7
> CALL●/MEDIA/VIDEO/XP1:switch(P4:P7)
< mO●/MEDIA/VIDEO/XP1:switch
CONNECTION
#1
< CHG●/MEDIA/VIDEO/XP1.DestinationConnectionList=P4:P7
Example:
> OPEN
< o-●/MEDIA/VIDEO
< o-●/EDID
< o-●/LOG
Unsubscribe from a node
Command format: CLOSE●[nodePath]
Response format: c-●[nodePath]
Example:
> CLOSE●/MEDIA/VIDEO
< c-●/MEDIA/VIDEO
Unsubscribe from multiple nodes
In order to unsubscribe to multiple nodes, the asterisk wildchar can be used.
Command format: CLOSE●[nodePath]/*
Response format: c-●[nodePath]/*
Example:
> CLOSE●/MEDIA/VIDEO/*
< c-●/MEDIA/VIDEO/*
8.3.7. Notifications about the changes of the properties
When the value of a property is changed and the user is subscribed to the node, which the
property belongs to, an asynchronous notification is generated. This is notification is called
as the ‘change message’. The format of such a message is very similar to the response for
the ‘GET’ command.
Format: CHG●[nodePath].[propertyName]=[newPropertyValue]
Example:
< CHG /EDID.EdidStatus=F48:E1;F49:E2;F48:E3;F48:E4;F48:E5
A short example of how to use the subscription
In the following, an example is presented, how the subscriptions are working and how to
use them. In the example 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.
Explanation: The first user (Connection #1) set a subscription to a node. Later the other
user (Connection #2) made a change, and thanks for the subscription, the first user got a
notification about the change.
Page 86 / 122 Section 8. LW3 Programmers’ reference
Page 87
8.4. Media layer properties
Value
1st character
2nd character
3rd character
0
-
reserved
No sublayer
1
The port belongs
to the video layer
The port is active on
sublayer #1
2
The port belongs
to the audio layer
The port is active on
sublayer #2
8.4.1. SublayerCount
The total number of sublayers on each layer. The layers can be divided to sublayers, which
have separate crosspoints. If an input port and an output port belong to different sublayers,
they are unable to be connected. For this product all the layers contain only one sublayer.
8.4.2. PortCount
The total number of input and output ports on the actual layer. E.g. SW4-TPS-TX240 video
layer contains 7 ports: DP input, 2xHDMI inputs, DVI-D input, Test pattern, HDMI local
output and TPS output.
8.4.3. PortMap
Each port is described by 4 characters in this property, these are separated by semicolons.
The first character is “I” or “O” depending on the direction of the port (input or output). The
other 3 character is a decimal number, which identifies the type of the connector displayed
in the Control Software (HDMI, DVI, DP, etc…).
Example: /MEDIA/VIDEO.PortMap=I002;I003;O901
HDMI-TPS-TX200 series
User’s Manual
8.4.4. ActiveSublayerMask
Each port is described by 3 characters in this property, these are separated by semicolons:
Example: /MEDIA/VIDEO.ActiveSublayerMask=101;101;101;101;101;101;101
8.4.5. P1-P7 – port numbers
Name of the ports belong to the layer. See more information in section 11.4 on page 118.
8.5. Video port and crosspoint settings
Info: Port numbers are device-dependent, see more details in section 11.4 on page 118.
8.5.1. Query the video crosspoint setting
Command format: GET●/MEDIA/VIDEO/XP1.DestinationConnectionList
Section 8. LW3 Programmers’ reference Page 87 / 122
Response format: pr●/MEDIA/VIDEO/XP1.DestinationConnectionList=<input>:<output>;
<input>:<output>
Legend: <input>: Video input port number
<output>: Video output port number
Example:
> GET●/MEDIA/VIDEO/XP1.DestinationConnectionList
< pr●/MEDIA/VIDEO/XP1.DestinationConnectionList=P2:P6;P2:P7
Explanation: P2 input port is connected to the output ports (local and TPS output).
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Page 88
T002F
HEX 0 0 2 F
BIN
00
00
00
00
00
10
11
11
00
reserved
unknown
unknown
unknown
unknown
01
reserved
10
emb. audio no
present
not HDCP-
encrypted
signal not
present
not
connected
11
embedded
audio present
HDCP-
encrypted
signal
present
connected
P1:T002F
Signal present / connection status
Embedded audio / HDCP status
Reserved
Reserved
Mute / lock state
Port number
8.5.2. Query the status of source ports
Command format: GET●/MEDIA/VIDEO/XP1.SourcePortStatus
Response format: pr●/MEDIA/VIDEO/XP1.SourcePortStatus=[<port#1>:<status>;
<port#2>:<status>;…;<port#n>:<status>]
Example:
> GET●/MEDIA/VIDEO/XP1.SourcePortStatus
< pr●/MEDIA/VIDEO/XP1.SourcePortStatus= P1:T002F;P2:T00FF;
P3:T002A;P4:T00AA;P5:T00AA
Legend:
Mute / lock state
T: unlocked, unmuted
L: locked, unmuted
M: unlocked, muted
U: locked, muted
Status bits
Explanation: (T002F) Video signal is connected to Port # 1, the signal is present and not
HDCP-encrypted. The port is unlocked, unmuted.
8.5.3. Switching video input
Command format: CALL●/MEDIA/VIDEO/XP1:switch(<input>:<output>;
<input>:<output>)
Response format: mO●/MEDIA/VIDEO/XP1:switch
Legend: <input>: Video input port number
<output>: Video output port number
Example:
Explanation: P1 input port has been switched to the output ports (Local HDMI and TPS).
Info: In this case the outputs are linked; the change will affect both local and TPS output port.
Page 88 / 122 Section 8. LW3 Programmers’ reference
> CALL●/MEDIA/VIDEO/XP1:switch(P1:P7)
< mO●/MEDIA/VIDEO/XP1:switch
Page 89
8.5.4. Query the video Autoselect settings
<set>
Explanation
1st letter
E: Autoselect is enabled
D: Autoselect is disabled
2nd letter
K: Keep the first active video input selected (First detect
mode)
P: Priority detect: always the highest priority active video
input will be selected as transmitted video input
L: Last detect: always the last attached input is switched to
the output automatically
3rd letter
M: The output will be disconnected (muted screen)
B: The crosspoint is not changed (blank screen)
Command format: GET●/MEDIA/VIDEO/XP1.DestinationPortAutoselect
Response format: pr●/MEDIA/VIDEO/XP1.DestinationPortAutoselect=<output>:<set>;
<output>:<set>
Legend: <output>: Video output port number
<set>: Autoselect setting, described by a three-letter-code:
HDMI-TPS-TX200 series
User’s Manual
Example:
> GET●/MEDIA/VIDEO/XP1.DestinationPortAutoselect
< pr●/MEDIA/VIDEO/XP1.DestinationPortAutoselect=P6:DPM;
P7:DPM
Explanation: The setting is “DPM” on the output video ports: Autoselect is currently
disabled (D); the mode is set to “priority detect” (P), and the port will be disconnected if
there is no signal on any of the checked ports (M). Since the outputs are linked, the change
will affect local and link out.
8.5.5. Change the Autoselect mode
Command format: CALL●/MEDIA/VIDEO/XP1.setDestinationPortAutoselect(
<output>:<set>)
Response format: mO●/MEDIA/VIDEO/XP1.setDestinationPortAutoselect
Legend: see 8.5.4 on page 89.
Example1:
> CALL●/MEDIA/VIDEO/XP1:setDestinationPortAutoselect(P7:EPM)
< mO●/MEDIA/VIDEO/XP1:setDestinationPortAutoselect
Explanation: The setting is changed to “EPM”: Autoselect is enabled (E); the mode is set
to “priority detect” (P), and the port will be disconnected if a higher priority port becomes
active (M).
Example2:
> CALL●/MEDIA/VIDEO/XP1:setDestinationPortAutoselect(P7:D)
< mO●/MEDIA/VIDEO/XP1.setDestinationPortAutoselect
Explanation: The setting is changed to “DPM”: Autoselect is disabled (D). The other
settings remain unchanged. Since the outputs are linked, the change will affect local and
link out.
Section 8. LW3 Programmers’ reference Page 89 / 122
Page 90
Priority
0 1 2 3 4
Video input port
P1
P2
P3
P4
P5
Priority
0 1 2 3 4
Video input port
P1
P2
P4
P3
P5
8.5.6. Query the input port priority
Command format: GET●/MEDIA/VIDEO/XP1.SourcePortPriority
Response format: pr●/MEDIA/VIDEO/XP1.SourcePortPrioirty=(<port1>:<prio>;
<port2>:<prio>;…;<portn>:<prio>)
Legend: <port>: Input port number (from 1 to n)
<prio>: Priority number (from 0 to 31).
Example:
> GET●/MEDIA/VIDEO/XP1.SourcePortPriority
< pr●/MEDIA/VIDEO/XP1.SourcePortPriority=P1:0;P2:1;P3:2;P4:3;
P5:4
Explanation: The current priority order of the video input ports is the following:
Highest priority is assigned to P1 port.
Info: The same priority number can be set to different input ports. In this case the input port with
the lowest port number will have the highest priority. E.g. setting the priority of P2 and P3
to “0”, P2 port will have higher priority since P2 is lower than P3.
Info: Setting priority to 31 means the given port will not be checked at automatic port selection.
8.5.7. Changing the input port priority
Command format: CALL●/MEDIA/VIDEO/XP1:setSourcePortPriority(<port1>:<prio>;
<port2>:<prio>;…;<portn>:<prio>)
Response format: mO●/MEDIA/VIDEO/XP1:setSourcePortPriority
Legend: <port>: Input port number
<prio>: Priority number from 0 to 31, equal numbers are allowed.
Example:
> CALL●/MEDIA/VIDEO/XP1:setSourcePortPriority(P1:0;P2:1;P4:2;
P3:3;P5:4)
< mO●/MEDIA/VIDEO/XP1:setSourcePortPriority
Explanation: The new priority order of the video input ports is the following:
Highest priority is set to P1 input video port.
Info: The order of the “<port>:<prio>” parameters does not matter.
Info: Setting priority to 31 means the given port will not be checked at automatic port selection.
Page 90 / 122 Section 8. LW3 Programmers’ reference
8.5.8. Mute an input port
Command format: CALL●/MEDIA/VIDEO/XP1:muteSource(<input>)
Response format: mO●/MEDIA/VIDEO/XP1:muteSource
Legend: <input>: Input port number
Example:
> CALL●/MEDIA/VIDEO/XP1:muteSource(P1)
< mO●/MEDIA/VIDEO/XP1:muteSource
Page 91
8.5.9. Unmute an input port
Command format: CALL●/MEDIA/VIDEO/XP1:unmuteSource(<input>)
Response format: mO●/MEDIA/VIDEO/XP1:unmuteSource
Legend: <input>: Input port number
Example:
> CALL●/MEDIA/VIDEO/XP1:unmuteSource(P1)
< mO●/MEDIA/VIDEO/XP1:unmuteSource
8.5.10. Lock an input port
Command format: CALL●/MEDIA/VIDEO/XP1:lockSource(<input>)
Response format: mO●/MEDIA/VIDEO/XP1:lockSource
Legend: <input>: Input port number
Example:
> CALL●/MEDIA/VIDEO/XP1:lockSource(P1)
< mO●/MEDIA/VIDEO/XP1:lockSource
HDMI-TPS-TX200 series
User’s Manual
8.5.11. Unlock an input port
Command format: CALL●/MEDIA/VIDEO/XP1:unlockSource(<input>)
Response format: mO●/MEDIA/VIDEO/XP1:unlockSource
Legend: <input>: Input port number
Example:
> CALL●/MEDIA/VIDEO/XP1:unlockSource(P1)
< mO●/MEDIA/VIDEO/XP1:unlockSource
8.5.12. Mute the output
Command format: CALL●/MEDIA/VIDEO/XP1:muteDestination(<output>)
Response format: mO●/MEDIA/VIDEO/XP1:muteDestination
Legend: <output>: Output port number
Example:
> CALL●/MEDIA/VIDEO/XP1:muteDestination(P7)
< mO●/MEDIA/VIDEO/XP1:muteDestination
8.5.13. Unmute the output
Command format: CALL●/MEDIA/VIDEO/XP1:unmuteDestination(<output>)
Response format: mO●/MEDIA/VIDEO/XP1:unmuteDestination
Legend: <output>: Output port number
Example:
> CALL●/MEDIA/VIDEO/XP1:unmuteDestination(P7)
< mO●/MEDIA/VIDEO/XP1:unmuteDestination
Section 8. LW3 Programmers’ reference Page 91 / 122
Page 92
8.5.14. Lock the output
Command format: CALL●/MEDIA/VIDEO/XP1:lockDestination(<output>)
Response format: mO●/MEDIA/VIDEO/XP1:lockDestination
Legend: <output>: Output port number
Example:
> CALL●/MEDIA/VIDEO/XP1:lockDestination(P7)
< mO●/MEDIA/VIDEO/XP1:lockDestination
Explanation: P7 port is locked.
8.5.15. Unlock the output
Command format: CALL●/MEDIA/VIDEO/XP1:unlockDestination(<output>)
Response format: mO●/MEDIA/VIDEO/XP1:unlockDestination
Legend: <output>: Output port number
Example:
> CALL●/MEDIA/VIDEO/XP1:unlockDestination(P7)
< mO●/MEDIA/VIDEO/XP1:unlockDestination
Explanation: P7 port is unlocked.
8.6. Audio port and crosspoint settings
Info: Port numbers are device-dependent, see more details in section 11.4 on page 118.
8.6.1. Query the audio crosspoint setting
Command format: GET●/MEDIA/AUDIO/XP1.DestinationConnectionList
Response format: pr●/MEDIA/AUDIO/XP1.DestinationConnectionList=<input>:<output>;
<input>:<output>
Legend: <input>: Audio input port number
<output>: Audio output port number
Example:
> GET●/MEDIA/AUDIO/XP1.DestinationConnectionList
< pr●/MEDIA/AUDIO/XP1.DestinationConnectionList=P5:P6;P5:P7
Explanation: P5 input is connected to P6 and P7 outputs.
8.6.2. Switching audio input
Command format: CALL●/MEDIA/AUDIO/XP1:switch(<input>:<output>)
Response format: mO●/MEDIA/AUDIO/XP1:switch
Legend: <input>: Audio input port number
<output>: Audio output port number
Example:
> CALL●/MEDIA/AUDIO/XP1:switch(P1:P6)
< mO●/MEDIA/AUDIO/XP1:switch
Explanation: P1 is switched to P6 and P7 output ports.
Page 92 / 122 Section 8. LW3 Programmers’ reference
Page 93
8.6.3. Query the audio Autoselect setting
<set>
Explanation
1st letter
E: Autoselect is enabled
D: Autoselect is disabled
2nd letter
K: Keep the first active video input selected (First detect
mode)
P: Priority detect: always the highest priority active video
input will be selected as transmitted video input
L: Last detect: always the last attached input is switched to
the output automatically
S: Static: audio and video input ports are assigned to each
other as a fixed setting (see section 5.1.5 on page 30).
3rd letter
M: The output will be disconnected (muted screen)
B: The crosspoint is not changed (blank screen)
Command format: GET●/MEDIA/AUDIO/XP1.DestinationPortAutoselect
Response format: pr●/MEDIA/AUDIO/XP1.DestinationPortAutoselect=<output>:<set>;
<output>:<set>
Legend: <output>: Audio output port number
HDMI-TPS-TX200 series
User’s Manual
Example:
> GET●/MEDIA/AUDIO/XP1.DestinationPortAutoselect
< pr●/MEDIA/AUDIO/XP1.DestinationPortAutoselect=P6:DPM;P7:DPM
Explanation: The setting is “DPM”: Autoselect is currently disabled (D); the mode is set to
“priority detect” (P), and the port will be disconnected if there is no signal on any of the
checked ports (M). Since the outputs are linked, the change will affect local and link out.
8.6.4. Change the audio Autoselect setting
Command format: CALL●/MEDIA/AUDIO/XP1:setDestinationPortAutoselect(
<output>:<set>)
Response format: mO●/MEDIA/AUDIO/XP1:setDestinationPortAutoselect
Legend: see 8.6.3 on page 93.
Example1:
> CALL●/MEDIA/AUDIO/XP1:setDestinationPortAutoselect(P7:EPM)
< mO●/MEDIA/AUDIO/XP1:setDestinationPortAutoselect
Explanation: The setting is changed to “EPM”: Autoselect is enabled (E); the mode is set
to “priority detect” (P), and the port will be disconnected if there is no signal on any of the
checked ports (M).
Example2:
> CALL●/MEDIA/AUDIO/XP1:setDestinationPortAutoselect(P7:D)
< mO●/MEDIA/AUDIO/XP1.setDestinationPortAutoselect
Explanation: The setting is changed to “DPM”: Autoselect is disabled (D). The other
settings remain unchanged. Since the outputs are linked, the change will affect local and
link out.
Section 8. LW3 Programmers’ reference Page 93 / 122
Page 94
8.7. RS-232 port configuration
.ControlProtocol
Protocol
0
LW2
1
LW3
.Baudrate
0 1 2 3 4 5 6 7 BAUD rate value
4800
7200
9600
14400
19200
38400
57600
115200
Info: There are two nodes under /SYS/RS232 node, ‘Link’ and ‘Local’. ‘Link’ is the serial line of
TPS output, ‘Local’ is the serial line of the Phoenix connector.
8.7.1. Protocol setting
Command format: SET●/SYS/MB/RS232/{Local|Link}.ControlProtocol={0|1}
Response format: pw●/SYS/MB/RS232/{Local|Link}.ControlProtocol={0|1}
Example:
> SET●/SYS/MB/RS232/Local.ControlProtocol=1
< pw●/SYS/MB/RS232/Local.ControlProtocol=1
Parameters:
Info: This read-only property shows the actual control protocol. For the local port it always follows
the ControlProtocol property, but it is not the same for the link RS-232 port. If the device is
connected to an MX-TPS-IB board, the ActiveProtocol is always LW2 on the link RS-232
port, LW3 is not supported through the link in this case. Besides the port settings (Baud
rate, databits, stop bits, parity) are ignored, since the followings pre-defined values are
valid: 115200, 8N1. The user can set the ControlProtocol to LW3, but this setting will take
effect only after connecting the transmitter to a TPS-RX-90/95 receiver.
8.7.2. BAUD rate setting
Command format: SET●/SYS/MB/RS232/{Local|Link}.Baudrate={0|1|2|3|4|5|6|7}
Response format: pw●/SYS/MB/RS232/{Local|Link}.Baudrate={0|1|2|3|4|5|6|7}
Example:
> SET●/SYS/MB/RS232/Local.Baudrate=2
< pw●/SYS/MB/RS232/Local.Baudrate=2
Parameters:
Explanation: The BAUD rate in the node ‘Local’ is set to 9600.
Info: The same BAUD rate is recommended to set on both sides. Please consider the possible
overflow when the difference is too big between the set BAUD rates.
Info: If the device is connected to an MX-TPS-IB, the port settings (Baud rate, databits, stop bits,
parity) are ignored, since the followings pre-defined values are valid: 115200, 8N1.
Page 94 / 122 Section 8. LW3 Programmers’ reference
Page 95
8.7.3. Databit setting
.DataBits
Data bits value
8
8
9
9
.StopBits
Stopbit value
0
1
1
1,5 2 2
.Parity
Parity setting
0
no parity
1
odd
2
even
Command format: SET●/SYS/MB/RS232/{Local|Link}.DataBits={8|9}
Response format: pw●/SYS/MB/RS232/{Local|Link}.DataBits={8|9}
Example:
> SET●/SYS/MB/RS232/Local.DataBits=8
< pw●/SYS/MB/RS232/Local.DataBits=8
Parameters:
8.7.4. Stopbits setting
Command format: SET●/SYS/MB/RS232/{Local|Link}.StopBits={0|1|2}
Response format: pw●/SYS/MB/RS232/{Local|Link}.StopBits={0|1|2}
Example:
HDMI-TPS-TX200 series
User’s Manual
> SET●/SYS/MB/RS232/Local.StopBits=0
< pw●/SYS/MB/RS232/Local.StopBits=0
Parameters:
8.7.5. Parity setting
Command format: SET●/SYS/MB/RS232/{Local|Link}.Parity={0|1|2}
Response format: pw●/SYS/MB/RS232/{Local|Link}.Parity={0|1|2}
Example:
> SET●/SYS/MB/RS232/Local.Parity=0
< pw●/SYS/MB/RS232/Local.Parity=0
Parameters:
Section 8. LW3 Programmers’ reference Page 95 / 122
8.7.6. RS-232 operation mode
Command format: SET●/SYS/MB/RS232.Rs232Mode={0|1|2}
Response format: pw●/SYS/MB/RS232.Rs232Mode={0|1|2}
Example:
> SET●/SYS/MB/RS232.Rs232Mode=1
< pw●/SYS/MB/RS232.Rs232Mode=1
Page 96
Parameters:
.Rs232Mode
RS-232
operation mode
0
Pass-through
1
Control
2
Command injection
8.8. Network configuration
Info: The transmitter needs to be restarted to apply changes after modification.
8.8.1. Query the DHCP state
Command format: GET●/MANAGEMENT/NETWORK.DhcpEnabled
Response format: pw●/MANAGEMENT/NETWORK.DhcpEnabled={true|false}
Example:
> GET●/MANAGEMENT/NETWORK.DhcpEnabled
< pw●/MANAGEMENT/NETWORK.DhcpEnabled=true
8.8.2. Change the DHCP state
Command format: SET●/MANAGEMENT/NETWORK.DhcpEnabled={true|false}
Response format: pw●/MANAGEMENT/NETWORK.DhcpEnabled={true|false}
Example:
> SET●/MANAGEMENT/NETWORK.DhcpEnabled=false
< pw●/MANAGEMENT/NETWORK.DhcpEnabled=false
8.8.3. Query the IP address
Command format: GET●/MANAGEMENT/NETWORK.IpAddress
Response format: pr●/MANAGEMENT/NETWORK.IpAddress=<IP_address>
Example:
> GET●/MANAGEMENT/NETWORK.IpAddress
< pr●/MANAGEMENT/NETWORK.IpAddress=192.168.0.102
8.8.4. Change the IP address (static)
Command format: SET●/MANAGEMENT/NETWORK.StaticIpAddress=<IP_address>
Response format: pw●/MANAGEMENT/NETWORK.StaticIpAddress=<IP_address>
Example:
> SET●/MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.105
< pw●/MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.105
Page 96 / 122 Section 8. LW3 Programmers’ reference
8.8.5. Query the subnet mask
Command format: GET●/MANAGEMENT/NETWORK.NetworkMask
Response format: pr●/MANAGEMENT/NETWORK.NetworkMask=<netmask>
Example:
> GET●/MANAGEMENT/NETWORK.NetworkMask
< pr●/MANAGEMENT/NETWORK.NetworkMask=255.255.255.0
Page 97
8.8.6. Change the subnet mask (static)
Command format: SET●/MANAGEMENT/NETWORK.StaticNetworkMask=<netmask>
Response format: pw●/MANAGEMENT/NETWORK.StaticNetworkMask=<netmask>
Example:
> SET●/MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0
< pw●/MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0
Info: Device needs to be restarted to apply changes.
8.8.7. Query the gateway address
Command format: GET●/MANAGEMENT/NETWORK.GatewayAddress
Response format: pr●/MANAGEMENT/NETWORK.GatewayAddress=<gw_address>
Example:
> GET●/MANAGEMENT/NETWORK.GatewayAddress
< pr●/MANAGEMENT/NETWORK.GatewayAddress=192.168.0.1
8.8.8. Change the gateway address (static)
HDMI-TPS-TX200 series
User’s Manual
Command format: SET●/MANAGEMENT/NETWORK.StaticGatewayAddress=
<gw_address>
Response format: pr●/MANAGEMENT/NETWORK.StaticGatewayAddress=
<gw_address>
Example:
> SET●/MANAGEMENT/NETWORK.StaticGatewayAddress=192.168.0.5
< pw●/MANAGEMENT/NETWORK.StaticGatewayAddress=192.168.0.5
8.9. GPIO settings
Info: Use the GET command to query a parameter.
8.9.1. Set the direction of a GPIO pin
Command format: SET●/MEDIA/GPIO/P<pin_#>.Direction=<dir>
Response format: pw●/MEDIA/GPIO/ P<pin_#>.Direction=<dir>
Legend: <pin#>: number of the GPIO pin
<dir>: direction of the GPIO pin: I=input; O=output
Example:
> SET●/MEDIA/GPIO/P1.Direction=I
< pw●/MEDIA/GPIO/P1.Direction=I
8.9.2. Set the output value of a GPIO pin
Command format: SET●/MEDIA/GPIO/P<pin_#>.Output=<value>
Response format: pw●/MEDIA/GPIO/ P<pin_#>.Output=<value>
Legend: <pin#>: number of the GPIO pin
<value>: value of the GPIO pin: H=high level; O=low level
Example:
> GET●/MEDIA/GPIO/P1.Output
< pw●/MEDIA/GPIO/P1.Output=H
Explanation: Output level of GPIO pin1 is high.
Section 8. LW3 Programmers’ reference Page 97 / 122
Page 98
8.9.3. Toggle the value of a GPIO pin
Command format: CALL●/MEDIA/GPIO/P<pin_#>:toggle(1)
Response format: mO●/MEDIA/GPIO/ P<pin_#>:toggle
Legend: <pin#>: number of the GPIO pin
Example:
> CALL●/MEDIA/GPIO/P1:toggle(1)
< mO●/MEDIA/GPIO/P1:toggle
Explanation: If the direction of the pin is input: the output value is toggled.
If the direction of the pin is output: the output value and the input value
are toggled.
8.10. Event settings (conditions and actions)
20 events can be configured in the transmitter, these nodes are located under /EVENTS.
More details can be found in section 6.9 on page 51.
A simple example is presented hereby to demonstrate the process of setting an event by
protocol commands. The event will be set under the /EVENTS/E1 node and will contain the
following setting:
If signal is present on input port P1, the value of GPIO pin1 will be set to High.
The setting is stored in 6 different properties which are described in the followings.
8.10.1. Set the source node (condition)
Command format: SET●/EVENTS/E<event_nr>.SourceNode=
<node_path>”/”<node_name>
Response format: pw●/EVENTS/E<event_nr>.SourceNode=
<node_path>”/”<node_name>
Example:
> SET●/EVENTS/E1.SourceNode=/MEDIA/VIDEO/P1
< pw●/EVENTS/E1.SourceNode=/MEDIA/VIDEO/P1
Explanation: This node contains the path of the property that will fire the E1 event (the
path of the P1 video input port).
Info: Node path must be started with “/”.
8.10.2. Set the source property (condition)
Command format: SET●/EVENTS/E<event_nr>.SourceProperty=<property>
Response format: pw●/EVENTS/E<event_nr>.SourceProperty=<property>
Example:
> SET●/EVENTS/E1.SourceProperty=SignalPresent
< pw●/EVENTS/E1.SourceProperty=SignalPresent
Explanation: This node contains the property (SignalPresent) that will fire the E1 event
(signal present state of P1 port).
Page 98 / 122 Section 8. LW3 Programmers’ reference
Page 99
8.10.3. Set the value of the source property (condition)
Command format: SET●/EVENTS/E<event_nr>.SourcePropertyValue=<value>
Response format: pw●/EVENTS/E<event_nr>.SourcePropertyValue=<value>
Example:
> SET●/EVENTS/E1.SourcePropertyValue=1
< pw●/EVENTS/E1.SourcePropertyValue=1
Explanation: The E1 event will be fired, if this property is changed to the set value (signal
is present on input port P1).
8.10.4. Set the target node (action)
Command format: SET●/EVENTS/E<event_nr>.TargetNode=
<node_path>”/”<node_name>
Response format: pw●/EVENTS/E<event_nr>.TargetNode=
<node_path>”/”<node_name>
Example:
> SET●/EVENTS/E1.TargetNode=/MEDIA/GPIO/P1
< pw●/EVENTS/E1.TargetNode=/MEDIA/GPIO/P1
HDMI-TPS-TX200 series
User’s Manual
Explanation: This node contains the path of the property that will be changed after the E1
event is fired.
Info: Node path must be started with “/”.
8.10.5. Set the target property (action)
Command format: SET●/EVENTS/E<event_nr>.TargetProperty=<property>
Response format: pw●/EVENTS/E<event_nr>.TargetProperty=<property>
Example:
> SET●/EVENTS/E1.TargetProperty=Output
< pw●/EVENTS/E1.TargetProperty=Output
Explanation: The node contains the property that will be changed after E1 event is fired.
8.10.6. Set the value of the target property (action)
Command format: SET●/EVENTS/E<event_nr>.TargetPropertyValue=<value>
Response format: pw●/EVENTS/E<event_nr>.TargetPropertyValue=<value>
Example:
> SET●/EVENTS/E1.TargetPropertyValue=H
< pw●/EVENTS/E1.TargetPropertyValue=H
Explanation: If the E1 event is fired, this value will be stored in the set target property.
Section 8. LW3 Programmers’ reference Page 99 / 122
Page 100
8.11. EDID management
8.11.1. Query the emulated EDIDs
Command format: GET●/EDID.EdidStatus
Response format: pr●/EDID.EdidStatus([*\{<edid_id>":"<emulated_edid_id>";"\}])
Example:
> GET●/EDID.EdidStatus
< pr●/EDID.EdidStatus=F48:E1;F48:E2;F48:E3;F48:E4
Explanation: The available video input ports are listed from E1 to E4 and the emulated
EDID’s number is displayed. E.g. F48 (48
input port.
8.11.2. Query the validity of a dynamic EDID
Command format: GET●/EDID/D/D1.Validity
Response format: pr●/EDID/D/D1.Validity={true|false}
Example:
> GET●/EDID/D/D1.Validity
< pr●/EDID/D/D1.Validity=true
Explanation: The ‘Validity’ property is true, valid EDID is stored in D1 memory place.
8.11.3. Query a user EDID header
Command format: GET●/EDID/U/U1.Header
Response format: pr●/EDID/U/U1.Header={“Invalid”|<edid_header>}
Legend: <edid_header>: ID of manufacturer; preferred timing; monitor name
Example1:
> GET●/EDID/U/U1.Header
< pr●/EDID/U/U1.Header=Invalid
th
Factory) EDID is emulated on E1
Explanation1: The memory place U1 does not contain valid EDID.
Example2:
> GET●/EDID/U/U2.Header
< pr●/EDID/U/U2.Header=LWR;[email protected];D640x480p60
Explanation2: The memory place U2 contains valid EDID.
8.11.4. Emulating an EDID to an input port
Command format: CALL●/EDID:switch(<source>:<destination>)
Response format: mO●/EDID:switch
Example:
> CALL●/EDID:switch(F49:E2)
< mO●/EDID:switch
Legend: <source>: Source EDID memory places that can be Factory, User or
<destination>: The emulated EDID memory of the desired input port.
Dynamic EDID memory.
Page 100 / 122 Section 8. LW3 Programmers’ reference
Loading...