User’s Manual

UMX-TPS-TX120, -TX130, -TX140, -TX140K, -TX140-Plus FP-UMX-TPS-TX120, -TX130 WP-UMX-TPS-TX120-US Black, White WP-UMX-TPS-TX130-US Black, White WP-UMX-TPS-TX130-Plus-US Black, White

HDBaseTTM Multimedia Extender

 v3.1  15-07-2021

2 UMX-TPS-TX100 series – User's Manual 

Important Safety Instructions Waste Electrical & Electronic Equipment Common Safety Symbols WEEE Class II apparatus construction. The equipment should be operated only from the power source This marking shown on the product or its literature, Symbol Description indicated on the product. indicates that it should not be disposed with other household wastes at the end of its working life. To To disconnect the equipment safely from power, remove the power prevent possible harm to the environment or human Direct current cord from the rear of the equipment, or from the power source. The health from uncontrolled waste disposal, please MAINS plug is used as the disconnect device, the disconnect device separate this from other types of wastes and recycle it shall remain readily operable. Alternating current responsibly to promote the sustainable reuse of material There are no user-serviceable parts inside of the unit. Removal of the resources. Household users should contact either the cover will expose dangerous voltages. To avoid personal injury, do not retailer where they purchased this product, or their local government Double insulation remove the cover. Do not operate the unit without the cover installed. office, for details of where and how they can take this item for environmentally safe recycling. Business users should contact their The appliance must be safely connected to multimedia systems. supplier and check the terms and conditions of the purchase contract. Follow instructions described in this manual.  Caution, possibility of eletric shock This product should not be mixed with other commercial wastes for Ventilation disposal. Caution For the correct ventilation and to avoid overheating ensure enough 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. 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.



3 UMX-TPS-TX100 series – User's Manual 

Symbol Legend Document Information About Printing

The following symbols and markings are used in the document: This User’s Manual applies to the following versions of the mentioned Lightware Visual Engineering supports green technologies and software, firmware, and hardware: eco-friend mentality. Thus, this document is made for digital usage WARNING! Safety-related information which is highly primarily. If you need to print out few pages for any reason, follow the recommended to read and keep in every case! Item Version recommended printing settings: Lightware Device Controller (LDC) software 2.5.10b1 ▪ Page size: A4 ATTENTION! Useful information to perform a successful procedure; Lightware Device Updater V2 (LDU2) software 2.9.0b9 ▪ Output size: Fit to page or Match page size it is recommended to read. UMX-TPS-TX120, -TX130, -TX140, ▪ Orientation: Landscape 1.5.0b4 UMX-TPS-TX140K, TX140-Plus Firmware TIPS AND TRICKS: Thanks to the size of the original page, a border WP-UMX-TPS-TX120-US, -TX130-US, DIFFERENCE: Feature or function that is available with a specific package around the content (gray on the second picture below) makes WP-UMX-TPS-TX130-Plus-US; 1.5.0b6 firmware/hardware version or product variant. possible to organize the pages better. After punching the printed FP-UMX-TPS-TX120, -TX130 pages, they can be placed easily into a ring folder. UMX-TPS-TX120, -TX130, -TX140, 2.0 INFO: A notice which may contain additional information. Procedure UMX-TPS-TX140K, TX140-Plus can be successful without reading it. 1 2 3 Hardware WP-UMX-TPS-TX120-US, -TX130-US, 1.2 WP-UMX-TPS-TX130-Plus-US DEFINITION: The short description of a feature or a function. FP-UMX-TPS-TX120, -TX130 1.2

Document revision: v3.1 TIPS AND TRICKS: Ideas which you may have not known yet but can be useful. Release date: 15-07-2021 Editor: Laszlo Zsedenyi Hashtag (#) Keywords in the Document

Navigation Buttons This user's manual contains keywords with hashtag (#) to help you to find the relevant information as quick as possible. Go back to the previous page. If you clicked on a link previously,  you can go back to the source page by the button. The format of the keywords is the following:  Navigate to the Table of Contents. # The usage of the keywords: use the Search function (Ctrl+F / Cmd+F)  Step back one page. of your PDF reader application, type the # (hashtag) character and the wished keyword.  Step forward to the next page. The #new special keyword indicates a new feature/function that has just appeared in the latest firmware or software version. Example #dhcp This keyword is placed at the DHCP setting command in the LW3 Programmer's reference section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4 UMX-TPS-TX100 series – User's Manual 

Table of Contents

1. INTRODUCTION...... 8 3.4.6. DVI-I Connector...... 33 4.14. USB Interface (KVM Function)...... 48 1.1. Description...... 9 3.4.7. Analog Stereo Audio (Jack)...... 34 4.15. Consumer Electronics Control (CEC) Feature...... 49 1.2. Box Contents and Optional Accessories...... 10 3.4.8. Analog Stereo Audio (Phoenix)...... 34 4.16. Further Built-in Features...... 49 1.3. Features...... 11 3.4.9. Ethernet Connector (TPS and LAN Ports)...... 34 4.16.1. Transmitter Cloning – Configuration Backup and Restore...... 49 1.3.1. List of Features (in alphabetical order)...... 11 3.4.10. RS-232 Connector...... 35 4.17. Software Control Modes...... 49 3.4.11. IR Connector...... 35 1.3.2. Feature Availability...... 12 5. SOFTWARE CONTROL - LIGHTWARE DEVICE CONTROLLER...... 50 1.4. Model Comparison...... 13 3.4.12. IR Detector...... 35 5.1. Install and Update...... 51 1.5. Typical Application...... 14 3.4.13. GPIO - General Purpose Input/Output Ports...... 35 3.4.14. USB Port ...... 35 5.2. Running the LDC...... 51 2. PRODUCT OVERVIEW...... 15 3.5. Connecting Steps...... 36 5.3. Connecting to a Device (Device Discovery Window)...... 52 2.1. Front View - UMX-TPS-TX100 series...... 16 3.5.1. FP/WP-UMX-TPS-TX100 series...... 36 5.3.1. Ethernet Tab...... 52 2.2. Rear View - UMX-TPS-TX100 series...... 17 3.5.2. UMX-TPS-TX100 series...... 36 5.3.2. Serial Tab...... 53 2.3. Front View - WP-UMX-TPS-TX100 series...... 18 3.6. Powering Options...... 37 5.3.3. USB Tab...... 53 2.4. Rear View - WP-UMX-TPS-TX100 series...... 18 5.3.4. Further Tools...... 53 4. DEVICE CONCEPT...... 38 2.5. Front View - FP-UMX-TPS-TX100 series...... 19 5.4. Crosspoint Menu...... 54 2.5.1. Rear View - FP-UMX-TPS-TX100 series...... 20 4.1. TPS Extender Concept...... 39 5.5. Port Properties Windows...... 55 2.6. Front Panel LEDs...... 20 4.2. TPS Interface...... 39 5.5.1. Analog Video Inputs...... 55 2.7. Rear Panel LEDs...... 21 4.3. Port Diagrams...... 40 5.5.2. Digital Video Inputs...... 56 2.8. Front Panel Buttons...... 22 4.3.1. Standalone Extenders...... 40 5.5.3. TPS Video Output...... 56 2.8.1. Video Select Button...... 22 4.3.2. Wall Plate / Floor Plate Extenders...... 40 5.5.4. Analog Audio Inputs...... 57 2.8.2. Audio Select Button...... 22 4.4. Video Interface...... 41 5.5.5. Digital Audio Inputs...... 58 2.9. Special Functions...... 23 4.4.1. Video Input Modes...... 41 5.5.6. TPS Audio Output...... 58 2.9.1. Programmable Show Me Button...... 23 4.4.2. Input Source Selection Modes...... 41 5.6. The CEC Tool...... 59 2.9.2. Enable DHCP (Dynamic) IP Address...... 23 4.5. The Autoselect Feature...... 41 5.7. Diagnostic Tools...... 60 2.9.3. Reset to Factory Default Settings...... 23 4.6. Audio Interface...... 42 5.7.1. Cable Diagnostics...... 60 2.9.4. Reseting the Device...... 23 4.6.1. Audio Input Modes...... 42 5.7.2. Test Pattern...... 61 2.9.5. Control Lock...... 23 4.6.2. Audio Options - Example...... 42 5.7.3. Frame Detector...... 62 2.9.6. Entering Firmware Update Mode...... 23 4.7. Serial Interface...... 43 5.8. EDID Menu...... 62 4.7.1. Technical Background...... 43 5.8.1. EDID Operations...... 63 3. INSTALLATION...... 24 4.7.2. RS-232 Signal Transmission – Example...... 43 5.8.2. EDID Summary Window...... 63 3.1. Mounting Options - Standalone Transmitters...... 25 4.7.3. RS-232 Recognizer...... 44 5.8.3. Editing an EDID...... 64 3.1.1. 1U High Rack Shelf...... 25 4.8. Ethernet Interface...... 44 5.8.4. Creating an EDID - Easy EDID Creator...... 64 3.1.2. Under-desk Double Mounting Kit...... 25 4.8.1. Device Control over Ethernet...... 44 5.9. Control Menu...... 65 3.2. Mounting Options - Floor Plates...... 26 4.8.2. Wake-on-Lan...... 44 5.9.1. RS-232 Tab...... 65 3.2.1. MKM Mounting Option...... 26 4.8.3. TCP Recognizer...... 45 5.9.2. Message Recognizer...... 65 3.2.2. MKS Mounting Option...... 28 4.9. Basic IT Security...... 45 5.9.3. GPIO Tab...... 66 3.2.3. GES Mounting Option...... 29 4.10. Batch Commands...... 45 5.9.4. Ethernet...... 67 3.3. Mounting Options - Wall Plates...... 32 4.11. IR Interface...... 46 5.9.5. Infra Tab...... 69 3.4. Electrical Connections...... 33 4.11.1. Technical Background...... 46 5.9.6. Macros...... 71 3.4.1. Locking 12V DC Connection...... 33 4.11.2. Advanced IR functionality...... 47 5.9.7. Variables...... 72 3.4.2. 48V DC Connection...... 33 4.12. GPIO Interface...... 47 5.10. Event Manager...... 74 3.4.3. VGA Connector...... 33 4.12.1. Description...... 47 5.10.1. The Event Editor...... 74 3.4.4. HDMI Connector...... 33 4.12.2. GPIO Options - Example...... 47 5.10.2. Create or Modify an Event...... 75 3.4.5. DisplayPort Connector...... 33 4.13. The Event Manager Feature...... 47 5.10.3. Special Tools and Accessories...... 76

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5 UMX-TPS-TX100 series – User's Manual 

Table of Contents

5.10.4. Clear One or More Event(s)...... 77 6.4.7. View Crosspoint Size...... 91 7.4.7. Lock the Front Panel Buttons...... 103 5.10.5. Export and Import Events...... 77 6.4.8. Change the Video Autoselect Mode...... 91 7.4.8. Disable the Default Function of the Front Panel Buttons...... 103 5.10.6. Event Creating - Example...... 77 6.4.9. Change the Audio Autoselect Mode...... 92 7.4.9. Dark Mode...... 103 5.11. Settings Menu...... 78 6.4.10. Change the Video Input Priorities...... 92 7.4.10. Dark Mode Delay...... 103 5.11.1. Status...... 78 6.4.11. Change the Audio Input Priorities...... 92 7.4.11. Running a Macro...... 104 5.11.2. Network...... 79 6.5. Network Configuration...... 93 7.5. Cleartext Login Protection...... 104 5.11.3. Front Panel...... 79 6.5.1. Query the Current IP Status...... 93 7.5.1. Setting the Login Password...... 104 5.11.4. Backup...... 80 6.5.2. Set the IP Address...... 93 7.5.2. Login the Device...... 104 5.11.5. System...... 80 6.5.3. Set the Subnet Mask...... 93 7.5.3. Logout from the Device...... 104 5.12. Configuration Cloning (Backup Tab)...... 81 6.5.4. Set the Gateway Address...... 93 7.5.4. Enable the Cleartext Login Function...... 104 5.12.1. Steps in a Nutshell...... 81 6.5.5. Apply Network Settings...... 93 7.6. Video Port Settings...... 105 5.12.2. Save the Settings of a Device (Backup)...... 81 6.5.6. Enable/disable the Ethernet Port...... 94 7.6.1. Query the Status of Source Ports...... 105 5.12.3. Upload the Settings to a Device (Restore)...... 82 6.6. RS-232 Settings...... 94 7.6.2. Query the Status of Destination Port...... 106 5.12.4. Create and Restore Backups from the Device Memory...... 82 6.6.1. RS-232 Mode Setting...... 94 7.6.3. Query the Video Crosspoint Setting...... 106 5.13. The Built-In Miniweb...... 83 6.6.2. RS-232 Parameters Settings...... 94 7.6.4. Disconnect Video Input...... 106 5.13.1. Opening the Miniweb...... 83 6.6.3. RS-232 Control Protocol Port Setting...... 95 7.6.5. Switching Video Input...... 106 5.13.2. Miniweb Customization...... 84 6.6.4. Serial Port Format Setting (Link port)...... 95 7.6.6. Querying the Connected Input Port Number...... 106 5.14. Advanced View Window...... 85 6.6.5. Serial Port Protocol Setting (Link port)...... 95 7.6.7. Query the Video Autoselect Settings...... 107 6.7. GPIO Port Configuration...... 95 7.6.8. Change the Autoselect Mode...... 107 6. LW2 PROGRAMMER'S REFERENCE...... 86 6.7.1. Setting the Level and Direction for Each Pins...... 95 7.6.9. Query the Input Port Priority...... 107 6.1. LW2 Protocol Description...... 87 6.8. LW2 Commands – Quick Summary...... 96 7.6.10. Change the Input Port Priority...... 107 6.2. Instructions for the Terminal Application Usage...... 87 7.6.11. Mute an Input Port...... 108 7. LW3 PROGRAMMERS’ REFERENCE...... 98 6.3. General LW2 Commands...... 88 7.6.12. Unmute an Input Port...... 108 6.3.1. List of All Available LW2 Commands...... 88 7.1. Overview...... 99 7.6.13. Lock an Input Port...... 108 6.3.2. View Product Type...... 88 7.2. Instructions for the Terminal Application Usage...... 99 7.6.14. Unlock an Input Port...... 108 6.3.3. Device Label Query...... 88 7.3. Protocol Rules...... 99 7.6.15. Mute Output...... 108 6.3.4. Query Control Protocol...... 88 7.3.1. LW3 Tree Structure and Command Structure (examples)...... 99 7.6.16. Unmute Output...... 108 6.3.5. View Firmware Version of the CPU...... 88 7.3.2. General Rules...... 99 7.6.17. Lock Output...... 108 6.3.6. Connection Test...... 88 7.3.3. Legend for the Control Commands...... 100 7.6.18. Unlock Output...... 108 6.3.7. Compile Time...... 88 7.3.4. Command Types...... 100 7.6.19. HDCP Setting (Input Port)...... 109 6.3.8. View Serial Number...... 89 7.3.5. Prefix Summary...... 100 7.6.20. Test Pattern Generator Mode...... 109 6.3.9. View Installed Board...... 89 7.3.6. Error Messages...... 100 7.6.21. Test Pattern Color...... 109 6.3.10. View Firmware for All Controllers...... 89 7.3.7. Escaping...... 101 7.6.22. Test Pattern Resolution...... 109 6.3.11. Query Health Status...... 89 7.3.8. Signature...... 101 7.6.23. HDCP Setting (Output Port)...... 110 6.3.12. Restart the Device...... 89 7.3.9. Subscription...... 101 7.6.24. HDMI Mode Settings (Output Port)...... 110 6.3.13. Restore Factory Default Settings...... 89 7.3.10. Notifications about the Changes of the Properties...... 101 7.6.25. Color Space Setting (Output Port)...... 110 6.4. AV Port Settings...... 90 7.4. System Commands...... 102 7.6.26. TPS Mode Settings...... 110 6.4.1. Switch an Input to the Outputs...... 90 7.4.1. Query the Product Name...... 102 7.7. Audio Port Settings...... 111 6.4.2. Mute Output...... 90 7.4.2. Set the Device Label...... 102 7.7.1. Query the Status of Source Ports...... 111 6.4.3. Unmute Output...... 90 7.4.3. Query the Serial Number...... 102 7.7.2. Query the Status of Destination Port...... 112 6.4.4. Lock Output...... 90 7.4.4. Query the Firmware Version...... 102 7.7.3. Query the Audio Crosspoint Setting...... 112 6.4.5. Unlock Output...... 91 7.4.5. Resetting the Device...... 102 7.7.4. Switching Audio Input...... 112 6.4.6. View Connection State on the Output...... 91 7.4.6. Restore the Factory Default Settings...... 102

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6 UMX-TPS-TX100 series – User's Manual 

Table of Contents

7.7.5. Query the Audio Autoselect Settings...... 112 7.13. Ethernet Tool Kit...... 123 7.18. RS-232 Message Sending...... 132 7.7.6. Change the Autoselect Mode...... 113 7.13.1. Device Filter Based on MAC Address...... 123 7.18.1. Sending a Message (ASCII-format) via RS-232...... 132 7.7.7. Query the Input Port Priority...... 113 7.13.2. LW2 Control Port Blocking...... 124 7.18.2. Sending a Text (ASCII-format) via RS-232...... 132 7.7.8. Change the Input Port Priority...... 113 7.13.3. HTTP Port Blocking...... 124 7.18.3. Sending a Binary Message (HEX-format) via RS-232...... 132 7.7.9. Mute an Audio Input...... 114 7.13.4. HTTP Post Receiving Blocking...... 124 7.18.4. Using Hexadecimal Codes...... 132 7.7.10. Unmute an Audio Input...... 114 7.13.5. Powering on a Computer over Ethernet (Wake-on-LAN)...... 124 7.19. RS-232 Message Recognizer...... 133 7.7.11. Lock an Input Port...... 114 7.13.6. Setting the Host Name...... 124 7.19.1. Enable the Recognizer...... 133 7.7.12. Unlock an Input Port...... 114 7.14. Ethernet Message Sending...... 125 7.19.2. Set the Delimiter Hex...... 133 7.7.13. Mute Audio Output...... 114 7.14.1. Sending a TCP Message (ASCII-format)...... 125 7.19.3. Set the Timeout...... 133 7.7.14. Unmute Audio Output...... 114 7.14.2. Sending a TCP Text (ASCII-format)...... 125 7.19.4. Querying the Last Recognized Message (String)...... 134 7.7.15. Lock Output...... 114 7.14.3. Sending a TCP Binary Message (HEX-format)...... 125 7.19.5. Querying the Last Recognized Message(Hex)...... 134 7.7.16. Unlock Output...... 114 7.14.4. Sending a UDP Message (ASCII-format)...... 125 7.19.6. Clearing the Last Recognized Stored Message...... 134 7.8. Analog Audio Input Level Settings...... 115 7.14.5. Sending a UDP Text (ASCII-format)...... 126 7.19.7. Querying the Last Recognized Active Message (String)...... 134 7.8.1. Volume ...... 115 7.14.6. Sending a UDP Binary Message (HEX-format)...... 126 7.19.8. Querying the Last Recognized Active Message (Hex)...... 134 7.8.2. Balance...... 115 7.15. HTTP Messaging...... 126 7.19.9. Set the Active Timeout...... 135 7.9. Event Manager Basics...... 116 7.15.1. Setting the Target IP Address...... 126 7.19.10. Running an Immediate Event Action...... 135 7.9.1. How to arrange an Event?...... 116 7.15.2. Setting the TCP Port...... 126 7.20. Sending CEC Commands...... 136 7.9.2. Setting a Condition by Linking Another Condition...... 116 7.15.3. Setting the Target Path...... 126 7.20.1. Press&Release Commands...... 136 7.9.3. Setting a Condition by Linking More Conditions...... 116 7.15.4. Setting the Message Header...... 127 7.20.2. Further Commands...... 136 7.9.4. Setting an Action by Specifying a Direct Path...... 117 7.15.5. Sending a Post Message...... 127 7.20.3. Sending an OSD String...... 136 7.9.5. Setting an Action by Linking Another Action...... 117 7.15.6. Sending a Put Message...... 127 7.20.4. Sending CEC Commands in Hex Format...... 137 7.9.6. Setting an Action by Linking a Macro...... 117 7.16. TCP Message Recognizer...... 127 7.20.5. Querying the Last Received CEC Message...... 137 7.10. Event Manager Tool Kit...... 117 7.16.1. Setting the IP Address of the TCP Server...... 127 7.21. Infrared Port Configuration...... 137 7.10.1. Setting the Delay...... 117 7.16.2. Setting the TCP/IP Port Number of the TCP Server...... 128 7.21.1. Enable Command Injection Mode...... 137 7.10.2. Setting the Name of the Event...... 118 7.16.3. Connecting to a TCP Server...... 128 7.21.2. Enable/Disable Output Signal Modulation...... 137 7.10.3. Enable the Event...... 118 7.16.4. Disconnecting from a TCP Server...... 128 7.22. Infrared Message Sending...... 138 7.10.4. Triggering a Condition...... 118 7.16.5. Setting the Delimiter Hex...... 128 7.22.1. Sending Pronto Hex Codes in Little-endian Format via IR Port.138 7.10.5. Querying the Condition Counter...... 118 7.16.6. Setting the Timeout...... 128 7.22.2. Sending Pronto Hex Codes in Big-endian Format via IR Port....138 7.10.6. Querying the Condition Trigger Counter...... 119 7.16.7. Querying the Last Recognized Message (String)...... 128 7.23. GPIO Port Configuration...... 139 7.10.7. Testing an Action...... 119 7.16.8. Querying the Last Recognized Message (Hex)...... 129 7.23.1. Set the Direction of a GPIO Pin...... 139 7.11. Variable-Management...... 119 7.16.9. Clearing the Last Recognized Stored Message...... 129 7.23.2. Set the Output Level of a GPIO Pin...... 139 7.11.1. Value Assignment...... 119 7.16.10. Querying the Last Recognized Active Message (String)...... 129 7.23.3. Toggle the Level of a GPIO Pin...... 139 7.11.2. Addition and Subtraction (Add Method)...... 119 7.16.11. Querying the Last Recognized Active Message (Hex)...... 129 7.24. EDID Management...... 139 7.11.3. Addition and Subtraction (Cycle Method)...... 120 7.16.12. Set the Active Timeout...... 129 7.24.1. Query the Emulated EDIDs...... 139 7.11.4. Value Change with Intervals (Case)...... 121 7.16.13. Running an Immediate Event Action...... 129 7.24.2. Query the Validity of a Dynamic EDID...... 140 7.11.5. Scan and Store...... 121 7.17. RS-232 Port Configuration...... 130 7.24.3. Query the Preferred Resolution of an User EDID...... 140 7.11.6. Reformatting a Value...... 122 7.17.1. Protocol Setting...... 130 7.24.4. Emulating an EDID to an Input Port...... 140 7.12. Ethernet Port Configuration...... 122 7.17.2. BAUD Rate Setting...... 130 7.24.5. Emulating an EDID to All Input Ports...... 140 7.12.1. Set the DHCP State...... 122 7.17.3. Databits Setting...... 130 7.24.6. Copy an EDID to User Memory...... 140 7.12.2. Change the IP Address (Static)...... 122 7.17.4. Stopbits Setting...... 131 7.24.7. Deleting an EDID from User Memory...... 140 7.12.3. Change the Subnet Mask (Static)...... 123 7.17.5. Parity Setting...... 131 7.24.8. Resetting the Emulated EDIDs...... 140 7.12.4. Change the Gateway Address (Static)...... 123 7.17.6. RS-232 Operation Mode...... 131 7.25. LW3 Commands - Quick Summary...... 141 7.12.5. Apply Network Settings...... 123 7.17.7. Command Injection Enable...... 131

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7 UMX-TPS-TX100 series – User's Manual 

8. FIRMWARE UPDATE...... 147 11.5.2. Audio Ports...... 171 8.1. Introduction...... 148 11.6. Mechanical Drawings...... 172 8.2. Preparation...... 148 11.6.1. UMX-TPS-TX100 series...... 172 8.2.1. About the Firmware Package (LFP2 File)...... 148 11.6.2. WP-UMX-TPS-TX100 series...... 173 8.2.2. LDU2 Installation...... 148 11.6.3. FP-UMX-TPS-TX100 series...... 173 8.3. Running the Software...... 149 11.7. Port Numbering...... 174 8.3.1. LDU2 Interfaces...... 149 11.7.1. WP-UMX-TPS-TX120-US...... 174 8.3.2. The Updating Steps...... 150 11.7.2. WP-UMX-TPS-TX130-US / WP-UMX-TPS-TX130-Plus-US...... 174 8.4. Updating via GUI...... 151 11.7.3. UMX-TPS-TX120...... 174 8.5. Command Line Interface (CLI)...... 152 11.7.4. UMX-TPS-TX130...... 174 8.5.1. How to Run...... 152 11.7.5. UMX-TPS-TX140 / UMX-TPS-TX140-Plus...... 175 8.5.2. How to Use...... 153 11.7.6. FP-UMX-TPS-TX120...... 175 8.6. CLI Commands...... 153 11.7.7. FP-UMX-TPS-TX130...... 175 8.6.1. Help...... 153 11.8. Maximum Extension Distances...... 175 8.6.2. LDU2 Version...... 153 11.9. Factory EDID List...... 176 8.6.3. Check For New LDU2 Version...... 153 11.10. Release Notes of the Firmware Packages...... 178 8.6.4. Device Info...... 154 11.10.1. UMX-TPS-TX100 Series...... 178 8.6.5. Update...... 154 11.10.2. WP- and FP-UMX-TPS-TX100 series...... 181 8.6.6. Restore...... 155 11.11. Hashtag Keyword List...... 184 8.6.7. Package Options...... 155 11.12. Further Information...... 185 8.6.8. Complex Examples...... 156 8.6.9. Exit Codes...... 157 8.7. If the Update is not successful...... 157 9. TROUBLESHOOTING...... 158 9.1. Use Cases...... 159 9.2. How to Speed Up the Troubleshooting Process...... 160 10. TECHNOLOGIES...... 161 10.1. EDID Management...... 162 10.1.1. Understanding the EDID...... 162 10.1.2. Advanced EDID Management...... 162 10.2. HDCP Management...... 163 10.2.1. Protected and Unprotected Content...... 163 10.2.2. Disable Unnecessary Encryption...... 163 10.3. Pixel Accurate Reclocking ...... 164 11. APPENDIX...... 165 11.1. Specifications...... 166 11.2. Factory Default Settings...... 169 11.3. Applied Ports (Network Settings)...... 169 11.4. Content of the Backup File...... 170 11.5. Cable Wiring Guide...... 171 11.5.1. Serial Ports...... 171

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 8

Introduction 1Thank you for choosing Lightware’s UMX-TPS-TX100 series device. In the first chapter we would like to introduce the device highlighting the most important features in the below listed sections:

ç Description ç Box Contents and Optional Accessories ç Features ç Model Comparison ç Typical Application

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 9

1.1. Description Number of This transmitter was designed to extend digital and analog video signals (e.g. VGA, DVI 1.0, HDMI 1.4 and HDBaseTTM TPS extender outputs DP 1.1) and audio signals (analog stereo audio from local inputs or embedded 7.1 HBR audio). Video signals with HDCP encryption are also supported. Analog signals (both audio and video) are converted to digital USB KVM format and the audio signals can be de-embedded from the video. Thus, many combinations of the audio/ UMX-TPS-TX140K features 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 Universal input interface: Transmitter Number of inputs connector. Advanced EDID Management forces the required resolution from any video source and fixes the analog and digital signals are accepted output format conforming to the system requirements. The unit offers bi-directional and transparent IR, Number RS-232 and Ethernet transmission. Furthermore, the IR and RS-232 connection support command injection, HDBaseTTM of allowing it to send any IR or RS-232 control command directly from the LAN connection. The built-in USB Floorplate TPS extender outputs port offers KVM extension in UMX-TPS-TX140K model. Remote powering (Power over Ethernet) is available through a single CAT cable, but local power supply can also be used. UMX-TPS transmitter can be mounted on a rack shelf or used standalone while the WP-UMX- FP-UMX-TPS-TX130 TPS and FP-UMX-TPS transmitters designed to place into a wall, furniture, or a floorbox. The transmitters are compatible with both the HDBaseTTM extenders and matrix switchers. Transmitter Number of inputs Compatible Devices Universal input interfaces - analog and digital signals The transmitter is compatible with other Lightware TPS receivers, matrix TPS and TPS2 boards, 25G TPS2 are also accepted boards, as well as third-party HDBaseT extenders, displays, but not compatible with the phased out TPS-90 extenders. Number The device can The transmitter is compatible HDBaseTTM of be mounted into with any third-party HDBaseTTM Wallplate TPS extender outputs B225R outlet box device.

HDBaseTTM and the HDBaseT Alliance logo are trademarks of the HDBaseT Alliance. WP-UMX-TPS-TX130-Plus-US White

USB Compatibility Universal input interface: Transmitter Advanced The color The USB KVM extension is available between UMX-TPS-TX140K and HDMI-TPS-RX220AK models. analog and digital Number control of the signals are also accepted of inputs features enclosure Model Denomination About the Serial Number Number of Advanced TM Lightware devices contain a label indicating the unique serial number of the product. The structure is the HDBaseT TPS extender outputs control features following: 7A000941 6-digit running sequence number UMX-TPS-TX140-Plus 1: Jan 4: Apr 7: Jul A: Oct Universal input interfaces - Transmitter Number of inputs Month of the manufacturing: 2: Feb 5: May 8: Aug B: Nov analog and digital signals 3: Mar 6: Jun 9: Sep C: Dec are also accepted Year of the manufacturing: 7=2017 A=2020 D=2023 (3-9, A-Y) 8=2018 B=2021 E=2024 9=2019 C=2022 F=2025

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 10

1.2. Box Contents and Optional Accessories The optional accessories can be purchased separately; please contact [email protected].

Supplied accessories Optional accessories

Safety and Quick Warranty Start TX Info Guide

Safety and Phoenix® Phoenix® Phoenix® Fixing screws Switch/outlet Transmitter 12V DC Infrared emitter 48V DC Mounting warranty info, Combicon 3-pole Combicon 5-pole Combicon 8-pole for mounting box (B225R) for device power adaptor unit power adaptor bracket kit * QSG connector connector connector (4 pcs.) mounting

UMX-TPS-TX120      ------

UMX-TPS-TX130      -  - - - -

UMX-TPS-TX140        - - - -

UMX-TPS-TX140K        - - - -

UMX-TPS-TX140-Plus        - - - -

FP-UMX-TPS-TX120   - -  - - -  -  *

FP-UMX-TPS-TX130   - -  - - -  -  *

WP-UMX-TPS-TX120-US Black   - -  - -  (black)(   -

WP-UMX-TPS-TX120-US White   - -  - -  (white)(   -

WP-UMX-TPS-TX130-US Black   - -  - -  (black)(   -

WP-UMX-TPS-TX130-US White   - -  - -  (white)(   -

WP-UMX-TPS-TX130-Plus-US Black   - -  - -  (black)(   -

WP-UMX-TPS-TX130-Plus-US White   - -  - -  (white)(   -

* Each model has its own mounting kit – please see more details in the Mounting Options - Floor Plates section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 11

1.3. Features GPIO Control Port ATTENTION! The availability of below features are device-dependent, see the following page. 7 GPIO pins operating at TTL digital signal levels and can be controlled with both LW2 and LW3 commands. 1.3.1. List of Features (in alphabetical order) HDCP-compliant 4K and 3D Support The device fulfills the HDCP standard. HDCP capability on the digital video inputs can be High bandwidth allows extension of resolutions up to 4K and even 3D sources and displays are disabled when non-protected content is extended. supported. Infra Code Sending Autoselect Function for Video Inputs IR code sending in Pronto Hex format – in Command injection mode, too. The code sending is The Autoselect feature can sense the port status on the video input ports and select available as an Action in Event manager, too. automatically one of them. Various modes are available: first detect, last detect, priority detect. Miniweb Basic IT-security LWR The Miniweb is able to display an adaptive surface with a virtual crosspoint and buttons for These entry-level network security improvements help to prevent unauthorized access to the Event manager Actions. The miniweb can be displayed in a mobile device, too. Lightware device: plain-text login, TCP port blocking and MAC address filtering. Pixel Accurate Reclocking Batch Commands Each output has a clean, jitter free signal, eliminating signal instability and distortion caused by A batch of LW3 commands (salvo) can be run by the Lightware device either by a previously long cables or connector reflections. stored macro or by sending a file to the device with the desired commands. Remote Power Breakaway Audio/Video Switching The transmitters are PoE-compatible and can be powered locally by the supplied power Breakaway audio/video switching allows for switching audio and video separately by de- adaptor, or remotely via the TPS connection with a compatible power source equipment. embedding and embedding audio from/into HDMI signals. RS-232 RS-232 Recognizer Consumer Electronics Control CEC x Support recognizing incoming RS-232 messages to integrate with 3rd party devices like the Supports transmitting standard CEC commands in order to remote control the source or sink 11 0100 1 videoconference codec devices. device. RS-232 Transmission Dark Mode RS-232 AV systems can also contain serial port controllers and controlled devices. Serial port pass- All illuminating elements of the front/rear panel can be switched on and off. This feature is through supports any unit that works with standard RS-232. useful in live-stage shows or other environments where flashing LEDs would be distracting. Signal Transmission up to 170 m Deep Color Support and Conversion 170M Video and audio signal transmission (HDMI, Ethernet, RS-232, and Infra-Red) over a single It is possible to transmit the highest quality 36-bit video streams for perfect color reproduction. @1080p60Hz CAT5e…CAT7e cable. TCP TCP Recognizer Event Manager x Support recognizing the incoming TCP messages to integrate with 3rd party devices like the The Event Manager tool takes care of all the necessary control in a smaller configuration by 11 0100 1 videoconference codec devices. performing predefined actions in response to device status changes. TPS Cable Diagnostic Tool Event Manager + The TPS Cable Diagnostics Tool within the LDC software will help you identify potential twisted Triggering a condition, defining variables and checking two conditions for an action – these pair cable issues in your TPS‑capable (HDBaseT compliant) system. features are available by the improved Event Manager. USB Extension Forced Button Lock KVM extension for USB HID devices (Human Interface Devices, e.g. keyboard, mouse, The front panel buttons can be locked and unlock is only possible via LW3 protocol command. presenter).

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 12

1.3.2. Feature Availability Advanced Control Pack Advanced Control Pack v3 Basic Features (from FW pack (from FW pack v1.5.0b4) v1.3.0b11)

RS-232 RS-232 LWR TCP CEC x x 170M 11 0100 1 11 0100 1 @1080p60Hz 4K and 3D Support for Function Autoselect Video Inputs Audio/Video Breakaway Switching Dark mode Deep Color Support and Conversion Manager Event lock button Forced PortGPIO Control HDCP-compliant Miniweb Accurate Pixel Reclocking Remote Power Transmission RS-232 up Signal Transmission 170 m to TPS Cable Diagnostic Tool USB Extension Consumer Electronics Control Code Sending Infra RS-232 Recognizer Security Basic IT Batch Commands Manager + Event Recognizer TCP

* TX120        -        ------ -

* TX130  ------ -

* UMX-TPS- TX140  ------ -

TX140-Plus  -       

TX140K 

* TX120-US White        -        ------ -

* TX120-US Black        -        ------ -

* TX130-US White        -        ------ - WP-UMX- TPS- * TX130-US Black        -        ------ -

TX130-Plus-US White        -        -       

TX130-Plus-US Black        -        -       

* TX120        -        ------ - FP-UMX- TPS- * TX130        -        ------ -

* Only the Combine Links feature is available in these devices.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 13

1.4. Model Comparison The available models have different features depending on their design. The following table contains the most important differences between the models:

Video ports Audio ports Interface ports Firmware-related features

Advanced Number of Advanced Control Pack HDMI VGA DVI-I Jack 3.5 Phoenix Infra I/O Infra input mini Events in Event Control Pack input input input DP input input input Ethernet connectors sensor RS-232 GPIO USB-B Manager v3

TX120   - -  -   -  - - 20 - -

TX130    -  -   -   - 20 - -

Standalone models TX140         -   - 20 - - UMX-TPS- from FW pack from FW pack TX140-Plus         -   - 100 v1.3.0b11 v1.5.0b4 from FW pack from FW pack TX140K         -    100 v1.3.0b11 v1.5.0b4

TX120-US Black   - -  -  -   - - 20 - -

TX120-US White   - -  -  -   - - 20 - -

TX130-US Black   -   -  -   - - 20 - - Wall plate models WP-UMX-TPS- TX130-US White   -   -  -   - - 20 - -

from FW pack from FW pack TX130-Plus-US Black   -   -  -   - - 100 v1.3.0b11 v1.5.0b6 from FW pack from FW pack TX130-Plus-US White   -   -  -   - - 100 v1.3.0b11 v1.5.0b6

FP-UMX-TPS-TX120   - -  -  -   - - 20 - - Floor plate models FP-UMX-TPS-TX130   -   -  -   - - 20 - -

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

1. Introduction UMX-TPS-TX100 series – User's Manual 14

1.5. Typical Application Standalone Application Diagram - UMX-TPS-TX140K Standalone Application Diagram - UMX-TPS-TX140

Active speakers

Volume control

Blu-ray player

TPS link good link TPS

No TPS link TPS No

Low power mode power Low

IR emitter enumerated USB

Control mode mode Control

Pass-through mode Pass-through

Command Injection mode mode Injection Command

Powered but no operation no but Powered upgrade mode upgrade

IR detector power No

Normal operation operation Normal

for audio de-emebedding audio for

Embedded audio present and de-embedded de-embedded and present audio Embedded

Firmware Firmware

Embedded audio not present or muted or present not audio Embedded

Embedded audio format not supported not format audio Embedded

Autoselect enabled Autoselect

Signal present on selected input selected on present Signal

encrypted encrypted

Input not selected not Input

Input selected, signal not present not signal selected, Input

signal replaced with red screen red with replaced signal

Output signal HDCP HDCP signal Output device connected, encrypted encrypted connected, device

encrypted

Non HDCP capable capable HDCP Non

Output signal not HDCP HDCP not signal Output

or muted or

Signal present Signal

Sn

Output signal not present not signal Output

Input signal present signal Input Projector SIGNAL HDCP

Input signal not present not signal Input 2

Keyboard Link TPS Remote power (PoE) power Remote

HDMI OUT

A SIGNAL HDCP 1

HDMI OUT

Sn: Sn: Sn:

H

Laptop AWG23 use performance best For

D

M

(IEEE 802.3af) 802.3af) (IEEE

Mouse I

-

T Device can be remote powered over TPS link with PoE PoE with link TPS over powered remote be can Device

P SIGNAL S

-

_

12V DC--- X 2

2

2

1.5A 0 A

K HDMI IN 12V 1A 12V

PIN: 2mm PIN: 1 (PoE)

DC

Bidirectional RS-232 Bidirectional PIN: 2mm CA

T6 or CAT7 SFTP cable SFTP CAT7 or T6 TPS IN Made in EU, Hungary EU, in Made Bidirectional IR Bidirectional

Ethernet 10/100 Ethernet

HDMI, 3D, 4K supported 4K 3D, HDMI,

RoHS TT _

12V DC PP ---

SS 1.5A

LL

oonngg

DDii

ss HDMI-

DVI-I IN tt aa

nn Remote control cc

AUDIO2 IN ee

RR

eecceeii vv

UMX-TPS- eerr TPS-RX220AK IR emitter

LIVE

RS-232 HH 12V DC

PC DD

SRVC MM

II--

LINK TT PPSS

--

RR

MAC XX IR IN IR OUT 99

TX140 77 Power ( PoE ) HDMI-TPS-RX97 S IN TP adaptor GPIO Electric RS-232

PIN: 2.1mm TX RX projector

12V 1A DC screen 12V DC UMX-TPS- power TX140K

1 2 3 4 5 6 PLAY 7 8

STOP

adaptor BT AAC 2 00:03:16

EJECT

CD / USB / SD / AUX / BT / FM / AM PUSH TO EJECT

TEXT LOCK SD ALL/ FOLDER DVI-I IN RANDOM

REPEAT

CD/USB/SD AUDIO2 IN 3 HD Projector AUX/ BT 2 USB 1 6 AUX IN LIVE RS-232 SRVC 5 POWER 4 LINK Remote WiFi IR IN IR OUT

Media player TPS OUT (PoE) control HDMI Analog audio 12V DC power access GPIO

RS-232

adaptor PIN: 2.1mm TX RX TBP6 IR detector DVI TPS (up to 170 m) 12V 1A DC

Button panel LAN Infrared Ethernet Touch panel 12V DC PC Power HDMI Analog audio adaptor Ethernet RS-232 Power VGA TPS (up to 170 m) USB 2.0

Ethernet DisplayPort RS-232 switch DVI Infrared Standalone Application Diagram - WP-UMX-TPS-TX130-US LAN Power

12V DC

Integrated System Diagram - UMX-TPS-TX140 power

Sn: Sn: Sn:

For best performance use AWG23 AWG23 use performance best For (IEEE 802.3af) 802.3af) (IEEE HDMI-

adaptor PoE with link TPS over powered remote be can Device WP-UMX-TPS-TX130-US

12V 1A 12V

PIN: 2mm PIN:

DC

Bidirectional RS-232 Bidirectional CA

T6 or CAT7 SFTP cable SFTP CAT7 or T6 Made in EU, Hungary EU, in Made

Bidirectional IR Bidirectional

12V DC 10/100 Ethernet TPS-RX97

HDMI, 3D, 4K supported 4K 3D, HDMI,

RoHS TT

PP

SS

LL

SHOW oonngg

ME power DDii

ss

tt

AUDIO aa

nn

cc

SELECT ee

RR

VIDEO WiFi eecceeii vv SELECT eerr

AUDIO IR INPUT STATUSDP adaptor 7 97 X9 RX -R S- PS TP -T I- MI DM HD H HDMI VGA TPS LinkRESET DP access ETHERNET HDMI Autoselect Remote PoE 3 ( ) VIDEO AUDIO TPS IN 2 DP IN controller

O

Sn: Sn: Sn:

For best performance use AWG23 AWG23 use performance best For

(IEEE 802.3af) 802.3af) (IEEE

Device can be remote powered over TPS link with PoE PoE with link TPS over powered remote be can Device

12V 1A 12V

PIN: 2mm PIN: HDMI-TPS-

DC

Bidirectional RS-232 Bidirectional CA

T6 or CAT7 SFTP cable SFTP CAT7 or T6

Made in EU, Hungary EU, in Made Bidirectional IR Bidirectional

Ethernet 10/100 Ethernet

HDMI, 3D, 4K supported 4K 3D, HDMI, RoHS TTPP

SS

Speaker LL

oonngg

DDiisstt RX97

aa

nn

cc

ee

Ethernet RReecceeiivveerr

WP-UMX-TPS-TX130-US Blu-ray HH

DDMMII-- player TT

PPSS--

RR XX9977 HD Projector

( PoE ) S IN TP AV Receiver

Ethernet 12V DC switch power Ethernet switch adaptor

OUT 8 Laptop HDMI Analog audio OUT 7

OUT 6

OUT 5 IN 8

OUT 4 MAC UMX-TPS-TX140 IN 7 Ethernet VGA TPS (up to 170 m)

OUT 3 IN 6

OUT 2 IN 5

OUT 1 12V power onIN TPS 4 connector. Only use with compatible devices! DisplayPort RS-232 MX-HDMI-3D-OB-A DVI-I IN IN 3

AUDIO2 IN S/PDIF I/O 1 S/PDIF I/O 2 S/PDIF I/O 3 S/PDIF I/O 4 S/PDIF I/O 5 S/PDIF I/O 6 S/PDIF I/O 7 S/PDIF I/O 8 8CH OUTPUT BOARD FOR HDMI WITH 3D AND ANALOG AUDIO TPS OUT 1 IN TPS 2 OUT 2 TPS OUT 3 TPS OUT 4 TPS OUT 5 TPS OUT 6 TPS OUT 7 TPS OUT 8 12V 4A MX-TPS-OB-S

LIVE DC IN IN 1 Projector RS-232 12V power on TPS connector. Only use with compatible devices! SRVC 8 CH TPS OUTPUT BOARD WITH DIGITAL AUDIO LINK LAN Power MX-HDMI-3D-IB-A IR IN IR OUT

8CH INPUT BOARD FOR HDMI WITH 3D AND ANALOG AUDIO TPS IN 1 TPS IN 2 TPS IN 3 TPS IN 4 TPS IN 5 TPS IN 6 TPS IN 7 TPS IN 8 12V 3A MX-TPS-IB-S

GPIO DC IN 8 CH TPS INPUT BOARD

RS-232

PIN: 2.1mm TX RX

12V 1A DC

MX-FR17 Local monitor 12V DC power HDMI adaptor Analog audio Laptop TPS (up to 170 m) LAN RS-232 PC or MAC Power

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 15

Product Overview 2The following sections are about the physical structure of the device, input/ output ports and connectors: ç Front View - UMX-TPS-TX100 series ç Rear View - UMX-TPS-TX100 series ç Front View - WP-UMX-TPS-TX100 series ç Rear View - WP-UMX-TPS-TX100 series ç Front View - FP-UMX-TPS-TX100 series ç Front Panel LEDs ç Rear Panel LEDs ç Front Panel Buttons ç Special Functions

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 16

2.1. Front View - UMX-TPS-TX100 series UMX-TPS-TX140 /UMX-TPS-TX140-Plus UMX-TPS-TX120 1 2 3 4 6 789 q 1 2 3 5 678 9

UMX-TPS-TX140K 1 2 3 4 5 6 789 q UMX-TPS-TX130 1 2 3 5 678 9

1 VGA input D-SUB connector for analog video signal.

2 Audio1 input 3.5 mm Jack connector for asymmetric analog audio input signal. 1 VGA input D-SUB connector for analog video signal. 3 HDMI input HDMI connector for DVI video or HDMI video and audio. 2 Audio1 input 3.5 mm Jack connector for asymmetric analog audio input signal. 4 DisplayPort input DisplayPort connector for DisplayPort audio/video signal. 3 HDMI input HDMI connector for DVI video or HDMI video and audio. 5 USB KVM Mini-B type connector for KVM extension for USB HID (Human Interface 4 DisplayPort input DisplayPort connector for DisplayPort audio/video signal. Devices, e.g. keyboard, mouse, presenter). This port transmits the USB data from the extender towards the PC. #usb #usbkvm 5 Input Status LEDs LEDs give feedback about the current status of the unit and input signals. See the details in the Front Panel LEDs section. #status 6 Input Status LEDs LEDs give feedback about the current status of the unit and input signals. See the details in the Front Panel LEDs section. #status 6 Video Select button Button for switching between video sources. See the details in the Video Select Button section. #crosspoint #switch #testpattern #button 7 Video Select button Button for switching between video sources. See the details in the Video Select Button section. #crosspoint #switch #testpattern #button 7 Reset button Pushing the button reboots the unit. #reset #reboot 8 Reset button Pushing the button reboots the unit. #reset #reboot 8 Audio Select button Button for switching between audio sources. See the details in the Audio Select Buttonsection. #audio #analogaudio 9 Audio Select button Button for switching between audio sources. See the details in the Audio Select Button section. #audio #analogaudio 9 Show Me button Special functions can be reached using this button (firmware update (bootload) mode, DHCP settings, restore factory default settings, q Show Me button Special functions can be reached using this button (firmware update condition launching in Event Manager). #dhcp #factorydefault (bootload) mode, DHCP settings, restore factory default settings, condition launching in Event Manager). #dhcp #factorydefault

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 17

2.2. Rear View - UMX-TPS-TX100 series UMX-TPS-TX140 / UMX-TPS-TX140-Plus UMX-TPS-TX120 12 3 4 5 6 7 8 9 12 4 5 6 7

UMX-TPS-TX140K

UMX-TPS-TX130 12 3 4 5 6 7 8 9 12 3 4 5 6 7 9

1 12V DC input 12V DC input for local powering. For more details see the Locking 12V DC Connection section or see all the available Powering Options.

1 12V DC input 12V DC input for local powering. For more details see the Locking 12V DC 2 RS-232 3-pole Phoenix connector for controlling the device with LDC or third-party control Connection section or see all the available Powering Options. connector systems, or third-party device control. Pin assignment can be found in the RS-232 Connector section. 2 RS-232 3-pole Phoenix connector for controlling the device with LDC or third-party control connector systems, or third-party device control. Pin assignment can be found in the RS-232 3 GPIO 8-pole Phoenix connector for configurable general purpose input/output ports. Pin Connector section. assignment can be found in the GPIO - General Purpose Input/Output Ports section. 3 GPIO 8-pole Phoenix connector for configurable general purpose input/output ports. Pin 4 Ethernet Locking RJ-45 connector for configuring the device using Lightware Device assignment can be found in the GPIO - General Purpose Input/Output Ports section. Controller (LDC), or updating it using Lightware Device Updater (LDU). Any third- party control system can use this port to control the device.

4 Ethernet Locking RJ-45 connector for configuring the device using Lightware Device TM Controller (LDC), or updating it using Lightware Device Updater (LDU). Any third- 5 TPS OUT Locking RJ45 connector for HDBaseT signal transmission. Maximum CATx party control system can use this port to control the device. (PoE) cable distances can be found in the Maximum Extension Distances section. 5 TPS OUT Locking RJ45 connector for HDBaseTTM signal transmission. Maximum CATx 6 Status LEDs The LEDs give feedback about the actual state of the device. See the details in the (PoE) cable distances can be found in the Maximum Extension Distances section. Rear Panel LEDs section. 6 Status LEDs The LEDs give feedback about the actual state of the device. See the details in the 7 IR IN and 3-pole TRS connector, also known as 3.5 mm (1/8”) jack plug for optional IR Rear Panel LEDs section. OUT receiver (IR IN) and transmitter (IR OUT) connection. Pin assignments can be found in the IR Connector section. 7 IR IN and 3-pole TRS connector, also known as 3.5 mm (1/8”) jack plug for optional IR OUT receiver (IR IN) and transmitter (IR OUT) connection. Pin assignments can be 8 Audio2 input 5-pole Phoenix connector for balanced analog audio input. Pin assignment can found in the IR Connector section. be found in the Analog Stereo Audio (Phoenix) section. 8 Audio2 input 5-pole Phoenix connector for balanced analog audio input. Pin assignment can 9 DVI-I input DVI-I connector for analog / DVI / HDMI signals. Pin assignment can be found in be found in the Analog Stereo Audio (Phoenix) section. the DVI-I Connector section. 9 DVI-I input DVI-I connector for analog / DVI / HDMI signals. Pin assignment can be found in the DVI-I Connector section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 18

2.3. Front View - WP-UMX-TPS-TX100 series 2.4. Rear View - WP-UMX-TPS-TX100 series WP-UMX-TPS-TX120-US WP-UMX-TPS-TX130-US / WP-UMX-TPS-TX130-Plus-US WP-UMX-TPS-TX120-US / WP-UMX-TPS-TX130-US / 1 1 WP-UMX-TPS-TX130-Plus-US 1 2 7 2 7 3 8 3 8 4 4 9 9 5 q 5 q 2 3 6 6 w

1 Input Status LEDs LEDs give feedback about the current status of the unit and input signals. See the details in the Front Panel LEDs section.

2 Audio Select button Button for switching between audio sources. See the details in the Audio Select Button section. #audio #analogaudio 1 RS-232 connector 3-pole Phoenix connector for controlling the device with LDC or third-party control systems, or third-party device control. Pin assignment can be found 3 Video Select button Button for switching between video sources. See the details in the Video in the RS-232 Connector section. Select Button section. #crosspoint #switch 2 TPS output (PoE) Locking RJ45 connector for HDBaseTTM signal transmission. Maximum 4 Ethernet Locking RJ-45 connector for configuring the device using Lightware CATx cable distances can be found in the Maximum Extension Distances Device Controller (LDC), or updating it using Lightware Device Updater section. (LDU). Any third-party control system can use this port to control the device. 3 48V DC input Power the device remotely by a PoE-compatible power injector (TPS-PI- 1P1). If the device has to be powered by a local adaptor (PSU-48VP1), 5 VGA input D-SUB connector for analog video signal. connect the output to the 2-pole Phoenix connector on the rear of the wall plate. See more details about powering options in the 48V DC Connection 6 Audio input 3.5 mm Jack connector for asymmetric analog audio input signal. section or see all the available Powering Options. 7 Show Me button Special functions can be reached using this button (firmware update (bootload) mode, DHCP settings, restore factory default settings, condition launching in Event Manager). #dhcp #factorydefault

8 Reset button Pushing the button reboots the unit. #reboot #reset

9 IR detector IR Detector can sense IR light which can be forwarded to the receiver side or use for controlling functions.

q HDMI input HDMI connector for DVI video or HDMI video and audio.

w DisplayPort input DisplayPort connector for DisplayPort audio/video signal.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 19

2.5. Front View - FP-UMX-TPS-TX100 series 1 Input Status LEDs LEDs give feedback about the current status of the unit and input signals. See the details in the Front Panel LEDs section. #status FP-UMX-TPS-TX120 1 2 Audio Select button Button for switching between audio sources. See the details in the Audio Select 2 7 Button section. 3 Video Select button Button for switching between video sources. See the details in the Video Select 3 Button section. 8 4 4 Ethernet Locking RJ-45 connector for configuring the device using Lightware Device Controller (LDC), or updating it using Lightware Device Updater (LDU). Any 9 third-party control system can use this port to control the device. 5 q 5 VGA input D-SUB connector for analog video signal.

6 6 Audio input 3.5 mm Jack connector for asymmetric analog audio input signal.

7 Show Me button Special functions can be reached using this button (firmware update FP-UMX-TPS-TX130 (bootload) mode, DHCP settings, restore factory default settings, condition 1 launching in Event Manager). 2 7 8 Reset button Pushing the button reboots the unit.

3 9 IR detector IR Detector can sense IR light which can be forwarded to the receiver side or 8 use for controlling functions. 4 q HDMI input HDMI connector for DVI video or HDMI video and audio. 9 w DisplayPort input DisplayPort connector for DisplayPort audio/video signal. 5 q #analogaudio #audio #button #crosspoint #switch #testpattern #network #dhcp #reset reboot 6 w #restart #nosyncscreen

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 20

2.5.1. Rear View - FP-UMX-TPS-TX100 series 2.6. Front Panel LEDs 1 2 3 INFO: The operation of the status LEDs of WP-UMX-TPS-TX100 series and FP-UMX-TPS-TX100 series models are the same. ATTENTION! When Dark mode is enabled, no LEDs are on, even though the device is fully functional. #status

VIDEO input LEDs off Video source is not selected. green blinking Video source is selected and signal is not detected. green on Video source is selected and signal is present. AUDIO input LEDs off Audio source is not selected. green blinking Audio source is selected and signal is not detected. TM Audio source is selected and the port is active but not embedded 1 TPS output (PoE) Locking RJ45 connector for HDBaseT signal transmission. Maximum CATx green on (with short pause) cable distances can be found in the Maximum Extension Distances section. to the output video stream (DVI output mode). Audio source is selected, the port is active and the audio is green on (continuously) 2 RS-232 connector 3-pole Phoenix connector for controlling the device with LDC or third-party embedded to the output video stream (HDMI output mode). control systems, or third-party device control. Pin assignment can be found in Autoselect LED the RS-232 Connector section. off Autoselect function is disabled. 3 48V DC input Power the device remotely by a PoE-compatible power injector (TPS-PI-1P1). Autoselect function is enabled, searching for signal (the video green blinking If the device has to be powered by a local adaptor (PSU-48VP1), connect the input LEDs are also blinking). output to the 2-pole Phoenix connector on the rear of the floor plate. See more Autoselect function is enabled, the active video signal is found green on details about powering options in the 48V DC Connection section or see all (the selected video input's LED is also ON). the available Powering Options. HDCP LED off Video output signal is not encrypted with HDCP. red on Video output signal is HDCP-encrypted.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 21

Firmware Version Indication 2.7. Rear Panel LEDs After being powered on, the transmitter lights up all LEDs, then displays its firmware version using three LEDs on the front panel: the upper three in the left column. The top LED means the first number of the LIVE LED firmware version – actually this is the main version. The second and the third LEDs from the top indicate the off The device is not powered. second and the third numbers of the firmware version which mean the subversions. #firmwareversion green blinking (slow) The device is powered and operational. VGA Audio1 HDCP INPUT STATUS HDMI HDMI Autoselect VGA AUDIO green blinking (fast) The device is in firmware update (bootload) mode. DP DP DVI-A Video DP DP DVI-D DVI-D Audio2 HDMI HDMI VIDEO AUDIO Autoselect TPS LINK green on The device is powered but not operational. VIDEO AUDIO 1.3.2 INPUT STATUS 1.4.0 RS-232 LED UMX-TPS-TX140 WP-UMX-TPS-TX130-US off RS-232 ports (Local and Link) are in Passthrough mode. Example - WP-UMX-TPS-TX130-US green blinking Command injection mode is active. The process after the device is switched on or rebooted is the following: green on RS-232 ports (Local and Link) are in Control mode. Step 1. VGA LED blinks once the first number (1). Step 2. DP LED blinks twice the second number (2). SRVC LED * Step 3. HDMI LED stays dark showing the third number (0). green on Test pattern is the selected and active input source. USB KVM LED * No USB link between the transmitter and the controlled device off (e.g. PC). green on The USB is enumerated. LINK LED off No TPS link between the transmitter and the receiver. green blinking (slow) Low power mode is active. green blinking (fast) Ethernet fallback mode is active. green on TPS link is established, HDBaseT or Long Reach mode is active.

* Only the UMX-TPS-TX140K model has USB KVM LED, but it does not contain SRVC LED. #status

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 22

2.8. Front Panel Buttons 2.8.2. Audio Select Button INFO: WP-UMX-TPS-TX130-US and FP-UMX-TPS-TX130-MKM models have the same functionality. The Desired audio input can be selected by the Audio Select button from the front panel. The selection operation of the front panel buttons is also similar. #button #crosspoint #switch order of the inputs depends on the model as follows: AUDIO Analog audio Embedded digital audio 2.8.1. Video Select Button UMX-TPS-TX120: SELECT Desired video input can be selected by the Video Select button from the front panel. The selection order of the inputs depends on the model as follows: Analog audio Embedded digital audio VIDEO UMX-TPS-TX130: VGA HDMI Autoselect SELECT UMX-TPS-TX120: Audio1 Audio2 Embedded audio UMX-TPS-TX140: VGA HDMI DVI-D DVI-A UMX-TPS-TX130: Autoselect WP-UMX-TPS-TX120-US, Analog audio Embedded digital audio VGA HDMI DP DVI-D DVI-A WP-UMX-TPS-TX120-Plus-US: UMX-TPS-TX140: Autoselect WP-UMX-TPS-TX130-US, Analog audio Embedded digital audio WP-UMX-TPS-TX120-US, VGA HDMI Autoselect WP-UMX-TPS-TX130-Plus-US: WP-UMX-TPS-TX120-Plus-US: Analog audio Embedded digital audio FP-UMX-TPS-TX130-MKM: WP-UMX-TPS-TX130-US, VGA HDMI DP Autoselect WP-UMX-TPS-TX130-Plus-US: INFO: Embedded digital audio is received on the digital video input port (HDMI / DP / DVI-D) which is VGA HDMI DP Autoselect currently selected. If analog video input signal (VGA / DVI-A) is selected which cannot contain embedded FP-UMX-TPS-TX130-MKM: audio, this source is skipped. #audio #analogaudio

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

2. Product Overview UMX-TPS-TX100 series – User's Manual 23

2.9. Special Functions 2.9.5. Control Lock

2.9.1. Programmable Show Me Button Press the Audio Select and Show Me buttons together (within 100 ms) RESET to disable/enable front panel buttons; front panel LEDs blink 4 times Action or an operation can be assigned to the Show Me button as this button press is a condition when locking/unlocking. If the control lock is enabled and a button that can be selected in the Event Manager. See more details in the Event Manager section. SHOW ME is pressed, front panel LEDs blink 3 times. #controllock VIDEO AUDIO SHOW HighlightMe (Default Function) SELECT SELECT ME

DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- 2.9.6. Entering Firmware Update Mode UMX-TPS series). ATTENTION! This function is applicable only in special cases when the device is to be updated by the This feature is to help finding the desired device in the Device discovery window of Lightware Device Lightware Device Updater (LDU) software. Do not use this option with LDU2 software. Controller software. Press the Show Me button for 5 seconds until the front panel LEDs start to blink slowly, then release the button. In parallel, the device is highlighted in green for 4 seconds in the Device discovery It may happen that the firmware update process is not successful and the device cannot be window of the LDC, see the Highlighting the Device section. switched to bootload mode automatically. In this case, the device can be forced into firmware update mode as follows: SHOW 2.9.2. Enable DHCP (Dynamic) IP Address ME Step 1. Make sure the transmitter is powered off. The device has a static IP address as a factory default setting. If this setting does not fit Step 2. Press and keep pressed the Show Me button. to the circumstances during install or usage, DHCP can be enabled from the front panel: 5 Step 3. Power on the transmitter while the Show Me button is being pressed. If the device is switched to sec SHOW Step 1. Make sure the device is powered on and operational. ME firmware update mode the LIVE LED is blinking quickly (less than 500 ms duty cycle). The other LEDs Step 2. Press and keep pressed the Show Me button for 5 seconds. are off. Step 3. After 5 seconds front panel LEDs start blinking; release the button and press it 3 times again quickly The procedure of firmware update can be found in theFirmware Update chapter. (within 3 seconds). Step 4. The LEDs get dark, DHCP gets enabled. #network #dhcp 2.9.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. 10 sec SHOW Step 2. Press and keep pressed the Show Me button for 10 seconds. After 5 seconds front ME panel LEDs start blinking but keep on pressing the button. Step 3. After 10 seconds the LEDs start blinking faster; release the button and press it 3 times again quickly (within 3 seconds). Step 4. The LEDs get dark, the device restores the factory default settings and reboots. Factory default settings are listed in the Factory Default Settings section. #factorydefault 2.9.4. Reseting the Device In few cases (after firmware update, etc) you may need to reset the RESET device. Pushing the reset button results the same as you disconnect and reconnect the power adaptor to the transmitter. To reseting the

device follow the steps: VIDEO AUDIO SHOW Step 1. Push the button with a thin object for a second. SELECT SELECT ME Step 2. Wait until the device reboots. You can use the transmitter when the LIVE LED is blinking slowly again. ATTENTION! Reseting the device does not reset the settings to factory defaults. To reset factory default settings see the previous section. # reset # reboot #restart Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 24

3Installation The chapter is about the installation of the device and connecting to other appliances, presenting also the mounting options and further assembly steps

ç Mounting Options - Standalone Transmitters ç Mounting Options - Floor Plates ç Mounting Options - Wall Plates ç Electrical Connections ç Connecting Steps ç Powering Options

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 25

3.1. Mounting Options - Standalone Transmitters 3.1.2. Under-desk Double Mounting Kit To mount the transmitter Lightware supplies optional accessories for different usage. There are two kinds of mounting kits with similar fixing method. The device has two mounting holes with inner thread on the bottom side; see the bottom view in the Mechanical Drawings section. To order mounting accessories please contact [email protected]. More details about the accessories and the mounting can be found in the Mounting Assembly Guide. WARNING! Always use the supplied screws. Using different (e.g. longer) screws may damage the device. Under-desk double mounting kit INFO: The transmitter is half-rack sized. The UD-kit double makes it easy to mount a single transmitter on any flat surface (e.g. furniture). 3.1.1. 1U High Rack Shelf This accessory allows rack mounting for half-rack, quarter-rack and pocket sized units.

1U high rack shelf

1U high rack shelf provides mounting holes for fastening two half-rack or four quarter-rack sized units. Pocket sized devices can also be fastened on the self. INFO: The chipboard screws are not supplied with the mounting kit.

ATTENTION! Always use all the four screws for fixing the rack shelf ears to the rack rail. Choose properly sized screws for mounting. Keep minimum two threads left after the nut screw.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 26

3.2. Mounting Options - Floor Plates Dimensions of the Bracket 3.2.1. MKM Mounting Option The following drawing and table represents the dimensions of the Lightware brackets assembled with the transmitter unit. The values are in mm. Floor Box Compatibility Table Tab The FP-UMX-TPS MKM kit can be ordered separately, please contact [email protected]. Fixing screw Compatible Floor Boxes Compatible Lightware mounting bracket kit: FP-UMX-TPS MKM Kit Handle Product family Part number Sample picture FP-UMX-TPS-TX100 series transmitter CRMB265-3GRY FP-UMX-TPS MKM 53.4 bracket CRMB265-3GRYL 217 MK Cablelink Plus Modular 77 Floorboxes CRMB340-4GRY Dimensions and layout of the MKM bracket CRMB340-4GRYL Mounting Steps - FP-UMX-TPS MKM Kit Step 1. Assembling of the bracket: insert both handle tab parts to the bracket and fix them with the two supplied CRMB265-3GRY M3x6 PH fixing screws. Do not tighten well the screws, the tabs must stay movable.

CRMB265-3GRYL Ackermann Cablelink Modular Floorboxes CRMB340-4GRY

CRMB340-4GRYL

INFO: The transmitter unit can be mounted to the place of a compartment (a service power module or an unserviced data module)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 27

Step 2. Insert the bracket into the frame. Step 4. Fasten the fixing screws to fix the device into the floor box frame.

Step 5. Place the transmitter to the bracket.

Step 3. Move the handles towards the frame. Align the tab on the assembly with the top slot in the frame.

Step 6. Fasten the all four M3x6 PH fixing screws to fix the device to the bracket.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 28

3.2.2. MKS Mounting Option Mounting Steps - FP-UMX-TPS MKS Kit Floor Box Compatibility Table Step 1. Place the MKS bracket to the floor box so that the screw holes are able to fit. Fasten the bracket with both supplied DIN 7981 3,5x19 PZ2 self tapping screws. The FP-UMX-TPS MKS kit can be ordered separately, please contact [email protected].

Compatible Service Outlet Boxes Compatible Lightware mounting bracket kit: FP-UMX-TPS MKS Kit Product family Part number Sample picture CUB100UK-1 CUB200UK-2 CUB265UK-3 MK Cablelink Plus CUB340UK-4 Screed System CUB100XUK-1 CUB200XUK-2 CUB265XUK-3 Step 2. Place the transmitter to the bracket. CUB340XUK-4 CRB100UK-70-1GRY CRB265UK-70-3GRY MK Cablelink Single Pan CRB340UK-70-4GRY Boxes CRB100UK-1GRY CRB265UK-3GRY CRB340UK-4GRY NXB200X-2 NXB265X-2 MK Cablelink Onix Plus NXB265X-3 Screeded Floor System Step 3. Fasten the all four M3x6 PH fixing screws to fix the device to the bracket. NXB340X-3 NXB340X-4

INFO: The transmitter unit can be mounted FP-UMX-TPS-TX100 to the place of a compartment (a serviced/ series transmitter unserviced power plate or an unserviced 59.3 FP-UMX-TPS MKS data plate). bracket

36 178 77

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 29

3.2.3. GES Mounting Option

Floor Box Compatibility Tables Compatible Service Outlets (Rectangular) Compatible Lightware mounting bracket: FP-UMX-TPS GES4 Kit Compatible Service Outlets (Rectangular) Product family Type Part number Sample picture Compatible Service Outlets (Rectangular) GES9-3B U 7011 7405 07 7 Compatible Lightware mounting bracket: FP-UMX-TPS GES4 Kit GES9-3B U 9011 7405 07 9 Product family Type Part number Sample picture GES9-3B U 1019 7405 08 1 GES4 U 7011 7405 19 6 OBO Bettermann GES9-3S U 7011 7405 08 3 GES4 U 9011 7405 20 0 GES9, rectangular GES9-3S U 9011 7405 08 5 GES4 U 1019 7405 20 4 OBO Bettermann GES9-3S U 1019 7405 08 7 GES4-2U10T 7011 7405 14 5 GES4, rectangular GES9M-2 10U 7405 37 1 GES4-2U10T 9011 7405 14 6 GES4-2U10T 1019 7405 14 7 INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an UT4 module. GES4M-2 10U 7405 19 1 Compatible Service Outlets (Round) GES6 U 7011 7405 30 8 Compatible Service Outlets (Round) GES6 U 9011 7405 31 2 Compatible Lightware mounting bracket: FP-UMX-TPS GES4 Kit GES6 U 1019 7405 31 6 Product family Type Part number Sample picture OBO Bettermann GES6-2U10T 7011 7405 32 1 GES6, rectangular GESR4 U 7011 7405 43 6 GES6-2U10T 9011 7405 32 2 OBO Bettermann GES6-2U10T 1019 7405 32 3 GESR4 U 9011 7405 44 0 GESR4, round GES6M-2 10U 7405 29 9 GESR4 U 1019 7405 44 4 INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an UT3 module. GESR7 10U 7011 7405 45 2

GESR7 10U 9011 7405 45 6 OBO Bettermann GESR7, round GESR7 10U 1019 7405 46 0

GESRA7 10U 7405 54 4

INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an UT3 module.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 30

Compatible Device Installation Units (Floor Boxes) Compatible Service Outlets (Rectangular) Compatible Lightware mounting bracket: FP-UMX-TPS GES9 Kit Compatible Lightware mounting bracket: FP-UMX-TPS GES4 Kit

Product family Type Part number Sample picture Product family Type Part number Sample picture

GESR9 U 7011 7405 52 8 UDHOME4 2V MT U 7427 24 8 GESR9 U 9011 7405 53 2 OBO Bettermann UDHOME4 GESR9 U 1019 7405 53 6 UDHOME4 2M MT U 7427 25 2 GESR9-2U12T 7011 7405 46 5

GESR9-2U12T 9011 7405 46 6 INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an MT3 OBO Bettermann module. GESR9, round GESR9-2U12T 1019 7405 46 7 Compatible Lightware mounting bracket: FP-UMX-TPS GES9 Kit GESR9 SR U 7011 7405 51 2 Product family Type Part number Sample picture GESR9 SR U 9011 7405 51 6

GESR9 SR U 1019 7405 52 0 UDHOME9 2V GB V 7427 30 0 OBO Bettermann GESRA9 10U 7405 58 0 UDHOME9

INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an UT4 UDHOME9 2M GB V 7427 30 4 module.

INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an GB3 module.

Compatible Lightware mounting bracket: OBO Bettermann UDHOME9 Product family Type Part number Sample picture

UDHOME9 2V MT V 7427 30 8 OBO Bettermann UDHOME9 UDHOME9 2M MT V 7427 31 2

INFO: The transmitter unit assembled with the supplied brackets can be mounted to the place of an MT4 module.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 31

Mounting Steps - FP-UMX-TPS GES4 / GES9 Kits Step 2. Place the transmitter to the brackets. The FP-UMX-TPS GES4 / GES9 kits can be ordered separately, please contact [email protected]. Dimensions of the Brackets The following drawing and table represents the dimensions of the Lightware brackets assembled with the transmitter unit. The two types of GES bracket pairs have different dimensions. The values are in mm.

Parameter LW GES-4 LW GES-9 L H 53.4 53.4 L 174.1 216.1 GES-4 / GES-9 bracket pair W 76 76 FP-UMX-TPS-TX100 series transmitter H

W Step 3. Fasten the all four M3x6 PH fixing screws to fix the device to the brackets.

Mounting Steps

Step 1. Place the two half of the brackets of GES4 / GES9 to the floor box. Hook up the upper ears of the brackets to the top mounting slot.

GES4/GES7 GES9

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 32

3.3. Mounting Options - Wall Plates Mounting Steps - WP-UMX-TPS-TX100 series The transmitter can be easily mounted into an industrial standard switch/outlet box (B225R): Switch / Outlet Box Compatibility Table INFO: The switch/outlet box is not supplied with the mounting kit but it can be purchased separately. Compatible Lightware Devices: Please contact [email protected] for the details. Model Color of the front panel

WP-UMX-TPS-TX120-US Black Black B225R outlet box WP-UMX-TPS-TX130-US Black Black Fixing screw WP-UMX-TPS-TX130-Plus-US Black Black 109.2 WP-UMX-TPS-TX120-US White White WP-UMX-TPS-TX130-US White White WP-UMX-TPS-TX130-Plus-US White White

Type Part number Picture Front side of the 70.6 100.6 extender

Step 1. Insert the extender into the B225R outlet box and position it to get the holes aligned.

B225R outlet box Carlon B225R-UPC 7TAA040070R0000

Step 2. Fasten the front side of the extender to the B225R outlet box by fitting all the screws.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 33

3.4. Electrical Connections 3.4.5. DisplayPort Connector 3.4.1. Locking 12V DC Connection UMX-TPS-TX140, UMX-TPS-TX140-Plus, UMX-TPS-TX140K, WP-UMX-TPS-TX130-US, and WP-UMX-TPS-TX130-Plus-US models provide standard 20-pole DisplayPort connector for input. Always use high quality DP cable for connecting DisplayPort devices. 3.4.6. DVI-I Connector UMX-TPS-TX130, UMX-TPS-TX140, UMX-TPS-TX140K and UMX-TPS-TX140-Plus transmitters provide a standard 29-pole DVI-I connector for input where digital and analog pins are connected internally. Hence users can use the connector receiving DVI-A (analog video) and DVI-D signals (digital video and digital audio) as well. Locking DC connector ATTENTION! Only one (DVI-A or DVI-D) mode is available at a time. You can use the Video Select button to choose the input source. UMX-TPS-TX100 series transmitters are built with locking 12V DC connector. Do not forget to turn the plug clockwise direction before disconnecting the power adaptor. #power Always use high quality DVI cable for connecting DVI devices. WARNING! Always use the supplied 12V power adaptor. Warranty void if damage occurs due to use of a The following drawing and table show the pinout of DVI-I connector and the position of analog and digital different power source. signal pins. 3.4.2. 48V DC Connection FP/WP-UMX-TPS-TX100 series transmitters are built with 2-pole Phoenix connector for 48V DC 1A power connection.

Pin nr. Signal 1 + Pin Signal Pin Signal 2 - 1 TMDS Data2- 16 Plug Detect 2 TMDS Data2+ 17 TMDS Data0- 2-pole Phoenix connector and plug pin assignments 3 TMDS Data2 Shield 18 TMDS Data0+ 3.4.3. VGA Connector 4 not connected 19 TMDS Data0 Shield The transmitter provides a standard 15-pole D-SUB female connector for connecting 5 not connected 20 not connected VGA devices. Always use high-quality VGA cable for connecting sources and 6 DDC Clock 21 not connected displays; using a VGA cable where all the pins are wired (including the DDC channel's wires) is highly recommended. 7 DDC Data 22 TMDS Clock Shield 8 Analog Vertical Sync 23 TMDS Clock+ 3.4.4. HDMI Connector 9 TMDS Data1- 24 TMDS Clock- The extender provides standard 19-pole HDMI connector for input. Always use high quality 10 TMDS Data1+ C1 Analog Red HDMI cable for connecting sources and displays. 11 TMDS Data1 Shield C2 Analog Green 12 not connected C3 Analog Blue 13 not connected C4 Analog Horizontal Sync 14 +5V Power C5 GND 15 GND (for +5V)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 34

3.4.7. Analog Stereo Audio (Jack) RJ45 LED States

The connector is used for receiving unbalanced analog audio signal. It is also known as (3.5 mm Ethernet port or approx. 1/8”) audio jack, phone jack, phone plug and mini-jack plug. LED1, amber LED2, green Pin nr. Signal OFF no link 10 Mbps 1 Left 2 Right Blinking activity N/A 3 Ground ON link is active 100 Mbps Jack audio plug pin assignments Wiring of TPS and LAN Cables You can find more information about audio functions in theAudio Interface section. Lightware recommends the termination of LAN cables on the basis of TIA/EIA T 568 A or TIA/EIA T 568 B 3.4.8. Analog Stereo Audio (Phoenix) standards. 5-pole Phoenix connector is used for balanced analog audio input in the UMX-TPS- TX140 and UMX-TPS-TX140-Plus transmitters. Unbalanced audio signals can be connected as well. See more details about the balanced and unbalanced input port wiring in the Cable Wiring Guide section.

Pin nr. Signal Pin TIA/EIA T568A Wire color TIA/EIA T568B Wire color 1 Left+ 1 white/green white/orange 2 Left- 3 Ground 2 green orange 4 Right- 3 white/orange white/green 5 Right+ 4 blue blue Analog audio connector and plug pin assignments 5 white/blue white/blue 6 orange green Compatible Plug Type Phoenix® Combicon series (3.5mm pitch, 5-pole), type: MC 1.5/5-ST-3.5. 7 white/brown white/brown You can find more information about analog audio function in theAudio Interface section. 8 brown brown

3.4.9. Ethernet Connector (TPS and LAN Ports) Pin assignments of RJ45 connector types The extender provides standard RJ45 connectors for TPS IN and LAN ports. Always use high quality Ethernet Maximum CATx cable distances can be found in the Maximum Extension Distances section. You can find cable for connecting transmitters and receivers. more information about TPS interface in the TPS Interface section.

Ethernet TPS connector of UMX-TPS- TPS connector of FP/WP-UMX- connector TX100 series transmitters TPS-TX100 series transmitters

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 35

3.4.10. RS-232 Connector 3.4.13. GPIO - General Purpose Input/Output Ports The extender contains a 3-pole Phoenix connector which is used for RS-232 serial connection. DIFFERENCE: Only the UMX-TPS-TX130, UMX-TPS-TX140 and UMX-TPS-TX140-Plus models contain GPIO port. Pin nr. Signal The GPIO port contains seven GPIO pins, which operate at TTL digital signal levels and can be set to high or low 1 Ground level (Push-Pull). The direction of the pins can be input or output (adjustable). Voltage ranges for GPIO inputs 2 TX data are the following: 3 RX data Input voltage [V] Output voltage [V] Max. current [mA] RS-232 connector pin assignments Logical low level 0 - 0.8 0 - 0.5V 30 Compatible Plug Type Logical high level 2 - 5 4.5 - 5V 18

Phoenix® Combicon series (3.5mm pitch, 3-pole), type: MC 1.5/3-ST-3.5. INFO: The maximum total current for the seven GPIO pins is 180 mA. You can find more information about RS-232 interface in theSerial Interface section. Pin nr. Level and direction 3.4.11. IR Connector 1 IR detector and IR emitter can be connected to the UMX-TPS-TX100 series extenders with TRS (Tip, 2 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. The pin assignments are the following for the detector and 3 the emitter: 4 5 6 Configurable 7 Detector – 3-pole-TRS Emitter – 2-pole-TS Ground 1 Tip Signal (active low) 1 Tip +5V GPIO connector and plug pin assignments 2 Ring GND 2 Ring Signal (active low) 3 Sleeve +5V 3 Sleeve Compatible plug type Phoenix® Combicon series (3.5mm pitch 8-pole), type: MC 1.5/8-ST-3.5. INFO: Ring pole of the emitter is optional. If your IR emitter has three-pole TRS plug, then the Ring and the Sleeve are the same signal (Output - ). You can find more information about GPIO interface in theGPIO Interface section. You can find more information about Infrared interface in theIR Interface section. 3.4.14. USB Port 3.4.12. IR Detector DIFFERENCE: Only the UMX-TPS-TX140K model is supplied with USB port. FP/WP-UMX-TPS-TX100 series transmitters are built with an IR detector on front panel of the wall plate. The The USB port allow USB extension and control the transmitter. The UMX-TPS-TX140K are sensor is used for receiving IR signals from remote control or other IR emitter devices. assembled with mini-B type port (connecting a computer). For more information about the USB extension see the USB Interface (KVM Function)section. You can find more information about Infrared interface in theIR Interface section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 36

3.5. Connecting Steps 3.5.2. UMX-TPS-TX100 series 3.5.1. FP/WP-UMX-TPS-TX100 series

CATx Connect the transmitter and a compatible receiver or the matrix input board by a CATx cable via the TPS connectors. DVI DP Connect the transmitter and the sources using the inputs and VGA / DVI-I / HDMI / DisplayPort HDMI cables. VGA

Audio Optionally connect an asymmetric audio device with unbalanced audio signal (e.g. a VGA laptop) CATx Connect the transmitter and a compatible receiver or the matrix input board by a CATx cable via the to the 2.5" TRS (jack) audio input port. TPS connectors. Audio Optionally connect a symmetric audio device with balanced audio signal (e.g. a media player) to VGA Connect the transmitter and the sources using the inputs and VGA / DVI-I / HDMI / DisplayPort the 5-pole Phoenix audio input port. See the wiring guide for the connector in the Cable Wiring HDMI cables. Guide section. DP USB Only for UMX-TPS-TX140K: Optionally for USB HID extension: connect the transmitter to the Audio Optionally connect an asymmetric audio device with unbalanced audio signal (e.g. a VGA laptop) computer by the USB-B cable and connect USB HID device(s) to the compatible receiver. to the 2.5" TRS (jack) audio input port. IR Optionally for Infrared control: LAN Optionally connect the transmitter to a LAN network in order to control the device. - Connect the IR emitter to the IR OUT port of the device. - Connect the IR detector to the IR IN port of the device. RS-232 Optionally connect a controller/controlled device (e.g. relay box) to the RS-232 port. LAN Optionally connect the transmitter to a LAN network in order to control the device. Power See powering options in the next section. RS-232 Optionally for RS-232 control: connect an external device (e.g. touch panel) to the RS-232 port. GPIO Optionally connect a controller/controlled device (e.g. relay box) to the GPIO port. Power See powering options in the next section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

3. Installation UMX-TPS-TX100 series – User's Manual 37

3.6. Powering Options

A B C

A Using local PSU - connect the power adaptor to the DC input on the transmitter first, then to the AC power socket.

B Using PoE with connecting a transmitter: connect the TPS OUT (PoE) port of the transmitter to the TPS+PoE port of the TPS-PI-1P1 power injector by a CATx cable, and connect the TPS input port of the compatible receiver to the TPS port of the TPS-PI-1P1 by a CATx cable.

C Using PoE with connecting a matrix or an input board: connect the TPS OUT (PoE) port of the transmitter to the PoE-compatible TPS input port of the matrix or input board by a CATx cable.

ATTENTION! In case of connecting the transmitter to an input board of the matrix always connect an external PSU to the board. For the detailed information please read the user's manual of the matrix. ATTENTION! The Ethernet port does not support PoE. Only the TPS port support PoE function.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 38

Device Concept 4The following chapter describes the features of the device with a few real-life examples.

ç TPS Extender Concept ç TPS Interface ç Port Diagrams ç Video Interface ç The Autoselect Feature ç Audio Interface ç Serial Interface ç Ethernet Interface ç Basic IT Security ç Batch Commands ç IR Interface ç GPIO Interface ç The Event Manager Feature ç USB Interface (KVM Function) ç Consumer Electronics Control (CEC) Feature ç Further Built-in Features ç Software Control Modes

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 39

4.1. TPS Extender Concept 4.2. TPS Interface The UMX-TPS-TX100 series transmitters and wall plates are universal audio/video extenders with analog/ The device is built with TPS (Twisted Pair Single) interface which are using HDBaseTTM technology. It means digital conversion and audio embedding functions. The devices receive analog (VGA, DVI-A) and digital (DP, the unit transmits video, audio, Ethernet, RS-232, and Infrared signals via a single CATx cable. HDMI, DVI-D) video signals and transmits HDBaseT (TPS) signal including HDMI/DVI audio/video signals, Ethernet, RS-232, and Infrared signals. Analog audio signals can be received via the 3.5” TRS (jack) and the TPS Interface Working Modes 5-pole Phoenix connectors. The device can be controlled via Ethernet, RS-232 or Infrared and is able to The TPS working mode between the transmitter and the receiver is determined by the mode set in them. control third-party devices via the RS-232, Ethernet, Infrared interfaces. Both devices TPS mode settings together determine the finally established TPS transmission mode. The following TPS modes are defined in the transmitter: ▪ Auto: The TPS mode is determined automatically. ▪ HDBaseT: Ideal for high resolution signals up to 4K. ▪ Long reach: Ideal for big distances up to 1080p@60Hz with extended cable lengths. ▪ LPPF1*: Only RS-232 communication is transmitted (@ 9600 baud). ▪ LPPF2*: Only RS-232 (@ 9600 baud) and Ethernet communication are transmitted. * LPPF: Low Power Partial Functionality.

Selected mode on RX side LPPF1 LPPF2 HDBaseT Long reach Auto LPPF1 LPPF1 LPPF1 LPPF1 LPPF1 LPPF1 LPPF2 LPPF1 LPPF2 LPPF2 LPPF2 LPPF2

The summary of the interfaces of UMX-TPS-TX100 series transmitters HDBaseT LPPF1 LPPF2 HDBaseT Long reach HDBaseT Long reach LPPF1 LPPF2 Long reach Long reach Long reach on TX side

Selected mode Auto LPPF1 LPPF2 HDBaseT Long reach HDBaseT **

** If there is valid HDMI/DVI signal is on the TX side, the TPS mode will be HDBaseT on both side. If the transmitter does not transmits HDMI/DVI signal, the TPS mode will be changed to LPPF2 or LPPF1 automatically. Long reach mode is not available when both sides are set to Auto mode. When using automatic operation mode selection, the device determines the mode of operation. If both halves are set to Auto mode, the source side is the initiator. It will negotiate each state transition with its sink side partner. When one of the devices is configured to manual operation mode selection, the other device may be placed in automatic mode. In this case, the mode transition negotiation is initiated by the host-managed device and the auto-mode device follows through. The allowed cable lengths and resolutions are listed in the Maximum Extension Distances section. The summary of the interfaces of WP- and FP -UMX-TPS-TX100 series transmitters 1 Only for UMX-TPS-TX140, UMX-TPS-TX140K and UMX-TPS-TX140-Plus models. 2 Only for UMX-TPS-TX130, UMX-TPS-TX140, UMX-TPS-TX140K and UMX-TPS-TX140-Plus models. 3 Only for WP-UMX-TPS-TX130-US, WP-UMX-TPS-TX130-Plus-US, and FP-UMX-TPS-TX130 models. 4 Only for UMX-TPS-TX140K model.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 40

4.3. Port Diagrams 4.3.2. Wall Plate / Floor Plate Extenders 4.3.1. Standalone Extenders The following figure describes the port diagram of the WP-UMX-TPS-TX130-US transmitter. The principle of the operation is the same for the following models. The following figure describes the port diagram of the UMX-TPS-TX140 transmitter. The principle of the operation is the same for the following models. ▪ WP-UMX-TPS-TX120-US series ▪ WP-UMX-TPS-TX130-US series ▪ UMX-TPS-TX120, -TX130, -TX140 ▪ WP-UMX-TPS-TX130-Plus-US series ▪ UMX-TPS-TX140-Plus ▪ FP-UMX-TPS-TX120 ▪ UMX-TPS-TX140K ▪ FP-UMX-TPS-TX130

Port diagram of the WP-UMX-TPS-TX130-US transmitter

The device has three video input ports to receive analog video (VGA) and digital video (HDMI, DP) signals. The analog signal is converted to digital. A 3:1 digital audio/video switch decides which signal is routed toward the TPS output port. The device also has an analog audio input port (3.5mm Jack). The analog signals are converted to digital ones. The user can choose which audio signal is transmitted on the TPS output port: the analog audio source or the original embedded audio from the HDMI / DP ports.

Port diagram of the UMX-TPS-TX140 transmitter Besides, the device has four different interfaces to control the unit itself or third-party devices: infrared (input), RS-232, and Ethernet. The device has four video input ports to receive analog video (VGA, DVI-A) and digital video (HDMI, DP, DVI-D) signals. The analog signals are converted to digital. A 5:1 digital audio/video switch decides which signal is routed toward the TPS output port. The device also has two analog audio input ports (3.5mm Jack, 5-pole Phoenix). The analog signals are converted to digital ones. The user can choose which audio signal is transmitted on the TPS output port: one from the analog audio sources or the original embedded audio from the HDMI / DP / DVI-D ports. INFO: The DVI-D input accepts HDMI signal with embedded audio as well. Besides, the device has four different interfaces to control the unit itself or third-party devices: infrared (input and output), RS-232, Ethernet, and GPIO.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 41

4.4. Video Interface Automatic Input Selection - Example 4.4.1. Video Input Modes The device can receive digital video signal on the HDMI, DisplayPort, and DVI-D input ports and analog video signal on the VGA and the DVI-A input ports. INFO: Both the DVI-A and DVI-D signals can be received on the same DVI-I input port. 4.4.2. Input Source Selection Modes Video input source can be selected the following ways: ▪ pressing Video Select button on the device; ▪ using Lightware Device Controller (LDC); ▪ sending LW2 or LW3 protocol commands; or The Concept ▪ using the Autoselect function. If there is no other source connected to the transmitter, but the Laptop, VGA input will be automatically switched to the TPS output. If the Laptop and the PC are also connected to the transmitter, DVI-D input will 4.5. The Autoselect Feature be switched to the TPS output. If the Blu-ray player is connected on the HDMI input, and later the MacBook N There are three types of Autoselect as follows. New event? is connected on the DP input of the transmitter, it will be switched to the TPS output – independently of the Y presence of other video signals. ▪ First detect mode: selected input port is kept Settings connected to the output as long as it has an „First detect” Current „Last detect” ▪ TPS output: Set the Autoselect to Enabled. Set Autoselect mode to Priority detect. The priorities are the active signal. Autoselect mode Last connected following (the lowest number means the highest priority): ▪ Priority detect mode: always the highest Selected input is selected „Priority detect” priority active input is selected to transmit. port still has a N valid signal? Source device Input interface Input port Priority Port with ▪ Last detect mode: always the last attached Port with priority priority 0 has a Y MacBook DP IN I3 0 Y 0 is selected input is selected to transmit. valid signal? Remains Blu-ray player HDMI IN I2 1 selected N PC DVI-D IN I4 2 Port with Laptop VGA IN I1 3 Y Port with priority priority 1 has a 1 is selected valid signal? Priorities can be set in Lightware Device Controller software, see related settings in the TPS Video Output N and the TPS Audio Output sections.

Port with Port with priority priority 2 has a Y 2 is selected valid signal?

N

Port with Port with priority priority 30 has a Y 30 is selected valid signal?

N

Test Display „No signal” „Off” pattern generator No Audio/Video Test pattern setting transmission

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 42

4.6. Audio Interface 4.6.2. Audio Options - Example 4.6.1. Audio Input Modes The Concept The device can receive embedded digital audio signal on the HDMI, DisplayPort, and DVI-D input ports and analog audio signal on the Jack and the Phoenix input ports. Audio Embedding The transmitter has a built-in audio embedder function which means the audio signal being received on the analog audio input port can be embedded to the TPS output. The video and audio inputs can be combined with limitations. Below table contains the allowed connections:

Audio sources Analog audio Analog audio HDMI DP DVI-D (Jack) (Phoenix) HDMI  - -   DP -  -   DVI-D - -    VGA - - -   Three audio sources are connected to the transmitter: a Blu-ray player on the HDMI input (embedded HDMI audio); a Laptop on the analog audio input 1; and a Media player on the analog audio input 2. There are two Video sources DVI-A - - -   video sources as well: the Blu-ray player on the HDMI input (digital video with the embedded audio) and the Allowed audio connections Laptop on the VGA input (analog video). The following options are available for audio routing / signal selection: ATTENTION! Audio embedding is available where the pixel clocking of the video signal is up to 225 MHz. If the output video is 4K, the audio embedding function is not available. ▪ If the video input source of the HDTV is the Blu-ray player, you can select from the following audio sources: – the original embedded HDMI audio from the Blu-ray player; – the analog audio input 1 from the Laptop; – the analog audio input 2 from the Media player. ▪ If the video input source of the HDTV is the Laptop, you can select from the following audio sources: – the analog audio input 1 from the Laptop; – the analog audio input 2 from the Media player.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 43

4.7. Serial Interface Control Mode 4.7.1. Technical Background The incoming data from the given port is processed and interpreted by the CPU. The mode allows to control the transmitter directly. LW2 or LW3 protocol commands are accepted – depending on the current port Serial data communication can be established via the local RS-232 port (Phoenix connector) or via the TPS setting. lines. The RS-232 ports – which are connected to the CPU – can be configured separately (e.g. if the Baud rates are different, the CPU does the conversion automatically between the ports). The RS-232 port can be Command Injection Mode switched to Pass-through mode, Control mode, or Command Injection mode; see the figure below. In this mode, the transmitter works as an RS-232 bidirectional converter. The TPS signal is converted to RS-232 data and vice versa. TCP/IP port numbers are defined for the serial ports (TPS and local) for this purpose. E.g. the default Command Injection port number of the local RS-232 port is 8001. If a command is coming from the TPS interface which addresses to the port no. 8001, it will be transmitted to the Tx pin of the local RS-232 port. That works in the opposite direction of course and the method is the same on the serial interface of the TPS port as well. 4.7.2. RS-232 Signal Transmission – Example The Concept The System controller can send commands to the transmitter and it is able to remote control the projector through the TPS receiver via RS-232.

Block diagram of the serial interface

The following settings are defined: Settings 1 The Local and the TPS serial ports are in Control mode. ▪ System controller: wireless IP connection to the same Ethernet as the transmitter is connected to. Use a dedicated software tool (e.g. a terminal) which is suitable for sending commands via TCP/IP to a The Local and the TPS serial ports are in Pass-through mode. 2 certain IP:port address. 3 The Local and the TPS serial ports are in Command Injection mode. ▪ Transmitter: set the RS-232 mode to Command Injection on TPS output port. Set the further parameters (Baud rate, Data bits, etc.) in accordance with the specifications of the projector. The transmitter will INFO: All settings are available in the LDC software, see settings in the RS-232 Tab section. transmit the RS-232 data toward the receiver. Only one mode can be used at the same time: Control mode, or Pass-through mode, or Command Injection ▪ Receiver: set the RS-232 mode to Pass-through on RS-232 port. mode. If you choose one of them, TPS serial link and local RS-232 port will operate in the same mode. ▪ Projector: note the RS-232 port setting that is specified by the Manufacturer. Connect a suitable serial cable with the proper wiring. Pass-through Mode In pass-through mode, the given device forwards the data that is coming from one of its ports to another same type of port. The command is not processed by the CPU. Incoming serial data is forwarded from local RS-232 port to the TPS output port and vice versa inside the transmitter.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 44

4.7.3. RS-232 Recognizer 4.8. Ethernet Interface RS-232 Recognizer Example The device can be controlled over the Ethernet port. This interface supports both LW2 and LW3 protocols. When the UMX-TPS-TX140-Plus has an active video signal, the transmitter login the VC codec automatically. 4.8.1. Device Control over Ethernet The interface can be also used to remote control a third-party device and establish the connection to Lightware Device Updater software and perform firmware update.

Third-party Device Control via Local Ethernet (Example)

Process Settings When signal presents on any HDMI input, the This condition and the action is set in Event manager. extender sends a message: 'ping'.  The serial communication is scanned continuously by the Video codec sends a message: 'Login name:'. The following ways are available for device control: recognizer in the extender and gets the 'Login name' string.  ▪ The system controller can communicate with the transmitter via Ethernet using LW2/LW3 protocol When 'Login name:' is detected in the string, the This condition and the action is set in Event manager. commands. extender sends a message: 'Admin'. ▪ The system controller can communicate with the projector by its IP:port address.  The serial communication is scanned continuously by ▪ The transmitter can send commands (e.g. as an action by the Event Manager) to the IP:port address Video codec sends a message: 'Password:'. the recognizer in the extender and gets the 'Password' of the projector by using LW3 protocol commands. See Event Manager usage in the Event Manager  string. section, and find the related LW3 protocol commands in theEthernet Message Sending section. When 'Password:' is detected in the string, the This condition and the action is set in Event manager. extender sends a message: 'Admin'. 4.8.2. Wake-on-Lan  DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- Login is established, Video codec is ready to use. UMX-TPS series). The well-known wake-on-lan feature (sending magic Packet to the target PC) is available. This can be used First, configure the recognizer for the serial communication, after that, set the events in the Event Manager (for to power on a computer automatically: just send a simple LW3 command, see the Powering on a Computer more details see the Event Manager section). The RS-232 recognizer settings has to be done with Lightware over Ethernet (Wake-on-LAN) section. Device Controller Software (see the Message Recognizer section) or with LW3 protocol commands (see the RS-232 Message Recognizer section). INFO: Please make sure the feature is enabled in the target PC and it is powered (but switched off). Settings in the Event manager ▪ E1. When the signal is present on O1 port of the UMX-TPS-TX140-Plus, it sends a message 'PING' on P1 port of RS-232 to the VC codec. For more details see Message Sending via RS-232 Serial Port section. ▪ E2. Set a condition where 'Login name:' is the recognized RS-232 message. Action is sending serial message ('Admin') on the P1 port to the VC codec. ▪ E3. Set a condition where 'Password:' is the recognized RS-232 message. Action is sending serial message ('Admin') on the P1 port to the VC codec.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 45

4.8.3. TCP Recognizer The IP Port Block feature is an additional protection for the Cleartext login. There are TCP/IP ports in Lightware devices which are not protected by the login, so you can disable them if necessary. Example: due DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package to the working method of the LW2 communication, the Cleartext login does not provide protection when LW2 v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- command is sent to the device, that is why the TCP port no.10001 shall be blocked manually. UMX-TPS series). Another level of security is the MAC Filtering tool. You can create an ’allowlist’ of network devices based on The feature is almost the same as in case of the RS-232 but for the network interface: the incoming TCP the MAC address which are allowed: messages can be processed which may trigger actions. The combination of the TCP recognizer and the Event Manager gives numerous opportunities for creating automatic room solutions. #tcprecognizer ▪ Controlling the device (Send option), or Querying parameters (Receive option) to/from the Lightware device. TCP Recognizer Example ▪ Below table shows the protection levels of these features. When the Projector switches off, the button light (1) of the TBP6-EU button panel is turned off automatically. IP Port Function MAC Filter Cleartext Login IP Port Block 80 HTTP Post&Get  -  81 LW3 control (miniweb)   - 6107 LW3 protocol   - 800x Command injection (RS-232)  -  When the power-off process is started in the projector, it will send a message over Ethernet. That message 900x Command injection (IR)  -  will be recognized by the Switcher and will be used as a Condition in Event Manager. 10001 LW2 protocol  -  How to setup the transmitter? Step 1. Configure the recognizer for the communication by the LDC, see the TCP Recognizer section, or by ATTENTION! Be careful when combining these functions; improper settings may cause malfunction. LW3 protocol commands (see the TCP Message Recognizer section). Define the desired device as a TCP client. (The Projector is saved as 'C1' in this example.) Most of these features are available in LDC, see the Settings Menu section. Step 2. Create the following event in the Event manager: 4.10. Batch Commands E1. When the (PWR!001 "On") message is recognized from the C1 client, the GPIO pin 1 is set to low level. DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package For more information about setting the events in LDC, see the Event Manager section. v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). 4.9. Basic IT Security These features can be used to process a group of pre-defined commands. The commands can be stored DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package in the device as macros or you can save the commands in a plain text file and send the device by an HTTP v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- message. UMX-TPS series). LW3 over HTTP (Command Salvo) These entry-level network security improvements help to prevent unauthorized access to the Lightware This feature allows the LW device to be controlled over HTTP. In this case, a batch of commands is sent device: #new over HTTP to the Lightware device for processing. Save the LW3 commands into a file, post it to the ▪ Cleartext login /protocol.lw3 file and the commands are processed immediately. #http IP Port Block ▪ Running Macros ▪ MAC Filtering In this case, the command sequences (macros) are stored in the device. You can create your custom macros The Cleartext Login tool allows setting a password for login, thus, the device will not accept any command in a file, upload into the device and run at any time. The number of the macros depends on the device type, coming from an interface (RS-232, Ethernet, etc…), only the device type and the serial number can be queried at most 50 macros can be saved in a UMX-TPS transmitter. See more information about the feature in the without login. You can set all affected TCP/IP ports individually to enable or disable. Macros section. #macro

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 46

4.11. IR Interface IR Signal Transmission - Example 1 ATTENTION! For the complete usage attach an IR emitter unit to the IR OUT and an IR detector unit to the IR IN connectors. 4.11.1. Technical Background The Infrared signal transmission is similar to the serial data communication. The transmitter contains dedicated IR I/O connection and also can transmit/receive IR signal via the TPS interface. The signal is in pronto HEX format in both cases.

The Concept An IR detector is attached to the Infrared input port of the TPS receiver and IR signals are sent by the Remote controller. The TPS Receiver is connected to an UMX-TPS-TX100 series transmitter built with IR output port via TPS line. Settings: Set the TPS IR link of the Transmitter to Transparent mode. IR signals are received over the local IR input port of the Receiver by the Remote controller. The signals transmitted further over the TPS line to the Transmitter which can control the Blu-ray player via an IR emitter.

IR Signal Transmission - Example 2

Block diagram of the IR interface - UMX-TPS-TX100 series transmitters

The Concept The built-in IR detector of the Wallplate transmitter receives the IR signals from the Remote controller. The signal is transmitted via the TPS line to the TPS receiver. In this way the Remote controller can control the Projector via the Wallplate transmitter.

Block diagram of the IR interface - WP/FP-UMX-TPS-TX100 series transmitters The most trivial usage of the IR interface is the transparent mode: signal received or sent on local IR ports are transmitted directly on the TPS IR link port and vice versa. Beside of this there is an IR recognizer in the device where you can assign actions in Event Manager for. The third option is the command injection mode (like at serial interface in the previous section) where you can send IR commands over LAN. Command injection mode can be turned on and off by input/output ports. INFO: All settings are available in the LDC software, see settings in the Infra Tab section. INFO: The modulation of output IR signal can be turned off or on by LW3 command, see details in the Enable/Disable Output Signal Modulation section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 47

4.11.2. Advanced IR functionality Settings of the Transmitter DIFFERENCE: UMX-TPS-TX140-Plus, UMX-TPS-TX140K and WP-UMX-TPS-TX130-Plus-US can send ▪ For Relay 1: create an event in Event manager: when signal is present on Input 1 (I1) then set GPIO pins Little-endian pronto hex IR codes on its IR output port. to low level for Relay 1 opening. Also create another event when signal is not present on Input 1 (I1) It is possible in the following ways: then set GPIO pins to high level for Relay 1 closing. ▪ For Relay 2: create an event in Event manager when signal is present on Input 1 (I1) then set GPIO pins ▪ With Lightware Device Controller software (for more details see Sending pronto hex codes (Little-endian to high level for Relay 2 closing. Also create another event when signal is not present on Input 1 (I1) format) section) then set GPIO pins to low level for Relay 2 opening. ▪ With Event Manager (for more details see Sending pronto hex codes (Little-endian format) and Event Manager section) When the PC starts to play the video presentation, the signal is received over the VGA input so GPIO pins ▪ With LW3 protocol command (for more information see Sending Pronto Hex Codes in Little-endian send signal to Relay 1 to open which results turning off the lights. Furthermore GPIO pins also send signal to Relay 2 to close and the projection screen is rolled down. When the presentation is ended, signal ceases Format via IR Port) on the VGA input, so GPIO pins send signal to Relay 1 to close which results turning on the lights and sends Sending Bigger-endian pronto hex code is also available, see Sending Pronto Hex Codes in Big-endian signal to Relay 2 to open so projection screen returns to its enclosure. Format via IR Port. ATTENTION! Please always check the electrical parameters of the devices what you want to control. The 4.12. GPIO Interface maximum current of one GPIO pin is 30 mA, the maximum total current for the seven pins is 180 mA. 4.12.1. Description See the LDC settings for GPIO port in the GPIO Tab section. See also the details about the Event Manager settings in the Event Manager section. The GPIO (General Purpose Input/Output) port is a multi functional input/output interface to control the transmitter or third-party devices and peripherals. You can establish connection between the controller/ 4.13. The Event Manager Feature controllable device and the transmitter by the 8-pole Phoenix connector. Seven pin's direction is configurable The Event Manager feature means that the device can sense changes on its ports and is able to react independently based on needs of the application. according to the pre-defined settings. Lightware Device Controller contains a user-friendly software tool and 4.12.2. GPIO Options - Example allows to create Events by defining a Condition and an Action.

Event Manager example See more information about the settings in the Event Manager section.

The Concept Ceiling lamp is turned off by Relay 1 and projection screen is rolled down by Relay 2 when signal received from the PC over the VGA input. Both relays are controlled by the GPIO port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 48

Event Manager + 4.14. USB Interface (KVM Function) The AND Operator DIFFERENCE: Only the UMX-TPS-TX140K model is supplied with USB port. #usb #usbkvm DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- UMX-TPS-TX140K model supports HID-compliant (Human Interface Device) devices to transmit USB signal UMX-TPS series). between the source and sink devices. The UMX-TPS-TX140K transmitter connects to the controlled device The practical experience has shown that there is a need to examine more conditions (up to four) as follows: (e.g. PC) and the controlling devices (e.g. computer mouse, keyboard, touch panel) are connected to the if one of the set conditions becomes true (while the other conditions are fulfilled), then the set Action is compatible receiver. launched. For example, in a meeting room we have the following situation: ATTENTION! The compatible receiver for the USB KVM extension is HDMI-TPS-RX220AK. ▪ Signal is present on an input port, The device can be controlled over front panel USB mini B-type connector. This interface only supports LW3 ▪ A GPIO pin state becomes ’low’ (by an external device). protocol. The interface can be also used to establish a connection to the LDC software. If the two Conditions are present at the same time, the Action is launched. Just create the two Conditions into ATTENTION! Only HID-compliant devices are supported by the extenders. Non-HID devices (USB sticks, separate Events, then create a third Event, select the two Conditions and define theAction . webcams, etc.) will not be working with the UMX-TPS-TX140K. See the Combine Links section for the settings in LDC. ATTENTION! USB HUB devices are not supported by the UMX-TPS-TX140K transmitter. Event Manager Variables Technical background DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package The same USB data is transmitted on the RX side which is received on the TX side. The content of the v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- transmitted packets are unknown to the Lightware infrastructure so the data is not modified by any means UMX-TPS series). during transmission. A brand new area is opened by implementing the variables. You can create custom variables in number Key Features: or text format which can be used in the Event Manager. The variables can have the following properties/ methods: ▪ Supports all HID-compliant devices. ▪ Numeric (integer) type with min/max value setting, or string-type (determined automatically) ▪ Driver software for all connected USB devices has to be installed on the controlled computer. The ▪ Increment/step the numeric value, connected mouse and keyboard will be detected as a new hardware in the operating system. ▪ Value-dependent case operations, USB KVM Function - Example ▪ Reading and storing the value of an LW3 property into a string or a numeric variable. The defined variables are stored in a non-volatile memory and the value is kept in case of a reboot. The new opportunities allow creating a monitoring/controlling system without connecting an additional control processor. See the Variables section for the settings in LDC. Condition Trigger DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). The Concept This improvement in the Event Manager works as if a condition is detected. When a complex control system The PC is the sink device for the USB KVM function. The HDMI-TPS-RX220AK receiver is connected to the is built, a Condition may trigger numerous Actions. A typical example is when a system is powered on and TPS output of the transmitter via CATx cable. The keyboard and the mice are connected to the receiver at the ’ready-to-use’ state has to be loaded. In this case, there could be many actions which are based on the the end user side. same condition. In order to reduce the number of the commands, you can trigger one ’key’ condition, which could start the whole process. There is no restriction on the USB-HID devices if the driver is installed on the connected computer the USB KVM signal is transmitted to the receiver without any limitation. See the Condition Triggering section for the settings in LDC.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

4. Device Concept UMX-TPS-TX100 series – User's Manual 49

4.15. Consumer Electronics Control (CEC) Feature 4.16. Further Built-in Features DIFFERENCE: This feature is available only in WP-UMX-TPS-TX130-Plus-US, UMX-TPS-TX140-Plus and 4.16.1. Transmitter Cloning – Configuration Backup and Restore UMX-TPS-TX140K models from FW pack v1.3.0b11. Consumer Electronics Control (CEC) is a bi-directional communication, defined in the HDMI standard. This feature is for remote control of the source and sink devices in the A/V system. UMX-TPS-TX140-Plus model is able to send and receive CEC commands, on HDMI IN (I2) port towards the source, on HDMI OUT (O1) port towards the sink. For more information about sending CEC messages, see GPIO Port Configuration section. CEC has a dedicated pin in the HDMI connector. DVI connector does not contain this pin, so the CEC The transmitter (configuration) cloning of a UMX-TPS-TX100 series transmitter or wallplate is asimple transmission brakes when HDMI-DVI connector or adapter is in the signal route. method that eliminates the need to repeatedly configure certain devices to have identical (non-factory) CEC Application Example settings. If the devices are installed in the same type of system multiple times then it is enough to set up only one device to fit the user’s needs and then copy those settings to the others, thus saving time and resources. When active signal is detected on HDMI in, the transmitter sends a CEC message automatically to the HDTV See more information about the settings in the Configuration Cloning (Backup Tab) section. to wake up. Configuration cloning can be also done by LDU2 over Command Line for many devices in one step, see the Restore section. 4.17. Software Control Modes User has more possibilities to control the device besides the front panel buttons. The following list contains the software control modes: ▪ Lightware Device Controller (LDC) - you can connect to the device via our control software using Ethernet or RS-232 interface and control or configure the device as you wish. For the details see the Software Create an event in the event manager: Control - Lightware Device Controller chapter. ▪ Set as a condition, that the signal is present on the output (O1), ▪ LW2 protocol commands: you can configure the device by using the reduced command set ofLW2 ▪ Set as an action then send a CEC command 'Image view on' O1 output port. protocol. For more details see the LW2 Programmer's Reference chapter. See the details about the Event Manager settings in the Event Manager section. ▪ LW3 protocol commands: you can configure the device by using the full-range command set of LW3 protocol. For more details see the LW3 Programmers’ Reference chapter. ATTENTION! The CEC command sending over TPS interface is working only with CEC-transparent TPS receivers. For the details please download our Using CEC in Lightware Devices document on https://lightware.com/support/guides-and-white-papers website.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 50

Software Control - Lightware Device Controller 5The device can be controlled by a computer through the Ethernet and RS-232 ports using Lightware Device Controller (LDC). The software can be installed on a Windows PC or macOS. The application and the User’s manual can be downloaded from www.lightware.com.

ç Install and Update ç Running the LDC ç Connecting to a Device (Device Discovery Window) ç Crosspoint Menu ç Port Properties Windows ç The CEC Tool ç Diagnostic Tools ç EDID Menu ç Control Menu ç Event Manager ç Settings Menu ç Configuration Cloning (Backup Tab) ç The Built-In Miniweb ç Advanced View Window

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 51

5.1. Install and Update Step 2. Set the desired update setting in the Options section. INFO: After the installation, the Windows and the Mac application has the same look and functionality. ▪ If you do not want to check for the updates automatically, uncheck the circle, which contains the green This type of the installer is equal with the Normal install in case of Windows and results in an updateable tick. version with the same attributes. ▪ If you want to postpone the update, a reminder can be set with different delays from the drop down list. ▪ If the proxy settings traverse the update process, set the proper values then click the OK button. Minimum System Requirement Step 3. Click the Download update button to start the updating. RAM: 1 GB The updates can be checked manually by clicking the Check now button. Minimum display resolution: 1600x900 5.2. Running the LDC Installation for Windows OS The common way to start the software is double-click on Run the installer. If the User Account Control drops a pop-up message click . the LDC icon. But the LDC can be run by command line During the installation you will be prompted to select the type of the installation: normal and the snapshot parameters as follows: install: Connecting to a Device with Static IP Address Normal install Snapshot install The LDC is connected to a device with the indicated Available for Windows and macOS Available for Windows static IP address directly; the Device Discovery window The installer can update only this instance Cannot be updated is not displayed. When the port number is not set, the Only one updateable instance can exist for all users More than one different version can be installed for all users default port is used: 10001 (LW2 protocol). For LW3 devices use the 6107 port number. Comparison of installation types Format: LightwareDeviceController -i : ATTENTION! Using the Normal install as the default choice is highly recommended. Example: LightwareDeviceController -i 192.168.0.20:6107 Installation for macOS Connecting to a Device via a Serial Port Mount the DMG file with double clicking on it and drag the LDC icon over the Applications icon to copy the Format: LightwareDeviceController -c : program into the Applications folder. If you want to copy the LDC into another location just drag the icon over the desired folder. Example: LightwareDeviceController -c COM1:57600 ATTENTION! Please check the firewall settings on the macOS device. LDC needs to be added tothe The LDC is connected to a device with the indicated COM port directly; the Device Discovery window is not exceptions of the blocked software for the proper operation. displayed. If no Baud rate is set the application will detect it automatically.

Updating of LDC Adjusting the Zoom Step 1. Run the application. The window can be zoomed to a specific value to fit to the resolution of the desktop (higher/lower). '1' is the The Device Discovery window appears automatically and the program checks the available updates on default value (100%). Lightware’s website and opens the update window if the LDC found updates. Format: LightwareDeviceController -z The current and the update version number can be seen at the top of the window and they are shown in this Example: LightwareDeviceController -z 1.2 window even with the snapshot install. ATTENTION! The last set value is stored and applied when LDC is started without a parameter. The Update window can also be opened by clicking the About icon ? and the Update button.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 52

5.3. Connecting to a Device (Device Discovery Window) 5.3.1. Ethernet Tab The Ethernet tab consists of two lists. All devices list contains all Lightware devices which are available in the Connecting Steps connected network (in the 255.255.0.0 subnet). However, there is no need to browse all the available devices Step 1. Connect the device to a computer via USB, RS-232 or Ethernet. as you can expand the list of Favorite devices with any Lightware device that is connected via Ethernet by any Step 2. Run the controller software; device discovery window appears automatically. There are three tabs for the different type of interfaces: Ethernet, Serial, and USB. of the following ways: Step 3. Select the desired unit and click on the green Connect button (or just double-click on the device). ▪ Mark the desired device with the  symbol in the All Devices list, ▪ Press the Add button and add the device in the appearing window, or ▪ Import the list of favorite devices that was exported previously. Add New Favorite Device Press the Add button; in the appearing window you can enter the IP address. The host name of the desired device can be used instead if it is supported. That allows setting a unique name to identify the device in a network. If the host name is saved in this window and the IP address is changing, the device will be still available and connectible. ATTENTION! The host name connection-feature does not work when the target device is accessed over VPN. See more information about the host name property in the Setting the Host Name section.

Import/Export the List of Favorite Devices The list of favorite devices can be exported/imported by the dedicated buttons (saved as *.JSON file). The list can be imported later (in another computer, too), but please note that the current list will be overwritten by the imported list.

Changing the IP Address  To modify the IP address settings quickly it is not necessary to enter the device's settings/network menu, you can set them by clicking the pencil Device Discovery Window icon beside the IP address. You can see the new settings only in this window. The device needs some seconds to apply the new settings.

Identifying the Device  Clicking on the icon results the blinking of the status LEDs for 10 seconds. The feature helps to find the device itself physically.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 53

Highlighting the Device 5.3.4. Further Tools DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- The Tools menu contains the following options: UMX-TPS series). ▪ Log Viewer: The tool can be used for reviewing log files which have been saved previously. The opposite feature is also available to help finding the desired device. Press the Show Me button for 5 ▪ Create EDID: This tool opens the Easy EDID Creator wizard which can be used for creating unique EDIDs seconds until the front panel LEDs start to blink slowly. In parallel, the device is highlighted in green for 4 seconds in a few simple steps. Functionality is the same as the Easy EDID Creator. in the Device discovery window of the LDC. #highlightme ▪ Demo Mode: This is a virtual MX-FR17 matrix router with full functionality built into the LDC. Functions and options are the same as a real MX-FR17 device. The Terminal window is also available by pressing its button on the bottom.

INFO: "Highlight Me" is the default function of the Show Me button. If you assign a different function to the button, the feature above will not be available. 5.3.2. Serial Tab If the device is connected via the RS-232 port click on the Query button next to the desired serial port to display the device’s name and serial number. Double-click on the device or select it and click on the green Connect button.

ATTENTION! Before the device is connected via the local RS-232 port, make sure that Control mode and LW3 protocol are set on the serial port. Furthermore, the RS-232 port must be free and other serial connection is not established to the device over that port. 5.3.3. USB Tab Connect the device to a PC/computer over the USB mini-B type connector. Refresh the list and double-click on the device or select it and click on the green Connect button.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 54

5.4. Crosspoint Menu Port Tiles #status 2 1 The colors of the port tiles and the displayed icons represent different states and information: 1 Port name

2 Port icon 1 LINKOUT O1 3 4 3 Port number TPS 3 A 5 4 Signal present 2 indicator green: present 7 grey: not present 5 State indicators

State Indicators 4 Following icons display different states of the port/signal: 6 Icon Icon is grey Icon is black Icon is green Signal is not Signal is encrypted with encrypted with - 5 A HDCP HDCP

Port is unmuted Port is muted - 1 Main menu The available menu items are displayed. The active one is showed with A dark grey background color. 2 Information ribbon The label shows the device label which can be edited in the Port is unlocked Port is locked - Settings menu - Status tab. Device discovery window can be displayed by A clicking on this ribbon. Autoselect is Autoselect is - disabled enabled 3 Video input ports Each tile represents a video input port. The tile below the port shows the A current crosspoint setting; if the port is switched to the output, the color of TIPS AND TRICKS: Hover the mouse cursor to the information ribbon; the product name and the IP the tile is white, otherwise grey. #crosspoint #switch #testpattern address of the device will appear as a tooltip text. 4 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 #analogaudio 5 Advanced view Displaying Advanced View Window, showing the Terminal window and the LW3 protocol tree. #nosyncscreen 6 Audio output The audio output of the TPS out port. Clicking on the tile opens the TPS #label #devicelabel Audio Output. 7 Video output The video output of the TPS out port. Clicking on the tile opens the TPS Video Output.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 55

5.5. Port Properties Windows Available settings: #mute #unmute #lock #unlock #testpattern Clicking on the port tile opens the Port properties window. This section shows the available settings and ▪ Mute/unmute the port; #nosyncscreen status information by port types. ▪ Lock/unlock the port; ▪ Source: Auto / RGB / YUV; 5.5.1. Analog Video Inputs ▪ Analog options, see the details below; Port properties windows of VGA and DVI-A input ports provide similar settings and status information: ▪ No sync screen: configuration settings of theTest Pattern; ▪ Frame Detector; #framedetector ▪ Reloading factory default settings for the selected port. #factorydefault Analog Options Analog video signals are digitized on the input. The timing parameters can be adjusted here if needed. Timing presets can be saved for each resolution separately. User has 8 user presets to store different timing data.

Analog options and Presets windows in LDC

Port properties window of the VGA video input

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 56

5.5.2. Digital Video Inputs 5.5.3. TPS Video Output Clicking on the HDMI, DisplayPort, or DVI-D input port icon results opening the Port properties window. The Click on the output port to display its properties. The most important information and settings are available most important information and settings are available from the panel. from the panel.

Port properties window of the HDMI video input

Available settings: ▪ Mute/unmute the port; ▪ Lock/unlock the port; ▪ HDCP setting (enable / disable); ▪ No sync screen: configuration settings of theTest Pattern; ▪ Frame Detector; Port properties window of TPS video output ▪ Reloading factory default settings for the selected port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 57

Available settings: #mute #unmute #lock #unlock #testpattern 5.5.4. Analog Audio Inputs ▪ Mute/unmute the port; #nosyncscreen ▪ Lock/unlock the port; ▪ Autoselect settings: enable / disable, mode, and priorities. (See more details about Autoselect feature in The Autoselect Feature section); ▪ Signal type: Auto / DVI / HDMI 24 bit / HDMI 30 bit / HDMI 36 bit - The outgoing signal format can be selected by a drop-down menu; ▪ Connected source ▪ HDCP mode: Auto / Always - The transmitter forces the source sent the signal without encryption if the content allows when Auto mode is selected; ▪ Power 5V mode: Auto / Always on / Always off - The setting lets the source and the sink devices be connected – independently from the transmitted signal; ▪ Color space: Auto / RGB / YCbCr 4:4:4 / YCbCr 4:2:2 - The outgoing signal color space can be selected by a drop-down menu; INFO: The color space conversion supports resolutions up to 1600×1200@60Hz. When the pixel clock frequency is above 170MHz, the conversion does not execute, and the original content will be transmitted. ▪ TPS mode: Auto / HDBaseT / Long reach / LPPF1 / LPPF2. See more information about TPS modes in the TPS Interface section. ▪ Frame Detector; ▪ Cable Diagnostics; ▪ The CEC Tool (in UMX-TPS-TX140-Plus, UMX-TPS-TX140K and WP-UMX-TPS-TX130-Plus-US models) ▪ Reloading factory default settings for the selected port. #autoselect #mute #unmute #lock #unlock hdcp #status #colorspace #tpsmode Port properties window of the AUDIO1 (Jack) input

Certain parameters of the analog audio input signal can be set as follows: #analogaudio #audio ▪ Mute/unmute the port; ▪ Lock/unlock the port; ▪ 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) ▪ Reloading factory default settings for the selected port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 58

5.5.5. Digital Audio Inputs 5.5.6. TPS Audio Output Certain parameters of the digital audio output signal can be set as follows:

Port properties window of HDMI audio input

Certain parameters of the embedded audio input signal can be set as follows: ▪ Mute/unmute the port; ▪ Lock/unlock the port; Port properties window of the TPS audio output ▪ Reloading factory default settings for the selected port. Available settings: ▪ Mute/unmute the port; #mute #unmute #lock #unlock #audio ▪ Lock/unlock the port; ▪ Autoselect settings: enable / disable, mode, and priorities. (See more details about Autoselect feature in The Autoselect Feature section); ▪ Reloading factory default settings for the selected port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 59

5.6. The CEC Tool 1 Drop-down This list contains the basic CEC commands, most of them are displayed on the graphical command interface, too (on the left side). Click on the Send button to execute sending the command. UMX-TPS-TX140-Plus, UMX-TPS-TX140K and WP-UMX-TPS-TX130-Plus-US models are able to send and list receive Consumer Electronics Control (CEC) commands. This feature is for remote control of the source or sink device. CEC is a bi-directional communication via HDMI cable, in this case between the input port of the 2 Custom The text field is for sending hexadecimal commands to the source. The maximum transmitter and the source. #cec command length of the message could be 30 characters (15 bytes). Click on the Send button to textbox execute sending the command. 3 OSD string A max. 14 character-long text can be shown on the sink device. The send OSD (On-screen textbox display) command textbox is the input field of the string. Alphanumeric characters, glyphs and space are accepted. Click on the Send button to execute the command. 4 Received Displays all the sent (in red) CEC commands and the received answers (in blue) with a Command timestamp. box Legend of the received message: 1 < [10:33:17] ACK Answer for the acknowledged command. < [10:35:01] NACK 2 Answer for the not acknowledged command. < [10:33:17] IN PROGRESS The command is in progress at the moment. 3 < [10:33:17] FAILED Answer for other failure. < [10:35:40] feature_abort_<*> This is the most common answer from the third-party devices when the command is delivered, but the execution is refused. The cause of the refuse stands after 'feature_ abort' expression. 4 5 Clear Click on the Clear button to erase the content of the terminal window. button 6 CEC This panel provides the quick and easy management of CEC commands. These buttons command are pre-programmed with basic functions and sends commands towards the sink. button The communication is displayed in the Received Command box. For the list of the panel commands see GPIO Port Configuration section. Both the layout and functionality are 5 similar to the design of a remote control. 6 ATTENTION! Make sure that the controlled unit is CEC-capable and this function is enabled.

Layout of CEC panel on the HDMI input port

The CEC panel is available on the port properties window of the HDMI input and TPS output ports. ATTENTION! It can occur that the third-party device can receive, but not execute the command because it is not supported by the product. Check the accepted commands in the documentation of the device. INFO: The first 2x2 bytes of the CEC commands contains identification data of the source and destination address. When the port is input, it is always 04 (from TV to Playback device 1.)., when the port is output, it is always 40 (from Playback device 1. to TV).

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 60

5.7. Diagnostic Tools Table and Chart Views #cablediagnostics 5.7.1. Cable Diagnostics Cable diagnostics can be displayed in advanced modes as well. Two ways are available: table view and chart view. Data can be exported to a file on clicking on theExport data button. The cable diagnostics is a useful tool to determine any cable related issues in case of TPS connection. The estimated cable length and the quality of the link are measured periodically and the diagnostic window shows the values in real-time. If the green bars hit the first line in the middle they turn into red. It means the number of the errors – during the extension – is higher than recommended. 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 causes high error rates. Check the cable terminations or change the cable.

Table view of cable diagnostics

Reference Values #cablediagnostics

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 Above displayed “Video BER < 10-10” value means that on average there is 1 bad pixel after 1010 pixels, which means the number of the bit errors is about 1 pixel in every 80 seconds. INFO: You can find more details about maximum twisted pair cable distances in theMaximum Extension Distances section. Chart view of cable diagnostics

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 61

5.7.2. Test Pattern Test Pattern Configuration on Video Input Ports The port generates an image which can be displayed when there is no incoming signal on the port. Each port can have individual settings which can be set by clicking on the Configure button. #testpatttern

Mode: Auto: No sync screen signal is sent when there is no incoming signal. Always on: No sync screen signal is sent always, independently from the incoming signal. Always off: No signal is sent when there is no incoming signal. Resolution: Set the desired image resolution from the drop-down menu. Color: Click on the desired color or use the sliders and press the Set color button to store.

Port properties window of the Test pattern input

Test Pattern Configuration on Testpattern Port (I6)

Resolution: Set the desired image resolution from the drop-down menu. Color: Click on the desired color or use the sliders and press the Set color button to store.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 62

5.7.3. Frame Detector 5.8. EDID Menu The ports can show detailed information about the signal like full size and active video resolution. This Advanced EDID Management can be accessed by selecting the EDID menu. There are two panels: left one feature is a good troubleshooter if compatibility problems occur during system installation. To access this contains Source EDIDs, right one contains Destination places where the EDIDs can be emulated or copied. function, open the port properties window and click on Frame detector button.

Frame detector window

Lightware’s Frame Detector function works like a signal analyzer and makes possible to determine the exact EDID menu video format that is present on the port, thus helps to identify many problems. E.g. actual timing parameters Control Buttons may differ from the expected and this may cause some displays to drop the picture. #framedetector Frame Detector measures detailed timings on the video signals just like a built-in oscilloscope, but it is Exporting an EDID (save to a Transfer button: executing much more easy to use. Actual display area shows the active video size (light grey). Dark grey area of the file) EDID emulation or copying full frame is the blanking interval which can contain the info frames and embedded audio data for HDMI Importing an EDID (load from Deleting EDID (from User signals. Shown values are measured actually on the signal and not retrieved only from the HDMI info frames. a file) memory) Display EDID Summary Selecting all memory places window in the right panel Opening Advanced EDID Selecting none of the memory Editor with the selected EDID places in the right panel

Opening Easy EDID Creator #edid

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 63

5.8.1. EDID Operations 5.8.2. EDID Summary Window

Changing Emulated EDID #edid Select an EDID from Source panel and press Info button to display EDID summary. Step 1. Choose the desired EDID list on the source panel and select an EDID. Step 2. Press the Emulated button on the top of the Destination panel. Step 3. Select the desired port on the right panel (one or more ports can be selected); the EDID(s) will be highlighted with a yellow cursor. Step 4. Press the Transfer button to change the emulated EDID.

Learning an EDID The process is the same as changing the emulated EDID; the only difference is the Destination panel: press the User button. Thus, one or more EDIDs can be copied into the user memory either from the factory memory or from a connected sink (Dynamic).

Exporting an EDID ATTENTION! This function is working on Windows and macOS operating systems and under Firefox or Chrome web browsers only. Source EDID can be downloaded as a file (*.bin, *.dat or *.edid) to the computer. Step 1. Select the desired EDID from the Source panel (line will be highlighted with yellow). Step 2. Press the Export button to open the dialog box and save the file to the computer.

Importing an EDID Previously saved EDID (*.bin, *.dat or *.edid file) can be uploaded to the user memory: Step 1. Press the User button on the top of the Source panel and select a memory slot. Step 2. Press the Import button below the Source panel. Step 3. Browse the file in the opening window then press theOpen button. Browsed EDID is imported into the selected User memory. ATTENTION! The imported EDID overwrites the selected memory place even if it is not empty.

Deleting EDID(s) EDID summary window 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 the desired memory slot(s); one or more can be selected (“Select All” and “Select None” buttons can be used). The EDID(s) will be highlighted with yellow. Step 3. Press the Delete selected button to delete the EDID(s).

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 64

5.8.3. Editing an EDID 5.8.4. Creating an EDID - Easy EDID Creator Select an EDID from Source panel and press the Edit button to display Advanced EDID Editor Since above mentioned Advanced EDID Editor needs more complex knowledge about window. The editor can read and write all descriptors, which are defined in the standards, EDID, Lightware introduced a wizard-like interface for fast and easy EDID creation. With including the additional CEA extensions. Any EDID from the device’s memory or a saved Easy EDID Creator it is possible to create custom EDIDs in four simple steps. By clicking EDID file can be loaded into the editor. The software resolves the raw EDID and displays it asreadable on the Create button below Source panel, Easy EDID Creator is opened in a new window. For more details about information to the user. All descriptors can be edited, and saved in an EDID file, or uploaded to the User EDID Editor please visit our website (www.lightware.com) and download the EDID Editor Application note. memory. For more details about EDID Editor please visit our website (www.lightware.com) and download the EDID Editor Application note. #edid

EDID Creator Window

EDID Editor window

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 65

5.9. Control Menu 5.9.2. Message Recognizer 5.9.1. RS-232 Tab DIFFERENCE: This feature is available in UMX-TPS-TX140-Plus, UMX-TPS-TX140K and WP-UMX-TPS-TX130-US models. The device can analyze and store the received serial data. For more information see the RS-232 Recognizer section. Check the Enable message recognizer on this port option to switch the recognizer on. Delimiter sequence text box is for setting the delimiter string in hex format. When this string is detected in the incoming serial data, the device saves the RS-232 message data from the first bit till the delimiter (or the data between the two delimiters). INFO: 0D0A is the factory default value, this is the hexadecimal code of Carriage Return and Line Feed. LW3 protocol commands end with this formula, so the default value support the recognition of the LW3 commands and the stored changes automatically. If the Timeout is enabled and set, the received data is saved when the timeout is elapsed after the last received message. In Received messages box shows the last received and stored message in Text (RECOGNIZER.Rx), Hex RS-232 Tab in the Control Menu (RECOGNIZER.RxHex), and Hash (RECOGNIZER.Hash) The following settings and functions are available on the local and TPS link RS-232 port: format. The Hex and Hash contains the delimiter. ▪ RS-232 mode: Control, Pass-through, and Command Injection (for more details about serial interface Press the Clear button to erase this storage. modes see the Technical Background section); Clicking on Reload restores the Factory Default Settings of the recognizer. ▪ Baud rate: 4800, 7200, 9600, 14400, 19200, 38400, 57600, 115200; ATTENTION! The Message recognizer settings are mirrored on the Local and TPS out serial port. ▪ Data bits: 8 or 9; INFO: Message recognizer operates independently of the RS-232 mode. ▪ Parity: None, Odd, or Even; ▪ Stop bits: 1, 1.5, or 2; ▪ Command injection: enable or disable; ▪ Command injection port number; ▪ Control protocol: LW2 or LW3; ▪ Message sending via serial port; ▪ Reloading factory defaults (see factory default settings in the Factory Default Settings section). ATTENTION! The RS-232 Operation mode is mirrored on the Local and TPS out serial port. The other settings can be adjusted separately on the two ports. #rs232 #rs-232 #serial #commandinjection

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 66

Configuration Example for the Message Recognizer 5.9.3. GPIO Tab The detailed description below shows how to configure the message recognizer in RS-232 Recognizer Example. When the UMX-TPS-TX140-Plus has an active video signal, the transmitter login the VC codec automatically. The signal presence triggers a bi-directional communication with the VC codec via RS-232: Step 1. Turn on the recognizer: Enable it on the P1 serial port. Step 2. Set the delimiter (in hex format). In this case, the Delimiter (hex format: 3A) delimiter character is ':', which is '3a' in hex format. When the delimiter string is detected in the incoming ... Password : Login name : ... serial data, the serial message is stored in string (in Rx Stored string and ActiveRx property), hex (in RxHex and ActiveHex property) and hash (in Hash and ActiveHash property) format. These stored content can be set as a condition in the event manager. INFO: The stored content is the incoming data which arrives before the delimiter or between the two delimiters. Step 3. Set the Active timeout 100. This property is responsible for erasing the temporary storage (ActiveRx, ActiveRxHex, ActiveHash) after the elapsing time. In the below example, it can be seen how does the recognizer properties change during the communication: ç UMX-TPS-TX140-Plus: PING Rx RxHex Hash ActiveRx ActiveRxHex ActiveHash

GPIO Tab in the Control Menu æ VC codec: Login: The GPIO port has 7 pins, which operate at TTL digital signal levels and can be controlled by LDC or protocol Rx RxHex Hash ActiveRx ActiveRxHex ActiveHash commands. Select a GPIO pin and under the Port settings section; the settings (pin direction and input level) Login: 4C6F67696E3A 2D8A5E38 Login: 4C6F67696E3A 2D8A5E38 are displayed on the port tiles as well: #gpio ç UMX-TPS-TX140-Plus: Admin Active timeout is elapsed, so the values of the Active- prefixed properties are deleted. 1 GP1 P1 6 1 GPIO pin name 4 High level indicator * Rx RxHex Hash ActiveRx ActiveRxHex ActiveHash 2 GPIO port icon 5 Pin direction: Login: 4C6F67696E3A 2D8A5E38 2 5 Input: down arrow Output: up arrow æ VC codec: Password: 34 3 Low level indicator 6 GPIO port number Rx RxHex Hash ActiveRx ActiveRxHex ActiveHash Password: 50617373776F72643A 79059B26 Password: 50617373776F72643A 79059B26 * Highlighted with black means the current setting. ç UMX-TPS-TX140-Plus: Admin INFO: Output level can be set only in case of setting the pin direction to Output. In case of input direction Active timeout is elapsed, so the values of the Active- prefixed properties are deleted. the output level setting and the Toggle button is not available. Rx RxHex Hash ActiveRx ActiveRxHex ActiveHash For more details about GPIO interface see the GPIO Interface section. Password: 50617373776F72643A 79059B26

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 67

5.9.4. Ethernet HTTP Clients (HTTP Post and Put Message Sending) DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). ATTENTION! This feature means posting or putting HTTP messages from the Lightware device to another device. Encrypted transmission (HTTPS) is not supported. The HTTP Clients tab allows sending HTTP post and put messages to the desired server IP:port no. Control commands can be set to the target device, but it is not suitable for processing the response (e.g. querying a parameter/status) since the response is just an acknowledge (ACK). #http The feature is available also by LW3 commands, see the HTTP Messaging section.

Ethernet Tab in the Control Menu

Two ports are displayed in the Ethernet settings: Local, CPU, and TPS. You can check the status of the Ethernet line by each ports: the speed and the duplexity of the connection. The following settings are available for the local port: ▪ Enable / disable the port; ▪ Reloading factory defaults. ATTENTION! If the Ethernet port is set to disabled, this may break the connection with the device. INFO: CPU Ethernet port cannot be disabled. HTTP Clients tab in the Control/Ethernet menu When you press the enter in the Http header or Http body text box, the \r\n is added automatically.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 68

TCP Clients (TCP Message Recognizer) SalvoHttp Status Page (Receiving HTTP Message) DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). UMX-TPS series). This tab is the preparing and monitoring interface for the TCP recognizer which may trigger Event Manager ATTENTION! This feature means sending HTTP messages from an external device to the Lightware device. Actions. A simple example can be seen in the TCP Message Recognizer section. Encrypted transmission (HTTPS) is not supported. In this case, a batch of commands can be sent over HTTP to the Lightware device for processing. Post the commands to the /protocol.lw3 address and the commands are processed immediately and sequentially. #http Control commands can be sent to the Lightware device, but it is not suitable for querying a parameter/status since the LW3 responses are not sent back to the sender. ATTENTION! If the Cleartext Login (Login Settings) is enabled in the device, the login has to be the first command. No commands will be processed without a successful login. See the syntax in the Cleartext Login Protection section.

TCP Clients tab in the Control/Ethernet menu The target device has to be set as a TCP client (three clients can be set): Step 1. Type and set the Target IP address. Step 2. Type and set the TCP port number. Step 3. Make sure the same TCP port is opened and Enabled in the target device. Step 4. Press the Connect to target button. Step 5. Make the target device send a message and check it in the Detected messages list. ▪ Auto reconnect: Numeric value; sets the time (seconds) between the automatic reconnections. ▪ Delimiter: When the delimiter hex string is detected in the incoming data, the message is saved from SalvoHttp tab in the Control/Ethernet menu the first bit until the delimiter (or the data between the two delimiters). ▪ Timeout: If there is no response within the set time interval (milliseconds), the data will be accepted, that is received from the last delimiter. ▪ Trigger Action: If data is received that is closed with the recognized delimiter, an Action can be run. Type the number of the Event (without letter 'E'). #tcprecognizer #message

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 69

5.9.5. Infra Tab Description Function ATTENTION! The device has no built-in Infrared receiver and transmitter. For the complete usage attach an IR emitter unit to the IR OUT and an IR detector unit to the IR IN connectors. ID Code number. Infra-Red (IR) receiver and transmitter options can be found on this tab. There are three submenus are Name You can give an unique name for the desired code. available under it: IR codes, Ports, and Clear all IR codes. Fingerprint (hash) Fingerprint code in pronto hexa format. IR Codes Detected Indicator gives feedback about the given IR code is detected currently. User can set the name of the IR code, the fingerprint (hash), and the repeat timeout in ms, actions can be ordered to each IR code as well. Repeat timeout (ms) You can set a timeout to avoid the involuntary code recurrence.

Action buttons for the desired IR code: Save: saving the fingerprint. Actions Cancel: canceling the fingerprint. Learn: learning the detected IR code. You can check the detected IR codes in this panel. Pushing Clear button Detected IR fingerprints deleting all current fingerprints and switch on or off the automatic scrolling with the Autoscroll pipe.

20 fingerprints can be stored in the device at the same time. Each of them can be ordered to an action in Event Manager. Learning IR Codes Step 1. Connect the IR detector unit to the IR IN port of the transmitter. Step 2. Click on the Learn button. Step 3. Turn the remote controller to the IR detector. A pop-up window appears in LDC - press your remote button to learn. Step 4. Once the code is received, a new window pops up in LDC - learning completed. Click OK to continue. Step 5. Optionally type a unique name for the code in the Name text box. The default name is code#, e.g. code0.

IR codes window in Control menu

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 70

Ports Section of the UMX-TPS-TX100 Series Devices Ports Section of the UMX-TPS-TX140-Plus UMX-TPS-TX140K and WP-UMX-TPS-TX130-US Models User can set the name and command injection port to each sources and destinations. For more details about IR interface see the IR Interface section.

Infra tab - Ports window for the UMX-TPS-TX140-Plus model Infra tab - Ports window for the UMX-TPS-TX100 series devices The user can set the name and command injection port to each sources and destinations. For more details about IR interface see the IR Interface section. The message sending function (little-endian pronto hex code) is available in this section. #commandinjection

Sending pronto hex codes (Little-endian format) Copy the raw, little endian-format IR code into the Send Pronto Hex entry field and click theSend button. The maximum length of the code can be 765 characters (765 bytes). For more details about the accepted IR code formats, see Sending Pronto Hex Codes in Little-endian Format via IR Port section. This entry field does not store the code. The code can be saved into the action in the event manager with the following parameters: Category: Infra; Expression: Send pronto hex; Port: D1; Pronto hex: In the Event Manager, the maximum length of the code can be 184 characters (184 bytes). INFO: Sending bigger endian-format code is available with LW3 protocol command, see Sending Pronto Hex Codes in Big-endian Format via IR Port section.

Clear all IR codes Clicking on the button results deleting all stored IR fingerprints.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 71

5.9.6. Macros DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). DEFINITION: Macro is a batch of pre-defined commands stored in the device. #macro You can create your custom macros in a file, upload to the device and run at any time. The number of the macros depends on the device type, UMX-TPS transmitters can handle up to 50 macros.

Important Notes about Macros ▪ The macros are stored in the internal device preses. ▪ The commands of a macro are executed sequentially (even if error happens at a command). ▪ Macros allow long commands that is suitable for e.g. infra code sending. ▪ Macros cannot be edited in the device. ▪ Macros are not saved when backup is created. See the Saving the Macros section. Macro File Structure Format: Example:

; ;myDeviceMacros ;Begin ;Begin myMacro1 CALL /MEDIA/VIDEO/XP:unmuteSource(I3) ;End CALL /MEDIA/VIDEO/XP:switch(I3:O1;I3:O2) Discovered Macros in the device shown under Control/Macros submenu ;Begin ;End myMacro1 ;Begin myMacro2 Adding Macros by Preserving the Current Preset and Macros ;End CALL /MEDIA/VIDEO/XP:unmuteSource(I4) If you follow the steps below, the existing macros of the selected preset will be preserved. But if there is a CALL /MEDIA/VIDEO/XP:switch(I4:O1;I4:O2) macro with the same name already in the device, it will be removed and the new will be available. ;End myMacro2 Step 1. Navigate to the Settings/Backup submenu. : it will be displayed in the Settings/Backup submenu (device configurations list). Step 2. Select the device configurationpreset at the bottom of the page. : each Macro must have a unique name. Step 3. Press the Download button and click Save in the pop-up window. : LW3 SET and CALL commands. Syntax is not checked, error is not reported. Step 4. Open the file with a simple text editor and add the desired macros to the bottom of the commands ATTENTION! If you use the same name for a new macro, the existing one will be deleted. between the ;Begin and ;End labels. Open a simple text editor and save the file with 'LW3' extension. Step 5. Save the file and navigate to theSettings/Backup submenu. Step 6. Select the device configurationpreset. Uploading New Macros into the Internal Device Configuration Preset Step 7. Press the Upload button, browse the LW3 file and pressOpen . The uploading steps are the following: Step 1. Create the filewith macros according to the macro file structure and save it. Saving the Macros Step 2. Navigate to the Settings/Backup submenu. When you make a backup of the device, the macros are not saved in that file. Sometimes, it is necessary to Step 3. Select the device configurationpreset at the bottom of the page. save the macros into a file and for example apply them in another (same type of) device. Follow these steps: Step 4. Press the Upload button, browse the LW3 file and pressOpen . Step 1. Navigate to the Settings/Backup submenu. ATTENTION! The preset and the macros of the selected slot will be erased. If there is a macro with the Step 2. Select the device configurationpreset at the bottom of the page. same name already in the device, it will be removed and the new one will be available. Step 3. Press the Download button and click Save in the pop-up window.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 72

5.9.7. Variables Value Section DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package You can set the value of the variable by the field. The type of the variable is determined automatically based v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- on its value (numeric/string). UMX-TPS series). Add / Cycle Section You can create custom variables in number or text format which can be used in the Event Manager. The variables can have the following properties/methods: #variables This section can be used for numeric types. ▪ Operand: the increment, the number that will be added to the current value (negative value is accepted). ▪ Numeric (integer) type with min/max value setting, or string-type (determined automatically) ▪ Min (optional): the lowest allowed value ▪ Increment/step the numeric value, ▪ Max (optional): the highest allowed value ▪ Value-dependent case operations, ▪ Add button: the operand will be added to the current value. If the result would be higher than the max ▪ Reading and storing the values of LW3 properties into string or numeric variables. setting, the max will be valid; if the result would be lower than the min setting, the min will be valid ▪ The max length of a string variable can be 15 characters. Numeric variable is defined between ▪ Cycle button: the operand will be added to the current value. If the result would be beyond the limit -2147483648 and 2147483647. (min/max), the value will be stepped to the other end of the interval. The defined variables are stored in a non-volatile memory and the value is kept in case of a reboot. Examples The following shows the difference between the Add and the Cycle options. The input values are the same in both cases: Add Add Add Add Add ▪ Min: 1 1 2 3 4 5 ▪ Max: 5 ▪ Operand: 1 Cycle Cycle Cycle Cycle Cycle 1 2 3 4 5

In Add case: when the value hits the limit (max), the operand will not increase the value any more. In Cycle case: when the value hits the limit (max), the value will be stepped to the other end of the interval. Similar case happens vice versa: when the operand is a negative number and the value hits the min value. TIPS AND TRICKS: Set min=1, max=2, operand=1 and use the cycle method. Thus, the value of the variable can be toggled which can be linked to a property with two states (e.g. low/high level) in Event manager.

Case Convert This tool can be used to change the value of a variable if it fits in any of the defined intervals. The check and the change will be performed only if you press the Convert button. A typical example when two different ranges of values have to meet: Incoming values: between 0 and 255 (e.g. the slider of a controller can have these values). Outgoing values: between 0 and 100 (e.g. the controlled device accepts these values). Defined cases: Min Max New value Min Max New value Case 1 1 25 10 Case 6 126 150 60 Case 2 26 50 20 Case 7 151 175 70 Case 3 51 75 30 Case 8 176 200 80 Case 4 76 100 40 Case 9 201 225 90 Variables tab in the Control menu Case 5 101 125 50 Case 10 226 255 100

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 73

Scan and Store This tool can be used to get the value (or a part) of an LW3 property. The defined path will be checked according to the pattern and the result will be saved into the variable (number or string type). Press the ? button to open the pattern options: Pattern Pattern description %s String of characters stopping at the first whitespace character %s The next of characters (string) stopping at the first whitespace %c One character %c The next of characters %[] Defined character set, specified between brackets %[^] Negated character set, specified between brackets which will be skipped %* Ignored part User-defined text

Examples Scanned Node Path 1 Property Value Pattern 1 result /MANAGEMENT/STATUS.CpuTemperature 32 C; 0;75; 0;79;21;34; %s 32 /MANAGEMENT/STATUS.CpuFirmware 1.3.0b0 r1 %12s 1.3.0b0 /MEDIA/VIDEO/I6.Resolution 640x480p60 %3c 640 /MEDIA/UART/P1.Rs232Configuration 57600, 8N1 %*[^,], %s 8N1 /MEDIA/AUDIO/XP.SourcePortStatus T000A;T000A;T0008;T000A;T000C %*6c%5c T000A /MEDIA/VIDEO/I6.Resolution 640x480p60 %[^b]%* 640 /MANAGEMENT/NETWORK.HostName lightware-00005031 lightware- 00005031

1 defined by the user

Reformat The value of the variable can be changed by adding text as prefix and/or postfix. Type %s to indicate where to insert the original value. Example ▪ Original value: 3 ▪ Pattern: input%s ▪ Modified value: input3

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 74

5.10. Event Manager 5.10.1. The Event Editor The feature means that the device can sense changes on its ports and able to react Press the Edit button in the desired Event line to open the Event editor window. 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 1 or HDCP active) are necessary to display but it is not easy when the device is hard to access (e.g. built under the desk). 2 6 The Event manager can be configured to perform an action if a condition has been detected. E.g. the desired setup is that after a certain type of signal has been detected on I1 port, the port has to be switched to O1. The settings can be done via the LDC in the Events menu, or by LW3 protocol commands. Configurable events number depends on the device what you are using actually. Numerous new ideas and requests have been received in connection with the features and settings of the Event manager since the first release. Therefore, the user interface has been re-designed and many new 3 7 functions implemented. The Event editor can be opened by pressing the Edit button at each Event. There is a grey bar on the left of the Event panel in each line. If a condition and an action are set and the Event is enabled, the bar is displayed in green.

4 8

5

1 Event header The name of the Event is displayed. Type the desired name and press the Set name button. The Event can be cleared by the Clear button. Use the tick mark to enable/disable the Event. 2 Condition header If the condition is set, the description (white colored text) and the exact LW3 protocol expression (yellow colored text) can be seen. If the advanced mode was used the description is “Custom condition”. 3 Condition panel The Wizard, the Advanced or the Link tool is available to set the condition. The parameters and settings are displayed below the buttons. 4 Condition counter The set condition can be tested to see the working method in the practice. 5 Delay settings The action can be scheduled to follow the condition after the set time value. 6 Action header If the action is set, the description (white colored text) and the exact LW3 protocol expression (yellow colored text) can be seen. If the advanced mode was used the description is “Custom action”. Control menu, Event Manager tab 7 Action panel The Wizard, the Advanced or the Link tool is available to set the action. The parameters and settings are displayed below the buttons. 8 Action test The set action can be tested to see the working method in the practice.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 75

5.10.2. Create or Modify an Event The Link Tool

Wizard Mode The new interface allows creating more actions for the same condition. In that case, a condition can trigger The wizard mode lists the most common conditions more actions. To set such an Event, the Link tool has and actions, so the user does not have to look for LW3 been introduced. nodes and properties. Step 1. Click on the Edit button of the desired Event; the Step 1. Click on the Edit button of the desired Event; Event editor is displayed. the Event editor is displayed. Step 2. The wizard mode is displayed as default, press Step 2. The wizard mode is displayed as default. the Link button. Select the desired Category first (e.g. Audio or Step 3. All the saved Events are analyzed and the Video). conditions are listed (it takes some seconds to Step 3. Select the desired Expression from the finish). The Show advanced expressions option drop-down menu. If any other parameter is allows showing the exact path and set the necessary to set, it is going to be displayed. value of the given property. Step 4. Press the Apply button to store the settings of Step 4. Select the desired Condition and press the Apply the Condition. button to store the settings. INFO: This mode is also available for setting the INFO: This mode is also available for setting the Action. Action.

Advanced Mode Combine Links The goal of this mode is the same as of the wizard: set the properties and methods for conditions and DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- actions. The difference is the number of the available and usable properties and methods of the LW3 UMX-TPS series). protocol. Advanced mode allows almost all of it. The first generation of the Event Manager Step 1. Click on the Edit button of the desired is able to sense a change (one condition) Event; the Event editor is displayed. but in some cases that is not enough. The Step 2. The wizard mode is the default, press the practical experience has shown there is a Advanced button. The LW3 protocol tree is need to examine more conditions as follows: displayed showing the list of the properties if one of the set conditions becomes true in the drop-down menu. Navigate to the (while the other conditions are fulfilled), desired node. then the set Action is launched. The Combine Step 3. Select the desired Property from the menu. Links tool allows setting these Conditions. The manual of the property is displayed Follow the steps below: below to help to select the necessary Step 1. Create individual Conditions in property and to set the value. separate Events. Step 4. Set the desired value and operator, then Step 2. Create a new Event and navigate to press the Apply button to store settings. the Combine Links tab in the Editor. INFO: This mode is also available for setting the Step 3. Select up to four Conditions in the left Action. panel. Step 4. Set the desired Action (and do not forget to enable the Events). INFO: This mode is available for setting the Condition only.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 76

Linking a Macro (Action) TIPS AND TRICKS: The Test button is also placed on the Action panel in the Event list. Thus, you can check the Actions without opening the Event editor. DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus Delay the Action models from FW package v1.5.0b4 (UMX- no delay Condition = true Perform the action TPS series) and in WP-UMX-TPS-TX130- In most cases the Action is Plus-US models from FW package v1.5.0b6 performed immediately after simple delay Condition = true Delay Perform the action (WP-UMX-TPS series). the Condition is detected. But sometimes a delay is necessary still exist Condition = true Delay Condition = true Perform the action Macros stored in the device can be run as between the Condition and the Actions. Thus, a lot of commands can be run Action. Therefore, the new Event continously Condition = true by using only one Event. The commands will Perform the action manager contains the Delay panel exist Delay be processed one-by-one after each other. which allows that feature with Time #macro below settings: Step 1. Click on the Edit button of the desired ▪ No delay: when the Condition is detected, the Action is launched. Event; the Event editor is displayed. ▪ Simple delay: when the Condition is detected, the Action is launched after the set time interval. Step 2. The wizard mode is the default, press ▪ Still true after: when the Condition is detected, the Action is launched after the set time interval only if the Macros button in the Action panel. the Condition still exists. Step 3. Select the desired Macro from the list then press the Apply button to store ▪ Continuously true: when the Condition is detected, the Action is launched after the set time interval only settings. if the Condition has been existing continuously. If the Use variables option is enabled, you can link a variable by the $ character. If you do so (e.g. $1), the TIPS AND TRICKS: Show advanced expressions option is a useful tool when you look for the path or value device will handle it as the V1 variable. You can send the value of the variable e.g. as a TCP message. of a property but just the expression is displayed. The option is available in the Event list window or when See more information about the Macro settings in the Macros section. Link tool is used. 5.10.3. Special Tools and Accessories Variables

The Name of the Event DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- The name of a port can be changed by typing the new name and clicking the Set button. The following UMX-TPS series). characters are allowed when naming: letters (A-Z) and (a-z), numbers (0-9), special characters: hyphen ( - ), underscore ( _ ), and space ( ). The variables and the tools (shown in the Control/Variables tab) can be used in the Event Manager. Condition Wizard #variables Enable or Disable an Event The desired variable can be checked if its value is changed to a specific value. The set Event can be enabled or disabled in the Event list, or directly in the Event editor window by setting Action Wizard the tick mark beside the name. The value of a variable can be set/changed by the same methods as in the Control/Variables tab: Testing the Condition ▪ Setting the exact value When the desired Condition is arranged, the setting can be tested. The Event list and the Event editor contains ▪ Increasing the value with/without limits a small panel that shows if the set condition is detected; the Counter can be reset by the button in Event editor. If the Condition is true, the detected mark turns green for two seconds and the Counter is increased. ▪ Converting the value (e.g. interval change)

Testing the Action ▪ Scanning and storing, or reformatting a property/parameter If the Use variables option is enabled, you can link a variable by the $ character. If you do so (e.g. $1), the The method is the same as testing the Condition, but in this case, the Action can be triggered manually by device will handle it as the V1 variable. You can send the value of the variable e.g. as a TCP message. pressing the Test button.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 77

Condition Triggering 5.10.6. Event Creating - Example DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package The following example shows you on a real-life situation how to set up an Event. v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- The Concept UMX-TPS series). The UMX-TPS-TX140 is connected to a projector by the TPS output port. The transmitter is also connected This function works as if a condition is detected. When a complex control system is built, a Condition may to the projector by the RS-232 port and can send commands via the serial line. The task is to turn on the trigger numerous Actions. A typical example is when a system is powered on and the ’ready-to-use’ state has projector when signal is detected on the TPS output port. to be loaded. In this case, there could be many actions which are based on the same condition. In order to reduce the number of the commands, you can trigger one ’key’ condition, which could start the whole process.

RS-232 Settings Make sure that the serial line is established between the transmitter and the projector. Check that the RS- 232 settings of the transmitter is set exactly the same which required for the projector: baud rate, data bits, 5.10.4. Clear One or More Event(s) parity, stop bits. The transmitter needs to be set to: Control protocol: LW3; and RS-232 mode: Pass-through. Clear an Event See the relevant LDC settings in the RS-232 Tab section. Press the Clear button in the Event list or in the header section in the Event editor. Setting the Event

Clear all Events You can create the Event in the Wizard in few simple steps: Step 1. Set the condition. When all the Events must be cleared press the Load factory defaults button above the Event list. You will be prompted to confirm the process. Select the required parameters to set the condition: ▪ Category: Video; 5.10.5. Export and Import Events ▪ Expression: Signal is detected on a port; The feature allows saving all the Events. The backup file can be uploaded to another UMX-TPS-TX100 series ▪ Port: O1. transmitter. Click on the Apply button to complete the procedure. When it is done, the condition appears on the upper side Export all the Events in textual and LW3 command format as well. Step 1. Press the Export button above the Event list. Step 2. The Save as dialog box will appear. Set the desired folder and file name, then press theSave button. The generated file is a simple text file which contains LW3 protocol commands. The file can be viewed by a simple text editor, e.g. Notepad. ATTENTION! Editing the file is recommended only for expert users.

Import all the Events Step 1. Press the Import button above the Event list. Step 2. The Open dialog box will appear. Select the desired folder and file, then press theOpen button.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 78

Step 2. Set the action. 5.11. Settings Menu If the condition is fulfilled, the following action needs to be launched: the receiver sends a command to the 5.11.1. Status projector over the serial line: ▪ Power on - the required command which is accepted by the projector: PWR0 For this instance the command has to be closed with the characters so they need to be escaped. You can use the following format for escaping:

<\x0d\x0a><\x0d\x0a>...

...<\x0d\x0a> In the current case the command is: PWR0\x0d\x0a Select the required parameters to set the action: ▪ Category: RS-232; ▪ Expression: Send RS-232 message; ▪ Port: P1; ▪ Message: PWR0\x0d\x0a

Status tab in Settings menu

The most important hardware and software related information can be found on this tab: hardware and firmware version, serial numbers, temperatures, operation time, and voltage information. Device label can be changed to unique description by the Set button. #label #devicelabel #status #firmwareversion #producttype #serialnumber #miniweb #builtinweb #web INFO: The Device label is a user-editable name displayed next to the main menu. The Product name is a read- only property. Step 3. Enable the Event. Please note that the Miniweb-related descriptions can be found in The Built-In Miniweb section. Select the E1 enabled pipe in upper left corner to set the Event as launched. Identify Me Feature INFO: If you do not find the required category/expression/etc what you need, choose the Advanced mode in the Wizard where the entire LW3 structure tree is available. For Clicking on the Identify me button results the blinking of the status (in green) for 10 seconds. The feature example instead of signal detection you can set a specified resolution or color range helps identifying the device itself in the rack shelf. #identifyme either as a condition.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 79

5.11.2. Network MAC Filter Allowlist DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). Another level of the security is the MAC Filtering tool. You can create a list of network devices based on the MAC address which are allowed: #macfilter ▪ Controlling the device (Send option), or ▪ Querying parameters (Receive option) to/from the Lightware device. Do not forget to press the Apply changes button to store the new settings. ATTENTION! The first three lines are factory default values and they are necessary for the proper working. ATTENTION! If the device is installed in a network where it gets IP address from a DHCP server and you plan to use the MAC filtering, make sure the MAC address of the DHCP server is added to the white list. Otherwise, the device will not get IP address and will be unreachable. 5.11.3. Front Panel

Network tab in Settings menu Front panel tab in the Settings menu General Front panel operation LEDs and buttons can be configure in this tab. IP address and DHCP settings can be set on this tab. Always press the Apply settings button to save changes. Factory defaults settings can be recalled with a dedicated button. ▪ You can disable the functionality of the front panel buttons with marking the Lock front panel option. This is same method of the control lock made by the front panel buttons. See the details in the Control TCP/IP Ports and Services Lock section. #controllock #buttonlock #lockbutton DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package ▪ Dark mode enable/disable: video and audio LEDs on the front panel are turned off 60 seconds after v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- enabling the dark mode. #darkmode UMX-TPS series). ▪ Enable default function for Video Select / Audio Select / Function (Show me) button: when this property is The IP Port Block feature is an additional protection for the Cleartext login, see the Cleartext Login (Login disabled, it means that pushing the button will not perform the original function. This makes the Settings) section. There are TCP/IP ports in Lightware devices which are not protected by the login, so you button free for programming custom function by the Event Manager. This setting is also available via can disable them if necessary. For example, due to the working method of the LW2 communication, the LW3 protocol, for more details see the Disable the Default Function of the Front Panel Buttons section. Cleartext login does not provide protection when LW2 command is sent to the device, that is why the TCP port no.10001 shall be blocked manually. #dhcp #ipaddress #network #portblock

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 80

5.11.4. Backup Further functions Details about this function can be found in the Configuration Cloning (Backup Tab) section. ▪ Download system log - saving the file of the device. ▪ Load factory defaults - recalling factory defaults settings and values. All factory default settings are 5.11.5. System listed in the Factory Default Settings section. ▪ Reboot - rebooting the system. #factory #log #systemlog #reboot #restart

System tab in Settings menu

Cleartext Login (Login Settings) DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). This cleartext login tool allows setting a password, thus, the device will not accept any command coming from a control interface (RS-232, Ethernet, etc…) without login. The device will be visible in the Device Discovery window (as the device type and the serial number can be queried without login) but connection can be established only after successful login. The login is valid until a TCP socket break in case of Ethernet connection. #login ATTENTION! If the login is enabled, the password will be asked when opening The Built-In Miniweb. INFO: The login password is erased and the login is disabled when restoring the factory default values.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 81

5.12. Configuration Cloning (Backup Tab) 5.12.1. Steps in a Nutshell Configuration cloning of Lightware LW3 devices is a simple method that eliminates the need to repeatedly Installing multiple devices with the same customized configuration settings can be done in a few easy steps: configure certain devices to have identical (non-factory) settings. If the devices are installed in the same Step 1. Configure one device with all your desired settings using the LDC software. type of system multiple times then it is enough to set up only one device to fit the user’s needs and then copy Step 2. Backup the full configuration file to your computer. those settings to the others, thus saving time and resources. Step 3. If needed, make some modifications to the configuration file using a text editor (e.g. Notepad). E.g. modifying the static IP address is necessary when DHCP is not used. Step 4. Connect to the other device which has to be configured and upload (restore) your configuration file. Step 5. Done! You can have as many totally identical, customized devices as you like. ATTENTION! Macros cannot be saved into the backup file. If you have macros stored in a Configuration slot, download it separately and upload it in the target device. 5.12.2. Save the Settings of a Device (Backup) Step 1. Apply the desired settings in the transmitter (port parameters, crosspoint, etc.) Step 2. Select the Settings / Backup tab from the menu. Step 3. Write a short description in the text box on the left (optional). Step 4. Press the Create a full backup button. You will be prompted to save the file to the computer. The default file name is the following:

BACKUP__SN.LW3 Step 5. Set the desired file name, select the folder and save the file. TIPS AND TRICKS: Using the exact product type in the filename is recommended since it makes the file usage more comfortable. About the Backup File The backup file is a simple text file which contains LW3 protocol commands. The first line is the description and the further lines are the commands which will be executed during the restore process. The file can be viewed (and/or edited) by a simple text editor, e.g. Notepad. See the entire list of saved data in the Content of the Backup File section. ATTENTION! Editing the command lines is only recommended for expert users.

Backup tab in the Settings menu

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 82

5.12.3. Upload the Settings to a Device (Restore) WARNING! Please note that the settings will be permanently overwritten with the restored parameters in the device. Withdrawal is not possible. ATTENTION! The cloning can be successful if the backup file is downloaded from the same type of source device as the destination device. The Restoring Process Step 1. Select the Settings / Backup tab from the menu. Step 2. Click on the Choose file button on the right panel and browse the desired file. Step 3. The file is checked and the result will be displayed in the textbox below. If the file is correct, the settings can be restored. Step 4. Choose IP settings what you want to use after backup. You can apply settings from the backup file, keep actual settings, set it manually in a dialog box or apply DHCP. Step 5. Select the desired MAC filter settings to be applied in the device (if available). See more information about this feature in the MAC Filter Allowlist section. Step 6. Press the Start restore process button and click on the Yes button when asked. Step 7. Reboot the device to apply the network settings after finishing. 5.12.4. Create and Restore Backups from the Device Memory The device can store configurations in its own memory, an internal slot is available for this purpose.

You can save the configuration to the internal slot: ▪ without protection: it can be easily applied/deleted, or ▪ with protection: it can be protected by a password to apply or delete the configuration. Loading the selected Deleting the selected configuration configuration Saving the current configuration Loading a configuration from to the selected slot without a file to the selected slot protection Saving the current configuration Saving the selected to the selected slot with a configuration as a file password The preset can be used for the macros as well, please see the Macros section. WARNING! Loading factory default settings will erase the internal preset in the device memory!

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 83

5.13. The Built-In Miniweb 5.13.1. Opening the Miniweb DEFINITION: The miniweb is a dedicated location in the memory where an HTML file can be uploaded The Miniweb is available by: to. If the http:///index.html page or the http:///index.html is ▪ Opening a web browser and typing the http://.index.html or the http:// in the opened in a web browser the file is displayed. address line, or ATTENTION! The Miniweb is available from FW package v1.1.5b1. The default control page can installed ▪ Launching the LDC, connecting to the device, navigating to Settings/Status and pressing the Open in the device during the first firmware update process by the user if the necessary parameter is enabled. miniweb button. See the Step 3. Check the update parameters. section. INFO: The host name can be used instead of the IP address; see the Setting the Host Name section. The default control page allows the followings: ▪ Source selection: This block can be used to select an input or enable/disable the Autoselect remotely e.g. from a mobile device. ▪ Action triggers: The action trigger buttons can be used to perform a configured Event Action without waiting for the condition to occur. This can be done remotely by a mobile device, too.

The Control Page Displayed in a Desktop Browser (with Action Trigger Buttons)

#miniweb #builtinweb #web

The Control Page Displayed in a Smartphone Browser Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 84

The Default Status Page Customized HTML If there is no control page uploaded, the default status page will be displayed (which is also available by The default control page can be replaced in the LDC; navigate to the Settings/Status page. Custom HTML file opening the /status.html address. can be uploaded by pressing the Choose filebutton. Pay attention to the size of the HTML file. Only one file is allowed and the maximum file size is 10 KB. Press the Reset button to remove the control page. The default control page can be restored during a firmware update process, see the Step 3. Check the update parameters. section.

The Factory Default Status Page (status.html) 5.13.2. Miniweb Customization The buttons of Action triggers section are linked to Actions of certain Events in the Event Manager. These buttons are displayed only for specific events: ▪ Any Event which does not have the @W suffix in its name willnot be displayed as a trigger button. ▪ The displayed trigger buttons will get a text label with the event name except the suffix. To add the desired Action as a button, append the name of the desired Event with the @W characters - see The Built-in Miniweb Section in LDC below (type uppercase for 'W' as it is case-sensitive):

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

5. Software Control - Lightware Device Controller UMX-TPS-TX100 series – User's Manual 85

5.14. Advanced View Window

1 2 3 4 1 LW3 protocol help Pushing the button results a help window opening which describes the most important information about LW3 protocol commands in HTML format. 2 Protocol tree LW3 protocol tree; select an item to see its content. 3 Edit mode The default appearance is the read-only mode. If you want to modify the values or parameters, tick the option. You will be prompted to confirm your selection. 6 4 Warning mode If this is checked, a warning window pops up when you enable Edit mode. 5 5 Node list Correspondent parameters and nodes are shown which are connected to the selected item in the protocol tree. The commands typed in these fields are escaped automatically Manual button: Manual (short description) of the node can be called and displayed in the terminal window. Set button: Saves the value/parameter typed in the textbox. Call button: Calls the method, e.g. reloads factory default settings. 6 Terminal window Commands and responses with time and date are listed in this window. Sent command starts with ‘>’ character, received response starts with ‘<’ character. The color of each item depends on the type of the command and response. The content of the window can be emptied by the Clear button. If the Autoscroll option is ticked, the list is scrolled automatically when a new line is added. 7 7 Command line The commands typed in this line are not escaped automatically. See more information in the Escaping section.

#advancedview #terminal

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 86

LW2 Programmer's Reference 6The 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.

ç LW2 Protocol Description ç Instructions for the Terminal Application Usage ç General LW2 Commands ç AV Port Settings ç Network Configuration ç RS-232 Settings ç GPIO Port Configuration ç LW2 Commands – Quick Summary

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 87

6.1. LW2 Protocol Description 6.2. Instructions for the Terminal Application Usage The protocol description hereinafter stands for Lightware protocol. The commands can be sent to the device Terminal Application in RAW format via the TCP/IP port no. 10001. The LW2 protocol commands can be applied to the The receiver accepts commands surrounded by curly brackets - { } - and responds data surrounded by receiver using a terminal application. You need to round brackets - ( ) - only if a command was successfully executed. All input commands are converted to install one of them to your control device, for example uppercase, but respond commands can contain upper and lower case letters as well. Putty or CLI. #terminal Legend for Control Commands Establishing Connection Format Explanation Follow the steps for establishing connection to the receiver: Input number in 1 or 2 digit ASCII format (01, 5, 07, 16, etc.) Step 1. Connect the receiver to a LAN over Ethernet. Output number in 1 or 2 digit ASCII format Step 2. Open the terminal application (e.g. Putty). input or output port number in 1 or 2 digit ASCII format * Step 3. Add the IP address of the device (default: 192.168.0.100) and the port number (10001). Input number in 2 digit ASCII format (01, 02, 10, 12 etc.) Step 4. Select the Raw connection type, and open the Output number in 2 digit ASCII format (01, 02, 10, 12 etc.) connection. input or output number in 2 digit ASCII format* Once the terminal window is opened, you can enter the LW2 protocol commands which are listed in the Location number in 1, 2 or 3 digit ASCII format following sections. id number in 1 or 2 digit ASCII format id number in 2 digit ASCII format CrLf Carriage return, Line feed (0x0D, 0x0A)

· Space character (0x20)

→ Each command issued by the controller ← Each response received from the router

* The command has the same arguments on the input ports and the output port, as well.

LW2 protocol command communication in a terminal window

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 88

6.3. General LW2 Commands 6.3.4. Query Control Protocol 6.3.1. List of All Available LW2 Commands This command queries the active protocol of the currently used control interface. Command and Response Command and Response #protocol ȩ {lcmd} ȩ {P_?} Ȩ (LCMD# LCMD: List all commands)CrLf Ȩ (CURRENT·PROTOCOL·=·#)CrLf Ȩ CrLf Example Ȩ (LCMD END)CrLf ȩ {p_?} Example Ȩ (CURRENT PROTOCOL = #1) ȩ {lcmd} '#1' means the device communicates with LW2 protocol. Ȩ (LCMD# LCMD: List all commands) 6.3.5. View Firmware Version of the CPU Ȩ (LCMD# PING: Always response PONG) Ȩ (LCMD# CT: Compile time) Command and Response #firmwareversion Ȩ ... ȩ {F} Ȩ (LCMD END) Ȩ (FW:)CrLf INFO: The response is longer, not all the lines can be seen in the example. Example 6.3.2. View Product Type ȩ {f} The device responds its name. Ȩ (FW:1.6.0b13 r99) Command and Response #producttype is the firmware version. It is followed by string which may indicate special versions. ȩ {i} 6.3.6. Connection Test Ȩ (I:)CrLf Simple test to see if the connection is established successfully. Example Command and Response ȩ {i} ȩ {PING} Ȩ (I:UMX-TPS-TX140) Ȩ (PONG!)CrLf 6.3.3. Device Label Query Example This command is for querying the label of the device which can be changed in the Status menu in LDC or by ȩ {ping} LW3 command, see the Set the Device Label section. Ȩ (PONG!) Command and Response #label #devicelabel 6.3.7. Compile Time ȩ {label} Returns the date, when the CPU firmware was compiled. Ȩ (LABEL=)CrLf Command and Response Example ȩ {CT} ȩ {label} Ȩ (Complied: )CrLf Ȩ (LABEL=UMX-TPS-TX140_ConferenceRoom) Example ȩ {ct} Ȩ (Compiled: Sep 30 2016 14:07:56)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 89

6.3.8. View Serial Number 6.3.11. Query Health Status The device responds its 8-digit serial number. Internal voltages and measured temperature values are shown. Command and Response #serialnumber Command and Response #status ȩ {S} ȩ {ST} Ȩ (SN:)CrLf Ȩ (ST·)CrLf Example Example ȩ {s} ȩ {st} Ȩ (SN:5A004254) Ȩ (ST CPU 12.16V 5.03V 3.30V 3.33V 3.37V 1.30V 1.86V 1.00V 53.22C 53.26C) The serial number structure can be found in the About the Serial Number section. 6.3.12. Restart the Device 6.3.9. View Installed Board The device can be restarted without unplugging power. Shows the hardware name and revision of the installed cards. Command and Response #reboot #restart Command and Response ȩ {RST} ȩ {IS} Ȩ Ȩ (SL#·0·)CrLf Example Ȩ (SL·END)CrLf ȩ {rst} Example Ȩ ȩ {is} The device reboots; no response is sent in this case. Ȩ (SL# 0 UMX-TPS-TX140K) 6.3.13. Restore Factory Default Settings Ȩ (SL END) Settings can be reset to factory default values as follows: The device reports its motherboard (slot 0). Command and Response 6.3.10. View Firmware for All Controllers ȩ {FACTORY=ALL} Shows the firmware versions of all installed controllers. Ȩ (FACTORY ALL…)CrLf Command and Response Example ȩ {FC} ȩ {factory=all} Ȩ (CF·)CrLf Ȩ (FACTORY ALL…). Ȩ (CF·)CrLf All settings and parameters are reset to factory default, see the table in the Factory Default Settings section. Ȩ … #factory Ȩ (CF END)CrLf Example ȩ {fc} Ȩ (CF UMX-TPS-TX140K 1.5.0b1 r53) Ȩ (CF END) The device has one control panel.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 90

6.4. AV Port Settings 6.4.2. Mute Output 6.4.1. Switch an Input to the Outputs Mute the output. The output signal is turned off. Switching an input to output . Following commands with A, V, AV parameter value can take effect Command and Response #mute #lock #unmute #unlock 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. #crosspoint #switch Ȩ (1MT)CrLf Command and Response Example ȩ {@} ȩ {#01 A} Ȩ (O•I)CrLf Ȩ (1MT01 A) Parameters ATTENTION! Muting does not change the state of the crosspoint but disables the output itself. This way Parameter Parameter description Value Value description the last connection can be easily restored with an unmute command. Switching a muted output does not unmute the output. Signal type of the layer A audio layer V video layer 6.4.3. Unmute Output AV audio & video layer Unmute the output. Output port O1 Command and Response Input port I1..I6 Device-dependent, see the Port Numbering section 0 Using the '0' (zero) value the input will be disconnected and ȩ {+} no signal will appear on the output. Ȩ (0MT)CrLf INFO: The parameter usually can be skipped for legacy purposes. In this case, the devices change Example all (Video & Audio) layers but using status commands it displays information about only the Video layer. ȩ {+01 V} Please use AV option, when available. Ȩ (0MT01 V) Example 1 INFO: Unmuting an output makes the previous connection active as the crosspoint state has not been ȩ {2@1 AV} changed by the muting command, only the output was disabled. Ȩ (O01 I02 AV) 6.4.4. Lock Output I2 audio and I2 video input ports are switched to O1 output port. Locking an output port. Output’s state cannot be changed until unlocking. Example 2 Command and Response ȩ {0@1} ȩ {#>} Ȩ (O01 I00) Ȩ (1LO)CrLf ATTENTION! The response of this command does not show if the output is muted. To check the mute Example status a separate query has to be used like {VC}. ȩ {#>01 A} ATTENTION! Analog video inputs does not contain embedded audio. If you use the AV option in case of Ȩ (1LO01 A) VGA input (I1) the audio will be switched to the analog audio input 1 (I1) and in case of DVI-A input (I5) the audio will be switched to the analog audio input 2 (I5).

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 91

6.4.5. Unlock Output 6.4.7. View Crosspoint Size Unlocking an output port. The connection on output can be changed. Shows the physical crosspoint size. Command and Response Command and Response ȩ {+<} ȩ {getsize•} Ȩ (0LO)CrLf Ȩ (SIZE=)CrLf Example Parameters ȩ {+<01 V} Parameter Parameter description Value Value description Ȩ (0LO01 V) Crosspoint size x O1 video output port is unlocked. Signal type of the layer A audio layer V video layer INFO: The device issues the above response regardless of the previous state of the output (either it was AV audio & video layer locked or unlocked). Example 6.4.6. View Connection State on the Output ȩ {GETSIZE AV} Viewing the crosspoint state of the device; showing the input port numbers connected to the outputs. Ȩ (SIZE=6x1 V) Command and Response #crosspoint #switch Ȩ (SIZE=5x1 A) ȩ {VC•} The device has a video crosspoint (6 inputs and 1 output) and an audio crosspoint (5 inputs and 1 output). Ȩ (ALL)CrLf 6.4.8. Change the Video Autoselect Mode Parameters The autoselect mode of the video outputs can be changed. O01 shows the corresponding output’s connection state. Command and Response #autoselect Parameter Parameter description Value Value description ȩ {AS_V=;} Signal type of the layer A audio layer Ȩ (AS_V=;)CrLf V video layer Parameters AV audio & video layer State letters Parameter Parameter description Value Value description Showing the E autoselect is enabled Letter State Example Autoselect state D autoselect is disabled L Output is locked L01 The autoselect mode F First detect mode M Output is muted M01 setting L Last detect mode U Output is locked and muted U01 P Priority detect mode Example The output port numbers are listed in Port Numbering section. ȩ {VC AV} Example Ȩ (ALLV 01 02) ȩ {as_v1=E;P} Ȩ (ALLA 02 02 02) Ȩ (AS_V1=E;P) I1 video input port is connected to the O1 video output port; I2 video input port is connected to the O2 video The Autoselect mode of audio output1 is enabled and set to Priority mode. output port; I2 audio input port is connected to all the audio output ports (O1, O2, O3). INFO: The Autoselect mode can be queried by typing the {as_v=?} command.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 92

6.4.9. Change the Audio Autoselect Mode 6.4.11. Change the Audio Input Priorities The autoselect mode of the audio output can be changed. The settings of audio input priority can be changed as follows. Command and Response Command and Response ȩ {AS_A=;} ȩ {PRIO_A=;;…;} Ȩ (AS_A=;)CrLf Ȩ (PRIO_A=;;…;)CrLf Parameters Parameters See the previous section. See the previous section. Example Example ȩ {as_a1=E;P} ȩ {prio_a1=1;0;2} Ȩ (AS_A1=E;P) Ȩ (PRIO_A1=1;0;2) The Autoselect mode of audio output1 is enabled and set to Priority mode. Input 2 has the highest priority (0), Input 1 has the second highest (1). Input 3 has the lowest priority (2). INFO: The Autoselect mode can be queried by typing the {as_a=?} command. ATTENTION! Always set all the priority of the ports when changing, otherwise, the change will not be executed and the response will be the current setting (like querying the priority setting). 6.4.10. Change the Video Input Priorities INFO: The audio priorities can be queried by typing the {prio_a=?} command. The settings of video input priority can be changed as follows. Command and Response ȩ {PRIO_V=;;…;} Ȩ (PRIO_V=;;…;)CrLf Parameters

Parameter Parameter description Value Value description Priority number of the input 0-5, 0: highest priority ports 31 5: lowest priority 31: skip the port from the priority list See more details about port numbering in the Port Numbering section. Example ȩ {prio_v1=1;0;2;3} Ȩ (PRIO_V1=1;0;2;3) ATTENTION! Always set all the priority of the ports when changing, otherwise, the change will not be executed and the response will be the current setting (like querying the priority setting). INFO: The video priorities can be queried by typing the {prio_v=?} command.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 93

6.5. Network Configuration 6.5.3. Set the Subnet Mask 6.5.1. Query the Current IP Status Subnet mask can be set as follows. The IP address settings can be queried as follows. #dhcp #ipaddress #network Command and Response ȩ Command and Response {IP_NETMASK=} Ȩ (IP_NETMASK=)CrLf ȩ {IP_STAT=?} Parameters Ȩ (IP_STAT=;;;)CrLf Parameters See the Query the Current IP Status section. Example Parameter Parameter description Value Value description ȩ {ip_netmask=255.255.255.0} Assignment of the IP address 0 static Ȩ 1 dynamic (DHCP) (IP_NETMASK=255.255.255.0) IP address (four decimal octets separated by dots) INFO: The subnet mask can be queried by typing the {ip_address=?} command. The response contains the fix IP subnet mask that is stored in the device even if DHCP is enabled; in this case, this IP subnet Subnet mask (four decimal octets separated by dots) mask is not valid. Gateway address (four decimal octets separated by dots) 6.5.4. Set the Gateway Address Example Gateway address can be set as follows. ȩ {ip_stat=?} Command and Response Ȩ (IP_STAT=0;192.168.0.100;255.255.255.0;192.168.0.1) ȩ {IP_GATEWAY=} The device has a static (fix) IP address: 192.168.0.100; the subnet mask is 255.255.255.0, the gateway address is 192.168.0.1. Ȩ (IP_GATEWAY=)CrLf Parameters 6.5.2. Set the IP Address See the Query the Current IP Status section. IP address can be set as follows. Example Command and Response ȩ {ip_gateway=192.168.0.50} ȩ {IP_ADDRESS=;} Ȩ (IP_GATEWAY=192.168.0.50) Ȩ (IP_ADDRESS=;)CrLf Parameters INFO: The gateway address can be queried by typing the {ip_gateway=?} command. The response contains the static IP gateway address that is stored in the device even if DHCP is enabled. In that case, the latest See the previous section. valid gateway address (for static IP) is stored. Example 6.5.5. Apply Network Settings ȩ {ip_address=0;192.168.0.110} Apply the network settings and restart the network interface. Ȩ (IP_ADDRESS=0;192.168.0.110) Command and Response INFO: The IP address can be queried by typing the {ip_address=?} command. The response contains the ȩ {ip_apply} fix IP address that is stored in the device even if DHCP is enabled; in this case, this IP address is not valid. Ȩ (IP_APPLY)CrLf Example ȩ {ip_apply} Ȩ (IP_APPLY)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 94

6.5.6. Enable/disable the Ethernet Port 6.6.2. RS-232 Parameters Settings Command and Response The parameters of local RS -232 port can be set as follows. ȩ {ETH_ENABLE=} Command and Response Ȩ (ETH_ENABLE=)CrLf ȩ {RS232_LOCAL_FORMAT=;;;} Parameters Ȩ (RS232_LOCAL_FORMAT=;;;)CrLf If the parameter is 0, the port is disabled. If its value is 1, the port is enabled. Parameters

Example Parameter Parameter description Value Parameter value ȩ {ETH_ENABLE=1} X No change Ȩ (ETH_ENABLE=1) 4800 4800 6.6. RS-232 Settings 7200 7200 9600 9600 6.6.1. RS-232 Mode Setting Baud rate 14400 14400 RS -232 mode can be set as follows. See more details about RS -232 modes in the Serial Interface section. 19200 19200 #rs232 #rs-232 #serial #commandinjection 38400 38400 Command and Response 57600 57600 ȩ {RS232=} 115200 115200 Ȩ (RS232=)CrLf X No change Parameters Data bit 8 8 Parameter Parameter description Value Parameter value 9 9 CONTROL Control mode X No change RS-232 operation mode CI Command injection mode N None Parity PASS Event Manager (Pass-through) mode E Even Example O Odd ȩ {rs232=control} X No change Ȩ 1 1 (RS232=CONTROL) Stop Bit 1,5 1,5 INFO: The current RS-232 mode can be queried by the {RS232=?} command. 2 2 Example ȩ {rs232_local_format=9600;8;O;X} Ȩ (RS232_LOCAL_FORMAT=9600;8;O;X) Explanation RS -232 port is set as the following: the baud rate to 9600, data bit to 8, parity to odd, and stop bit is not changed, remained 1. INFO: The actual RS-232 parameters can be queried by the {RS232_LOCAL_FORMAT=?} command.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 95

6.6.3. RS-232 Control Protocol Port Setting 6.6.5. Serial Port Protocol Setting (Link port) The control protocol of local RS -232 port can be set as follows. This command sets the communication protocol of the link RS-232 port (TPS port). Command and Response #protocol Command and Response ȩ {RS232_LOCAL_PROT=} ȩ {RS232_LINK_PROT=} Ȩ (RS232_LOCAL_PROT=)CrLf Ȩ (RS232_LINK_PROT=)CrLf Parameters Parameters

Parameter Parameter description Value Parameter value See the previous section. LW2 LW2 control protocol Example RS-232 control protocol LW3 LW3 control protocol ȩ {RS232_LINK_PROT=LW2} Example Ȩ (RS232_LINK_PROT=LW2) ȩ {rs232_local_prot=lw2} 6.7. GPIO Port Configuration Ȩ (RS232_LOCAL_PROT=LW2) DIFFERENCE: This section refers to the UMX-TPS-TX130, -TX140, TX140K and TX140-Plus models only. INFO: The actual RS-232 parameters can be queried by the {RS232_LOCAL_PROT=?} command. 6.7.1. Setting the Level and Direction for Each Pins 6.6.4. Serial Port Format Setting (Link port) GPIO pins can be configured as follows. See more details about GPIO connector inthe GPIO - General This command sets the format of the link RS-232 port (TPS port). Purpose Input/Output Ports section and about the interface in the GPIO Interface section. Command and Response Command and Response #gpio ȩ ȩ {RS232_LINK_FORMAT=;;;} {GPIO=

;} Ȩ Ȩ (RS232_LINK_FORMAT=;;;)CrLf (GPIO=;)CrLf Parameters Parameters See the previous section. Parameter Parameter description Value Value description Example GPIO pin number 0-6 static The direction of the communication I Input ȩ {RS232_LINK_FORMAT=38400;X;X;1} O Output Ȩ (RS232_LINK_FORMAT=38400;8;N;1) The level of the pin L Low The databit and parity settings have not been changed. H High T Toggle between low and high Example ȩ {gpio1=O;H} Ȩ (GPIO1=O;H) GPIO pin 1 is set to output with high level. INFO: The current GPIO pin configuration can be queried by typing the {GPIO=?} command.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 96

6.8. LW2 Commands – Quick Summary

General LW2 Commands List of All Available LW2 Commands Unmute Output ȩ {lcmd} ȩ {+} View Product Type Lock Output ȩ {i} ȩ {#>} Device Label Query Unlock Output ȩ {label} ȩ {+<} Query Control Protocol View Connection State on the Output ȩ {P_?} ȩ {VC•} View Firmware Version of the CPU View Crosspoint Size ȩ {F} ȩ {getsize•} Connection Test Change the Video Autoselect Mode ȩ {PING} ȩ {AS_V=;} Compile Time Change the Audio Autoselect Mode ȩ {CT} ȩ {AS_A=;} View Serial Number Change the Video Input Priorities ȩ {S} ȩ {PRIO_V=;;…;} View Installed Board Change the Audio Input Priorities ȩ {IS} ȩ {PRIO_A=;;…;} View Firmware for All Controllers Network Configuration ȩ {FC} Query the Current IP Status Query Health Status ȩ {IP_STAT=?} ȩ {ST} Set the IP Address Restart the Device ȩ {IP_ADDRESS=;} ȩ {RST} Set the Subnet Mask Restore Factory Default Settings ȩ {IP_NETMASK=} ȩ {FACTORY=ALL} Set the Gateway Address AV Port Settings ȩ {IP_GATEWAY=} Switch an Input to the Outputs Apply Network Settings ȩ {@} ȩ {ip_apply} Mute Output Enable/disable the Ethernet Port ȩ {#} ȩ {ETH_ENABLE=}

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

6. LW2 Programmer's Reference UMX-TPS-TX100 series – User's Manual 97

RS-232 Settings RS-232 Mode Setting ȩ {RS232=} RS-232 Parameters Settings ȩ {RS232_LOCAL_FORMAT=;;;} RS-232 Control Protocol Port Setting ȩ {RS232_LOCAL_PROT=} Serial Port Format Setting (Link port) ȩ {RS232_LINK_FORMAT=;;;} Serial Port Protocol Setting (Link port) ȩ {RS232_LINK_PROT=} GPIO Port Configuration Setting the Level and Direction for Each Pins ȩ {GPIO=

;}

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 98

LW3 Programmers’ Reference 7The device can be controlled through Lightware 3 (LW3) protocol commands to ensure the compatibility with other Lightware products. The supported LW3 commands are described in this chapter.

ç Overview ç Instructions for the Terminal Application Usage ç Protocol Rules ç System Commands ç Cleartext Login Protection ç Video Port Settings ç Audio Port Settings ç Analog Audio Input Level Settings ç Event Manager Basics ç Event Manager Tool Kit ç Variable-Management ç Ethernet Port Configuration ç Ethernet Tool Kit ç Ethernet Message Sending ç HTTP Messaging ç TCP Message Recognizer ç RS-232 Port Configuration ç RS-232 Message Sending ç RS-232 Message Recognizer ç Sending CEC Commands ç Infrared Port Configuration ç Infrared Message Sending ç GPIO Port Configuration ç EDID Management ç LW3 Commands - Quick Summary

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 99

7.1. Overview 7.3. Protocol Rules The Lightware Protocol #3 (LW3) is implemented in almost all new Lightware devices (matrix switchers, 7.3.1. LW3 Tree Structure and Command Structure (examples) signal extenders and distribution amplifiers) since 2012. The protocol is ASCII-based and all commands are terminated with a carriage return (Cr, ‘\r’) and line feed (Lf, ‘\n’) pair. It is organized as a tree structure  /  that provides outstanding flexibility and user-friendly handling with ‘nodes’, ‘properties’ and ‘methods’. The MEDIA  VIDEO Advanced View of the Lightware Device Controller software is the perfect tool for browsing and learning how  XP the LW3 protocol can be used in practice. SourcePortCount SourcePortStatus Path of the method/property 7.2. Instructions for the Terminal Application Usage DestinationPortCount DestinationPortStatus Command type Method/property Terminal Application DestinationPortAutoselect (GET/SET/CALL/MAN) Parameters The LW3 protocol commands can be applied to the [...]  receiver using a terminal application. You need to I1  I2 install one of them to your control device, for example  I3 Command ç CALL /MEDIA/VIDEO/XP:switch(I1:O1) Putty or CLI. #terminal  I4 Response æ mO /MEDIA/VIDEO/XP:switch  I5 Establishing Connection  I6  O1 Follow the steps for establishing connection to the Prefix of the response Method/property receiver:  AUDIO  UART Path of the method/property Step 1. Connect the receiver to a LAN over Ethernet.  IR Step 2. Open the terminal application (e.g. Putty).  GPIO  ETHERNET Step 3. Add the IP address of the device (default:  EDID 192.168.0.100) and the port number (6107).  SYS Step 4. Select the Raw connection type, and open the  MANAGEMENT connection. [...] Once the terminal window is opened, you can enter 7.3.2. General Rules the LW3 protocol commands which are listed in the ▪ All names and parameters are case-sensitive. following sections. ▪ The nodes are separated by a slash (‘/’) character. ▪ The node name can contain the elements of the English alphabet and numbers. ▪ The command lines have to be closed by Carriage return and Line Feed (CrLf). ▪ Use the TCP port no. 6107 when using LW3 protocol over Ethernet. ▪ The length of a line (command/response, command type / prefix, path, method/property and parameters together) can be max. 800 byte. ▪ When a command is issued by the device, the received response cannot be processed by the CPU. ▪ The node paths describe the exact location of the node, listing each parent node up to the root.

LW3 protocol command communication in a terminal window

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 100

7.3.3. Legend for the Control Commands SET command Command and Response – Example The SET command can be used to modify the value of a property. Use the dot character (.) when addressing the property: ç GET·/MEDIA/VIDEO/I2.SignalPresent ç æ pr·/MEDIA/VIDEO/I2.SignalPresent= SET /MEDIA/VIDEO/I1.ColorSpaceMode=0 æ pw /MEDIA/VIDEO/I1.ColorSpaceMode=0 Format Description CALL command Input port number Output port number A method can be invoked by the CALL command. Use the colon character (:) when addressing the method: Input or output port number ç CALL /MEDIA/VIDEO/XP:switch(I1:O1) Location number æ mO /MEDIA/VIDEO/XP:switch Specific property defined and described in the command MAN command Batched parameters: the underline means that more expressions or parameters The manual is a human readable text that describes the syntax and provides a hint for how to use the can be placed by using a semicolon, e.g. I2;I4;I5 or F27:E1;F47:E2 primitives. For every node, property and method in the tree there is a manual, type the MAN command to get  Sent command the manual:  Received response ç MAN /MEDIA/VIDEO/O1.Pwr5vMode · Space character æ pm /MEDIA/VIDEO/O1.Pwr5vMode ["0" | "1" | "2"] 0 - Auto, 1 - Always On, 2 - Always Off Further not listed are defined at each commands. 7.3.5. Prefix Summary 7.3.4. Command Types DEFINITION: The prefix is a 2-character long code that describes the type of the response. GET command The following prefixes are defined in the LW3 protocol: The GET command can be used to get the child nodes, properties and methods of a specific node. It can also Prefix Description Prefix Description be used to get the value of a property. Use the dot character (.) when addressing a property: n- a node pm a manual for the property ç GET /.SerialNumber nE an error for a node m- a method æ pr /.SerialNumber=87654321 nm a manual for a node mO a response after a success method execution GETALL command pr a read-only property mF a response after a failed method execution The GETALL command can be used to get all child nodes, properties and methods of a node with one pw read-write property mE an error for a method command. pE an error for the property mm a manual for a method ç GETALL /MEDIA/UART 7.3.6. Error Messages æ ns /MEDIA/UART/P1 There are several error messages defined in the LW3 protocol, all of them have a unique error number. æ ns /MEDIA/UART/P2 æ pr /MEDIA/UART.PortCount=2 ç CALL /MEDIA/VIDEO/XP:switch(IA:O1) æ pr /MEDIA/UART.PortUi=P1:12209;P2:12224 æ mE /MEDIA/VIDEO/XP:switch %E004:Invalid value æ pr /MEDIA/UART.P1=Local RS-232 æ pr /MEDIA/UART.P2=TPS out RS-232

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 101

7.3.7. Escaping Subscribe to a Node Unsubscribe from a Node DEFINITION: An escape sequence is a sequence of characters that does not represent itself when used ç OPEN /MEDIA/VIDEO ç CLOSE /MEDIA/VIDEO inside a character or string literal, but is translated into another character or a sequence of characters. æ o- /MEDIA/VIDEO æ c- /MEDIA/VIDEO

Property values and method parameters can contain characters which are used as control characters in the Subscribe to Multiple Nodes Unsubscribe from Multiple Nodes 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). OPEN /MEDIA/VIDEO/* ç CLOSE /MEDIA/VIDEO/* æ Control characters are the following: \ { } # % ( ) \r \n \t o- /MEDIA/VIDEO/* æ c- /MEDIA/VIDEO/* The original message: CALL /MEDIA/UART/P1:sendMessage(Set(01)) Get the Active Subscriptions ç The escaped message: CALL /MEDIA/UART/P1:sendMessage(Set\(01\)) OPEN æ o- /MEDIA/VIDEO 7.3.8. Signature æ o- /EDID DEFINITION: The signature is a four-digit-long hexadecimal value that can be optionally placed before æ o- /DISCOVERY every command to keep a command and the corresponding responses together as a group. Each line is terminated with a carriage return (Cr, ‘\r’) and line feed (Lf, ‘\n’) characters. In several cases the 7.3.10. Notifications about the Changes of the Properties number of the lines in the response cannot be determined in advance, e.g. the client intends to receive for the When the value of a property is changed and the user is subscribed to the node, which the property belongs whole response and also wants to be sure, that the received lines belong together and to the same command. to, an asynchronous notification is generated. This is notification is called as the ‘change message’. The In these cases, a special feature the ‘signature’ can be used. The response to that particular command will format of such a message is very similar to the response for the GET command: also be preceded by the signature, and the corresponding lines will be between brackets: æ CHG /EDID.EdidStatus=F48:E1 ç 1700#GET /EDID.* æ {1700 A Short Example of How to Use the Subscription æ pr /EDID.EdidStatus=F89:E1;D1:E2;D1:E3;D1:E4;F89:E5 There are two independent users controlling the device through two independent connections (Connection #1 æ m- /EDID:copy and Connection #2). The events in the rows occur after each other. æ m- /EDID:delete ç OPEN /MEDIA/AUDIO/O3 æ æ o- /MEDIA/AUDIO/O3 m- /EDID:reset Connection #1 æ m- /EDID:switch ç GET /MEDIA/AUDIO/O3.VolumePercent æ æ pw /MEDIA/AUDIO/O3.VolumePercent=100.00 } m- /EDID:switchAll æ } ç GET /MEDIA/AUDIO/O3.VolumePercent æ pw /MEDIA/AUDIO/O3.VolumePercent=100.00 INFO: The lines of the signature are also Cr and Lf terminated. Connection #2 ç SET /MEDIA/AUDIO/O3.VolumePercent=50.00 7.3.9. Subscription æ pw /MEDIA/AUDIO/O3.VolumePercent=50.00 } DEFINITION: Subscription to a node means that the user will get a notification if a property of the node æ CHG /MEDIA/AUDIO/O3.VolumePercent=50.00  Connection #1 changes. The first user (Connection #1) set a subscription to a node. Later the other user (Connection #2) made a change, A user can subscribe to any node. These notifications are asynchronous messages and are useful to keep and thanks for the subscription, the first user got a notification about the change. the client application up to date, without having to periodically poll the node to detect a changed property. When the user does not want to be informed about the changes anymore, he can simply unsubscribe from the node. ATTENTION! The subscriptions are handled separately for connections. Hence, if the connection is terminated all registered subscriptions are deleted. After reopening a connection all subscribe commands have to be sent in order to get the notifications of the changes on that connection.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 102

7.4. System Commands 7.4.4. Query the Firmware Version 7.4.1. Query the Product Name Command and Response #firmwareversion The name of the product is a read-only parameter and cannot be modified. ç GET·/SYS/MB.FirmwareVersion æ pr·/SYS/MB.FirmwareVersion= Command and Response ç GET·/.ProductName Example æ pr·/.ProductName= ç GET /SYS/MB.FirmwareVersion æ pr /SYS/MB.FirmwareVersion=1.3.2b1 r43 Example ç GET /.ProductName 7.4.5. Resetting the Device æ pr /.ProductName=UMX-TPS-TX140-Plus The transmitter can be restarted – the current connections (LAN, RS-232) will be terminated. 7.4.2. Set the Device Label Command and Response #reboot #reset #restart ATTENTION! The device label can be changed to a custom text in the Status tab of the LDC software. This ç CALL·/SYS:reset() writable parameter is not the same as the ProductName parameter. #devicelabel æ mO·/SYS:reset= The default format of the device label is: LW__ Example Command and Response ç CALL /SYS:reset() ç SET·/MANAGEMENT/UID.DeviceLabel= æ mO /SYS:reset= æ pw·/MANAGEMENT/UID.DeviceLabel= 7.4.6. Restore the Factory Default Settings The Device Label can be 39 character length and ASCII characters are allowed. Longer names are truncated. Command and Response #factorydefaults Example ç CALL·/SYS:factoryDefaults() ç SET /MANAGEMENT/UID.DeviceLabel=UMX-TPS_Control_room æ mO·/SYS:factoryDefaults= æ pw /MANAGEMENT/UID.DeviceLabel=UMX-TPS_Control_room Example 7.4.3. Query the Serial Number ç CALL /SYS:factoryDefaults() Command and Response æ mO /SYS:factoryDefaults= ç GET·/.SerialNumber The device is restarted, current connections are terminated, and the default settings are restored. See the æ pr·/.SerialNumber= complete list in the Factory Default Settings section.

Example ç GET /.SerialNumber æ pr /.SerialNumber=87654321

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 103

7.4.7. Lock the Front Panel Buttons 7.4.9. Dark Mode

Command and Response #frontpanel #controllock #button This command turns LEDs off the on the transmitter. #darkmode ç SET /MANAGEMENT/UI.ControlLock= Command and Response æ pw /MANAGEMENT/UI.ControlLock= ç SET /MANAGEMENT/UI/DARKMODE.DarkModeEnable= Parameters æ pw /MANAGEMENT/UI/DARKMODE.DarkModeEnable=

Identifier Parameter description Value Explanation Parameters None - All functions of the front panel button are 1 Identifier Parameter description Value Explanation enabled. true Dark mode is enabled. Locked - The front panel buttons are locked and Status of the dark mode false Dark mode is disabled. Control lock status of 2 they can be unlock by pressing Audio select and the front panel buttons Show me buttons or with LW3 protocol command. Example Force locked - Locking and unlocking of the front ç SET /MANAGEMENT/UI/DARKMODE.DarkModeEnable=true 3 panel buttons are possible only via protocol æ command. pw /MANAGEMENT/UI/DARKMODE.DarkModeEnable=true 7.4.10. Dark Mode Delay Example The LEDs on the front panel turn off after some delay time , which can be set in seconds. ç SET /MANAGEMENT/UI.ControlLock=1 æ pw /MANAGEMENT/UI.ControlLock=1 Command and Response 7.4.8. Disable the Default Function of the Front Panel Buttons ç SET /MANAGEMENT/UI/DARKMODE.DarkModeDelay= æ This setting makes possible to set an event with Event Manager where the Condition is pressing a button pw /MANAGEMENT/UI/DARKMODE.DarkModeDelay= and the original function of the chosen button will not be executed. Parameters Command and Response Delay time in seconds. ç SET /MANAGEMENT/UI/BUTTONS/.DefaultFunctionEnable= Example æ pw /MANAGEMENT/UI/BUTTONS/.DefaultFunctionEnable= ç SET /MANAGEMENT/UI/DARKMODE.DarkModeDelay=10 Parameters æ pw /MANAGEMENT/UI/DARKMODE.DarkModeDelay=10

Identifier Parameter description Value Parameter value B1 Video select Button identifier number B2 Audio select B2 Show me button Enable The function is enabled. Status of the default function Disable The function is disabled.

Example ç SET /MANAGEMENT/UI/BUTTONS/B1.DefaultFunctionEnable=false æ pw /MANAGEMENT/UI/BUTTONS/B1.DefaultFunctionEnable=false

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 104

7.4.11. Running a Macro 7.5.2. Login the Device DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package Command and Response v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- ç CALL·/LOGIN:login() UMX-TPS series). æ mO·/LOGIN:login DEFINITION: Macro is a batch of pre-defined commands stored in the device. #macro Example You can create your custom macros in a file, upload to the device and run at any time. The uploading can be done over LDC, see the Uploading New Macros into the Internal Device Configuration Preset section. The ç CALL /LOGIN:login(pr0t3ctED) following LW3 command is suitable only for running a macro. æ mO /LOGIN:login Command and Response After a successful login, the LoggedIn property becomes true and the LW3 tree is available. ç CALL·/CTRL/MACROS:run() 7.5.3. Logout from the Device æ mO·/CTRL/MACROS:run Command and Response Example ç CALL·/LOGIN:logout() ç CALL /CTRL/MACROS:run(Macro1) æ mO·/LOGIN:logout æ mO /CTRL/MACROS:run Example 7.5. Cleartext Login Protection ç CALL /LOGIN:logout(pr0t3ctED) æ DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package mO /LOGIN:logout v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- After a successful logout, the LoggedIn property becomes false and the LW3 tree is protected. UMX-TPS series). 7.5.4. Enable the Cleartext Login Function This cleartext login tool allows setting a password for login, thus, any change in the device can be performed only after a successful login – coming from any control interface (RS-232, Ethernet, etc…). The login is valid ATTENTION! This property can be changed only, if the LoggedIn property is true. until a TCP socket break in case of Ethernet connection. #login Command and Response ATTENTION! If the login is enabled, the miniweb is not available. ç SET·/LOGIN:LoginEnable= INFO: The login password is erased and the login is disabled when restoring the factory default values. æ pw·/LOGIN.LoginEnable= The following can be queried without login: Parameters ▪ ProductName If the parameter is true (or 1), the Cleartext login function is enabled, if the parameter is false (or ▪ PartNumber and SerialNumber 0), the function is disabled. Please note that the function can be enabled without setting a password by the ▪ FirmwareVersion and Firmware PackageVersion setPassword method. ▪ MacAddress Example 7.5.1. Setting the Login Password ç SET /LOGIN.LoginEnable=true Command and Response æ pw /LOGIN.LoginEnable=true ç CALL·/LOGIN:setPassword() æ mO·/LOGIN:setPassword Example ç CALL /LOGIN:setPassword(pr0t3ctED) æ mO /LOGIN:setPassword

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 105

7.6. Video Port Settings The Most Common Received Port Status Responses INFO: Video port numbering can be found in the Port Numbering section. #status T 0 0 A A 7.6.1. Query the Status of Source Ports 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 T00AA Unlocked, No embedded Not Not Command and Response Unmuted Reserved Reserved Reserved Reserved No signal audio encrypted connected ç GET·/MEDIA/VIDEO/XP.SourcePortStatus æ pr·/MEDIA/VIDEO/XP.SourcePortStatus=;;<…>; T 0 0 A B The response contains 5 ASCII characters for each port. The first character indicates the mute/lock state, 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 1 the next four characters represent a 2-byte HEX code showing the current state of the input ports. T00AB Unlocked, No embedded Not Unmuted Reserved Reserved Reserved Reserved No signal Connected Example audio encrypted ç GET /MEDIA/VIDEO/XP.SourcePortStatus T 0 0 A F æ pr /MEDIA/VIDEO/XP.SourcePortStatus=M00AA;T00AF;T00AA;T00EF;T000A;T002E 0 0 0 0 0 0 0 0 1 0 1 0 1 1 1 1 T00AF Unlocked, Parameters No embedded Not Signal Unmuted Reserved Reserved Reserved Reserved Connected Letter (Character 1) M0 0 A A audio encrypted presents Mute state Lock state T 0 0 E F T Unmuted Unlocked Letter Mute / Lock status Reserved character, always 0. 0 0 0 0 0 0 0 0 1 1 1 0 1 1 1 1 L Unmuted Locked Byte 1 T00EF Unlocked, Reserved character, always 0. Unmuted Embedded Not Signal M Muted Unlocked Embedded audio / HDCP status Reserved Reserved Reserved Reserved Connected Byte 2 audio presents encrypted presents U Muted Locked Signal present / Connection status T 0 0 B F Byte 1 Byte 2 0 0 0 0 0 0 0 0 1 0 1 1 1 1 1 1 T00BF Unlocked, Character 2 Character 3 Character 4 Character 5 No embedded Signal Unmuted Reserved Reserved Reserved Reserved Encrypted Connected BIT 7-6 BIT 5-4 BIT 3-2 BIT 1-0 BIT 7-6 BIT 5-4 BIT 3-2 BIT 1-0 audio presents Signal Embedded Connection Reserved Reserved Reserved Reserved HDCP status present T 0 0 F F audio status status status 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 T00FF Unlocked, 0 0 Unknown Embedded Signal Unmuted Reserved Reserved Reserved Reserved Encrypted Connected 0 1 Reserved audio presents presents No Not Not 1 0 embedded No signal Only for analog video ports: Character 5 is E (11 10) which means signal is present but the cable is not Reserved Reserved Reserved Reserved encrypted connected audio connected. The explanation is analog video ports have no hotplug signal which indicates the connection Embedded Signal status. 1 1 audio Encrypted Connected presents presents T 0 0 E F 0 0 0 0 0 0 0 0 1 1 1 0 1 1 1 1 T00EF Unlocked, Embedded Not Signal Unmuted Reserved Reserved Reserved Reserved Connected audio presents encrypted presents

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 106

7.6.2. Query the Status of Destination Port 7.6.5. Switching Video Input

Command and Response #status Command and Response #crosspoint #switch ç GET·/MEDIA/VIDEO/XP.DestinationPortStatus ç CALL·/MEDIA/VIDEO/XP:switch(:) æ pr·/MEDIA/VIDEO/XP.DestinationPortStatus=;;<…>; æ mO·/MEDIA/VIDEO/XP:switch

Parameters Example The response contains 5 ASCII characters for each port. The first character indicates the ç CALL /MEDIA/VIDEO/XP:switch(I2:O1) mute/lock state, the next 2-byte long HEX code showing the current state of the output port. æ mO /MEDIA/VIDEO/XP:switch Example Example 2 ç GET /MEDIA/VIDEO/XP.DestinationPortStatus ç CALL /MEDIA/VIDEO/XP:switch(0:O1) æ pr /MEDIA/VIDEO/XP.DestinationPortStatus=M00BF æ mO /MEDIA/VIDEO/XP:switch Legend When using 0 (zero) value as an input, the input will be disconnected and no signal will appear on the output. See at previous section. 7.6.6. Querying the Connected Input Port Number Example and Explanation DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- M 0 0 B F UMX-TPS series). 0 0 0 0 0 0 0 0 1 0 1 1 1 1 1 1 The response of this command shows the input port that is connected to the queried output port. Unlocked, No embedded Signal Command and Response #crosspoint Muted Reserved Reserved Reserved Reserved Encrypted Connected audio presents ç GET·/MEDIA/VIDEO/.ConnectedSource 7.6.3. Query the Video Crosspoint Setting æ pr·/MEDIA/VIDEO/.ConnectedSource= Command and Response Example ç GET·/MEDIA/VIDEO/XP.DestinationConnectionList ç GET /MEDIA/VIDEO/O1.ConnectedSource æ pr·/MEDIA/VIDEO/XP.DestinationConnectionList= æ pr /MEDIA/VIDEO/O1.ConnectedSource=I1

Example ç GET /MEDIA/VIDEO/XP.DestinationConnectionList æ pr /MEDIA/VIDEO/XP.DestinationConnectionList=I1 7.6.4. Disconnect Video Input

Command and Response #crosspoint #switch ç CALL·/MEDIA/VIDEO/XP:switch(0:) æ mO·/MEDIA/VIDEO/XP:switch

Example ç CALL /MEDIA/VIDEO/XP:switch(0:O1) æ mO /MEDIA/VIDEO/XP:switch Input ports are disconnected from the O1 port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 107

7.6.7. Query the Video Autoselect Settings 7.6.9. Query the Input Port Priority

Command and Response Command and Response ç GET·/MEDIA/VIDEO/XP.DestinationPortAutoselect ç GET·/MEDIA/VIDEO/XP.PortPriorityList æ pr·/MEDIA/VIDEO/XP.DestinationPortAutoselect=;;<…>; æ pr·/MEDIA/VIDEO/XP.PortPrioirtyList=;;<…>; Parameters The response shows the priority of each output one after another. The priority number can be from 0 to 31; 0 is the highest- and 30 is the lowest priority. 31 means that the port will be skipped from the priority list. Identifier Parameter description Value Parameter value Parameters Two-letter code of the E Autoselect is enabled. st The input port priority order of the given output port: ,,<…>, Autoselect settings – 1 letter D Autoselect is disabled. F First detect: the first active video input is selected. Example Priority detect: always the highest priority active ç GET /MEDIA/VIDEO/XP.PortPriorityList Two-letter code of the P Autoselect settings – 2nd letter video input will be selected. æ pr /MEDIA/VIDEO/XP.PortPriorityList=0,1,2,3,4,5 Last detect: always the last attached input is L Parameters switched to the output automatically. Example Output Video input port I1 I2 I3 I4 I5 I6 ç GET /MEDIA/VIDEO/XP.DestinationPortAutoselect Priority 0 1 2 3 4 5 æ pr /MEDIA/VIDEO/XP.DestinationPortAutoselect=EL Highest priority is assigned to I1 port. Explanation ATTENTION! The same priority number can be set to different input ports. When the priority numbers The response shows the settings of each output one by one. EL: the Autoselect is Enabled on output, selected match, the input port with the lowest port number will have the highest priority. mode is Last detect. For more details see The Autoselect Feature section. 7.6.10. Change the Input Port Priority 7.6.8. Change the Autoselect Mode Command and Response Command and Response #autoselect ç CALL·/MEDIA/VIDEO/XP:setAutoselectionPriority(\(\):);(\(\):) ç CALL·/MEDIA/VIDEO/XP:setDestinationPortAutoselect(;;<…>;) æ mO·/MEDIA/VIDEO/XP:setAutoselectionPrioirty æ mO·/MEDIA/VIDEO/XP.setDestinationPortAutoselect Parameters Parameters See the previous section. The parameter is the Priority number from 0 to 31, equal numbers are allowed (31 means that the port will be skipped from the priority list). An input port priority can be set on an output port. Many settings can Example 1 be executed by separating a semicolon (no space), see the example below. ç CALL /MEDIA/VIDEO/XP:setDestinationPortAutoselect(O1:EP) Example æ mO /MEDIA/VIDEO/XP:setDestinationPortAutoselect ç CALL /MEDIA/VIDEO/XP:setAutoselectionPriority(I1\(O1\):4;I2\(O1\):4) The setting is changed to EP: Autoselect is enabled (E); the mode is set to priority detect (P). æ mO /MEDIA/VIDEO/XP:setAutoselectionPriority Example 2 Explanation ç CALL /MEDIA/VIDEO/XP:setDestinationPortAutoselect(O1:D) æ mO /MEDIA/VIDEO/XP:setDestinationPortAutoselect The priority number of input 1 and Input 2 has been set to 4 on output 1. The example shows that certain control characters have been escaped: the backslash “\” character is inserted before the “(“ and “)” characters. The setting is changed to DPM: Autoselect is disabled (D). The other settings remain unchanged. Since the See more information about the escaping in the Escaping section. outputs are linked, the change will affect local and link out.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 108

7.6.11. Mute an Input Port 7.6.15. Mute Output

Command and Response #mute #unmute Command and Response ç CALL·/MEDIA/VIDEO/XP:muteSource() ç CALL·/MEDIA/VIDEO/XP:muteDestination() æ mO·/MEDIA/VIDEO/XP:muteSource æ mO·/MEDIA/VIDEO/XP:muteDestination

Example Example ç CALL /MEDIA/VIDEO/XP:muteSource(I1) ç CALL /MEDIA/VIDEO/XP:muteDestination(O1) æ mO /MEDIA/VIDEO/XP:muteSource æ mO /MEDIA/VIDEO/XP:muteDestination 7.6.12. Unmute an Input Port 7.6.16. Unmute Output

Command and Response Command and Response ç CALL·/MEDIA/VIDEO/XP:unmuteSource() ç CALL·/MEDIA/VIDEO/XP:unmuteDestination() æ mO·/MEDIA/VIDEO/XP:unmuteSource æ mO·/MEDIA/VIDEO/XP:unmuteDestination

Example Example ç CALL /MEDIA/VIDEO/XP:unmuteSource(I1) ç CALL /MEDIA/VIDEO/XP:unmuteDestination(O1) æ mO /MEDIA/VIDEO/XP:unmuteSource æ mO /MEDIA/VIDEO/XP:unmuteDestination 7.6.13. Lock an Input Port 7.6.17. Lock Output

Command and Response #mute #unmute#lock #unlock Command and Response ç CALL·/MEDIA/VIDEO/XP:lockSource() ç CALL·/MEDIA/VIDEO/XP:lockDestination() æ mO·/MEDIA/VIDEO/XP:lockSource æ mO·/MEDIA/VIDEO/XP:lockDestination

Example Example ç CALL /MEDIA/VIDEO/XP:lockSource(I1) ç CALL /MEDIA/VIDEO/XP:lockDestination(O1) æ mO /MEDIA/VIDEO/XP:lockSource æ mO /MEDIA/VIDEO/XP:lockDestination 7.6.14. Unlock an Input Port 7.6.18. Unlock Output

Command and Response Command and Response ç CALL·/MEDIA/VIDEO/XP:unlockSource() ç CALL·/MEDIA/VIDEO/XP:unlockDestination() æ mO·/MEDIA/VIDEO/XP:unlockSource æ mO·/MEDIA/VIDEO/XP:unlockDestination

Example Example ç CALL /MEDIA/VIDEO/XP:unlockSource(I1) ç CALL /MEDIA/VIDEO/XP:unlockDestination(O1) æ mO /MEDIA/VIDEO/XP:unlockSource æ mO /MEDIA/VIDEO/XP:unlockDestination

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 109

7.6.19. HDCP Setting (Input Port) 7.6.21. Test Pattern Color

HDCP capability can be enabled/disabled on the input ports, thus, non-encrypted content can be seen on a Command and Response non-HDCP compliant display. See more information in the HDCP Management section. ç SET·/MEDIA/VIDEO/.FreeRunColor= Command and Response #hdcp æ pw·/MEDIA/VIDEO/.FreeRunColor= ç SET·/MEDIA/VIDEO/.HdcpEnable= Parameters æ pw·/MEDIA/VIDEO/.HdcpEnable= RGB color in RR;GG;BB format (separated by semicolons). Parameters Example ç Identifier Parameter description Value Parameter value SET /MEDIA/VIDEO/I1.FreeRunColor=10;80;20 æ pw /MEDIA/VIDEO/I1.FreeRunColor=10;80;20 HDCP enable/disable true HDCP encryption is enabled. setting false HDCP encryption is disabled. The test pattern color is on VGA input (I1) is set to green. 7.6.22. Test Pattern Resolution Example ç SET /MEDIA/VIDEO/I2.HdcpEnable=true Command and Response æ pw /MEDIA/VIDEO/I2.HdcpEnable=true ç SET·/MEDIA/VIDEO/.FreeRunResolution= æ INFO: HDCP can be set for digital video inputs (I2, I3, I4) only. The function is unavailable on the analog pw·/MEDIA/VIDEO/.FreeRunResolution= inputs (I1, I5). Parameters 7.6.20. Test Pattern Generator Mode Identifier Parameter description Value Parameter value The output port can send a special image towards the sink device for testing purposes. The setting is 0 640x480p60 available on the input ports with the below-listed parameters. 1 720x480i60 Command and Response #testpattern #nosyncscreen 2 720x480p60 ç SET·/MEDIA/VIDEO/.FreeRunMode= 3 720x576i50 æ pw·/MEDIA/VIDEO/.FreeRunMode= 4 720x576p50 Parameters Applied resolution of the 5 800x600p60 Identifier Parameter description Value Parameter value test pattern generator 6 1024x768p60 Always off: the test pattern is not displayed on 0 7 1280x720p60 the output. 8 1280x1024p60 Test pattern generator Always on: the test pattern is displayed on the 1 mode output. 9 1280x1080i60 Auto: the test pattern is displayed if there is no 10 1920x1080p60 2 signal on the input port. 11 1920x1200p60

Example Example ç SET /MEDIA/VIDEO/I1.FreeRunMode=2 ç SET /MEDIA/VIDEO/I2.FreeRunResolution=10 æ pw /MEDIA/VIDEO/I1.FreeRunMode=2 æ pw /MEDIA/VIDEO/I2.FreeRunResolution=10

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 110

7.6.23. HDCP Setting (Output Port) 7.6.25. Color Space Setting (Output Port)

HDCP capability can be set to Auto/Always on the output ports, thus, non-encrypted content can be Command and Response #colorspace transmitted to a non-HDCP compliant display. See more information in the HDCP Management section. ç SET·/MEDIA/VIDEO/.ColorSpaceSetting= Command and Response #hdcp æ pw·/MEDIA/VIDEO/.ColorSpaceSetting= ç SET·/MEDIA/VIDEO/.HdcpModeSetting= Parameters æ pw·/MEDIA/VIDEO/.HdcpModeSetting= Identifier Parameter description Value Parameter value Parameters 0 Auto Identifier Parameter description Value Parameter value 1 RGB Color space conversion 0 Auto 2 YCbCr 4:4:4 HDCP mode 1 Always 3 YCbCr 4:2:2

Example Example ç SET /MEDIA/VIDEO/O1.HdcpModeSetting=0 ç SET /MEDIA/VIDEO/O1.ColorSpaceSetting=2 æ pw /MEDIA/VIDEO/O1.HdcpModeSetting=0 æ pw /MEDIA/VIDEO/O1.ColorSpaceSetting=2 7.6.24. HDMI Mode Settings (Output Port) 7.6.26. TPS Mode Settings Command and Response Command and Response #tpsmode ç SET·/MEDIA/VIDEO/.HdmiModeSetting= ç SET·/REMOTE/.tpsModeSetting= æ pw·/MEDIA/VIDEO/.HdmiModeSetting= æ pw·/REMOTE/.tpsModeSetting= Parameters Parameters Identifier Parameter description Value Parameter value Identifier Parameter description Value Parameter value 0 Auto A Auto 1 DVI H HDBaseT HDMI mode 2 HDMI 24 bit TPS mode L Long reach 3 HDMI 30 bit 1 LPPF1 4 HDMI 36 bit 2 LPPF2 Example INFO: See more information about TPS modes in the TPS Interface section. ç SET /MEDIA/VIDEO/O1.HdmiModeSetting=2 Example æ pw /MEDIA/VIDEO/O1.HdmiModeSetting=2 ç SET /REMOTE/S1.tpsModeSetting=A æ pw /REMOTE/S1.tpsModeSetting=A INFO: Use the GET command to query the parameter.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 111

7.7. Audio Port Settings Example and Explanation (for input 2, M000B): INFO: Audio port numbering can be found in the Port Numbering section. M 0 0 0 B

7.7.1. Query the Status of Source Ports Unlocked, 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 Muted Command and Response #status Reserved Reserved Reserved Reserved Reserved Reserved No signal Connected ç GET·/MEDIA/AUDIO/XP.SourcePortStatus The Most Common Received Port Status Responses æ pr·/MEDIA/AUDIO/XP.SourcePortStatus=;;<…>; T 0 0 0 A The response contains 5 ASCII characters for each port. The first character indicates the mute/lock state, the next four characters represent a 2-byte HEX code showing the current state of the input ports. T000A Unlocked, 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 Unmuted Example Reserved Reserved Reserved Reserved Reserved Reserved No signal Not connected ç GET /MEDIA/AUDIO/XP.SourcePortStatus T 0 0 0 B æ pr /MEDIA/AUDIO/XP.SourcePortStatus=T000F;M000B;T000A;T000A;T000C T000B Unlocked, 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 Legend: Unmuted Reserved Reserved Reserved Reserved Reserved Reserved No signal Connected Letter (Character 1) Mute state Lock state T 0 0 0 F T 0 0 0 F Letter Mute / Lock status T Unmuted Unlocked 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 Reserved character, always 0. T000F Unlocked, L Unmuted Locked Byte 1 Reserved character, always 0. Unmuted Reserved Reserved Reserved Reserved Reserved Reserved Signal presents Connected M Muted Unlocked Reserved character, always 0. Byte 2 U Muted Locked Signal present / Connection status Only for Phoenix audio port: Character 5 is C (11 00) which means signal is present but the cable connection status is unknown. The explanation is Phoenix connector has no pin which can indicate the connection Byte 1 Byte 2 status so this is always unknown. Character 2 Character 3 Character 4 Character 5 T 0 0 0 C BIT 7-6 BIT 5-4 BIT 3-2 BIT 1-0 BIT 7-6 BIT 5-4 BIT 3-2 BIT 1-0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 Signal T000C Unlocked, Connection Reserved Reserved Reserved Reserved Reserved Reserved present Unmuted status Reserved Reserved Reserved Reserved Reserved Reserved Signal presents Unknown status 0 0 Unknown 0 1 Reserved

Not 1 0 Reserved Reserved Reserved Reserved Reserved Reserved No signal connected

Signal 1 1 Connected presents

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 112

7.7.2. Query the Status of Destination Port 7.7.5. Query the Audio Autoselect Settings

Command and Response Command and Response ç GET·/MEDIA/AUDIO/XP.DestinationPortStatus ç GET·/MEDIA/AUDIO/XP.DestinationPortAutoselect æ pr·/MEDIA/AUDIO/XP.DestinationPortStatus= æ pr·/MEDIA/AUDIO/XP.DestinationPortAutoselect= The response contains 5 ASCII characters for each port. The first character indicates the mute/lock state, The response shows the settings of each output one by one. the next 2-byte long HEX code showing the current state of the output port. Parameters Example Identifier Parameter description Value Parameter value ç GET /MEDIA/AUDIO/XP.DestinationPortStatus Two-letter code of the æ E Autoselect is enabled. pr /MEDIA/AUDIO/XP.DestinationPortStatus=T000F Autoselect settings st D Autoselect is disabled. Legend 1 letter F First detect: the first active audio input is selected. See at previous section. Priority detect: always the highest priority active P Example and Explanation Two-letter code of the audio input will be selected. Autoselect settings Last detect: always the last attached input is T 0 0 0 F nd L 2 letter switched to the output automatically. 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 Static: the audio input follows the selected video Unlocked, S Signal if the video signal contains embedded audio. Unmuted Reserved Reserved Reserved Reserved Reserved Reserved Connected presents Example 7.7.3. Query the Audio Crosspoint Setting ç GET /MEDIA/AUDIO/XP.DestinationPortAutoselect Command and Response æ pr /MEDIA/AUDIO/XP.DestinationPortAutoselect=EL ç GET·/MEDIA/AUDIO/XP.DestinationConnectionList Explanation æ pr·/MEDIA/AUDIO/XP.DestinationConnectionList= EL: the Autoselect is Enabled on output, selected mode is Last detect. Example INFO: For more information about the Autoselect feature see The Autoselect Feature section. ç GET /MEDIA/AUDIO/XP.DestinationConnectionList æ pr /MEDIA/AUDIO/XP.DestinationConnectionList=I5 I5 input port is connected to the output port. 7.7.4. Switching Audio Input

Command and Response #audio ç CALL·/MEDIA/AUDIO/XP:switch(:) æ mO·/MEDIA/AUDIO/XP:switch

Example ç CALL /MEDIA/AUDIO/XP:switch(I2:O1) æ mO /MEDIA/AUDIO/XP:switch

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 113

7.7.6. Change the Autoselect Mode 7.7.7. Query the Input Port Priority

Command and Response #audio Command and Response ç CALL·/MEDIA/AUDIO/XP:setDestinationPortAutoselect(:) ç GET·/MEDIA/AUDIO/XP.PortPriorityList æ mO·/MEDIA/AUDIO/XP.setDestinationPortAutoselect æ pr·/MEDIA/AUDIO/XP.PortPrioirtyList=;;<…>;

Parameters The response shows the priority of each output one after another. The priority number can be from 0 to 31; 0 is the highest- and 30 is the lowest priority. 31 means that the port will be skipped from the priority list. See at previous section. Parameters Example 1 The input port priority order of the given output port: ,,…, ç CALL /MEDIA/AUDIO/XP:setDestinationPortAutoselect(O1:EL) æ mO /MEDIA/AUDIO/XP:setDestinationPortAutoselect Example The setting is changed to EPM: Autoselect is enabled (E); the mode is set to Priority detect (P), and the port will ç GET /MEDIA/AUDIO/XP.PortPriorityList be disconnected if a higher priority port becomes active (M). æ pr /MEDIA/AUDIO/XP.PortPriorityList=0,1,2,3,4,5

Example 2 Output ç CALL /MEDIA/AUDIO/XP:setDestinationPortAutoselect(O1:D) Video input port I1 I2 I3 I4 I5 I6 æ mO /MEDIA/AUDIO/XP:setDestinationPortAutoselect Priority 0 1 2 3 4 5 The setting is changed to DPM Autoselect is disabled (D). The other settings remain unchanged. Since the Highest priority is assigned to I1 port. outputs are linked, the change will affect local and link out. ATTENTION! The same priority number can be set to different input ports. When the priority numbers INFO: For more information about the Autoselect feature see The Autoselect Feature section. match, the input port with the lowest port number will have the highest priority. 7.7.8. Change the Input Port Priority

Command and Response #audio ç CALL·/MEDIA/AUDIO/XP:setAutoselectionPriority<(in>\(\):);(\(\):) æ mO·/MEDIA/AUDIO/XP:setAutoselectionPrioirty

Parameters

Priority number from 0 to 31, equal numbers are allowed (31 means that the port will be skipped from the priority list). An input port priority can be set on an output port. Many settings can be executed by separating a semicolon (no space), see the example below.

Example ç CALL /MEDIA/VIDEO/XP:setAutoselectionPriority(I1\(O1\):4;I2\(O1\):4) æ mO /MEDIA/VIDEO/XP:setAutoselectionPriority The priority number of input 1 and Input 2 has been set to 4 on output 1. The example shows that certain control characters have been escaped: the backslash “\” character is inserted before the “(“ and “)” characters. See more information about the escaping in the Escaping section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 114

7.7.9. Mute an Audio Input 7.7.13. Mute Audio Output

Command and Response #audio #mute Command and Response #audio #mute ç CALL·/MEDIA/AUDIO/XP:muteSource() ç CALL·/MEDIA/AUDIO/XP:muteDestination() æ mO·/MEDIA/AUDIO/XP:muteSource æ mO·/MEDIA/AUDIO/XP:muteDestination

Example Example ç CALL /MEDIA/AUDIO/XP:muteSource(I1;I3) ç CALL /MEDIA/AUDIO/XP:muteDestination(O1) æ mO /MEDIA/AUDIO/XP:muteSource æ mO /MEDIA/AUDIO/XP:muteDestination 7.7.10. Unmute an Audio Input 7.7.14. Unmute Audio Output

Command and Response #audio #unmute Command and Response #unmute ç CALL·/MEDIA/AUDIO/XP:unmuteSource() ç CALL·/MEDIA/AUDIO/XP:unmuteDestination() æ mO·/MEDIA/AUDIO/XP:unmuteSource æ mO·/MEDIA/AUDIO/XP:unmuteDestination

Example Example ç CALL /MEDIA/AUDIO/XP:unmuteSource(I1;I2) ç CALL /MEDIA/AUDIO/XP:unmuteDestination(O1) æ mO /MEDIA/AUDIO/XP:unmuteSource æ mO /MEDIA/AUDIO/XP:unmuteDestination 7.7.11. Lock an Input Port 7.7.15. Lock Output

Command and Response #audio #lock Command and Response #lock ç CALL·/MEDIA/AUDIO/XP:lockSource() ç CALL·/MEDIA/AUDIO/XP:lockDestination() æ mO·/MEDIA/AUDIO/XP:lockSource æ mO·/MEDIA/AUDIO/XP:lockDestination

Example Example ç CALL /MEDIA/AUDIO/XP:lockSource(I2;I4) ç CALL /MEDIA/AUDIO/XP:lockDestination(O1) æ mO /MEDIA/AUDIO/XP:lockSource æ mO /MEDIA/AUDIO/XP:lockDestination 7.7.12. Unlock an Input Port 7.7.16. Unlock Output

Command and Response #audio #unlock Command and Response #unlock ç CALL·/MEDIA/AUDIO/XP:unlockSource() ç CALL·/MEDIA/AUDIO/XP:unlockDestination() æ mO·/MEDIA/AUDIO/XP:unlockSource æ mO·/MEDIA/AUDIO/XP:unlockDestination

Example Example ç CALL /MEDIA/AUDIO/XP:unlockSource(I1;I4) ç CALL /MEDIA/AUDIO/XP:unlockDestination(O1) æ mO /MEDIA/AUDIO/XP:unlockSource æ mO /MEDIA/AUDIO/XP:unlockDestination

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 115

7.8. Analog Audio Input Level Settings 7.8.1. Volume

Command and Response #analogaudio #volume ç SET·/MEDIA/AUDIO/.Volume= æ pw·/MEDIA/AUDIO/.Volume=

Parameters Sets the input volume (attenuation) between -95.625 dB and 0 dB in step of -0.375 dB. The value is rounded up if necessary to match with the step value. Example ç SET /MEDIA/AUDIO/I1.Volume=-15 æ pw /MEDIA/AUDIO/I1.Volume=-15.000 7.8.2. Balance

Command and Response #analogaudio #balance ç SET·/MEDIA/AUDIO/.Balance= æ pw·/MEDIA/AUDIO/.Balance=

Parameters

Sets the balance; 0 means left balance, 100 means right balance, step is 1. Center is 50 (default).

Example ç SET /MEDIA/AUDIO/I5.Balance=75 æ pw /MEDIA/AUDIO/I5.Balance=75

Explanation The balance level of the right audio sink is set to 75%, the left one is set to 25%.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 116

7.9. Event Manager Basics 7.9.2. Setting a Condition by Linking Another Condition The Event Manager in the LDC allows creating any kind of Events. Sometimes, the events have to be arranged Command and Response or modified by LW3 commands from another device. These commands are detailed in the coming sections. ç SET·/EVENTS/E.Condition= 7.9.1. How to arrange an Event? æ pw·/EVENTS/E.Condition= The following are necessary to have a successful event: Parameters ▪ Defining theCondition The means the number (location) of the linked event without letter 'E'. ▪ Defining theAction Example ▪ Setting the Delay (optional) ç ▪ Name the Event and set to Enabled. (Setting the Event to Enabled as the last step is recommended.) SET /EVENTS/E2.Condition=1 æ pw /EVENTS/E2.Condition=1 Command and Response The Condition of the E2 Event is set to be the same as set at E1 Event. ç SET·/EVENTS/E.Condition= æ pw·/EVENTS/E.Condition= 7.9.3. Setting a Condition by Linking More Conditions Parameters DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- UMX-TPS series). The structure of the is: .=. The first generation of the Event Manager is able to sense a change (one condition) but in some cases that Example 1 – property changes to a set value is not enough. The practical experience has shown there is a need to examine more conditions (up to four) ç SET /EVENTS/E1.Condition=/MEDIA/VIDEO/I1.SignalPresent=1 as follows: if one of the set conditions becomes true (while the other conditions are fulfilled), then the set æ pw /EVENTS/E1.Condition=/MEDIA/VIDEO/I1.SignalPresent=1 Action is launched. The Condition is fulfilled if theSignalPresent property changes to '1'. Command and Response Example 2 – property changes anything but the set value ç SET·/EVENTS/E.Condition=&&& æ In some cases, the opposite is necessary: when the property does not equal with the value. If you need so, pw·/EVENTS/E.Condition=&&& the ConditionInverted property must be set to true: Parameters ç SET /EVENTS/E2.Condition=/MEDIA/VIDEO/O1.ConnectedSource=I1 The parameters mean the numbers (locations) of the linked Events without letter 'E'. Up to four æ pw /EVENTS/E2.Condition=/MEDIA/VIDEO/O1.ConnectedSource=I1 event number can be set. ç SET /EVENTS/E2.ConditionInverted=true Example æ pw /EVENTS/E2.ConditionInverted=true ç SET /EVENTS/E4.Condition=1&2&3 The Condition is fulfilled if theConnectedSource property does not equal with 'I1' (in other words: if other input æ pw /EVENTS/E4.Condition=1&2&3 port is connected to O1 than I1). If two Conditions exist and the third is detected (changes to true), the Condition of E4 will be fulfilled and the Example 3 – property changes to anything Action of E4 will be launched. DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- TIPS AND TRICKS: You do not have to define Actions for E1, E2 and E3 Events and you can leave those UMX-TPS series). Disabled. When not the property value matters, but the change of the property value, the change can be set as a condition. In this case, put a ? character to the end of the desired property: ç SET /EVENTS/E3.Condition=/MEDIA/VIDEO/O1.ConnectedSource? æ pw /EVENTS/E3.Condition=/MEDIA/VIDEO/O1.ConnectedSource? If the ConnectedSource property changes (due to a crosspoint-switch), the set Condition is fulfilled. Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 117

7.9.4. Setting an Action by Specifying a Direct Path 7.10. Event Manager Tool Kit Command and Response 7.10.1. Setting the Delay ç SET·/EVENTS/E.Action= In most cases, the Action is performed immediately after the Condition is detected. But sometimes a delay æ pw·/EVENTS/E.Action= is necessary between the Condition and the Action, thus, the following delay options are defined: Parameters no delay Condition = true Perform the action The structure of the is: .=. Properties and methods are handled in the same way: dot (.) stands after the path in both cases, colon (:) is not used. Do not use simple delay Condition = true Delay Perform the action brackets for methods. The parameter is optional in case of certain methods. still true after Condition = true Delay Condition = true Perform the action Example ç continously Condition = true SET /EVENTS/E1.Action=/MEDIA/VIDEO/XP.switch=I4:O1 Perform the action true æ pw /EVENTS/E1.Action=/MEDIA/VIDEO/XP.switch=I4:O1 Delay Time 7.9.5. Setting an Action by Linking Another Action Command and Response (summary) Command and Response ç SET·/EVENTS/E.ConditionTimeout=

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 118

Example 1 (simple delay) 7.10.3. Enable the Event ç SET /EVENTS/E1.ConditionTimeout=10 Command and Response æ pw /EVENTS/E1.ConditionTimeout=10 ç SET·/EVENTS/E.Enabled= If the Condition is detected (the ConditionDetect property becomes true), the ConditionTimeoutPending property æ pw·/EVENTS/E.Enabled= becomes true. 10 seconds later the ConditionTimeoutPending property becomes false and the set Action is launched. Parameters Example 2 ('still true after' delay type) When the property value is true (or 1), the Action will be launched if the Condition is detected. If the property is false (or 0), the Action will not run, however, the Condition counter will be increased when detected. ç SET /EVENTS/E1.ConditionTimeout=10 Example æ pw /EVENTS/E1.ConditionTimeout=10 ç SET /EVENTS/E1.ConditionTimeoutPending=true ç SET /EVENTS/E1.Enabled=true æ pw /EVENTS/E1.ConditionTimeoutPending=true æ pw /EVENTS/E1.Enabled=true If the Condition is detected (the ConditionDetect property becomes true) the ConditionTimeoutPending property 7.10.4. Triggering a Condition becomes true. 10 seconds later the Condition is checked again (the ConditionTimeoutPending property DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package becomes false). If the Condition can be detected again (the ConditionDetect property becomes true again), the v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- Condition is fulfilled and the set Action is launched. UMX-TPS series). Example 3 ('continuously true' delay type) This feature works like a condition is fulfilled. When a complex control system is built, a Condition may ç SET /EVENTS/E1.ConditionTimeout=10 trigger numerous Actions. A typical example is when a system is powered on and the ’ready-to-use’ state æ pw /EVENTS/E1.ConditionTimeout=10 has to be loaded. In this case, there could be many actions which are based on the same condition. In order to reduce the number of the commands, you can trigger one ’key’ condition, which starts the whole process. ç SET /EVENTS/E1.ConditionTimeoutContinuous=true æ pw /EVENTS/E1.ConditionTimeoutContinuous=true Command and Response If the Condition is detected (the ConditionDetect property becomes true), the ConditionTimeoutPending property ç CALL·/EVENTS/E:triggerCondition(1) becomes true. If the Condition can be detected in the following 10 seconds continuously (the ConditionDetect æ mO·/EVENTS/E:triggerCondition property stays true), the Condition is fulfilled, theConditionTimeoutPending property becomes false, and the set Example Action is launched. ç CALL /EVENTS/E1:triggerCondition(1) 7.10.2. Setting the Name of the Event æ mO /EVENTS/E1:triggerCondition Command and Response The Condition of Event1 is fulfilled, the set Action will be launched (after the delay if set). ç SET·/EVENTS/E.Name= 7.10.5. Querying the Condition Counter æ pw·/EVENTS/E.Name= This property shows how many times the Condition has been detected and triggered altogether. The counter Parameters is reset at boot. The may contain letters (A-Z) and (a-z), numbers (0-9), special characters: hyphen ( - ), underscore Command and Response ( _ ), and space ( ) up to 20 characters. Longer string results an error, unaccepted characters are skipped. ç GET·/EVENTS/E.ConditionCount Example æ pw·/EVENTS/E.ConditionCount= ç SET /EVENTS/E1.Name=Projector_ON Example æ pw /EVENTS/E1.Name=Projector_ON ç GET /EVENTS/E1.ConditionCount æ pw /EVENTS/E1>.ConditionCount=5

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 119

7.10.6. Querying the Condition Trigger Counter 7.11. Variable-Management DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). UMX-TPS series). This property shows how many times the Condition has been triggered but does not contain the number of Custom variables (30 pcs.) can be defined in number or text format which are available also in the Event real detections. The counter is reset at boot. Manager. The maximum length of a variable can be 15 characters and they are stored in a non-volatile Command and Response memory, thus, the value is kept in case of a reboot. The type of the variable (text or string) is determined automatically based on the value. If an operation cannot be performed (e.g. adding number value to a string- ç GET·/EVENTS/E.ExternalConditionTriggerCount type variable), error will be the response. #variables æ pw·/EVENTS/E.ExternalConditionTriggerCount= 7.11.1. Value Assignment Example Command and Response ç GET /EVENTS/E1.ExternalConditionTriggerCount ç SET·/CTRL/VARS/V.Value= æ pw /EVENTS/E1.ExternalConditionTriggerCount=2 æ pw·/CTRL/VARS/V.Value= 7.10.7. Testing an Action Parameters This tool is for launching the Action without detecting or triggering the Condition. Parameter Parameter description Value Value description Command and Response The location of the variable 1-30 ç CALL·/EVENTS/E:ActionTest(1) String can be max 15 characters. Numeric variable is The value of the variable Custom æ mO·/EVENTS/E:ActionTest defined between -2147483648 and 2147483647. Example Example ç CALL /EVENTS/E1:ActionTest(1) ç SET /CTRL/VARS/V1.Value=120 æ mO /EVENTS/E1:ActionTest æ pw /CTRL/VARS/V1.Value=120 7.11.2. Addition and Subtraction (Add Method) The value of a numeric variable can be increased by adding a positive value or it can be decreased by adding a negative value. Minimum and maximum values can be defined as limits. Command and Response ç CALL·/CTRL/VARS/V:add(;;) æ mO·/CTRL/VARS/V:add Parameters Parameter Parameter description Value Value description The location of the variable 1-30 The value that is added to the variable Integer Negative value is also accepted The lowest allowed value (optional) Integer Negative value is also accepted The highest allowed value (optional) Integer Negative value is also accepted

If the value of the variable is higher or equals with , the new value will be . Likewise, in case of setting: if the value of the variable is lower or equals with , the new value will be .

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 120

Examples 7.11.3. Addition and Subtraction (Cycle Method) Change messages (CHG) can be seen after each response for the better understanding, which is not the part The value of a numeric variable can be increased by adding a positive value or it can be decreased by adding of the command, but it can be set as described in the Subscription section. a negative value. Minimum and maximum values can be defined as limits. This method has the feature that Example 1 – addition Example 2 – subtraction if the value hits the limit (min/max), the value will be stepped to the other end of the interval. ç GET /CTRL/VARS/V1.Value ç GET /CTRL/VARS/V1.Value Command and Response æ pw /CTRL/VARS/V1.Value=6 æ pw /CTRL/VARS/V1.Value=10 ç CALL·/CTRL/VARS/V:cycle(;;) ç CALL /CTRL/VARS/V1:add(1) ç CALL /CTRL/VARS/V1:add(-2) æ mO·/CTRL/VARS/V:cycle æ mO /CTRL/VARS/V1:add æ mO /CTRL/VARS/V1:add Parameters æ CHG /CTRL/VARS/V1.Value=7 æ CHG /CTRL/VARS/V1.Value=8 Parameter Parameter description Value Value description ç ç CALL /CTRL/VARS/V1:add(1) CALL /CTRL/VARS/V1:add(-2) The location of the variable 1-30 æ æ mO /CTRL/VARS/V1:add mO /CTRL/VARS/V1:add The value that is added to the variable Integer Negative value is also accepted æ CHG /CTRL/VARS/V1.Value=8 æ CHG /CTRL/VARS/V1.Value=6 The lowest allowed value (optional) Integer Negative value is also accepted ç CALL /CTRL/VARS/V1:add(2) ç CALL /CTRL/VARS/V1:add(-10) The highest allowed value (optional) Integer Negative value is also accepted æ mO /CTRL/VARS/V1:add æ mO /CTRL/VARS/V1:add æ CHG /CTRL/VARS/V1.Value=10 æ CHG /CTRL/VARS/V1.Value=-4 If the calculated value is beyond the limit (min/max), the value will be stepped to the other end of the interval. Examples Example 3 – addition with 'max' value Example 4 – subtraction with 'min' value Change messages (CHG) can be seen after each response for the better understanding, which is not the part ç ç GET /CTRL/VARS/V1.Value GET /CTRL/VARS/V1.Value of the command, but it can be set as described in the Subscription section. æ pw /CTRL/VARS/V1.Value=16 æ pw /CTRL/VARS/V1.Value=14 Example 1 – addition Example 2 – subtraction ç CALL /CTRL/VARS/V1:add(2;10;20) ç CALL /CTRL/VARS/V1:add(-2;10;20) ç ç æ mO /CTRL/VARS/V1:add æ mO /CTRL/VARS/V1:add GET /CTRL/VARS/V1.Value GET /CTRL/VARS/V1.Value æ æ æ CHG /CTRL/VARS/V1.Value=18 æ CHG /CTRL/VARS/V1.Value=12 pw /CTRL/VARS/V1.Value=18 pw /CTRL/VARS/V1.Value=13 ç ç ç CALL /CTRL/VARS/V1:add(2;10;20) ç CALL /CTRL/VARS/V1:add(-2;10;20) CALL /CTRL/VARS/V1:cycle(1;10;20) CALL /CTRL/VARS/V1:cycle(-2;10;20) æ æ æ mO /CTRL/VARS/V1:add æ mO /CTRL/VARS/V1:add mO /CTRL/VARS/V1:cycle mO /CTRL/VARS/V1:cycle æ æ æ CHG /CTRL/VARS/V1.Value=20 æ CHG /CTRL/VARS/V1.Value=10 CHG /CTRL/VARS/V1.Value=19 CHG /CTRL/VARS/V1.Value=11 ç ç ç CALL /CTRL/VARS/V1:add(2;10;20) ç CALL /CTRL/VARS/V1:add(-2;10;20) CALL /CTRL/VARS/V1:cycle(1;10;20) CALL /CTRL/VARS/V1:cycle(-2;10;20) æ æ æ mO /CTRL/VARS/V1:add æ mO /CTRL/VARS/V1:add mO /CTRL/VARS/V1:cycle mO /CTRL/VARS/V1:cycle æ æ æ CHG /CTRL/VARS/V1.Value=20 æ CHG /CTRL/VARS/V1.Value=10 CHG /CTRL/VARS/V1.Value=20 CHG /CTRL/VARS/V1.Value=20 ç CALL /CTRL/VARS/V1:cycle(1;10;20) ç CALL /CTRL/VARS/V1:cycle(-2;10;20) æ mO /CTRL/VARS/V1:cycle æ mO /CTRL/VARS/V1:cycle æ CHG /CTRL/VARS/V1.Value=10 æ CHG /CTRL/VARS/V1.Value=18 ç CALL /CTRL/VARS/V1:cycle(1;10;20) æ mO /CTRL/VARS/V1:cycle æ CHG /CTRL/VARS/V1.Value=11

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 121

7.11.4. Value Change with Intervals (Case) 7.11.5. Scan and Store This command can be used to change the value of a variable if it fits in any of the defined intervals. This command can be used to get the value (or a part of the value) of an LW3 property. The defined path will be scanned according to the pattern and the result will be the value of the variable (number or string type). Command and Response Command and Response ç CALL·/CTRL/VARS/V:case( ;) æ mO·/CTRL/VARS/V:case ç CALL·/CTRL/VARS/V:scanf(.;) æ mO·/CTRL/VARS/V:scanf Parameters Parameters Parameter Parameter description Value The location of the variable 1-30 Parameter Parameter description Value The lowest value of the interval Integer The location of the variable 1-30 The highest value of the interval Integer . The LW3 property with node The new value that will be valid if the current value is in the interval Integer The pattern that scans the property for the desired result see below

The parameters are divided by a space character, and the interval groups are divided by semicolon. Up to 16 Pattern options cases can be defined. Pattern Pattern description Examples %s String of characters stopping at the first whitespace character ç CALL /CTRL/VARS/V1:case(10 20 15) %s The next of characters (string) stopping at the first whitespace æ mO /CTRL/VARS/V1:case %c One character A typical example when two different ranges of values have to meet: %c The next of characters Incoming values: between 0 and 255 (e.g. the slider of a controller can have these values). %[] Defined character set, specified between brackets Outgoing values: between 0 and 100 (e.g. the controlled device accepts these values). %[^] Negated character set, specified between brackets which will be skipped Defined cases: %* Ignored part Min Max New value Case 1 1 25 10 User-defined text Case 2 26 50 20 Case 3 51 75 30 The patterns can be combined to get the desired result as shown in the examples. Case 4 76 100 40 ATTENTION! Do not forget to escape the % character as shown in below example. Case 5 101 125 50 Case 6 126 150 60 Examples Case 7 151 175 70 ç CALL /CTRL/VARS/V1:scanf(/MEDIA/AUDIO/XP.SourcePortStatus;\%5c) Case 8 176 200 80 æ mO /CTRL/VARS/V1:scanf Case 9 201 225 90 ç GET /CTRL/VARS/V1.Value Case 10 226 255 100 æ pw /CTRL/VARS/V1.Value=T00AA The command looks like: A simple pattern has been applied: we need the first five characters from the property value. ç CALL /CTRL/VARS/V1:case(1 25 10;26 50 20;51 75 30;76 100 40;101 125 50;126 150 60;151 175 70; 176 200 80; 201 225 90; 226 255 100) æ mO /CTRL/VARS/V1:case

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 122

Further Examples 7.12. Ethernet Port Configuration . Property Value Scanned result 7.12.1. Set the DHCP State /MANAGEMENT/STATUS.CpuTemperature 42 C; 0;75; 0;7 %s 42 ATTENTION! When you change a network property the new value is stored but the applySettings method /MANAGEMENT/STATUS.CpuFirmware 1.3.0b3 r32 %12s 1.3.0b3 must be called always to apply the new settings. When two or more network parameters are changed the /MEDIA/VIDEO/XP.DestinationPortStatus T00AA;T00AF %6c T00AA applySettings method is enough to call once as a final step. /MEDIA/UART/P1.Rs232Configuration 57600, 8N1 %*[^,], %s 8N1 Command and Response #dhcp #network #ipaddress ç /MEDIA/AUDIO/XP.SourcePortStatus T000A;T000B;T000F %*6c%5c T000B SET·/MANAGEMENT/NETWORK.DhcpEnabled= æ pw·/MANAGEMENT/NETWORK.DhcpEnabled= /MANAGEMENT/NETWORK.HostName lightware-00005031 lightware-%[0-9] 00005031 Parameters 7.11.6. Reformatting a Value If the parameter is true, the current IP address setting is DHCP, if the parameter is false the The value of the variable can be changed by adding text as prefix and/or postfix. current IP address is static. ATTENTION! Think about the length of the value: 15 characters are allowed, the others are truncated. Example Command and Response ç SET /MANAGEMENT/NETWORK.DhcpEnabled=true ç CALL·/CTRL/VARS/V:printf(%s) æ pw /MANAGEMENT/NETWORK.DhcpEnabled=true æ mO·/CTRL/VARS/V:printf ç CALL /MANAGEMENT/NETWORK:applySettings(1) æ mO /MANAGEMENT/NETWORK:applySettings Parameters INFO: The applySettings method will save and apply the new value and results the device to reboot. Parameter Parameter description Value Value description The location of the variable 1-30 INFO: The current setting can be queried by the GET command. The text before the original value of the property (optional) Custom ASCII characters 7.12.2. Change the IP Address (Static) %s The original value of the variable Command and Response The text following the original value of the property (optional) Custom ASCII characters ç SET·/MANAGEMENT/NETWORK.StaticIpAddress= Example æ pw·/MANAGEMENT/NETWORK.StaticIpAddress= ç GET /CTRL/VARS/V1.Value Example ç pw /CTRL/VARS/V1.Value=01 ç SET /MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.85 ç CALL /CTRL/VARS/V1:printf(PWR%s) æ pw /MANAGEMENT/NETWORK.StaticIpAddress=192.168.0.85 æ mO /CTRL/VARS/V1:printf ç CALL /MANAGEMENT/NETWORK:applySettings(1) ç GET /CTRL/VARS/V1.Value æ mO /MANAGEMENT/NETWORK:applySettings æ pw /CTRL/VARS/V1.Value=PWR01 INFO: The applySettings method will save and apply the new value and results the device to reboot. The 'PWR' string has been inserted before the original value. INFO: The current setting can be queried by the GET command.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 123

7.12.3. Change the Subnet Mask (Static) 7.13. Ethernet Tool Kit Command and Response #ipaddress 7.13.1. Device Filter Based on MAC Address ç SET·/MANAGEMENT/NETWORK.StaticNetworkMask= DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package æ pw·/MANAGEMENT/NETWORK.StaticNetworkMask= v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). Example You can create a list of network devices based on the MAC address which are allowed controlling the device, ç SET /MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0 or querying parameters to/from the Lightware device. #macfilter æ pw /MANAGEMENT/NETWORK.StaticNetworkMask=255.255.255.0 A TTENTION! If the device is installed in a network where it gets IP address from a DHCP server and you ç CALL /MANAGEMENT/NETWORK:applySettings(1) plan to use the MAC filtering, make sure the MAC address of the DHCP server is added to the white list. æ mO /MANAGEMENT/NETWORK:applySettings Otherwise, the device will not get IP address and will be unreachable. INFO: The applySettings method will save and apply the new value and results the device to reboot. Command and Response INFO: The current setting can be queried by using the GET command. ç SET·/MANAGEMENT/MACFILTER.MACaddress=;;; 7.12.4. Change the Gateway Address (Static) æ pw·/MANAGEMENT/MACFILTER.MACaddress=;;; Command and Response The filter is disabled as default. Set theFilterEnable property to true as shown in the example. ç SET·/MANAGEMENT/NETWORK.StaticGatewayAddress= Parameters æ pw·/MANAGEMENT/NETWORK.StaticGatewayAddress= Parameter Parameter description Values Value description Example Location of the address 1-8 The default values of 1, 2 and 3 ensure to access the device (e.g. LDC Device ç SET /MANAGEMENT/NETWORK.StaticGatewayAddress=192.168.0.5 Discovery) after enabling the MAC filter æ pw /MANAGEMENT/NETWORK.StaticGatewayAddress=192.168.0.5 The MAC address of the Unique value Hex format, divided by a colon ç CALL /MANAGEMENT/NETWORK:applySettings(1) device æ mO /MANAGEMENT/NETWORK:applySettings Enable/disable the false (or 0) The device is not allowed to query parameter querying option parameters from the LW device INFO: The applySettings method will save and apply the new value and results the extender to reboot. true (or 1) The device is allowed to query parameters INFO: The current setting can be queried by using the GET command. from the LW device 7.12.5. Apply Network Settings Enable/disable the false (or 0) The device is not allowed to change parameter setting option parameters in the LW device Command and Response true (or 1) The device is allowed to change parameters ç CALL·/MANAGEMENT/NETWORK:ApplySettings(1) in the LW device Unique name for the better Any string Up to 5 ASCII characters (longer names are æ m0·/MANAGEMENT/NETWORK:ApplySettings identification (optional) truncated) Example Example ç CALL /MANAGEMENT/NETWORK:ApplySettings(1) ç SET /MANAGEMENT/MACFILTER/MACaddress4=(04:D4:C4:4D:01:43;1;1;Tech) æ m0 /MANAGEMENT/NETWORK:ApplySettings æ pw /MANAGEMENT/MACFILTER/MACaddress4=(04:D4:C4:4D:01:43;1;1;Tech) All network settings which are changed have been applied and network interface restarts. ç SET /MANAGEMENT/MACFILTER.FilterEnable=true æ pw /MANAGEMENT/MACFILTER.FilterEnable=true New MAC address is saved into the 4th property with name 'Tech', which may query/set parameters from/in the Lightware device. The FilterEnable property is set to true, thus, the filter is enabled.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 124

7.13.2. LW2 Control Port Blocking 7.13.5. Powering on a Computer over Ethernet (Wake-on-LAN) DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). UMX-TPS series). The well-known wake-on-lan feature (sending magic Packet to the target PC) is available by the following This command is for blocking the LW2 control port; it is an additional protection for the Cleartext login function. command: Command and Response #portblock Command and Response ç SET·/MANAGEMENT/SERVICEFILTER.Lw2Enabled= ç CALL·/MEDIA/ETHERNET:wakeOnLan(MAC_address) æ pw·/MANAGEMENT/SERVICEFILTER.Lw2Enabled= æ mO·/MEDIA/ETHERNET:wakeOnLan Example Example ç SET /MANAGEMENT/SERVICEFILTER.Lw2Enabled=false ç CALL /MEDIA/ETHERNET:wakeOnLan(AA:BB:CC:22:14:FF) æ pw /MANAGEMENT/SERVICEFILTER.Lw2Enabled=false æ mO /MEDIA/ETHERNET:wakeOnLan 7.13.3. HTTP Port Blocking Please make sure the feature is enabled in the target PC and it is powered (but switched off). DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package 7.13.6. Setting the Host Name v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- DIFFERENCE: This feature is available from FW packages v1.5.0b4 (UMX-TPS series) and v1.5.0b6 (WP- UMX-TPS series). UMX-TPS series). This command is for blocking the HTTP port (80); it is an additional protection for the Cleartext login function. The host name is a property that can be used instead of the IP address when connecting to the device. It is Command and Response also suitable for finding in the Device Discovery window of the LDC, see more details in theAdd New Favorite Device section. Furthermore, it can be used to open the The Built-In Miniweb. If the IP address of the device ç SET·/MANAGEMENT/SERVICEFILTER.HttpEnabled= is changing, the host name can be used as a fixed property. æ pw·/MANAGEMENT/SERVICEFILTER.HttpEnabled= Command and Response Example ç SET·/MANAGEMENT/NETWORK.HostName= ç SET /MANAGEMENT/SERVICEFILTER.HttpEnabled=true æ pw·/MANAGEMENT/NETWORK.HostName= æ pw /MANAGEMENT/SERVICEFILTER.HttpEnabled=true Parameters 7.13.4. HTTP Post Receiving Blocking The can be 1-64 character long and the following are allowed for naming: the elements of DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package the English alphabet and numbers. Hyphen (-) and dot (.) is also accepted except as last character. v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). Example ç This command is for blocking HTTP posts; it is an additional protection for the Cleartext login function. SET /MANAGEMENT/NETWORK.HostName=my-umx-tps æ pw /MANAGEMENT/NETWORK.HostName=my-umx-tps Command and Response ç SET·/MANAGEMENT/SERVICEFILTER.HttpEnabled= æ pw·/MANAGEMENT/SERVICEFILTER.HttpEnabled= Example ç SET /MANAGEMENT/SERVICEFILTER.HttpEnabled=true æ pw /MANAGEMENT/SERVICEFILTER.HttpEnabled=true

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 125

7.14. Ethernet Message Sending 7.14.3. Sending a TCP Binary Message (HEX-format) The device can be used for sending a message to a certain IP:port address. The three different commands The command is for sending a binary message in Hexadecimal format. This method does not require escaping allow controlling the connected (third-party) devices. the control and non-printable characters. 7.14.1. Sending a TCP Message (ASCII-format) Command and Response The command is for sending a command message in ASCII-format. This method allows escaping the control ç CALL·/MEDIA/ETHERNET.tcpBinary(:=) characters. æ mO·/MEDIA/ETHERNET:tcpBinary Command and Response Example ç CALL·/MEDIA/ETHERNET:tcpMessage(:=) ç CALL /MEDIA/ETHERNET:tcpBinary(192.168.0.103:6107=0100000061620000cdcc2c40) æ mO·/MEDIA/ETHERNET:tcpMessage æ mO /MEDIA/ETHERNET:tcpBinary Example The '0100000061620000cdcc2c40' message is sent to the indicated IP:port address. ç CALL /MEDIA/ETHERNET:tcpMessage(192.168.0.103:6107=C00) INFO: There is no need to insert a space or other separator character between the binary messages. æ mO /MEDIA/ETHERNET:tcpMessage 7.14.4. Sending a UDP Message (ASCII-format) The 'C00' message is sent to the indicated IP:port address. The command is for sending a UDP message in ASCII-format. This method allows escaping the control characters. Example with HEX codes Command and Response ç CALL /MEDIA/ETHERNET:tcpMessage(192.168.0.20:5555=C00\x0a\x0d) ç CALL·/MEDIA/ETHERNET:udpMessage(:=) æ mO /MEDIA/ETHERNET:tcpMessage æ mO·/MEDIA/ETHERNET:udpMessage The 'C00' message with CrLf (Carriage return and Line feed) is sent to the indicated IP:port address. Example The \x sequence indicates the HEXA code; see more information in the Escaping section. ç CALL /MEDIA/ETHERNET:udpMessage(192.168.0.103:6107=C00) 7.14.2. Sending a TCP Text (ASCII-format) æ mO /MEDIA/ETHERNET:udpMessage The command is for sending a text message in ASCII-format. This method does not allow escaping or inserting The 'C00' message is sent to the indicated IP:port address. control characters. Example with HEX codes Command and Response ç CALL /MEDIA/ETHERNET:udpMessage(192.168.0.20:9988=C00\x0a\x0d) ç CALL·/MEDIA/ETHERNET:tcpText(:=) æ mO /MEDIA/ETHERNET:udpMessage æ mO·/MEDIA/ETHERNET:tcpText The 'C00' message with CrLf (Carriage return and Line feed) is sent to the indicated IP:port address. The \x Example sequence indicates the HEXA code; see more information in the Escaping section. ç CALL /MEDIA/ETHERNET:tcpText(192.168.0.103:6107=pwr_on) æ mO /MEDIA/ETHERNET:tcpText The 'pwr_on' text is sent to the indicated IP:port address.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 126

7.14.5. Sending a UDP Text (ASCII-format) 7.15. HTTP Messaging The command is for sending a text message in ASCII-format via UDP-protocol. This method does not allow DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package escaping or inserting control characters. v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- Command and Response UMX-TPS series). ç CALL·/MEDIA/ETHERNET:udpText(:=) Http post and put messages can be sent from the Lightware device for more integration with third-party devices. #http æ mO·/MEDIA/ETHERNET:udpText ATTENTION! This feature means posting or putting HTTP messages from the Lightware device to another Example device. Encrypted transmission (HTTPS) is not supported. ç CALL /MEDIA/ETHERNET:udpText(192.168.0.20:9988=open) 7.15.1. Setting the Target IP Address æ mO /MEDIA/ETHERNET:udpText Command and Response The 'open' text is sent to the indicated IP:port address. ç SET·/CTRL/HTTP/C1.ServerIP= 7.14.6. Sending a UDP Binary Message (HEX-format) æ pw·/CTRL/HTTP/C1.ServerIP= The command is for sending a binary message in Hexadecimal format. This method does not require escaping Example the control and non-printable characters. ç SET /CTRL/HTTP/C1.ServerIP=192.168.0.220 Command and Response æ pw /CTRL/HTTP/C1.ServerIP=192.168.0.220 ç CALL·/MEDIA/ETHERNET:udpBinary(:=) æ mO·/MEDIA/ETHERNET:udpBinary 7.15.2. Setting the TCP Port Command and Response Example ç SET·/CTRL/HTTP/C1.ServerPort= ç CALL /MEDIA/ETHERNET:udpBinary(192.168.0.20:9988=433030) æ pw·/CTRL/HTTP/C1.ServerPort= æ mO /MEDIA/ETHERNET:udpBinary Example The '433030' message is sent to the indicated IP:port address. ç SET /CTRL/HTTP/C1.ServerPort=80 INFO: There is no need to insert a space or other separator character between the binary messages. æ pw /CTRL/HTTP/C1.ServerIP=80 7.15.3. Setting the Target Path This property sets the path in the target device where the post/put message to be sent. Command and Response ç SET·/CTRL/HTTP/C1.File= æ pw·/CTRL/HTTP/C1.File= Example ç SET /CTRL/HTTP/C1.File=/putxml æ pw /CTRL/HTTP/C1.File=/putxml

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 127

7.15.4. Setting the Message Header 7.16. TCP Message Recognizer Command and Response DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package ç SET·/CTRL/HTTP/C1.Header= v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). æ pw·/CTRL/HTTP/C1.Header= This tool can be used to recognize messages coming from a TCP server. You can link an immediate event Example Action that is run when a message is recognized, but you can also use it in Event manager. ç SET /CTRL/HTTP/C1.Header=Host: 192.168.0.220\r\nContent-Type: text/xml\r\nAuthorization: Basic YWRtaW46TGlnaHR3YXJlMDE= Preparation æ pw /CTRL/HTTP/C1.Header=Host: 192.168.0.220\r\nContent-Type: text/xml\r\nAuthorization: Basic Step 1. Set a TCP client in the Lightware device (three TCP clients can be run at the same time), set the YWRtaW46TGlnaHR3YXJlMDE= properties of the target TCP server. Step 2. Set the DelimiterHex and the TimeOut settings for the proper message processing 7.15.5. Sending a Post Message Step 3. Make sure the TCP/IP port is opened in the target device (think about Firewall settings in the network). Command and Response Step 4. Connect to the TCP server. ç CALL·/CTRL/HTTP/C1:post() Working Method æ mO·/CTRL/HTTP/C1:post A message got recognized from the incoming data, if one of the following occurs: Example ▪ The set DelimiterHex is detected in the message, or ç CALL /CTRL/HTTP/C1:post(LI1R_P) ▪ The set TimeOut has been elapsed since receiving the last data bit.

æ mO /CTRL/HTTP/C1:post MESSAGE MESSAGE MESSAGE ActiveProperty with delimiter Delimiter saved in Rx property saved in ActiveRx property Timeout ActiveRx property is cleared 7.15.6. Sending a Put Message MESSAGE MESSAGE MESSAGE ActiveProperty Command and Response with timeout TimeOut saved in Rx property saved in ActiveRx property Timeout ActiveRx property is cleared ç CALL·/CTRL/HTTP/C1:put() no timeout,* æ MESSAGE mO·/CTRL/HTTP/C1:put no delimiter Time Example ç CALL /CTRL/HTTP/C1:put(LI1R_P) later, or the TimeOut parameter is set meanwhile, the data appears in the Rx, RxHex, Hash and ActiveRx, æ mO /CTRL/HTTP/C1:put ActiveRxHex, ActiveRxHash properties. #tcprecognizer #message 7.16.1. Setting the IP Address of the TCP Server Command and Response ç SET·/CTRL/TCP/C.ServerIP= æ pw·/CTRL/TCP/C.ServerIP= Parameters The parameter can be 1, 2 or 3 as at most three TCP connections can be established at the same time. Example ç SET /CTRL/TCP/C1.ServerIP=192.168.1.14 æ pw /CTRL/TCP/C1.ServerIP=192.168.1.14

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 128

7.16.2. Setting the TCP/IP Port Number of the TCP Server 7.16.6. Setting the Timeout Command and Response When the set time is elapsed after the last received message and delimiter was not detected, the device saves the data into the Rx, RxHex, Hash properties. The timeout setting is useful if there is no special or easily ç SET·/CTRL/TCP/C.ServerPort= defined delimiter in the incoming data, but there is a time gap between the messages. æ pw·/CTRL/TCP/C.ServerPort= Command and Response Example ç SET·/CTRL/TCP/C.TimeOut= ç SET /CTRL/TCP/C1.ServerPort(4999) æ pw·/CTRL/TCP/C.TimeOut= æ pw /CTRL/TCP/C1.ServerPort(4999) Parameters 7.16.3. Connecting to a TCP Server The parameter sets the time value in milliseconds: 0 means the timeout is disabled, min. value Command and Response is 10. ç CALL·/CTRL/TCP/C:connect() Example æ mO·/CTRL/TCP/C:connect ç SET /CTRL/TCP/C1.TimeOut=20 Example æ pw /CTRL/TCP/C1.TimeOut=20 ç CALL /CTRL/TCP/C1:connect() 7.16.7. Querying the Last Recognized Message (String) æ mO /CTRL/TCP/C1:connect The recognized message is stored as a string in the below property till the next recognized message or until 7.16.4. Disconnecting from a TCP Server the clear() method is called. Command and Response TIPS AND TRICKS: When this property is set as a condition in the Event Manager, and the same strings follow each other, the action will execute once. (A Condition can be detected in Event Manager if a change ç CALL·/CTRL/TCP/C:disconnect() happens. But if the same string is saved into the property after each other, it will not cause a change.) æ mO·/CTRL/TCP/C:disconnect Command and Response Example ç GET·/CTRL/TCP/C.Rx ç CALL /CTRL/TCP/C1:disconnect() æ pr·/CTRL/TCP/C.Rx= æ mO /CTRL/TCP/C1:disconnect Parameters 7.16.5. Setting the Delimiter Hex The parameter can be max. 128 byte long. This property stores the delimiter that is between the messages (e.g. Cr, Lf, Delimiter Delimiter Example Space). The value has to be in hex format (e.g.0D, 0A, 20). ç GET /CTRL/TCP/C1.Rx Command and Response ...00PWR_0100... æ pr /CTRL/TCP/C1.Rx=PWR_off ç SET·/CTRL/TCP/C.DelimiterHex= Stored string æ pw·/CTRL/TCP/C.DelimiterHex= Parameters The parameter can be max. 8-character long (16 hex digit) in hex format. Example ç SET /CTRL/TCP/C1.DelimiterHex=00 æ pw /CTRL/TCP/C1.DelimiterHex=00

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 129

7.16.8. Querying the Last Recognized Message (Hex) 7.16.11. Querying the Last Recognized Active Message (Hex) The recognized message is stored as a hex message in the below property till the next recognized message Command and Response or until the clear() method is called. ç GET·/CTRL/TCP/C.ActiveRxHex Command and Response æ pr·/CTRL/TCP/C.ActiveRxHex= ç GET·/CTRL/TCP/C.RxHex Parameters æ pr·/CTRL/TCP/C.RxHex= The parameter is the recognized data in hex format. Example Example ç GET /CTRL/TCP/C1.RxHex ç GET /CTRL/TCP/C1.ActiveRxHex æ pr /CTRL/TCP/C1.RxHex=5057525F6F6666 æ pr /CTRL/TCP/C1.ActiveRxHex=4175644F75742B00 7.16.9. Clearing the Last Recognized Stored Message INFO: Please note that the property contains the data until the ActivePropertyTimeout is elapsed only. This method clears the stored recognized messages from Rx, RxHex and Hash properties. 7.16.12. Set the Active Timeout Command and Response This property is responsible for clearing the ActiveRx, ActiveRxHex, ActiveHash properties after the elapsed ç CALL·/CTRL/TCP/C:clear() time. Default value is 50ms. æ mO·/CTRL/TCP/C:clear Command and Response Example ç SET·/CTRL/TCP/C.ActivePropertyTimeout= ç CALL /CTRL/TCP/C1:clear() æ pw·/CTRL/TCP/C.ActivePropertyTimeout= æ mO /CTRL/TCP/C1:clear Parameters 7.16.10. Querying the Last Recognized Active Message (String) The parameter is the active timeout value (ms) between 0 and 255. The recognized data is stored in string in the below property temporary. When the time set in the ActiveTimeout Example property is elapsed, the property is cleared. ç SET /CTRL/TCP/C1.ActivePropertyTimeout=255 TIPS AND TRICKS: When this property is set as a condition in the Event Manager, and the same strings æ pw /CTRL/TCP/C1.ActivePropertyTimeout=255 follow each other, the action will execute every occasion. (A Condition can be detected in Event Manager if a change happens. In this case, the string is stored in the property and after the ActiveTimeout it will be 7.16.13. Running an Immediate Event Action cleared. If the same string is saved into the (empty) property that will cause a change.) When a message is recognized (DelimiterHex is detected in the message, or TimeOut has been elapsed Command and Response since receiving the last data bit) a specific Action of an Event can be run by the following command. ç GET·/CTRL/TCP/C.ActiveRx Command and Response æ pr·/CTRL/TCP/C.ActiveRx= ç SET·/CTRL/TCP/C.ActionTrigger= Parameters æ pw·/CTRL/TCP/C.ActionTrigger= The parameter is a max. 12 byte-long recognized data string. Parameters Example The means the number (location) of the linked Event Action without letter 'E'. (There is no need to define a Condition in the linked Event.) ç GET /CTRL/TCP/C1.ActiveRx æ pr /CTRL/TCP/C1.ActiveRx=AudOut+ Example INFO: Please note that the property contains the string until the ActivePropertyTimeout is elapsed only. ç SET /CTRL/TCP/C1.ActionTrigger=5 æ pw /CTRL/TCP/C1.ActionTrigger=5

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 130

7.17. RS-232 Port Configuration 7.17.2. BAUD Rate Setting INFO: Serial port numbering can be found in the Port Numbering section. Command and Response 7.17.1. Protocol Setting ç SET·/MEDIA/UART/.Baudrate= æ pw·/MEDIA/UART/.Baudrate= Command and Response #rs232 #rs-232 #serial #controlprotocol ç SET·/MEDIA/UART/.ControlProtocol= Parameters æ pw·/MEDIA/UART/.ControlProtocol= Identifier Parameter description Value Parameter value Parameters 0 4800 1 7200 Identifier Parameter description Value Parameter value 2 9600 Control protocol which is 0 LW2 protocol 3 14400 applied on the selected BAUD rate value serial port 1 LW3 protocol 4 19200 5 38400 Example 6 57600 ç SET /MEDIA/UART/P1.ControlProtocol=1 7 115200 æ pw /MEDIA/UART/P1.ControlProtocol=1 Example ç SET /MEDIA/UART/P1.Baudrate=2 æ pw /MEDIA/UART/P1.Baudrate=2 7.17.3. Databits Setting

Command and Response ç SET·/MEDIA/UART/.DataBits= æ pw·/MEDIA/UART/.DataBits=

Parameters

Identifier Parameter description Value Parameter value 8 8 Databits value 9 9 Example ç SET /MEDIA/UART/P1.DataBits=8 æ pw /MEDIA/UART/P1.DataBits=8

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 131

7.17.4. Stopbits Setting 7.17.6. RS-232 Operation Mode

Command and Response Command and Response #rs232 #rs-232 #serial #commandinjection ç SET·/MEDIA/UART/.StopBits= ç SET·/MEDIA/UART/.Rs232Mode= æ pw·/MEDIA/UART/.StopBits= æ pw·/MEDIA/UART/.Rs232Mode=

Parameters Parameters

Identifier Parameter description Value Parameter value Identifier Parameter description Value Parameter value 0 1 0 Pass-through Stopbits value 1 1,5 Stopbits value 1 Control 2 2 2 Command injection

Example Example ç SET /MEDIA/UART/P1.StopBits=0 ç SET /MEDIA/UART/P1.Rs232Mode=1 æ pw /MEDIA/UART/P1.StopBits=0 æ pw /MEDIA/UART/P1.Rs232Mode=1 7.17.5. Parity Setting INFO: See more information about RS-232 modes in the Technical Background section. Command and Response 7.17.7. Command Injection Enable

ç SET·/MEDIA/UART/ .Parity= Command and Response æ pw·/MEDIA/UART/.Parity= ç SET·/MEDIA/UART/.CommandInjectionEnable= Parameters æ pw·/MEDIA/UART/.CommandInjectionEnable=

Identifier Parameter description Value Parameter value Parameters 0 None Identifier Parameter description Value Parameter value Parity setting 1 Odd Command injection true Command injection is enabled. 2 Even enable/disable setting false Command injection is disabled. Example Example ç SET /MEDIA/UART/P1.Parity=0 ç SET /MEDIA/UART/P1.CommandInjectionEnable=true æ pw /MEDIA/UART/P1.Parity=0 æ pw /MEDIA/UART/P1.CommandInjectionEnable=true INFO: The Command injection status is stored in another read-only property: /MEDIA/UART/.CommandInjectionStatus.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 132

7.18. RS-232 Message Sending 7.18.4. Using Hexadecimal Codes 7.18.1. Sending a Message (ASCII-format) via RS-232 Hexadecimal codes can be inserted in the ASCII message when using: The command is for sending a command message in ASCII-format. This method allows escaping the control sendMessage command: CALL /MEDIA/UART/P1:sendMessage(C00\x0D) characters. For more information see the Escaping section. tcpMessage command: CALL /MEDIA/ETHERNET:tcpMessage(C00\x0D) Command and Response #message udpMessage command: CALL /MEDIA/ETHERNET:udpMessage(C00\x0D) ç CALL·/MEDIA/UART/P1:sendMessage() ▪ C00: the message. æ mO·/MEDIA/UART/P1:sendMessage ▪ \x: indicates that the following is a hexadecimal code. Example ▪ 0D: the hexadecimal code (Carriage Return) ç CALL /MEDIA/UART/P1:sendMessage(PWR0) æ mO /MEDIA/UART/P1:sendMessage The 'PWR0' message is sent out via the P1 serial port. 7.18.2. Sending a Text (ASCII-format) via RS-232 The command is for sending a command message in ASCII-format. This method does not require escaping the control and non-printable characters. Command and Response ç CALL·/MEDIA/UART/P1:sendText() æ mO·/MEDIA/UART/P1:sendText Example ç CALL /MEDIA/UART/P1:sendText(open) æ mO /MEDIA/UART/P1:sendText The 'open' text is sent out via the P1 serial port. 7.18.3. Sending a Binary Message (HEX-format) via RS-232 The command is for sending a binary message in Hexadecimal format. This method does not require escaping the control and non-printable characters. Command and Response ç CALL·/MEDIA/UART/P1:sendBinaryMessage() æ mO·/MEDIA/UART/P1:sendBinaryMessage Example ç CALL /MEDIA/UART/P1:sendBinaryMessage(433030) æ mO /MEDIA/UART/P1:sendBinaryMessage The '433030' message is sent out via the P1 serial port.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 133

7.19. RS-232 Message Recognizer 7.19.2. Set the Delimiter Hex DIFFERENCE: This feature is available only in UMX-TPS-TX140K 1.4.0b8 and UMX-TPS-TX140-Plus This property stores the delimiter that is between the messages (e.g. Cr, Lf, Space). The value has to be in models from FW package v1.3.0b11. in WP-UMX-TPS-TX130-Plus from FW package v1.4.0b8 hex format (e.g.0D, 0A, 20).

This tool can be used to recognize messages coming from the RS-232 port. The message can be used as a Delimiter (hex format: 3A) Condition in Event manager and define an Action for it.

Working Method ... Password : Login name : ... Stored string A message got recognized from the incoming data, if one of the following occurs: Command and Response ▪ The set DelimiterHex is detected in the message, or ç SET·/MEDIA/UART/RECOGNIZER.DelimiterHex= ▪ The set TimeOut has been elapsed since receiving the last data bit. æ pw·/MEDIA/UART/RECOGNIZER.DelimiterHex=

MESSAGE MESSAGE MESSAGE ActiveProperty Parameters with delimiter Delimiter saved in Rx property saved in ActiveRx property Timeout ActiveRx property is cleared The parameter can be max. 8-character long (or 16 hex digit) in hex format. MESSAGE MESSAGE ActiveProperty with timeout MESSAGE TimeOut ActiveRx property is cleared saved in Rx property saved in ActiveRx property Timeout Example no timeout,* ç SET /MEDIA/UART/RECOGNIZER.DelimiterHex=3a MESSAGE no delimiter Time æ pw /MEDIA/UART/RECOGNIZER.DelimiterHex=3a 7.19.3. Set the Timeout * In that case, the not-recognized data is kept in the memory (up to 128 bytes). If the DelimiterHex is detected When the set time is elapsed after the last received message and delimiter was not detected, the device later, or the TimeOut parameter is set meanwhile, the data appears in the Rx, RxHex, Hash and ActiveRx, saves the data into the Rx, RxHex, Hash properties. The timeout setting is useful if there is no special or easily ActiveRxHex, ActiveRxHash properties. defined delimiter in the incoming data, but there is a time gap between the messages. 7.19.1. Enable the Recognizer Command and Response Command and Response ç SET·/MEDIA/UART/RECOGNIZER.TimeOut= ç SET·/MEDIA/UART/.RecognizerEnable= æ pw·/MEDIA/UART/RECOGNIZER.TimeOut= æ pw·/MEDIA/UART/.RecognizerEnable= Parameters Parameters The parameter sets the timeout value in milliseconds: 0 means the timeout is disabled, min. Parameter Parameter description Values Value description value is 10. Serial port number P1, P2 Example Recognizer mode true Recognizer is enabled ç SET /MEDIA/UART/RECOGNIZER.TimeOut=20 false Recognizer is disabled æ pw /MEDIA/UART/RECOGNIZER.TimeOut=20

Example ç SET /MEDIA/UART/P1.RecognizerEnable=true æ pw /MEDIA/UART/P1.RecognizerEnable=true #recognizer #rs232recognizer #rs-232recognizer

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 134

7.19.4. Querying the Last Recognized Message (String) 7.19.7. Querying the Last Recognized Active Message (String) The recognized message is stored as a string in the below property till the next recognized message or until The recognized data is stored in string in the below property temporary. When the time set in the ActiveTimeout the RECOGNIZER.clear() method is called. property is elapsed, the property is cleared. TIPS AND TRICKS: When this property is set as a condition in the Event Manager, and the same strings TIPS AND TRICKS: When this property is set as a condition in the Event Manager, and the same strings follow each other, the action will execute once. (A Condition can be detected in Event Manager if a change follow each other, the action will execute every occasion. (A Condition can be detected in Event Manager if happens. But if the same string is saved into the property after each other, it will not cause a change.) a change happens. In this case, the string is stored in the property and after the ActiveTimeout it will be cleared. If the same string is saved into the (empty) property that will cause a change.) Command and Response Command and Response ç GET·/MEDIA/UART/RECOGNIZER.Rx æ pr·/MEDIA/UART/RECOGNIZER.Rx= ç GET·/MEDIA/UART/RECOGNIZER.ActiveRx æ pr·/MEDIA/UART/RECOGNIZER.ActiveRx= Parameters Parameters The parameter can be max. 12 byte-long recognized data string. The parameter is a max. 12 byte-long recognized data string. Example Example ç GET /MEDIA/UART/RECOGNIZER.Rx æ pr /MEDIA/UART/RECOGNIZER.Rx=Login: ç GET /MEDIA/UART/RECOGNIZER.ActiveRx æ pr /MEDIA/UART/RECOGNIZER.ActiveRx=Login: 7.19.5. Querying the Last Recognized Message(Hex) 7.19.8. Querying the Last Recognized Active Message (Hex) Command and Response Command and Response ç GET·/MEDIA/UART/RECOGNIZER.RxHex æ pr·/MEDIA/UART/RECOGNIZER.RxHex= ç GET·/MEDIA/UART/RECOGNIZER.ActiveRxHex æ pr·/MEDIA/UART/RECOGNIZER.ActiveRxHex= Parameters Parameters The parameter is the recognized data in hex format. The parameter is the recognized data in hex format. Example Example ç GET /MEDIA/UART/RECOGNIZER.RxHex æ pr /MEDIA/UART/RECOGNIZER.RxHex=FF1F4C6F67696E3A ç GET /MEDIA/UART/RECOGNIZER.ActiveRxHex æ pr /MEDIA/UART/RECOGNIZER.ActiveRxHex= 4C6F67696E3A 7.19.6. Clearing the Last Recognized Stored Message This method deletes all the stored received serial messages. Command and Response ç CALL·/MEDIA/UART/RECOGNIZER:clear() æ mO·/MEDIA/UART/RECOGNIZER:clear Example ç CALL /MEDIA/UART/RECOGNIZER:clear() æ mO /MEDIA/UART/RECOGNIZER:clear

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 135

7.19.9. Set the Active Timeout This property is responsible for clearing the ActiveRx, ActiveRxHex, ActiveHash properties after the elapsed time. Default value is 50ms. Command and Response ç SET·/MEDIA/UART/RECOGNIZER.ActivePropertyTimeout= æ pw·/MEDIA/UART/RECOGNIZER.ActivePropertyTimeout= Parameters The parameter is the active timeout value (ms) between 0 and 255. Example ç SET /MEDIA/UART/RECOGNIZER.ActivePropertyTimeout=255 æ pw /MEDIA/UART/RECOGNIZER.ActivePropertyTimeout=255 7.19.10. Running an Immediate Event Action DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- UMX-TPS series). When a message is recognized (DelimiterHex is detected in the message, or TimeOut has been elapsed since receiving the last data bit) a specific Action of an Event can be run by the following command. Command and Response ç SET·/CTRL/TCP/C.ActionTrigger= æ pw·/CTRL/TCP/C.ActionTrigger= Parameters The means the number (location) of the linked Event Action without letter 'E'. (There is no need to define a Condition in the linked Event.) Example ç SET /CTRL/TCP/C1.ActivePropertyTimeout=255 æ pw /CTRL/TCP/C1.ActivePropertyTimeout=255

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 136

7.20. Sending CEC Commands æ mO /MEDIA/CEC/I2:sendClick DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW 7.20.2. Further Commands package v1.3.0b11 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package Command and Response v1.4.0b8 (WP-UMX-TPS series). ç CALL·/MEDIA/CEC/:send() The device is able to send and receive Consumer Electronics Control (CEC) commands. This feature is for æ mO·/MEDIA/CEC/:send remote controlling the source or sink device. CEC is a bi-directional communication via the HDMI cable. Parameters INFO: The hidden first 2 bytes of the CEC command is static, it refers to the logical address of the sender and the addressee. If the port is input, it is always 04 (from TV to Playback device 1.), if the port is output, it is The parameter means the video input (I1-I4) or video output (O1-O2) port. The following is accepted always 40 (from Playback device 1. to TV). Broadcast addressing is also possible (in this case it is 0F or 4F). as : 7.20.1. Press&Release Commands image_view_on standby text_view_on active_source get_cec_version set_osd clear_osd give_power_status DIFFERENCE: This feature is available only in UMX-TPS-TX140K and TX140-Plus models from FW package v1.5.0b4 (UMX-TPS series) and in WP-UMX-TPS-TX130-Plus-US models from FW package v1.5.0b6 (WP- The set_osd command requires to send also another command, see the following section. UMX-TPS series). Example Below CEC commands are called 'push-button commands' like a button in a remote controller, e.g. volume up/down. When the CEC command is sent, the 'release' command is also sent in the background. Certain ç CALL /MEDIA/CEC/I2:send(standby) devices require this feature for the proper working, but this is necessary only for push-button commands. æ mO /MEDIA/CEC/I2:send Command and Response#cec 7.20.3. Sending an OSD String ç CALL·/MEDIA/CEC/:sendClick() The OSD string sending consists of two steps. First, set the OsdString property with the desired text, then call æ mO·/MEDIA/CEC/:sendClick the send method. Parameters Command and Response The parameter means the video input or output port. The following is accepted as : ç SET·/MEDIA/CEC/.OsdString= ok number_2 input_select rewind select_media_4 æ pw·/MEDIA/CEC/.OsdString= back number_3 display_info fast_forward select_media_5 ç CALL·/MEDIA/CEC/:send(set_osd) up number_4 power_legacy eject power_toggle æ mO·/MEDIA/CEC/I2:send down number_5 page_up skip_forward power_on Parameters left number_6 page_down skip_backward power_off Parameter Parameter description Values Value description right number_7 volume_up 3d_mode stop_function Video input or video I1-I4 Video inputs root_menu number_8 volume_down stop_record f1 output port O1-O2 Video outputs setup_menu number_9 mute_toggle pause_record f2 The desired OSD string Letters (A-Z) and (a-z), hyphen (-), underscore (_), contents_menu dot mute play_forward f3 numbers (0-9), and dot (.). Max length: 14 characters. favorite_menu enter unmute play_reverse f4 media_top_menu clear play select_next_media Example media_context_menu channel_up stop select_media_1 ç SET /MEDIA/CEC/I2.OsdString=Lightware number_0 channel_down pause select_media_2 æ pw /MEDIA/CEC/I2.OsdString=Lightware number_1 sound_select record select_media_3 ç CALL /MEDIA/CEC/I2:send(set_osd) Example æ mO /MEDIA/CEC/I2:send ç CALL /MEDIA/CEC/I2:sendClick(play)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 137

7.20.4. Sending CEC Commands in Hex Format 7.21. Infrared Port Configuration ç CALL·/MEDIA/CEC/:sendHex() INFO: Infrared input and output port numbering can be found in the Port Numbering section. æ mO·/MEDIA/CEC/:sendHex 7.21.1. Enable Command Injection Mode Parameters Command and Response #commandinjection Parameter Parameter description Values Value description Video input or video output I1-I4 Video inputs ç SET·/MEDIA/IR/.CommandInjectionEnable=true|false æ port O1-O2 Video outputs pw·/MEDIA/IR/.CommandInjectionEnable=true|false The desired CEC command Max. 30 character (15 byte) in hexadecimal format. Example ç Example SET /MEDIA/IR/S1.CommandInjectionEnable=true æ pw /MEDIA/IR/S1.CommandInjectionEnable=true ç CALL /MEDIA/CEC/I2:sendHex(8700E091) æ mO /MEDIA/CEC/I2:sendHex 7.21.2. Enable/Disable Output Signal Modulation 7.20.5. Querying the Last Received CEC Message Command and Response ç GET /MEDIA/CEC/.LastReceivedMessage ç SET·/MEDIA/IR/.EnableModulation=true|false æ pr /MEDIA/CEC/.LastReceivedMessage= æ pw·/MEDIA/IR/.EnableModulation=true|false Parameters Example Parameter Parameter description Values Value description ç SET /MEDIA/IR/D1.EnableModulation=false Video port I1-I4 or æ pw /MEDIA/IR/D1.EnableModulation=false O1-O2 Signal modulation is turned off on IR output (D1). The last incoming CEC message from the connected device. INFO: The default setting value is "true" (enabled).

Example ç GET /MEDIA/CEC/I2.LastReceivedMessage æ pr /MEDIA/CEC/I2.LastReceivedMessage=give_power_status TIPS AND TRICKS: This property can be a condition in the Event manager. When the connected device sends status information via CEC, it could be a trigger for an action.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 138

7.22. Infrared Message Sending 7.22.2. Sending Pronto Hex Codes in Big-endian Format via IR Port 7.22.1. Sending Pronto Hex Codes in Little-endian Format via IR Port DIFFERENCE: This feature is available only in UMX-TPS-TX140K, UMX-TPS-TX140-Plus and WP-UMX-TPS-TX130-Plus-US models. DIFFERENCE: This feature is available only in UMX-TPS-TX140K, UMX-TPS-TX140-Plus and WP-UMX-TPS-TX130-Plus-US models. Command and Response

Command and Response ç CALL·/MEDIA/IR/:sendProntoHexBigEndian() æ mO·/MEDIA/IR/:sendProntoHexBigEndian ç CALL·/MEDIA/IR/:sendProntoHex() æ mO·/MEDIA/IR/:sendProntoHex Parameters

Parameters Identifier Parameter description Parameter values Output port of the Local Infra output: D1; TPS Infra output: D2 Identifier Parameter description Parameter values Infrared interface Output port of the Local Infra output: D1; TPS Infra output: D2 Accepts maximum 765 character-long code in hexadecimal Infrared interface Pronto hex format format (0-9; A-F; a-f) without space character in big-endian Accepts maximum 765 character-long code in hexadecimal code Pronto hex format system. format (0-9; A-F; a-f) without space character in little-endian code system. INFO: This command can send exactly one pronto hex message. The header of the IR code contains the length of the whole code in hexa format. If the code is deficient or duplicated, it causes syntax error. INFO: This command can send exactly one pronto hex message. The header of the IR code contains the length of the whole code in hexa format. If the code is deficient or duplicated, it causes syntax error. For more details about the pronto hex codes see IR Interface section. For more details about the pronto hex codes see IR Interface section. Example

Example ç CALL /MEDIA/IR/D1:sendProntoHexBigEndian(0000006d0025000300a900a80015 003f0015003f0015 003f00150015001500150015001500150015001500150015003f0015003f0015003f001500150015001 ç CALL /MEDIA/IR/D1:sendProntoHex(00006D0025000300A900A80015 003F00150 03F0 50015001500150015001500150015003f0015003f0015 003f001500150015001500150015001500150 015003F0015001500150015001500150015001500150 0150015003F0015003F001500 01500150015001 500150015001500150015003f0015003f0015003f0015003f0015 003f0015070200a 3F00150015001500150 015001 500150015001500150015003F0015003F0015003F00150015001500 900a80015001500150e6e) 150015001500150015001500150015001500150015001500150015003F0015003F0015003F0015003 æ mO /MEDIA/IR/D1:sendProntoHexBigEndian F0015003F0015000207A900A8001500150015006E0E) æ mO /MEDIA/IR/D1:sendProntoHex TIPS AND TRICKS: Learning raw IR code with a terminal program:

TIPS AND TRICKS: Download a code which belongs to your controlled device from a web database from Step 1. Connect to the UMX-TPS-TX140-Plus device with a terminal program. the Internet. The downloaded codes are mostly in little-endian format. Step 2. Push the desired button of the remote control to scan the raw IR code. Step 3. Remove all the non-hexadecimal characters (e.g. spaces, h characters etc.) from the code. The pronto hex code which learned by a Lightware device is big-endian format.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 139

7.23. GPIO Port Configuration 7.23.3. Toggle the Level of a GPIO Pin INFO: Use the GET command to query a parameter. #gpio Command and Response Parameters ç CALL·/MEDIA/GPIO/:toggle() æ mO·/MEDIA/GPIO/ :toggle Parameter Description GPIO port number (1..8). Example: P1 Example ç CALL·/MEDIA/GPIO/P1:toggle() 7.23.1. Set the Direction of a GPIO Pin æ mO /MEDIA/GPIO/P1:toggle Command and Response Explanation ç SET·/MEDIA/GPIO/.Direction= If the direction of the pin is input: the output value is toggled. If the direction of the pin is output: the output æ pw·/MEDIA/GPIO/.Direction= value and the input value are toggled. Parameters 7.24. EDID Management Identifier Parameter description Value Parameter value Parameters #edid I Input Direction of the GPIO pin Parameter Description O Output The emulated EDID memory of the desired input port. Example: E1. Example Dynamic EDID memory index. Example: D1 ç SET /MEDIA/GPIO/P1.Direction=I User EDID memory index. Example: U1 æ pw /MEDIA/GPIO/P1.Direction=I Factory EDID memory index. Example: F1 7.23.2. Set the Output Level of a GPIO Pin 7.24.1. Query the Emulated EDIDs Command and Response Command and Response ç SET·/MEDIA/GPIO/.Output= æ pw·/MEDIA/GPIO/ .Output= ç GET·/EDID.EdidStatus æ pr·/EDID.EdidStatus=:;...;: Parameters Example Identifier Parameter description Value Parameter value ç GET /EDID.EdidStatus H Logical high level Level value of the GPIO pin æ pr /EDID.EdidStatus=D1:E1;D1:E2;D1:E3;D1:E4 L Logical low level Emulated EDID memory for input port is listed with the EDID number that is currently emulated on the input. Example ç SET /MEDIA/GPIO/P1.Output=H æ pw /MEDIA/GPIO/P1.Output=H

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 140

7.24.2. Query the Validity of a Dynamic EDID 7.24.6. Copy an EDID to User Memory

Command and Response #edid Command and Response ç GET·/EDID/D/.Validity ç CALL·/EDID:copy(:) æ pr·/EDID/D/.Validity= æ mO·/EDID:copy

Parameters Example The can be true or false. ç CALL /EDID:copy(D1:U1) æ mO /EDID:copy Example The EDID of the last connected sink of D1 (Output 1) has been copied to U1. ç GET /EDID/D/D1.Validity æ pr /EDID/D/D1.Validity=true 7.24.7. Deleting an EDID from User Memory 7.24.3. Query the Preferred Resolution of an User EDID Command and Response

Command and Response ç CALL·/EDID:delete() æ mO·/EDID:delete ç GET·/EDID/U/.PreferredResolution æ pr·/EDID/U/.PreferredResolution= Example

Example ç CALL /EDID:delete(U1) æ mO /EDID:delete ç GET /EDID/U/U2.PreferredResolution æ pr /EDID/U/U2.PreferredResolution=1920x1080p60.00Hz 7.24.8. Resetting the Emulated EDIDs 7.24.4. Emulating an EDID to an Input Port Command and Response

Command and Response ç CALL·/EDID:reset() æ mO·/EDID:reset ç CALL·/EDID:switch(:) æ mO·/EDID:switch Example

Example ç CALL /EDID:reset() æ mO /EDID:reset ç CALL /EDID:switch(F49:E2) æ mO /EDID:switch Calling this method switches all emulated EDIDs to factory default one. See the table in the Factory EDID List section. 7.24.5. Emulating an EDID to All Input Ports Command and Response ç CALL·/EDID:switchAll() æ mO·/EDID:switchAll Example ç CALL /EDID:switchAll(F47) æ mO /EDID:switchAll

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 141

7.25. LW3 Commands - Quick Summary System Commands Video Port Settings Query the Product Name Query the Status of Source Ports ç GET·/.ProductName ç GET·/MEDIA/VIDEO/XP.SourcePortStatus Set the Device Label Query the Status of Destination Port ç SET·/MANAGEMENT/UID.DeviceLabel= ç GET·/MEDIA/VIDEO/XP.DestinationPortStatus Query the Serial Number Query the Video Crosspoint Setting ç GET·/.SerialNumber ç GET·/MEDIA/VIDEO/XP.DestinationConnectionList Query the Firmware Version Disconnect Video Input ç GET·/SYS/MB.FirmwareVersion ç CALL·/MEDIA/VIDEO/XP:switch(0:) Resetting the Device Switching Video Input ç CALL·/SYS:reset() ç CALL·/MEDIA/VIDEO/XP:switch(:) Restore the Factory Default Settings Querying the Connected Input Port Number ç CALL·/SYS:factoryDefaults() ç GET·/MEDIA/VIDEO/.ConnectedSource Lock the Front Panel Buttons Query the Video Autoselect Settings ç SET /MANAGEMENT/UI.ControlLock= ç GET·/MEDIA/VIDEO/XP.DestinationPortAutoselect Disable the Default Function of the Front Panel Buttons Change the Autoselect Mode ç SET /MANAGEMENT/UI/BUTTONS/.DefaultFunctionEnable= ç CALL·/MEDIA/VIDEO/XP:setDestinationPortAutoselect(;;<…>;) Dark Mode Query the Input Port Priority ç SET /MANAGEMENT/UI/DARKMODE.DarkModeEnable= ç GET·/MEDIA/VIDEO/XP.PortPriorityList Dark Mode Delay Change the Input Port Priority ç SET /MANAGEMENT/UI/DARKMODE.DarkModeDelay= ç CALL·/MEDIA/VIDEO/XP:setAutoselectionPriority(\(\):);(\(\):) Running a Macro Mute an Input Port ç CALL·/CTRL/MACROS:run() ç CALL·/MEDIA/VIDEO/XP:muteSource() Cleartext Login Protection Unmute an Input Port ç Setting the Login Password CALL·/MEDIA/VIDEO/XP:unmuteSource() ç CALL·/LOGIN:setPassword() Lock an Input Port ç Login the Device CALL·/MEDIA/VIDEO/XP:lockSource() ç CALL·/LOGIN:login() Unlock an Input Port ç Logout from the Device CALL·/MEDIA/VIDEO/XP:unlockSource() ç CALL·/LOGIN:logout() Mute Output ç Enable the Cleartext Login Function CALL·/MEDIA/VIDEO/XP:muteDestination() ç SET·/LOGIN:LoginEnable= Unmute Output ç CALL·/MEDIA/VIDEO/XP:unmuteDestination()

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 142

Lock Output Query the Input Port Priority ç CALL·/MEDIA/VIDEO/XP:lockDestination() ç GET·/MEDIA/AUDIO/XP.PortPriorityList Unlock Output Change the Input Port Priority ç CALL·/MEDIA/VIDEO/XP:unlockDestination() ç CALL·/MEDIA/AUDIO/XP:setAutoselectionPriority<(in>\(\):);(\(\):) HDCP Setting (Input Port) Mute an Audio Input ç SET·/MEDIA/VIDEO/.HdcpEnable= ç CALL·/MEDIA/AUDIO/XP:muteSource() Test Pattern Generator Mode Unmute an Audio Input ç SET·/MEDIA/VIDEO/.FreeRunMode= ç CALL·/MEDIA/AUDIO/XP:unmuteSource() Test Pattern Color Lock an Input Port ç SET·/MEDIA/VIDEO/.FreeRunColor= ç CALL·/MEDIA/AUDIO/XP:lockSource() Test Pattern Resolution Unlock an Input Port ç SET·/MEDIA/VIDEO/.FreeRunResolution= ç CALL·/MEDIA/AUDIO/XP:unlockSource() HDCP Setting (Output Port) Mute Audio Output ç SET·/MEDIA/VIDEO/.HdcpModeSetting= ç CALL·/MEDIA/AUDIO/XP:muteDestination() HDMI Mode Settings (Output Port) Unmute Audio Output ç SET·/MEDIA/VIDEO/.HdmiModeSetting= ç CALL·/MEDIA/AUDIO/XP:unmuteDestination() Color Space Setting (Output Port) Lock Output ç SET·/MEDIA/VIDEO/.ColorSpaceSetting= ç CALL·/MEDIA/AUDIO/XP:lockDestination() TPS Mode Settings Unlock Output ç SET·/REMOTE/.tpsModeSetting= ç CALL·/MEDIA/AUDIO/XP:unlockDestination() Audio Port Settings Analog Audio Input Level Settings Query the Status of Source Ports Volume ç GET·/MEDIA/AUDIO/XP.SourcePortStatus ç SET·/MEDIA/AUDIO/.Volume= Query the Status of Destination Port Balance ç GET·/MEDIA/AUDIO/XP.DestinationPortStatus ç SET·/MEDIA/AUDIO/.Balance= Query the Audio Crosspoint Setting Event Manager Basics ç GET·/MEDIA/AUDIO/XP.DestinationConnectionList How to arrange an Event? Switching Audio Input ç SET·/EVENTS/E.Condition= ç CALL·/MEDIA/AUDIO/XP:switch(:) Setting a Condition by Linking Another Condition Query the Audio Autoselect Settings ç SET·/EVENTS/E.Condition= ç GET·/MEDIA/AUDIO/XP.DestinationPortAutoselect Setting a Condition by Linking More Conditions Change the Autoselect Mode ç SET·/EVENTS/E.Condition=&&& ç CALL·/MEDIA/AUDIO/XP:setDestinationPortAutoselect(:)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 143

Setting an Action by Specifying a Direct Path Scan and Store ç SET·/EVENTS/E.Action= ç CALL·/CTRL/VARS/V:scanf(.;) Setting an Action by Linking Another Action Reformatting a Value ç SET·/EVENTS/E.Action= ç CALL·/CTRL/VARS/V:printf(%s) Setting an Action by Linking a Macro Ethernet Port Configuration ç SET·/EVENTS/E.Action= Set the DHCP State Event Manager Tool Kit ç SET·/MANAGEMENT/NETWORK.DhcpEnabled= Setting the Delay Change the IP Address (Static) ç SET·/EVENTS/E.ConditionTimeout=

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 144

Sending a TCP Text (ASCII-format) Setting the Delimiter Hex ç CALL·/MEDIA/ETHERNET:tcpText(:=) ç SET·/CTRL/TCP/C.DelimiterHex= Sending a TCP Binary Message (HEX-format) Setting the Timeout ç CALL·/MEDIA/ETHERNET.tcpBinary(:=) ç SET·/CTRL/TCP/C.TimeOut= Sending a UDP Message (ASCII-format) Querying the Last Recognized Message (String) ç CALL·/MEDIA/ETHERNET:udpMessage(:=) ç GET·/CTRL/TCP/C.Rx Sending a UDP Text (ASCII-format) Querying the Last Recognized Message (Hex) ç CALL·/MEDIA/ETHERNET:udpText(:=) ç GET·/CTRL/TCP/C.RxHex Sending a UDP Binary Message (HEX-format) Clearing the Last Recognized Stored Message ç CALL·/MEDIA/ETHERNET:udpBinary(:=) ç CALL·/CTRL/TCP/C:clear() HTTP Messaging Querying the Last Recognized Active Message (String) ç Setting the Target IP Address GET·/CTRL/TCP/C.ActiveRx ç SET·/CTRL/HTTP/C1.ServerIP= Querying the Last Recognized Active Message (Hex) ç Setting the TCP Port GET·/CTRL/TCP/C.ActiveRxHex ç SET·/CTRL/HTTP/C1.ServerPort= Set the Active Timeout ç Setting the Target Path SET·/CTRL/TCP/C.ActivePropertyTimeout= ç SET·/CTRL/HTTP/C1.File= Running an Immediate Event Action ç Setting the Message Header SET·/CTRL/TCP/C.ActionTrigger= ç SET·/CTRL/HTTP/C1.Header= RS-232 Port Configuration Sending a Post Message Protocol Setting ç CALL·/CTRL/HTTP/C1:post() ç SET·/MEDIA/UART/.ControlProtocol= Sending a Put Message BAUD Rate Setting ç CALL·/CTRL/HTTP/C1:put() ç SET·/MEDIA/UART/.Baudrate= TCP Message Recognizer Databits Setting ç Setting the IP Address of the TCP Server SET·/MEDIA/UART/.DataBits= ç SET·/CTRL/TCP/C.ServerIP= Stopbits Setting ç Setting the TCP/IP Port Number of the TCP Server SET·/MEDIA/UART/.StopBits= ç SET·/CTRL/TCP/C.ServerPort= Parity Setting ç Connecting to a TCP Server SET·/MEDIA/UART/ .Parity= ç CALL·/CTRL/TCP/C:connect() RS-232 Operation Mode ç Disconnecting from a TCP Server SET·/MEDIA/UART/.Rs232Mode= ç CALL·/CTRL/TCP/C:disconnect() Command Injection Enable ç SET·/MEDIA/UART/.CommandInjectionEnable=

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 145

RS-232 Message Sending Further Commands Sending a Message (ASCII-format) via RS-232 ç CALL·/MEDIA/CEC/:send() ç CALL·/MEDIA/UART/P1:sendMessage() Sending an OSD String Sending a Text (ASCII-format) via RS-232 ç SET·/MEDIA/CEC/.OsdString= ç ç CALL·/MEDIA/UART/P1:sendText() CALL·/MEDIA/CEC/:send(set_osd) Sending a Binary Message (HEX-format) via RS-232 Sending CEC Commands in Hex Format ç ç CALL·/MEDIA/UART/P1:sendBinaryMessage() CALL·/MEDIA/CEC/:sendHex() Using Hexadecimal Codes Querying the Last Received CEC Message ç GET /MEDIA/CEC/.LastReceivedMessage RS-232 Message Recognizer Infrared Port Configuration Enable the Recognizer Enable Command Injection Mode ç SET·/MEDIA/UART/.RecognizerEnable= ç SET·/MEDIA/IR/.CommandInjectionEnable=true|false Set the Delimiter Hex Enable/Disable Output Signal Modulation ç SET·/MEDIA/UART/RECOGNIZER.DelimiterHex= ç SET·/MEDIA/IR/.EnableModulation=true|false Set the Timeout ç SET·/MEDIA/UART/RECOGNIZER.TimeOut= Infrared Message Sending Querying the Last Recognized Message (String) Sending Pronto Hex Codes in Little-endian Format via IR Port ç GET·/MEDIA/UART/RECOGNIZER.Rx ç CALL·/MEDIA/IR/:sendProntoHex() Querying the Last Recognized Message(Hex) Sending Pronto Hex Codes in Big-endian Format via IR Port ç GET·/MEDIA/UART/RECOGNIZER.RxHex ç CALL·/MEDIA/IR/:sendProntoHexBigEndian() Clearing the Last Recognized Stored Message GPIO Port Configuration ç CALL·/MEDIA/UART/RECOGNIZER:clear() Set the Direction of a GPIO Pin Querying the Last Recognized Active Message (String) ç SET·/MEDIA/GPIO/.Direction= ç GET·/MEDIA/UART/RECOGNIZER.ActiveRx Set the Output Level of a GPIO Pin Querying the Last Recognized Active Message (Hex) ç SET·/MEDIA/GPIO/.Output= ç GET·/MEDIA/UART/RECOGNIZER.ActiveRxHex Toggle the Level of a GPIO Pin Set the Active Timeout ç CALL·/MEDIA/GPIO/:toggle() ç SET·/MEDIA/UART/RECOGNIZER.ActivePropertyTimeout= EDID Management Running an Immediate Event Action Query the Emulated EDIDs ç SET·/CTRL/TCP/C.ActionTrigger= ç GET·/EDID.EdidStatus Sending CEC Commands Query the Validity of a Dynamic EDID Press&Release Commands ç GET·/EDID/D/.Validity ç CALL·/MEDIA/CEC/:sendClick()

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

7. LW3 Programmers’ Reference UMX-TPS-TX100 series – User's Manual 146

Query the Preferred Resolution of an User EDID ç GET·/EDID/U/.PreferredResolution Emulating an EDID to an Input Port ç CALL·/EDID:switch(:) Emulating an EDID to All Input Ports ç CALL·/EDID:switchAll() Copy an EDID to User Memory ç CALL·/EDID:copy(:) Deleting an EDID from User Memory ç CALL·/EDID:delete() Resetting the Emulated EDIDs ç CALL·/EDID:reset()

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 147

Firmware Update 8The endpoint devices can be updated by using Lightware Device Updater v2 (LDU2) software via Ethernet. The firmware pack with the necessary components (*.lfp2 file) for your specific product, and the LDU2 application can be downloaded from the Support page of our website www.lightware.com.

ç Introduction ç Preparation ç Running the Software ç Updating via GUI ç Command Line Interface (CLI) ç CLI Commands ç If the Update is not successful

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 148

ATTENTION! While the firmware is being updated, the normal operation mode is suspended asthe Installation in case of Windows OS transmitter is switched to bootload mode. Signal processing is not performed. Do not interrupt the Run the installer. If the User Account Control displays a pop-up message click Yes. firmware update. If any problem occurs, reboot the device and restart the process. Installation Modes 8.1. Introduction Lightware Device Updater v2 (LDU2) software is the second generation of the LFP- Normal install Snapshot install based (Lightware Firmware Package) firmware update process. Available for Windows, Available for Windows DIFFERENCE: The software can be used for uploading the packages with LFP2 macOS and Linux The installer can update extension only. LDU2 is not suitable for using LFP files, please use the LDU LDU LDU2 Cannot be updated software for that firmware update. only this instance One updateable instance Many different versions can be 8.2. Preparation may exist for all users installed for all users Most Lightware devices can be controlled over more interfaces (e.g. Ethernet, USB, RS-232). But the firmware ATTENTION! Using the default Normal install is highly recommended. can be updated usually over one dedicated interface, which is the Ethernet in most cases. INFO: If you have a previously installed version you will be prompted to remove the old version before If you want to update the firmware of one or more devices you need the following: installing the new one. ▪ LFP2 file, Installation in case of macOS ▪ LDU2 software installed on your PC or Mac. Mount the DMG file with double clicking on it and drag the Both can be downloaded from www.lightware.com/downloads. LDU2 icon over the Applications icon to copy the program Optionally, you can download the release notes file in HTML format. into the Applications folder. If you want to copy LDU2 into another location just drag the icon over the desired folder. 8.2.1. About the Firmware Package (LFP2 File) ATTENTION! Please check the firewall settings on the All the necessary tools and binary files are packed into the LFP2 package file. You need only this file to do macOS device. LDC needs to be added to the exceptions the update on your device. of the blocked software for the proper operation. ▪ This allows the use of the same LFP2 package for different devices. INFO: This type of installer is equal with the Normal install ▪ The package contains all the necessary components, binary, and other files. of Windows. ▪ The release notes is included in the LFP2 file which is displayed in the window where you select the firmware package file in LDU2. Installation in case of Linux 8.2.2. LDU2 Installation Step 1. Download the archive file (tar.gz) from www.lightware.com and unpack it to a temp ATTENTION! Minimum system requirement: 2 GB RAM. The minimum screen resolution is 1600x900. folder. INFO: The Windows and the Mac application has the same look and functionality. Step 2. Run the install_ldu2.sh file in the temp folder. The script will install LDU2 info the following folder: HOME/.local/share/lightware/ldu2. Download the software from www.lightware.com/downloads. Step 3. Above folder will contain this file: LightwareDeviceUpdaterV2.sh that can be used to start LDU2. INFO: This type of installer is equal with the Normal install of Windows.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 149

8.3. Running the Software Main Screen You have two options: When the software is started by the shortcut, the device discovery screen appears. Press the Search for devices button to start finding the Lightware devices: DISCOVER DEVICES ▪ Starting the LDU2 by double-clicking on the shortcut/program file, or ▪ Double-clicking on an LFP2 file. 8.3.1. LDU2 Interfaces The software can be used over: ▪ The Graphical User Interface (GUI), or by ▪ The Command Line Interface (CLI). LDU2 Auto-Update At startup, the software checks if a newer version is available on the web.

If you start the software by double-clicking on the LFP2 file, the firmware will be loaded. Press theDiscover devices button; all the devices will be listed which are compatible with the selected firmware pack. INFO: If you press the Choose package file button, the release notes of the LFP2 file will be displayed in the right panel; see the Step 1. Select the Firmware Package. section.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 150

Device List 8.3.2. The Updating Steps When the discovery has completed, the devices available on the network are listed in the application. ATTENTION! While the firmware is being updated, the normal operation mode is suspended as the device is switched to bootload mode. Signal processing is not performed. Do not interrupt the firmware update. If any problem occurs, reboot the unit and restart the process.

Keeping the Configuration Settings By default, device configuration settings are restored when firmware update is finished. If factory reset has been chosen in the parameters window, all device settings will be erased. In the case of factory reset, you can save the settings of the device in the Lightware Device Controller software and restore it later. The following chart demonstrates how this function works in the background. 1. Create a backup The current configuration of the device is being saved into a configuration backup file on your computer. 2. Start the Update The device reboots and starts in bootload mode (firmware update mode). 3. Update The CPU firmware is changed to the new one. 4. Factory reset If the desired device is not discovered, you can add it by typing the IP address in the dedicated field and press the Add device button. All configuration settings are restored to the factory default values. Legend of the Icons 5. Conversion / Restore The firmware package checks the backup data before the restore procedure, and if it is necessary,  IP address editor The IP address of the device can be changed in the pop-up window. a conversion is applied to avoid incompatibility problems between the firmware versions. All configuration settings are restored to the device after the conversion.  Identify me Clicking on the icon results the front panel LEDs blink for 10 seconds which helps to identify the device phisically. If the factory default option is selected in the Parameters window, the conversion / restore procedure will not be performed!  Favorite device The device has been marked, thus the IP address is stored. When a device is connected with that IP address, the star will highlighted in that line. 6. Finish  Further information Device is unreachable. Change the IP address by pressing the IP address Once the firmware update procedure is finished, the device reboots and is ready to use. available editor icon or use the front panel buttons (if available).  Cleartext login The password-protection is enabled. You have to enter the password enabled to perform the firmware update in the Parameters window or in the appearing window in the beginning of the update. Service mode The device is in bootload mode. Backup and restore cannot be performed in this case.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 151

8.4. Updating via GUI The Meaning of the Symbols Step 1. Select the Firmware Package. Show The log about the updating process of the device  details can be displayed in a new window. Click on the Choose Package File button and navigate to the location where the LFP2 file was saved. When you click on the name of package, the CHOOSE PACKAGE FILE Service The device is in bootload mode. Backup and restore preview of the release notes are displayed in the right panel. mode cannot be performed in this case.

Step 2. Select the desired devices for updating. Select the devices for updating; the selected line will be highlighted in green. If you are not sure which device to select, press the Identify me  button. It makes the front panel LEDs blink for 10 seconds. The feature helps to find the device physically.

After the package file is loaded, the list is filtered to show the compatible devices only. The current firmware version of the device is highlighted in orange if it is different from the version of the package loaded.

Step 3. Check the update parameters. DIFFERENCE: The appearing settings are device-dependent and can be different device by device.

Clicking on the Update Options button, special settings will be available like: UPDATE OPTIONS ▪ Creating a backup about the configuration, ▪ Restore the configuration or reloading the factory default settings after the firmware update, ▪ Uploading the default Miniweb (if available) ▪ Enter the password for the Cleartext login. #builtinweb #miniweb #web INFO: Hereby entered password will be used for all the selected devices where the Cleartext login is enabled. If the password is incorrect, a window will appear to get the correct one at each device during the update. INFO: If you start the update by double-clicking on the LFP file, above screen will be loaded right away. Please arrange the settings carefully.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 152

Step 4. Start the update and wait until it is finished. 8.5. Command Line Interface (CLI) Click on the Start Update button to start the procedure. The status is shown in DIFFERENCE: The Command Line Interface is available from LDU2 v2.9.0b9. percent in the right side of the device line and the overall process in the bottom START UPDATE progress bar. The CLI of the LDU2 software is a simple tool for creating scriptable device updates without the need of human interactions. It allows batch updating with the same features which are available in case of GUI If the Cleartext login is enabled and you did not enter the password in the Parameters window (or it is incorrect) usage. #new a window will appear to get the password at each device. 8.5.1. How to Run INFO: The device might reboot during the firmware update procedure. Running under Windows® OS The installer of LDU2 puts the following file into the installation folder: LightwareDeviceUpdaterV2_CLI.cmd CLI is available by this file, the exe is not suitable for that purpose. Open a command line window to execute or test the features directly. Step 1. Open an Explorer window where the cmd file is located, the default is: c:\Program Files (x86)\Lightware\Lightware Device Updater V2\LightwareDeviceUpdaterV2_CLI. cmd. Step 2. Click on the address line (highlighed with blue in the picture), type cmd.exe and press enter. The command interpreter window of Windows is opened at the path of the LDU2 install folder.

The log about the updating process can be displayed in a new window by pressing the  button. When the progress bar reaches 100% (Done is displayed at all devices), the update of all devices are finished successfully and a message appears; you can close the software.

Step 3. Now you can use the LightwareDeviceUpdaterV2_CLI.cmd file with the commands and options which are described in the coming sections: Running under Linux The Command Line Interface under Linux Operating Systems can be run by the following: LightwareDeviceUpdaterV2.sh Step 5. Wait until the unit reboots with the new firmware. Runing an update: Once the firmware update procedure is completed, the device is rebooted with the new firmware. Shutting bash LightwareDeviceUpdaterV2.sh update --ip 172.24.5.27 --package ~/Downloads/tps- down and restarting the device is recommended. tx200_1.3.1b3.lfp2 The commands and options are the same under Windows® and Linux, too. Following sections contain examples with LightwareDeviceUpdaterV2_CLI.cmd. Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 153

8.5.2. How to Use 8.6.2. LDU2 Version

Command Structure The response shows the version of the LDU2 and the version of the Script API (the Application Programming Interface that is used by the LDU2 and the script). The commands can be run over CLI by the following way: Command LightwareDeviceUpdaterV2_CLI.cmd [command] [options] LightwareDeviceUpdaterV2_CLI.cmd version [Command]: a certain command described in the coming sections; only one command can be run at a time [Options]: mandatory and/or optional parameters of the command, if any. Optional parameters have a Example default value, which can be found at each affected command. You only have to define the parameter if C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd version you want to apply a different value. The order of the options is arbitrary. C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar version Important Notes LDU2 version: 2.9.0b9 ▪ CLI is case-sensitive (including commands, options and other parameters). Script API version: 1.3.9 ▪ There is no limit regarding the number of the devices to update. At most 20 devices are updated 8.6.3. Check For New LDU2 Version simoultaneously, when one of them is finished, the following (21st) will be started automatically. ▪ If an update is failed, the IP address of the affected device(s) are listed at the end. The following command can be used to check if an update of LDU2 is available. This is just a request, since the CLI is not suitable for handling the complete installer of the software.

8.6. CLI Commands Command INFO: The commands and options described in the following sections are the same under Windows® and LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates Linux, too. The examples contain LightwareDeviceUpdaterV2_CLI.cmd. Example 1 About the Examples ▪ Sent command is in blue, response is in grey. c:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates ▪ If the response in practice is longer than listed in the example, this symbol can be seen: [...]. c:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar checkForUpdates Current LDU2 version: 2.9.1b1 8.6.1. Help LDU2 is up-to-date The defined commands and options can be listed by thehelp command. Example 2 Command c:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd checkForUpdates LightwareDeviceUpdaterV2_CLI.cmd help c:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar checkForUpdates Example Current LDU2 version: 2.9.1b1 New version is available online: v2.9.2b2 C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd help Download URL: http://update.lightware.hu/ldu2/lwr/v2.9.2b2/install_LDU2_v2.9.2b2.exe

C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar help Command line usage: Win: LightwareDeviceUpdaterV2_CLI.cmd [command] [options] Linux: LightwareDeviceUpdaterV2.sh [command] [options]

Commands: * help * version * update * deviceInfo * restore * packageOptions [...]

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 154

8.6.4. Device Info 8.6.5. Update The most important information about the selected device is displayed; see the example for more details. This command can be used to update the firmware of the devices.

Command Command LightwareDeviceUpdaterV2_CLI.cmd deviceInfo [options] LightwareDeviceUpdaterV2_CLI.cmd update [options] Options Options

Option Description Required? Option Description Required? -i or --ip List of IP addresses of devices to be updated one of them is -p or --package The path of the firmware package file yes -n or --hostName List of host names of devices to be updated mandatory -i or --ip List of IP addresses of devices to be updated one of them is -v or --packageVersion Shows installed package version only optional -n or --hostName List of host names of devices to be updated mandatory Folder to create device configuration backup at. Example 1 -b or --backupFolder optional Default: USER_HOME/.ldu2/backup C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd deviceInfo --ip -f or --factoryDefault Apply factory reset during device update. Default: false optional 192.168.1.14 -r or --reportProgress Report update progress in percentage form. Default: false optional C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar deviceInfo --ip Certain LFP2 packages have features which can be applied 192.168.1.14 Package-specific options optional Product name: UMX-TPS-TX140K at this command; see the Unmute Audio Output section. IP address: 192.168.1.14 Serial number: 00006363 ATTENTION! The configuration is restored automatically if the factory default option is not applied in the MAC address: a8:d2:36:ff:63:63 update command.In that case, there is no need to run the restore command after the update. Part number: 91540050 Device label: UMX-TPS-TX140K Example Package version: v1.5.0b4 CPU FW version: v1.5.0b4 C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip HW version: V20_DAX0 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --reportProgress Operation mode: Application mode C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip Example 2 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --reportProgress [2021-05-14 12:52:51.597] [ INFO] [ main] - Device IPs: [192.168.1.14] C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd deviceInfo --ip [2021-05-14 12:52:55.786] [ INFO] [ main] - All the selected devices are accessible over the network. 192.168.1.14 --packageVersion [2021-05-14 12:52:56.032] [ INFO] [ main] - All the selected devices are compatible with the specified package. C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar deviceInfo --ip [2021-05-14 12:52:56.600] [ INFO] [ 192.168.1.14] - Package version: 1.5.0b4 192.168.1.14 --packageVersion [2021-05-14 12:52:56.780] [ INFO] [ 192.168.1.14] - Login functionality is currently not enabled. v1.5.0b4 [2021-05-14 12:52:56.816] [ INFO] [ 192.168.1.14] - Creating backup of device settings... [2021-05-14 12:53:00.517] [ INFO] [ 192.168.1.14] - Backup HTTP enable properties [2021-05-14 12:53:01.051] [ INFO] [ProgressReporter] - Progress: 2% [2021-05-14 12:53:02.928] [ INFO] [ 192.168.1.14] - HTTP and HTTP post have got enabled on port 80 [2021-05-14 12:53:03.080] [ INFO] [ 192.168.1.14] - No miniweb file is found on the device. [2021-05-14 12:53:05.566] [ INFO] [ 192.168.1.14] - HTTP and HTTP post properties have got restored on port 80 [2021-05-14 12:53:05.613] [ INFO] [ 192.168.1.14] - Switching device into bootload mode... [2021-05-14 12:53:06.053] [ INFO] [ProgressReporter] - Progress: 5% [...]

The lines containing "ProgressReporter" can be enabled optionally. If it is enabled, the current state is displayed in every 5 seconds.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 155

8.6.6. Restore 8.6.7. Package Options Restores device configuration from a backup file. Shows package-specific update options.

TIPS AND TRICKS: This command can be used for uploading a configuration to numerous devices (aka Command Configuration cloning by CLI). LightwareDeviceUpdaterV2_CLI.cmd packageOptions [options] Command Options LightwareDeviceUpdaterV2_CLI.cmd restore [options] Option Description Required? Options -p or --package The path of the firmware package file yes Option Description Required? Example -i or --ip List of IP addresses of devices to be updated one of them is mandatory C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd packageOptions -n or --hostName List of host names of devices to be updated --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 -b or --backupFile The path of the configuration backup file yes C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar packageOptions Do not override the network settings of the device with the ones --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 in the backup file. It comes in handy when multiple devices' -k or --keepOriginalIp optional configuration is being restored from a single backup file. Backup and restore options: --skipPresetsAtRestore : if true, device presets will not be restored. (Default: false) Default: false --uploadDefaultMiniWeb : if true and no custom miniweb is present on the device, the default built-in ATTENTION! The configuration is restored automatically if the factory default option is not applied in the miniweb will be uploaded to the device. (Default: false) update command.In that case, there is no need to run the restore command after the update. Login options: --clearTextLoginPw : The cleartext login password used when updating devices. (Default: empty string) Example Test options: C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd restore --ip --test : if true, no update will be performed, communication with the device will be tested. (Default: 192.168.1.14 --backupFile c:\My_backup\backup_UMX_TPS_TX140K_SN00006363.lw3 --keepOriginalIp false)

C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar restore --ip C:\Program Files (x86)\Lightware\Lightware Device Updater V2> 192.168.1.14 --backupFile c:\My_backup\backup_UMX_TPS_TX140K_SN00006363.lw3 --keepOriginalIp [2021-05-14 14:11:04.631] [ INFO] [ main] - Executing configuration restore... Package option example can be seen in the following section. [2021-05-14 14:11:04.645] [ INFO] [ main] - Device IPs: [192.168.1.14]

INFO: The firmware package checks the backup data before the restore procedure and if it is necessary, a conversion is applied to avoid incompatibility problems between the firmware versions. In that case, two backup files are created: the original and a new one with "_converted" suffix. Using the last one for restoring is recommended.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 156

8.6.8. Complex Examples Example 2 The following options applied: Example 1 ▪ Cleartext login password is applied The following options applied: ▪ Custom backup folder is set ▪ Firmware is updated ▪ Current configuration is saved ▪ Factory default settings restored ▪ Firmware is updated and saved configuration is restored C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --ip 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --backupFolder c:\My_backup --clearTextLoginPw 192.168.1.14 --factoryDefault --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 qwer1234 C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --ip 192.168.1.14 --factoryDefault --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --backupFolder c:\My_backup --clearTextLoginPw [2021-05-14 14:20:26.242] [ INFO] [ main] - Device IPs: [192.168.1.14] qwer1234 [2021-05-14 14:20:29.860] [ INFO] [ main] - All the selected devices are accessible over the network. [2021-05-14 14:39:23.243] [ INFO] [ main] - Device IPs: [192.168.1.14] [2021-05-14 14:20:30.129] [ INFO] [ main] - All the selected devices are compatible with the specified [2021-05-14 14:39:26.379] [ WARN] [ pool-2-thread-1] - NetworkMask property is not available. Cannot determine package. whether the device is on the same network or not. [2021-05-14 14:20:30.709] [ INFO] [ 192.168.1.14] - Package version: 1.5.0b4 [2021-05-14 14:39:26.466] [ WARN] [ pool-2-thread-1] - Bonjour device builder error messages: [object Array] [2021-05-14 14:20:30.861] [ INFO] [ 192.168.1.14] - Login functionality is currently not enabled. [2021-05-14 14:39:26.535] [ INFO] [ main] - All the selected devices are accessible over the network. [2021-05-14 14:20:30.913] [ INFO] [ 192.168.1.14] - Switching device into bootload mode... [2021-05-14 14:39:26.753] [ INFO] [ main] - All the selected devices are compatible with the specified [2021-05-14 14:20:51.497] [ INFO] [ 192.168.1.14] - Gathering UID information from device... package. [2021-05-14 14:20:51.881] [ INFO] [ 192.168.1.14] - UID info - Device IP: 192.168.1.14 Product name: UMX- [2021-05-14 14:39:27.307] [ INFO] [ 192.168.1.14] - Package version: 1.5.0b4 TPS-TX140K Product part number: 91540050 Serial number: 00006363 Hardware version: V20_DAX0 MAC address: [2021-05-14 14:39:27.441] [ INFO] [ 192.168.1.14] - Logged in successfully. A8:D2:36:FF:63:63 [2021-05-14 14:39:27.471] [ INFO] [ 192.168.1.14] - Creating backup of device settings... [2021-05-14 14:20:52.224] [ INFO] [ 192.168.1.14] - Package version on device: 1.5.0b4 r66 [2021-05-14 14:39:31.010] [ INFO] [ 192.168.1.14] - Backup HTTP enable properties [2021-05-14 14:20:52.259] [ INFO] [ 192.168.1.14] - Updating UMX-TPS-TX100 series application fw - part 1... [2021-05-14 14:39:33.462] [ INFO] [ 192.168.1.14] - HTTP and HTTP post have got enabled on port 80 [2021-05-14 14:20:52.595] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s current version on [2021-05-14 14:39:33.656] [ INFO] [ 192.168.1.14] - No miniweb file is found on the device. device: 1.5.0b4 r56 [2021-05-14 14:39:36.091] [ INFO] [ 192.168.1.14] - HTTP and HTTP post properties have got restored on port 80 [2021-05-14 14:20:52.597] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s version in the package: [2021-05-14 14:39:36.186] [ INFO] [ 192.168.1.14] - Switching device into bootload mode... 1.5.0b4 r56 [2021-05-14 14:39:56.561] [ INFO] [ 192.168.1.14] - Gathering UID information from device... [2021-05-14 14:21:09.260] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s firmware version [2021-05-14 14:39:56.937] [ INFO] [ 192.168.1.14] - UID info - Device IP: 192.168.1.14 Product name: UMX- updated in FVS EEPROM. TPS-TX140K Product part number: 91540050 Serial number: 00006363 Hardware version: V20_DAX0 MAC address: [2021-05-14 14:21:09.263] [ INFO] [ 192.168.1.14] - Updating UMX-TPS-TX100 series application fw - part 2... A8:D2:36:FF:63:63 [2021-05-14 14:21:09.590] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s current version on [2021-05-14 14:39:57.301] [ INFO] [ 192.168.1.14] - Package version on device: 1.5.0b4 r66 device: 1.5.0b4 r56 [2021-05-14 14:39:57.714] [ INFO] [ 192.168.1.14] - Updating UMX-TPS-TX100 series application fw - part 1... [2021-05-14 14:21:09.591] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s version in the package: [2021-05-14 14:39:58.052] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s current version on 1.5.0b4 r56 device: 1.5.0b4 r56 [2021-05-14 14:21:30.832] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s firmware version [2021-05-14 14:39:58.053] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s version in the package: updated in FVS EEPROM. 1.5.0b4 r56 [2021-05-14 14:21:30.833] [ INFO] [ 192.168.1.14] - Updating VS100TX fw... [2021-05-14 14:40:14.848] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM1]'s firmware version [2021-05-14 14:21:31.161] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0 updated in FVS EEPROM. [2021-05-14 14:21:31.162] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63 [2021-05-14 14:40:14.850] [ INFO] [ 192.168.1.14] - Updating UMX-TPS-TX100 series application fw - part 2... [2021-05-14 14:21:44.106] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM. [2021-05-14 14:40:15.178] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s current version on [2021-05-14 14:21:44.107] [ INFO] [ 192.168.1.14] - Updating PS171 FW... device: 1.5.0b4 r56 [2021-05-14 14:21:44.433] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s current version on device: 1.0.6b0 [2021-05-14 14:40:15.179] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s version in the package: r0 1.5.0b4 r56 [2021-05-14 14:21:44.434] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s version in the package: 1.0.6b0 [2021-05-14 14:40:36.511] [ INFO] [ 192.168.1.14] - [umx-tps-tx100-f427.bin.ER_IROM2]'s firmware version r522 updated in FVS EEPROM. [2021-05-14 14:22:00.612] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s firmware version updated in FVS [2021-05-14 14:40:36.512] [ INFO] [ 192.168.1.14] - Updating VS100TX fw... EEPROM. [2021-05-14 14:40:36.837] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s current version on device: 1.1.0b0 r0 [2021-05-14 14:22:06.740] [ INFO] [ 192.168.1.14] - Setting system information... [2021-05-14 14:40:36.839] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s version in the package: 1.1.0b0 r63 [2021-05-14 14:22:12.862] [ INFO] [ 192.168.1.14] - Starting application... [2021-05-14 14:40:49.849] [ INFO] [ 192.168.1.14] - [vs100_tx.bin]'s firmware version updated in FVS EEPROM. [2021-05-14 14:23:56.190] [ INFO] [ 192.168.1.14] - Done [2021-05-14 14:40:49.851] [ INFO] [ 192.168.1.14] - Updating PS171 FW... [2021-05-14 14:40:50.177] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s current version on device: 1.0.6b0 All 1 update(s) finished successfully. r0

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

8. Firmware Update UMX-TPS-TX100 series – User's Manual 157

[2021-05-14 14:40:50.179] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s version in the package: 1.0.6b0 8.6.9. Exit Codes r522 [2021-05-14 14:41:06.386] [ INFO] [ 192.168.1.14] - [tps_family_ps171.bin]'s firmware version updated in FVS There is a return value in all cases, when a command run is finished. Currently, three codes are defined: EEPROM. [2021-05-14 14:41:12.514] [ INFO] [ 192.168.1.14] - Setting system information... Code Displayed text Description [2021-05-14 14:41:18.637] [ INFO] [ 192.168.1.14] - Starting application... [2021-05-14 14:43:03.605] [ INFO] [ 192.168.1.14] - Waiting for VS100... 0 N/A The update performed successfully [2021-05-14 14:43:05.237] [ INFO] [ 192.168.1.14] - Restoring device settings from the following backup file: 1 Update error (ErrorCode:1) The error happened during the update c:\My_backup\backup_91540050_00006363_2021-05-14_14-39-28_converted.lw3 ... [2021-05-14 14:43:14.325] [ INFO] [ 192.168.1.14] - Device settings have been restored 2 CLI error (ErrorCode:2 The error happened before starting the update [2021-05-14 14:43:14.358] [ INFO] [ 192.168.1.14] - Resetting device... [2021-05-14 14:43:19.071] [ INFO] [ 192.168.1.14] - Done The error line contains further information about the error.

® All 1 update(s) finished successfully. Querying the Exit Code under Windows

Example 3 c:\Program Files (x86)\Lightware\Lightware Device Updater V2\echo %errorlevel% 0 The following options applied: Querying the Exit Code under Linux ▪ Cleartext login password is applied ▪ Custom backup folder is set echo $? ▪ Current configuration is saved 0 ▪ Firmware is not updated but the process and the connection is tested So if this value is queried after the update and it is 0, the update performed successfully. C:\Program Files (x86)\Lightware\Lightware Device Updater V2>LightwareDeviceUpdaterV2_CLI.cmd update --test --ip 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --backupFolder c:\My_backup --clearTextLoginPw 8.7. If the Update is not successful qwer1234 ▪ Restart the process and try the update again. C:\Program Files (x86)\Lightware\Lightware Device Updater V2>lib\jre\bin\java.exe -jar lib\ldu2.jar update --test --ip 192.168.1.14 --package c:\Firmwares\umx-tps-tx100_v1.5.0b4.lfp2 --backupFolder c:\My_backup --clearTextLoginPw ▪ If the device cannot be switched to bootload (firmware update) mode, you can do that manually as qwer1234 written in the User's manual of the device. Please note that backup and restore cannot be performed [2021-05-14 14:45:37.351] [ INFO] [ main] - Device IPs: [192.168.1.14] in this case. [2021-05-14 14:45:40.396] [ WARN] [ pool-2-thread-1] - NetworkMask property is not available. Cannot determine whether the device is on the same network or not. ▪ If the backup cannot be created for some reason, you will get a message to continue the process [2021-05-14 14:45:40.481] [ WARN] [ pool-2-thread-1] - Bonjour device builder error messages: [object Array] without backup or stop the update. A root cause can be that the desired device is already in bootload [2021-05-14 14:45:40.551] [ INFO] [ main] - All the selected devices are accessible over the network. [2021-05-14 14:45:40.748] [ INFO] [ main] - All the selected devices are compatible with the specified (firmware update) mode, thus, the normal operation mode is suspended and backup cannot be made. package. ▪ If an update is not successful, the Export log button becomes red. If you press the button, you can [2021-05-14 14:45:41.347] [ INFO] [ 192.168.1.14] - PASSED - Test #01 - Communication over LW3 [2021-05-14 14:45:41.427] [ INFO] [ 192.168.1.14] - PASSED - Test #02 - Cleartext login - PW is correct download the log file as a ZIP package which can be sent to Lightware Support if needed. The log files [2021-05-14 14:45:41.474] [ INFO] [ 192.168.1.14] - Creating backup of device settings... contain useful information about the circumstances to find the root cause. #bootload [2021-05-14 14:45:45.010] [ INFO] [ 192.168.1.14] - Backup HTTP enable properties [2021-05-14 14:45:47.417] [ INFO] [ 192.168.1.14] - HTTP and HTTP post have got enabled on port 80 [2021-05-14 14:45:47.620] [ INFO] [ 192.168.1.14] - No miniweb file is found on the device. [2021-05-14 14:45:50.058] [ INFO] [ 192.168.1.14] - HTTP and HTTP post properties have got restored on port 80 [2021-05-14 14:45:50.060] [ INFO] [ 192.168.1.14] - PASSED - Test #03 - Configuration and/or device preset backup created [2021-05-14 14:45:50.080] [ INFO] [ 192.168.1.14] - Switching device into bootload mode... [2021-05-14 14:45:51.721] [ INFO] [ 192.168.1.14] - PASSED - Test #04 - Switch device into bootloader mode [2021-05-14 14:46:09.050] [ INFO] [ 192.168.1.14] - PASSED - Test #05 - Communication with bootloader [2021-05-14 14:46:09.063] [ INFO] [ 192.168.1.14] - Gathering UID information from device... [2021-05-14 14:46:09.403] [ INFO] [ 192.168.1.14] - PASSED - Test #06 - TFTP file transfer [2021-05-14 14:46:22.638] [ INFO] [ 192.168.1.14] - PASSED - Test #07 - Start application FW [2021-05-14 14:46:22.681] [ INFO] [ 192.168.1.14] - Done

All 1 update(s) finished successfully.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

9. Troubleshooting UMX-TPS-TX100 series – User's Manual 158

Troubleshooting 9Usually, if the system seems not to transport the signal as expected, the best strategy for troubleshooting is to check signal integrity through the whole signal chain starting from source side and moving forward to the receiver end.

Link to connections/cabling section.

Link to front panel operation section.

Link to LDC software section.

LW2 Link to LW2 protocol commands section.

LW3 Link to LW3 protocol commands section.

The following sections are available in the chapter: ç Use Cases ç How to Speed Up the Troubleshooting Process

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

9. Troubleshooting UMX-TPS-TX100 series – User's Manual 159

9.1. Use Cases Symptom Root cause Action Refer to At first, check front panel LEDs and take the necessary steps according to their states. For more information Audio signal about status, LEDs refer to Front Panel LEDs and Rear Panel LEDs sections. No audio is Source audio volume is Check the audio settings of the source. present on output low or muted Symptom Root cause Action Refer to Audio input port is Check the audio input port properties 5.5 Video signal muted LW3 7.7.1 No picture on the Device or devices are not Check the extenders and the other 3.4.1 Audio output port is Check the output port properties. 5.5 video output powered properly devices if they are properly powered; try muted to unplug and reconnect them. 3.4.2 LW2 6.4.6 Cable connection Cables must fit very well, check all the LW3 3.4 7.7.2 problem connectors (video and TPS cables). HDMI output HDMI mode was set to Check the properties of the output port 5.5.3 TPS mode problem Check the actual TPS mode and the 5.5.3 signal contains no DVI and set the signal type to HDMI or Auto. selected modes of the extenders. LW3 7.6.24 LW3 7.6.26 audio DVI EDID is emulated Check the EDID and select and HDMI The input port is muted Check the mute state of input port. 5.5 5.8 EDID to emulate. LW3 LW3 7.6.1 7.24 The output port is muted Check the mute state of output port. 5.5.3 RS-232 signal Connected serial Cable connection Check the connectors to fit well; check LW2 6.4.3 device does not problem the wiring of the plugs. 3.4.10 LW3 7.6.2 respond Display is not able to Check the emulated EDID; select another 5.8 RS-232 settings are Check the port settings of the transmitter 5.9.1 receive the video format (e.g. emulate the display’s EDID on the different and the connected serial device(s). LW3 7.17 input port). LW3 7.24 RS-232 mode is not right Check the RS-232 mode settings (control, HDCP is disabled Enable HDCP on the input and output 5.5.2 5.9.1 command injection, or disconnected) ports. LW3 7.17.6 5.5.3 LW3 7.6.19 Network Incorrect IP address is Use dynamic IP address by enabling 2.9.2 LW3 7.6.23 No LAN set (fix IP) DHCP option. Not the desired Video input is set to test Check test pattern settings in the connection can be 5.11.2 established picture displayed pattern (no sync screen) properties of the input ports. 5.7.2 LW3 7.12.1 on the video statically LW3 7.6.20 Restore the factory default settings (with 2.9.3 output fix IP). Video source is set to Check the crosspoint settings 5.4 5.11.5 Testpattern input (I6) LW2 6.4.6 LW2 6.3.13 LW3 7.6.3 LW3 7.4.6 Video output is set to Check video settings of the source. IP address conflict Check the IP address of the other test pattern (no sync devices, too. screen) as there is no picture on video source

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

9. Troubleshooting UMX-TPS-TX100 series – User's Manual 160

Symptom Root cause Action Refer to 9.2. How to Speed Up the Troubleshooting Process GPIO Lightware’s technical support team Connected device Cable connection Check the connectors to fit well; check is always working hard to provide 3.4.13 does not respond problem the wiring of the plugs. the fastest support possible. Our team’s response time is one of The direction of the Check and modify the direction setting 5.9.3 the best in the industry and in the Output level selected pin is set to of the desired pin LW2 6.7.1 toughest of cases we can directly cannot be changed input consult with the hardware or LW3 7.23 software engineer who designed USB KVM the product to get the information Cables are not Check the USB cable between TX and from the most reliable source. USB device does connected on both sides the computer. However, the troubleshooting process can be even faster… with not operate Not supported USB Keyboard, mouse (USB HID devices) are your help. device is connected supported mostly, check your device type. Miscellaneous There are certain pieces of information that push us in the right direction to finding the root cause of the problem. If we receive most of this information in the first e-mail or it is gathered at the time when you call Front panel Buttons are locked Unlock the buttons 2.9.5 us, then there is a pretty high chance that we will be able to respond with the final solution right away. buttons are out of operation 5.11.1 This information is the following: Error messages Different protocol is set Check the port protocol settings (LW2 5.9.1 ▪ Schematic (a pdf version is preferred, but a hand drawing is sufficient). received / LW3) and use the proper protocol ▪ Serial number(s) of the device(s) (it is either printed somewhere on the box or you can query it in the LW3 7.17.1 continuously commands. Device Controller software or on the built-in website). ▪ Firmware versions of the devices (please note that there may be multiple CPUs or controllers in the device and we need to know all of their firmware versions, a screenshot is the best option). ▪ Cable lengths and types. ▪ Patch panels, gender changers or anything else in the signal path that can affect the transmission. ▪ Signal type (resolution, refresh rate, color space, deep color). ▪ Emulated EDID(s) (please save them as file and send them to us). ▪ Actions to take in order to re-create the problem (if we cannot reproduce the problem, it is hard for us to find the cause). ▪ Photo or video about the problem (for example: "image noise" can mean many different things, it’s better if we see it too). ▪ Error logs from the Device Controller software. ▪ In the case of Event Manager issue the event file and/or backup file from the Device Controller software.

The more of the above information you can give us the better. Please send these information to the Lightware Support Team ([email protected]) to speed up the troubleshooting process.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

10. Technologies UMX-TPS-TX100 series – User's Manual 161

Technologies 10The following sections contain descriptions and useful technical information how the devices work in the background. The content is based on experiences and cases we met in the practice. These sections help to understand features and technical standards like the followings:

ç EDID Management ç HDCP Management ç Pixel Accurate Reclocking

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

10. Technologies UMX-TPS-TX100 series – User's Manual 162

10.1. EDID Management Problem: “I have changed to a different EDID on an input port of the Lightware device to have a different resolution but nothing happens.” 10.1.1. Understanding the EDID Solution: Some graphics cards and video sources read out the EDID only after power-up and later they do The Extended Display Identification Data (EDID) is the passport of display devices (monitors, TV sets, not sense that EDID has been changed. You need to restart your source to make it read out the projectors). It contains information about the capabilities of the display, such as supported resolutions, EDID again. refresh rates (these are called Detailed Timings), the type and manufacturer of the display device, etc. 10.1.2. Advanced EDID Management After connecting a source to a display (DVI, HDMI, DP), the source reads out the EDID to determine the resolution and refresh rate of the image to be transmitted. Each DVI sink (e.g. monitors, projectors, plasma displays, etc...) must support the EDID data structure. Source BIOS and operating systems are likely to query the sink using DDC2B protocol to determine what pixel formats and interface are supported. DVI standard uses EDID data structure to identify the monitor type and capabilities. Most DVI sources (VGA cards, set top boxes, etc.) will output DVI signal after accepting the connected sink’s EDID information. In the case of EDID readout failure or missing EDID, the source will not output DVI video signal. Lightware devices provide the Advanced EDID Management function that helps system integration. The built-in EDID Router can store and emulate factory pre-programmed- and User programmable EDIDs. The EDID of the attached monitors or projectors for each output are stored in a non-volatile memory. This way the EDID of a monitor is available when the monitor is unplugged or switched off. Any EDID can be emulated on any input. An emulated EDID can be copied from the EDID router’s memory (static EDID emulation), or from the last attached monitor’s memory (dynamic EDID emulation). For example, EDID Communication the Lightware device can be set up to emulate a sink device, which is connected to one of the outputs. In Most DVI computer displays have 128-byte long EDID structure. However, Digital Televisions and HDMI this case, the EDID automatically changes, if the monitor is replaced with another display device (as long as capable displays may have another 128 bytes, which is called E-EDID and defined by CEA (Consumer it has a valid EDID). Electronics Association). This extension contains information about additional Detailed Timings, audio EDID is independently programmable for all inputs without affecting each other. All inputs have their own capabilities, speaker allocation and HDMI capabilities. It is important to know that all HDMI capable devices EDID circuit. must have CEA extension, but not all devices with CEA extension are HDMI capable. INFO: The user is not required to disconnect the video cable to change an EDID as opposed to other Common Problems Related to EDID manufacturer’s products. EDID can be changed even if a source is connected to the input and powered ON. Problem: “My system consists of the following: a computer, a Lightware device, a WUXGA (1920x1200) LCD monitor, and an SXGA (1280x1024) projector. I would like to see the same image on the INFO: When EDID has been changed, the router toggles the HOTPLUG signal for 2 seconds. Some sources monitor and the projector. What EDID should I choose on the Lightware device?” do not sense this signal. In such cases, the source device must be restarted or powered OFF and ON again. Solution: If you want to see the image on both displays, you need to select the resolution of the smaller display (in this case SXGA), otherwise the smaller display may not show the higher resolution image.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

10. Technologies UMX-TPS-TX100 series – User's Manual 163

10.2. HDCP Management Not HDCP-compliant Sink 1. Lightware Visual Engineering is a legal HDCP adopter. Several functions have been developed which helps Not-HDCP compliant sink is connected to the receiver. Some sources (e.g. computers) always send HDCP to solve HDCP related problems. Complex AV systems often have both HDCP and non-HDCP components. encrypted signals if the receiver device reports HDCP compliancy, however, HDCP encryption is not required The transmitter allows transmitting HDCP encrypted and unencrypted signals. The devices will be still all the time (e.g. computer desktop image). If HDCP is enabled in the transmitter, the image will not be HDCP compliant as they will never output an encrypted signal to a non-HDCP compliant display device. If displayed on the sink. an encrypted signal is switched to a non-compliant output, a red screen alert or muted screen will appear. 10.2.1. Protected and Unprotected Content Many video sources send HDCP protected signal if they detect that the sink is HDCP capable – even if the content is not copyrighted. This can cause trouble if an HDCP capable device is connected between the source and the display. In this case, the content cannot be viewed on non-HDCP capable displays and interfaces like event controllers. Rental and staging technicians often complain about certain laptops, which are always sending HDCP encrypted signals if the receiver device (display, matrix router, etc.) reports HDCP Setting the HDCP parameter to Auto on the output port and disable HDCP on the input port, the transmitted compliancy. However, HDCP encryption is not required all the time e.g. computer desktop image, certain signal will not be encrypted if the content is not protected. Thus, non-HDCP compliant sinks will display non- laptops still do that. encrypted signal.

To avoid unnecessary HDCP encryption, Lightware introduced the HDCP enabling/disabling function: the Not HDCP-compliant Sink 2. HDCP capability can be disabled in the Lightware device. If HDCP is disabled, the connected source will detect that the sink is not HDCP capable, and turn off authentication. 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 10.2.2. Disable Unnecessary Encryption of the transmitter, the source will send encrypted signal. The sink is not HDCP compliant, thus, it will not HDCP Compliant Sink display the video signal but red screen will appear. If HDCP is disabled on the input port of the transmitter, the source will not send the signal. The solution is to replace the display device to an HDCP-capable one. All the devices are HDCP-compliant, no manual setting is required, both protected and unprotected contents are transmitted and displayed on the sink.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

10. Technologies UMX-TPS-TX100 series – User's Manual 164

10.3. Pixel Accurate Reclocking Jitter Signal reclocking is an essential important procedure in digital signal transmission. After passing the Signal instability in the time domain. The time difference between two signal transitions should be a fixed reclocking circuit, the signal becomes stable, jitter-free, and can be transmitted over more equipment like value, but noise and other effects cause variations. processors, or event controllers. Without reclocking, sparkles, noise, and jaggies appear on the image. + Lightware’s sophisticated Pixel Accurate Reclocking technology fixes more problems than general TMDS

reclocking. It removes not only intra-pair skew but inter-pair skew as well. The Pixel Accurate Reclocking - circuit eliminates the following errors: Jitter Intra-pair skew Skew between the + and - wires within a differential wire pair (e.g. Data2- and Data2+). It’s caused by different Noise wire lengths or slightly different wire construction (impedance mismatch) in DVI cable. It results in jitter. Electromagnetic interference between other electronic devices such as mobile phones, motors, etc. and the + DVI cable are coupled onto the signal. Too much noise results in increased jitter.

+

-

- Intra-pair skew Noise

Inter-pair skew Skew between two differential wire pairs in a cable. It is caused by different wire pair lengths or different number of twists in the DVI cable. Too much inter-pair skew results color shift in the picture or sync loss. +

-

+

-

Inter-pair skew

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 165

Appendix 11Tables, drawings, guides, and technical details as follows: ç Specifications ç Factory Default Settings ç Applied Ports (Network Settings) ç Content of the Backup File ç Cable Wiring Guide ç Mechanical Drawings ç Port Numbering ç Maximum Extension Distances ç Factory EDID List ç Release Notes of the Firmware Packages ç Hashtag Keyword List ç Further Information

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 166

11.1. Specifications DC power plug...... Phoenix® Combicon (2-pole) General Enclosure (UMX-TPS-TX100 series) Compliance...... CE Rack mountable...... no Electrical safety...... EN 62368-1:2014 Enclosure material...... 1 mm steel EMC (emission)...... IEC/EN 55032:2015 Dimensions in mm...... 221W x 100.4D x 26H EMC (immunity)...... IEC/EN 55035:2017 Dimensions in inch...... 8.7 W x 3.95 D x 1.02 H RoHS...... EN 63000:2018 Weight - UMX-TPS-TX120...... 629 g Warranty...... 3 years Weight - UMX-TPS-TX130...... 642 g Operating temperature...... 0° to +50°C (+32° to +122°F) Weight - UMX-TPS-TX140, -Plus...... 647 g Operating humidity...... 10% to 90%, non-condensing Weight - UMX-TPS-TX140K...... 660 g Cooling - UMX-TPS-TX100 series...... Passive Enclosure (WP-UMX-TPS-TX100 series) Cooling - WP/FP-UMX-TPS-TX100 series...... 1x built-in fan Rack mountable...... No

Power (UMX-TPS-TX100 series) Enclosure material...... 1 mm steel Power supply option...... Power adaptor / PoE Dimensions in mm...... 115.9W x 67.5D x 114.3H Power consumption (min / max)...... 4.5W / 6.5W Dimensions in inch...... 4.56 W x 2.65 D x 4.5 H Heat dissipation (min / max)...... 15 BTU/h / 22 BTU/h Weight...... 457 g Power over Ethernet (PoE)...... via TPS output (IEEE 802.3af) Enclosure (FP-UMX-TPS-TX100 series) Power Adaptor (supplied) Rack mountable...... No Supported power source...... 100-240 V AC; 50/60 Hz Enclosure material...... 1 mm steel Supplied power...... 12V DC, 1A Dimensions in mm...... 116 W x 54.4 D x 77 H AC power plug...... Interchangable (EU, UK, JP/US, AUS/NZ) Dimensions in inch...... 4.56 W x 2.14 D x 3.03 H DC power plug...... Locking DC connector (2.1/5.5 mm pin) Weight...... 330 g

Power (FP/WP-UMX-TPS-TX100 series) Weight with MKM bracket ...... 606 g Power supply option...... Power adaptor / PoE Video Ports Power consumption (min / max)...... 6.4W / 10.9W VGA Input Heat dissipation (min / max)...... 22 BTU/h / 37 BTU/h Connector type...... DE-15F (15-pole D-sub Female) Power over Ethernet (PoE)...... via TPS output (IEEE 802.3af) Supported video signal...... Analog RGB and YPbPr video Power Adaptor (not supplied) Color depth...... Up to 24 bits, 8 bit/color Supported power source...... 100-240 V AC; 50/60 Hz Max. data rate...... Up to 170 MHz video and graphics digitizer Supplied power...... 48V DC, 1A Max. resolution...... Up to 1600x1200@60 Hz AC power plug...... Interchangable (EU, UK, JP/US, AUS/NZ)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 167

HDMI Input DVI-I Input (with digital signal support Connector type...... 19-pole HDMI Type A receptacle Connector type...... 29-pole DVI-I A/V standard...... DVI 1.0, HDMI 1.4 A/V standard...... DVI 1.0, HDMI 1.4 HDCP compliance...... HDCP 1.4 HDCP compliance...... HDCP 1.4 Color space...... RGB, YCbCr Color space...... RGB, YCbCr Video delay...... 0 frame Video delay...... 0 frame Supported resolutions at 8 bits/color *...... Supported resolutions at 8 bits/color *...... up to 4096x2160@30Hz (4:4:4) or 4096x2160@60Hz (4:2:0) ...... up to 4096x2160@30Hz (4:4:4) or 4096x2160@60Hz (4:2:0) ...... up to 3840x2160@30Hz (4:4:4) or 3840x2160@60Hz (4:2:0) ...... up to 3840x2160@30Hz (4:4:4) or 3840x2160@60Hz (4:2:0) ...... 1920x1080@60Hz (4:4:4) up to 12 bits/color ...... 1920x1080@60Hz (4:4:4) up to 12 bits/color Reclocking...... Pixel Accurate Reclocking Reclocking...... Pixel Accurate Reclocking 3D support...... yes 3D support...... yes Audio formats...... 8 channel PCM Audio formats...... 8 channel PCM ...... Dolby TrueHD, DTS-HD Master Audio 7.1 ...... Dolby TrueHD, DTS-HD Master Audio 7.1 * All standard VESA, CEA and other custom resolutions up to 300MHz (HDMI1.4) are supported...... * All standard VESA, CEA and other custom resolutions up to 300MHz (HDMI1.4) are supported...... DisplayPort Input DVI-I Input (with analog signal support) Connector type...... 20-pole DisplayPort receptacle Connector type...... 29-pole, DVI-I A/V standard...... DP 1.1a A/V standard...... DVI 1.0 HDCP compliance...... HDCP 1.4 Color depth...... up to 24 bits, 8 bits/color Color space...... RGB, YCbCr Color space...... Analog RGB and YPbPr video Video delay...... 0 frame Max. video resolutions...... 1600x1200@60 Hz, 24 bits Supported resolutions at 8 bits/color...... Max. data rate...... Up to 170 MHz video and graphics digitizer

...... up to 4096x2400@30Hz EDID Management ...... up to 2560x1600@60Hz EDID emulation...... yes, advanced EDID management ...... 1920x1080@120Hz EDID memory...... 120 factory presets, 15 programmable Audio formats...... 8 channel PCM 3D support...... yes

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 168

TPS Output Port Control Ports Connector type...... RJ45 connector RS-232 Serial port Power over Ethernet (PoE)...... yes, (IEEE 802.3af) Connector type...... 3-pole Phoenix connector Compliance...... HDBaseTTM Baud rates...... Between 4800 and 115200 Baud HDCP compliance...... HDCP 1.4 Data bits...... 8 or 9 Transferred signals...... Video, Audio, RS-232, Infrared, Ethernet Parity...... None / Odd / Even Color space...... RGB, YCbCr Stop bits...... 1 / 1.5 / 2 Video delay...... 0 frame Ethernet Supported resolutions at 8 bits/color *...... Connector type...... RJ45 female connector ...... up to 4096x2160@30Hz (4:4:4) or 4096x2160@60Hz (4:2:0) Ethernet data rate...... 10/100Base-T, full duplex with autodetect ...... up to 3840x2160@30Hz (4:4:4) or 3840x2160@60Hz (4:2:0) Power over Ethernet (PoE)...... Not supported ...... 1920x1080@60Hz (4:4:4) up to 12 bits/color Infrared Audio formats...... 8 channel PCM Input connector type...... 3.5 mm TRS (approx. 1/8" jack) ...... Dolby TrueHD, DTS-HD Master Audio 7.1 Output connector type...... 3.5 mm TS (approx. 1/8" jack)

Audio Ports Input carrier frequency...... 38 kHz Analog Audio Input (Jack) Output signal...... modulated (38kHz) Connector type...... 3.5 mm TRS (1/8" jack) GPIO * Audio format...... 2-ch PCM Connector type...... 8-pole Phoenix connector Sampling frequency...... 48 kHz Number of configurable pins...... 7 Maximum input level...... +0 dBu, 0.77 Vrms, 2.19 Vpp Port direction...... Input or output Signal transmission...... unbalanced signal USB Specifications ** Volume...... -95.62 – 0 dB Connector type...... mini-B type Balance...... 0 - 100 (50 = center) Device class...... USB HID devices Analog Audio Input (Phoenix) USB HUB...... Not supported Connector type...... 5-pole Phoenix connector * GPIO port can be found on UMX-TPS-TX130, -TX140,- TX140K and -TX140-Plus models Audio format...... 2-ch PCM ** USB port can be found on UMX-TPS-TX140K model only Sampling frequency...... 48 kHz Maximum input level...... +4 dBu, 1.23 Vrms, 3.47 Vpp Signal transmission...... Balanced / unbalanced signals Balance...... 0 - 100 (50 = center) Volume...... -95.62 – 0 dB

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 169

11.2. Factory Default Settings Parameter Setting/Value

Parameter Setting/Value Databits 8 Crosspoint settings Parity None Video I1 (VGA in) Stopbits 1 Audio I1 (Analog audio in 1) Operation mode Pass-through Video port settings Command injection port nr. - Local 8001 HDCP Enabled Command injection port nr. - TPS 8002 Autoselect Disabled IR port settings Emulated EDID on analog video inputs Factory #89: Universal Analog EDID Command injection status Enabled Emulated EDID on digital video inputs Dynamic #1: Copy EDID from connected sink device. Comm. inj. input port nr. - Local 9001 Test pattern mode Auto Comm. inj. output port nr. - Local 9002 Test pattern resolution 640x480p Comm. inj. input port nr. - TPS 9003 Test pattern color (RGB code) #7F7F7F (grey) Comm. inj. output port nr. - TPS 9004 Test pattern resolution on Testpattern input (I6) 640x480p GPIO port settings Test pattern color (RGB code) on Testpattern input Output level High #108020 (green) (I6) Direction Input Output signal type Auto 11.3. Applied Ports (Network Settings) Output HDCP mode Auto The following ports are necessary to pass via a network switch/firewall for a proper working between the Power 5V mode Always on device and the softwares: Color space Auto Purpose/function Affected software Protocol Port nr. TPS mode Auto Firmware update TFTP LDU2 UDP 69 Analog audio port settings (I1 and I5) Volume 0.00 dB (100%) UDP 49990 Balance 50 (center) UDP 49995 Network settings Device Discovery LDC UDP 224.0.0.251:5353 IP address 192.168.0.100 Remote IP LDC UDP 230.76.87.82:37421 Subnet mask 255.255.255.0 Find me (LMDMP) - UDP 230.76.87.82:37422 Static gateway 192.168.0.1 LW2 protocol - TCP 10001 DHCP Disabled LW3 protocol - TCP 6107 LW2 port number 10001 HTTP port - TCP 80 LW3 port number 6107 RS-232 command injection - TCP 8001 HTTP port number 80 RS-232 settings IR command injection - TCP 9001, 9002 Control protocol LW2 Baud rate 57600

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 170

11.4. Content of the Backup File GPIO port configuration (pin 1-7) The backup file contains numerous settings and parameters saved from the device. When the file is uploaded Event manager: settings of all Events (E1-E100) to a device, the followings will be overwritten: Values of the variables Analog video input ports (VGA, DVI-A) Horizontal position, Vertical position, Active horizontal size, Active vertical size, Total horizontal size, Pixel phase Test pattern mode, Test pattern resolution, Test pattern color Digital video input ports (HDMI, DP, DVI-D) Video port name, Audio port name, HDCP setting Test pattern mode, Test pattern resolution, Test pattern color TPS output port Port name, HDCP mode, HDMI mode, Power +5V mode, Color space setting Analog audio input ports Port name, Volume, Balance Crosspoint settings Video crosspoint settings, audio crosspoint settings Autoselect (enable/disable, delay settings, priority list) Mute/lock state of video ports, Mute/lock state of audio ports Serial ports (local and TPS) RS-232 mode, Control protocol, Baud rate, Data bits, Stop bits, Parity Port name and Command Injection (CI) port number IR port Port status (enable / disable), Code length, Repetition code, Modulation state Input port name, Output port name CI status (enable / disable), CI port number Network settings DHCP status (enable / disable), Static IP address, Network mask, Gateway address, LW2/LW3/HTTP port nr MAC filter allowlist, Port blocking settings TCP client settings (/CTRL/TCP) Further settings RS-232 recognizer settings Cleartext login settings Device label, Control lock, Dark mode state, Button functions User presets (U1-U32), User EDID data (U1-U15), Event Manager: settings of all Events (E1-E20)

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 171

11.5. Cable Wiring Guide From Unbalanced Output to Balanced Input Inputs and outputs of audio devices are symmetric or asymmetric. The main advantage of the symmetric 2 x 6.3 (1/4") TS - Phoenix 2 x RCA - Phoenix 3.5 (1/8") TRS - Phoenix lines is the better protection against the noise therefore, they are widely used in the professional audio industry. Symmetric audio is most often referred to as balanced audio, as opposed to asymmetric, which is referred to as unbalanced audio. Ligthware products are usually built with 5-pole Phoenix connectors so we would like to help users assembling their own audio cables. See the most common cases below. ATTENTION! Symmetric and asymmetric lines can be linked with passive accessories (e.g. special cables), but in this case half of the line level is lost. ATTENTION! There are numerous types of regularly used connector and cable types to connect audio devices. Please always make sure that a connector or cable fits your system before use. From Balanced Output to Unbalanced Input ATTENTION! Never join the phase-inverted (negative, cold or -) poles (either right and left) to the ground or to each other on the output side, as this can damage the unit. Phoenix - 2 x 6.3 (1/4") TS Phoenix - 2 x RCA Phoenix - 3.5 (1/8") TRS INFO: Use a galvanic isolation in case of a ground loop.

11.5.1. Serial Ports The device is built with 3-pole Phoenix connector. See the below examples of connecting to a DCE (Data Circuit-terminating Equipment) or a DTE (Data Terminal Equipment) type device: Lightware device and a DCE Lightware device and a DTE D-SUB 9 and Phoenix D-SUB 9 and Phoenix

From Balanced Output to Balanced Input Phoenix - 2 x 6.3 (1/4") TRS Phoenix - 2 x XLR 2 x 6.3 TRS (1/4") - Phoenix

11.5.2. Audio Ports

The Pinout of the 5-pole Phoenix Connector 2 x XLR - Phoenix Phoenix - Phoenix Pin nr. Signal 1 Left+ 2 Left- 3 Ground 4 Right- 5 Right+

Compatible Plug Type: Phoenix® Combicon series (3.5mm pitch, 5-pole), type: MC 1.5/5-ST-3.5.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 172

11.6. Mechanical Drawings Top View 11.6.1. UMX-TPS-TX100 series UMX-TPS-TX140

UMX-TPS-TX140 can be seen in the pictures, but the dimensions are the same for all standalone transmitter Universal TPS Transmitter Rear LED functions Port legend LIVE Video only models. OFF: No power Audio only Blinking (1 sec): Normal operation 2 Video with embedded audio Fast blinking (0.5 sec): Firmware upgrade mode VIDEO SELECT: VGA HDMI DP DVI-D Continuous ON: Powered but no operation Front View Autoselect DVI-A RS-232 OFF: Pass-through mode Blinking: Command injection mode AUDIO SELECT: Audio1 HDMI emb. DP emb. ON: Control mode Audio2 DVI-D emb. SRVC VGA Audio1 HDCP RESET HDMI HDMI Autoselect Reserved

DP DP DVI-A Video 100.4

26 INPUT STATUS LED FUNCTIONS TPS link Audio2 DVI-D DVI-D OFF: No TPS link Blinking: Selected input has no signal VIDEO AUDIO Blinking: Low power mode VIDEO AUDIO SHOW Continuous ON: Signal present on active input VGA IN AUDIO1 IN 2 HDMI IN 3 DP IN INPUT STATUS SELECT SELECT ME ON: TPS link good Device can be remote powered over TPS link with PoE (IEEE 802.3af) 221 For best performance use AWG23 CAT6 or CAT7 SFTP cable

Sn: RoHS Rear View Made in EU, Hungary

PIN: 2.1mm RS-232 GPIO LIVE 5 AUDIO2 IN RS-232 SRVC LINK Side View TPS OUT ( PoE ) 12V 1A DC TX RX 1 2 3 4 5 6 7 Ethernet IR IN IR OUT LR 4 5 DVI-I IN

Bottom View

178.5 20

M3 thread M3 thread 84

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 173

11.6.2. WP-UMX-TPS-TX100 series 11.6.3. FP-UMX-TPS-TX100 series WP-UMX-TPS-TX130-US can be seen in the pictures, but the dimensions are the same for all wall plate FP-UMX-TPS-TX130 can be seen in the pictures, but the dimensions are the same for all floor plate models. models. Dimensions are in mm. Dimensions are in mm.

Front View Front View Ø7.5 90°/Ø (4x) 116 WP-UMX-TPS-TX130-US

VIDEO AUDIO SHOW SELECT SELECT ME

Ethernet INPUT STATUS VGA AUDIO

DP DP 77 HDMI HDMI Autoselect TPS LINK IR VIDEO AUDIO RESET 114.3

VGA IN AUDIO IN 2 DP IN 3 HDMI IN

115.9 Rear View Side View Rear View Side View 54.4 15.45 29.15 13.7

RS-232 48V 1A DC

TX RX TX 52 52 83.4

Sn: RoHS

Made in EU, Hungary

94 17.7 33.15 15.45 10.95 94 10.95 13 45.5 9 34.95 46 34.95

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 174

11.7. Port Numbering 11.7.3. UMX-TPS-TX120 11.7.1. WP-UMX-TPS-TX120-US Audio/Video Ports

Audio/Video Ports Video port nr. (LW3) Emulated Audio port nr. (LW3) Video port Audio port Port name Till fw From fw EDID Till fw From fw Video port nr. (LW3) Emulated Audio port nr. (LW3) nr. (LW2) nr. (LW2) Video port Audio port v1.0.3 v1.1.0 memory v1.0.3 v1.1.0 Port name EDID nr. (LW2) Till fw From fw nr. (LW2) Till fw From fw VGA in I1 P1 I1 E1 - - - v1.0.3 v1.1.0 memory v1.0.3 v1.1.0 HDMI in I2 P2 I2 E2 I2 P2 I2 VGA in I1 P1 I1 E1 - - - Test pattern I3 P3 I3 - - - - HDMI in I2 P2 I2 E2 I2 P2 I2 Audio in - - - - I1 P1 I1 Test pattern I3 P3 I3 - - - - TPS out O1 P4 O1 - O1 P3 O1 Audio in - - - - I1 P1 I1 TPS out O1 P4 O1 - O1 P3 O1 IR and RS-232 Ports

RS-232 and IR Ports Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) Local IR input S1 Local serial port P1 Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) Local IR output D1 TPS serial link P2 Local serial port P1 Local IR input S1 TPS IR input S2 TPS serial link P2 TPS IR input S2 TPS IR output D2 11.7.2. WP-UMX-TPS-TX130-US / WP-UMX-TPS-TX130-Plus-US 11.7.4. UMX-TPS-TX130 Audio/Video Ports Audio/Video Ports Video port nr. (LW3) Emulated Audio port nr. (LW3) Video port Audio port Video port nr. (LW3) Emulated Audio port nr. (LW3) Port name Till fw From fw EDID Till fw From fw Video port Audio port nr. (LW2) nr. (LW2) Port name EDID v1.0.3 v1.1.0 memory v1.0.3 v1.1.0 nr. (LW2) Till fw From fw nr. (LW2) Till fw From fw memory VGA in I1 P1 I1 E1 - - - v1.0.3 v1.1.0 v1.0.3 v1.1.0 DP in I2 P2 I2 I2 P2 I2 VGA in I1 P1 I1 E1 - - - HDMI in I3 P3 I3 E2 I3 P3 I3 HDMI in I2 P2 I2 E2 I2 P2 I2 Test pattern I4 P4 I4 - - - - DVI-D in I3 P3 I3 E3 I3 P3 I3 Audio in - - - - I1 P1 I1 DVI-A in I4 P4 I4 E4 - - - TPS out O1 P5 O1 - O1 P4 O1 Test pattern I5 P5 I5 - - - - Audio in - - - - I1 P1 I1 RS-232 and IR Ports TPS out O1 P6 O1 - O1 P4 O1

Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) IR and RS-232 Ports Local serial port P1 Local IR input S1 Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) TPS serial link P2 TPS IR input S2 Local IR input S1 Local serial port P1 Local IR output D1 TPS serial link P2 TPS IR input S2 TPS IR output D2

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 175

11.7.5. UMX-TPS-TX140 / UMX-TPS-TX140-Plus 11.7.7. FP-UMX-TPS-TX130

Audio/Video Ports Audio/Video Ports Emulated Video port nr. (LW3) Emulated Audio port nr. (LW3) Video port Video port Audio port Audio port Video port Audio port Port name EDID Port name EDID nr. (LW2) nr. (LW3) nr. (LW2) nr. (LW3) nr. (LW2) Till fw From fw nr. (LW2) Till fw From fw memory v1.0.3 v1.1.0 memory v1.0.3 v1.1.0 VGA in 1 I1 E1 - - VGA in I1 P1 I1 E1 - - - DP in 2 I2 2 I2 HDMI in I2 P2 I2 E2 I2 P2 I2 HDMI in 3 I3 E2 3 I3 DP in I3 P3 I3 E3 I3 P3 I3 Test pattern 4 I4 - - - DVI-D in I4 P4 I4 E4 I4 P4 I4 Audio in - - - 1 I1 DVI-A in I5 P5 I5 E5 - - - TPS out 1 O1 - 1 O1 Test pattern I6 P6 I6 - - - - Audio1 in - - - - I1 P1 I1 RS-232 and IR Ports Audio2 in - - - - I5 P5 I5 TPS out O1 P7 O1 - O1 P6 O1 Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) Local serial port P1 Local IR input S1 IR and RS-232 Ports TPS serial link P2 TPS IR input S2 Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) TPS IR output D1 Local IR input S1 Local serial port P1 Local IR output D1 TPS serial link P2 11.8. Maximum Extension Distances TPS IR input S2 Cable lengths ( Auto / Longreach TPS mode) Pixel clock TPS IR output D2 Resolution rate CAT5e AWG24 CAT7 AWG26** CAT7 AWG23 11.7.6. FP-UMX-TPS-TX120 1024x768@60Hz 65 MHz 100 m / 130 m* 90 m / 120 m* 120 m / 170 m* Audio/Video Ports 1280x720p@60Hz 73.8 MHz 100 m / 130 m* 90 m / 120 m* 120 m / 170 m* Emulated Video port Video port Audio port Audio port 1920x1080p@60Hz / 24bpp 148.5 MHz 100 m / 130 m* 90 m / 120 m* 120 m / 170 m* Port name EDID nr. (LW2) nr. (LW3) nr. (LW2) nr. (LW3) memory 1920x1200@60Hz 152.9 MHz 100 m / NA 90 m / NA 120 m / NA VGA in 1 I1 E1 - - 1600x1200@60Hz 162 MHz 100 m / NA 90 m / NA 120 m / NA HDMI in 2 I2 E2 2 I2 1920x1080@60Hz / 36bpp 223.6 MHz 70 m / NA 70 m / NA 100 m / NA Test pattern 3 I3 - - - Audio in - - - 1 I1 3840x2160@30Hz UHD 297 MHz 70 m / NA 70 m / NA 100 m / NA TPS out 1 O1 - 1 O1 4096x2160@30Hz 4K 297 MHz 70 m / NA 70 m / NA 100 m / NA

RS-232 and IR Ports * With Long reach operation mode which supports pixel clock frequencies up to 148.5 MHz. ** When remote powering is used with AWG26 cables, distances are 20% shorter. Port name Port nr. (LW2 / LW3) Port name Port nr. (LW2 / LW3) Local serial port P1 Local IR input S1 TPS serial link P2 TPS IR input S2 TPS IR output D1

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 176

11.9. Factory EDID List Mem Resolution Type EDID features

Mem Resolution Type EDID features F35 1280 x 720p @ 50.00 Hz H 2chLPCM F1 640 x 480p @ 60.00 Hz D F36 1280 x 720p @ 60.00 Hz H 2chLPCM F2 848 x 480p @ 60.00 Hz D F37 1920 x 1080i @ 50.04 Hz H 2chLPCM F3 800 x 600p @ 60.32 Hz D F38 1920 x 1080i @ 50.00 Hz H 2chLPCM F4 1024 x 768p @ 60.00 Hz D F39 1920 x 1080i @ 60.05 Hz H 2chLPCM F5 1280 x 768p @ 50.00 Hz D F40 1920 x 1080i @ 60.05 Hz H 2chLPCM F6 1280 x 768p @ 59.94 Hz D F41 1920 x 1080p @ 24.00 Hz H 2chLPCM F7 1280 x 768p @ 75.00 Hz D F42 1920 x 1080p @ 25.00 Hz H 2chLPCM F8 1360 x 768p @ 60.02 Hz D F43 1920 x 1080p @ 30.00 Hz H 2chLPCM F9 1280 x 1024p @ 50.00 Hz D F44 1920 x 1080p @ 50.00 Hz H 2chLPCM F10 1280 x 1024p @ 60.02 Hz D F45 1920 x 1080p @ 59.94 Hz H 2chLPCM F11 1280 x 1024p @ 75.02 Hz D F46 1920 x 1080p @ 60.00 Hz H 2chLPCM F12 1400 x 1050p @ 50.00 Hz D F47 1920 x 1080p @ 60.00 Hz U 2chLPCM 2chLPCM, 8chLPCM, DD, DTS, AAC, DD+, DTS-HD, F13 1400 x 1050p @ 60.00 Hz D F48 1920 x 1080p @ 60.00 Hz U MLP, DST, WMAP F14 1400 x 1050p @ 75.00 Hz D 2chLPCM, 8chLPCM, DD, DTS, AAC, DD+, DTS-HD, F49 1920 x 1080p @ 60.00 Hz U F15 1680 x 1050p @ 60.00 Hz D MLP, DST, WMAP F16 1920 x 1080p @ 50.00 Hz D F50 720 x 480i @ 30.03 Hz A F17 1920 x 1080p @ 60.00 Hz D F51 720 x 576i @ 25.04 Hz A F18 2048 x 1080p @ 50.00 Hz D F52 640 x 480p @ 60.00 Hz A F19 2048 x 1080p @ 60.00 Hz D F53 640 x 480p @ 75.00 Hz A F20 1600 x 1200p @ 50.00 Hz D F54 800 x 600p @ 50.00 Hz A F21 1600 x 1200p @ 60.00 Hz D F55 800 x 600p @ 60.32 Hz A F22 1920 x 1200p @ 50.00 Hz D F56 800 x 600p @ 75.00 Hz A F23 1920 x 1200p @ 59.56 Hz D F57 1024 x 768p @ 49.99 Hz A F24 2048 x 1200p @ 59.96 Hz D F58 1024 x 768p @ 60.00 Hz A F29 1920 x 1080p @ 60.00 Hz U F59 1024 x 768p @ 75.03 Hz A F30 1440 x 480i @ 60.05 Hz H 2chLPCM F60 1280 x 768p @ 50.00 Hz A F31 1440 x 576i @ 50.08 Hz H 2chLPCM F61 1280 x 768p @ 59.94 Hz A F32 640 x 480p @ 59.95 Hz H 2chLPCM F62 1280 x 768p @ 75.00 Hz A F33 720 x 480p @ 59.94 Hz H 2chLPCM F63 1360 x 768p @ 60.02 Hz A F34 720 x 576p @ 50.00 Hz H 2chLPCM F64 1364 x 768p @ 50.00 Hz A

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 177

Mem Resolution Type EDID features Mem Resolution Type EDID features F65 1364 x 768p @ 59.94 Hz A F107 2560 x 1440p @ 59.95 Hz H 2chLPCM F66 1364 x 768p @ 74.99 Hz A F108 2560 x 1600p @ 59.86 Hz H 2chLPCM F67 1280 x 1024p @ 50.00 Hz A F109 3840 x 2400p @ 24.00 Hz H 2chLPCM F68 1280 x 1024p @ 60.02 Hz A F110 3840 x 2160p @ 24.00 Hz H 2chLPCM F69 1366 x 1024p @ 60.00 Hz A F111 3840 x 2160p @ 25.00 Hz H 2chLPCM F70 1400 x 1050p @ 50.00 Hz A F112 3840 x 2160p @ 30.00 Hz H 2chLPCM F71 1400 x 1050p @ 60.00 Hz A F118 3840 x 2160p @ 30.00 Hz U 2chLPCM 2chLPCM, 8chLPCM, DD, DTS, AAC, DD+, DTS-HD, F72 1400 x 1050p @ 75.00 Hz A F119 3840 x 2160p @ 30.00 Hz U MLP, DST, WMAP F73 1920 x 540i @ 50.00 Hz A F120 3840 x 2160p @ 60.00 Hz H 2chLPCM F74 1920 x 540i @ 60.00 Hz A F75 1920 x 1080p @ 50.00 Hz A F76 1920 x 1080p @ 60.00 Hz A Legend F77 1600 x 1200p @ 50.00 Hz A D: DVI EDID F78 1600 x 1200p @ 60.00 Hz A H: HDMI EDID F79 1920 x 1200p @ 59.56 Hz A U: Universal EDID, supporting many standard resolutions: F80 1920 x 1200p @ 50.00 Hz A ▪ F29: Universal EDID for DVI signals (no audio support). F89 1920 x 1200p @ 59.56 Hz U ▪ F47: HDMI EDID supporting PCM audio. ▪ F48: HDMI EDID supporting all type of audio. F90 1920 x 2160p @ 59.99 Hz D ▪ F49: HDMI EDID supporting all type of audio and deep color. F91 1024 x 2400p @ 60.01 Hz D ▪ F89: Universal EDID for analog signals (no audio support). F94 2048 x 1536p @ 60.00 Hz D ▪ F118: HDMI EDID supporting PCM audio and 4K@30 Hz signals. F96 2560 x 1600p @ 59.86 Hz D ▪ F119: HDMI EDID supporting all type of audio and 4K@30 Hz signals. F97 3840 x 2400p @ 24.00 Hz D DiD (in column EDID features): with Display ID support F98 1280 x 720p @ 60.00 Hz H 2chLPCM Please note that minor changes in the factory EDID list may be applied in farther firmware versions. F99 1920 x 1080p @ 60.00 Hz H 2chLPCM F100 1024 x 768p @ 60.00 Hz H 2chLPCM F101 1280 x 1024p @ 50.00 Hz H 2chLPCM F102 1280 x 1024p @ 60.02 Hz H 2chLPCM F103 1280 x 1024p @ 75.02 Hz H 2chLPCM F104 1600 x 1200p @ 50.00 Hz H 2chLPCM F105 1600 x 1200p @ 60.00 Hz H 2chLPCM F106 1920 x 1200p @ 59.56 Hz H 2chLPCM

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 178

11.10. Release Notes of the Firmware Packages v1.4.0b8 11.10.1. UMX-TPS-TX100 Series Release date: 2019-07-23 v1.5.0b4 New feature: Release date: 2021-05-17 ▪ KVM transmission between USB HID (Human Interface Devices, e.g. keyboard, mouse, presenter over PC or a Laptop) for UMX-TPS-TX140K only! New feature: ▪ Added support for FP-UMX-TPS-TX120-GES, FP-UMX-TPS-TX130-GES product variants. ▪ Added property to indicate FeaturePackVersion (Advanced Control pack v3) ▪ New bootloader is used, which allows the connected TPS-RX95's to be updated remotely. ▪ Added AND operator for Event Manager Conditions (Advanced Control pack v3) ▪ Crosspoint properties and methods changed. Warning: If you are using an external controller for this ▪ Added Condition triggering for Event Manager (Advanced Control pack v3) for UMX-TPS-TX140-Plus device via LW3 protocol, the recent changes in property and node names may result in difficulties to and UMX-TPS-TX140K only! control the TPS device with the latest firmware. ▪ Added Condition detect on property change to anything in Event Manager (Advanced Control pack v3) ▪ WP-UMX-TPS-TX100-WHITE products are now supported. ▪ Added Variable handling for Event Manager (Advanced Control pack v3) for UMX-TPS-TX140-Plus and ▪ The method of storing device settings in EEPROM is updated, which may result in losing all the settings, UMX-TPS-TX140K only! logs and user EDID's after updating to 1.1.0. The LDU software contains a plug-in to help you keep the ▪ Added Permanent TCP clients with configurable target IP address, and Message recognizer for TCP actual settings after firmware update. clients (Advanced Control pack v3) for UMX-TPS-TX140-Plus and UMX-TPS-TX140K only! ▪ Event Manager configuration became more user friendly: actions can be triggered manually for testing ▪ Added LW3 command-salvo over Http POST (protocol.lw3) (Advanced Control pack v3) for UMX-TPS- and the user interface shows if any of the conditions are met. TX140-Plus and UMX-TPS-TX140K only! ▪ Event Manager updated: time delay can be configured between condition and action, a condition can ▪ Added Http message sending with sendHttpPost and sendHttpPut (target server IP, target filepath, trigger multiple actions at the same time, inverse condition can be used. header, body) (Advanced Control pack v3) for UMX-TPS-TX140-Plus and UMX-TPS-TX140K only! ▪ 3840x2160p60 YUV4:2:0 factory EDID added. ▪ Added method to send Wake On LAN packet (Advanced Control pack v3) ▪ IR command injection is now supported: data received on a specific TCP port is transmitted as IR ▪ Added cleartext login function (disabled by default) (Advanced Control pack v3) for UMX-TPS-TX140- signal, and the received IR frames are also sent to this TCP connection. Plus and UMX-TPS-TX140K only! ▪ Fan can be controlled manually with setFan() LW3 method. ▪ Added MAC filtering (Advanced Control pack v3) for UMX-TPS-TX140-Plus and UMX-TPS-TX140K only! ▪ EDID node properties changed: PreferredResolution, MonitorName and AudioInfo properties are added ▪ Added IP port and services filtering (Advanced Control pack v3) for UMX-TPS-TX140-Plus and UMX- ▪ The device is able to identify IR commands on either the local or link IR input port. This feature can be TPS-TX140K only! connected to Event Manager, which means, that the device can be programmed to do various actions, ▪ Added Macro capability (running partial device preset with tags) (Advanced Control pack v3) for UMX- if a specific IR command is detected. TPS-TX140-Plus and UMX-TPS-TX140K only! ▪ TCP and UDP messages can be sent by the device to control projectors and any other devices. This ▪ Added new method for CEC control button sendClick (Advanced Control pack v3) for UMX-TPS-TX140- feature can also be used with Event Manager. Plus and UMX-TPS-TX140K only! ▪ Audio and video port names are changed: 'I' is used for inputs and 'O' is used for outputs, instead of 'P'. ▪ Added LMDMP (Lightware Multicast Device Management Protocol) feature. ▪ New EDID driver is used, the content of some factory EDID's are changed according to EDID 1.3 and ▪ Modified DeviceLabel property default text to LW__ 1.4 standard. ▪ Added properties in root node: FirmwareVersion, PackageVersion, MacAddress. ▪ Autoselection connect and disconnect delay can be configured via LW3 methods. ▪ Minor performance improvements and modifications. ▪ Firmware platform library updated ▪ Added Network HostName property (default: lightware-). ▪ Sending IR codes (SendProntoHex e.g. send max. 200 Byte IR code with Event Actions) for UMX-TPS- TX140-Plus only! ▪ Added new ConnectedSource property for media output nodes. ▪ Added 'Disable default button function' option to support button customization in Event Manager ▪ Introduces \u201c--test\u201d option for the update CLI command. This \u201cupdate test mode\ Modified RS-232 modes ot support SendMessage in Control mode u201d checks communication with the device over various protocols. One can perform this verification ▪ step before actually starting the device update. ▪ CEC - sendCEC command (e.g. turn on the TV with Event Actions) for WP-UMX-TPS-TX130-Plus only!

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 179

▪ LWROS integration compatible for LDU2 only! v1.3.0b11 ▪ Added 'Dark mode' function to turn off front panel LEDs Release date: 2019-04-17 ▪ Modified DP input driver to fix HDCP issue with MacBooks New feature: ▪ RS232 Minimal Recognizer for Cisco compatibility (Cisco Login) for WP-UMX-TPS-TX130-Plus only! ▪ RS232 Minimal Recognizer for Cisco compatibility (Cisco Login) for UMX-TPS-TX140-Plus only! ▪ Improved GPIO detection ▪ Sending IR codes (SendProntoHex e.g. send max. 200 Byte IR code with Event Actions) for UMX-TPS- TX140-Plus only! ▪ Use LDU2 v1.2.5 or later for the update! ▪ Use LDU2 v1.2.3 or later for the update! ▪ Added 'User replaceable miniweb slot' to support built-in control webpage ▪ CEC - sendCEC command (e.g. turn on the TV with Event Actions) for UMX-TPS-TX140-Plus only! ▪ Added 'Forced button lock' function to lock buttons via protocol command Bugfix: Bugfix: ▪ Fixed Event Manager condition linking ▪ Poe enable state is now reloaded after reboot. v1.2.1b8 ▪ Input video parameter measurement speed improved. Release date: 2019-01-29 ▪ Unsupported dual link DVI EDIDs removed from factory EDID list. New feature: ▪ /SYS/MB/UMXDP node renamed to /SYS/MB/DP ▪ Firmware platform library updated ▪ Event manager conditions did not work if DP input properties were selected. ▪ Modified DP input driver to fix HDCP issue with MacBooks ▪ If the user switched to the currently selected port, the output was disconnected and connected again unnecessarily, which resulted in a picture drop. Fixed. ▪ Compatible for LDU2 only! ▪ Compatibility issues with Gefen HDMI 1.3 HdBaseT extender fixed. ▪ Modified RS-232 modes ot support SendMessage in Control mode ▪ In case of sending DVI signal on the output, the audio output port does not indicate signal present. ▪ Added 'Disable default button function' option to support button customization in Event Manager ▪ If the output was set to HDCP Always mode, the signal was sent out unencrypted, if the input port was ▪ Added 'Forced button lock' function to lock buttons via protocol command disconnected and connected again. This issue only happened, if the input signal was also unencrypted. ▪ Added 'Dark mode' function to turn off front panel LEDs ▪ If no sync screen is active, the output resolution is now reported correctly by the output port. ▪ Video crosspoint driver improvements ▪ Reporting the resolution of signals in YUV 4:2:0 colorspace fixed. ▪ AV input driver improvements ▪ In case of sending 1920x1200 no sync screen, the device did not notice the connection state changes on the inputs. Fixed. ▪ Improved GPIO detection speed (quick impulses can be detected, even low as 80ms) v1.3.2b1 v1.1.7b2 Release date: 2019-05-21 Release date: 2018-05-18 Bugfix: Bugfix: ▪ Use LDU2 v1.2.5 or later for the update! ▪ Rs232 even parity parameter bug fixed. v1.3.1b1 v1.1.6b1 Release date: 2019-04-17 Release date: 2018-04-10 Bugfix: New feature: ▪ bugfix ot support for previous HW versions ▪ New control.html.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 180

v1.1.5b1 v1.1.0b1 Release date: 2018-03-01 Release date: 2016-04-11 New feature: New feature: ▪ New miniweb. ▪ New EDID driver is used, the content of some factory EDID's are changed according to EDID 1.3 and 1.4 standard. v1.1.3b1 ▪ EDID node properties changed: PreferredResolution, MonitorName and AudioInfo properties are added Release date: 2017-10-18 ▪ Audio and video port names are changed: 'I' is used for inputs and 'O' is used for outputs, instead of 'P'. Bugfix: ▪ Crosspoint properties and methods changed. Warning: If you are using an external controller for this ▪ Fixed GPIO PortUiCode. device via LW3 protocol, the recent changes in property and node names may result in difficulties to v1.1.2b4 control the TPS device with the latest firmware. ▪ TCP and UDP messages can be sent by the device to control projectors and any other devices. This Release date: 2017-10-16 feature can also be used with Event Manager. New feature: ▪ IR command injection is now supported: data received on a specific TCP port is transmitted as IR signal, and the received IR frames are also sent to this TCP connection. ▪ The text names of the ports are changed to be more precise, and less ambiguous. ▪ The device is able to identify IR commands on either the local or link IR input port. This feature can be ▪ With too many devices connected, one can find it hard to pair the physically connected devices with the connected to Event Manager, which means, that the device can be programmed to do various actions, listed devices in LDC device discovery window. That is why Lightware is introducing the new IdentifyMe if a specific IR command is detected. feature, which identifies the desired device by blinking its LEDs for a period of time. That helps the user visually recognize the requested device. ▪ Factory default can be given in the board component. ▪ Now Bonjour shows firmware version as well. ▪ New bootloader is used, which allows the connected TPS-RX95's to be updated remotely. Bugfix: ▪ Event Manager updated: time delay can be configured between condition and action, a condition can trigger multiple actions at the same time, inverse condition can be used. ▪ Fixed a bug that made the 'continuously exists' timing mode unable to use. ▪ Dynamic edid can be deleted from code. ▪ Fixed a bug that caused Event Manager's 47th event to be unlink-able. ▪ 3840x2160p60 YUV4:2:0 factory EDID added. v1.1.1b1 ▪ Event Manager configuration became more user friendly: actions can be triggered manually for testing Release date: 2016-05-11 and the user interface shows if any of the conditions are met. New feature: ▪ FRAMEWORK update.BUGFIX: Minor bug fix in default emulated edids. ▪ Autoselection connect and disconnect delay can be configured via LW3 methods. ▪ The method of storing device settings in EEPROM is updated, which may result in losing all the settings, logs and user EDID's after updating to 1.1.0. The LDU software contains a plug-in to help you keep the Bugfix: actual settings after firmware update. ▪ Unsupported dual link DVI EDIDs removed from factory EDID list. ▪ Default emulated edid for UmxAvFrontend handling changed. ▪ Event manager conditions did not work if DP input properties were selected. Bugfix: ▪ Input background measurement speed improved. ▪ Error log is accessible at /MANAGEMENT/LOG/RAMLOG node. ▪ If the user switched to the currently selected port, the output was disconnected and connected again ▪ If no sync screen is active, the output resolution is now reported correctly by the output port. unnecessarily, which resulted in a picture drop. Fixed. ▪ Compatibility issues with Gefen HDMI 1.3 HdBaseT extender fixed. ▪ /SYS/MB/UMXDP node renamed to /SYS/MB/DP ▪ Reporting the resolution of signals in YUV 4:2:0 colorspace fixed. ▪ In case of sending DVI signal on the output, the audio output port does not indicate signal present.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 181

▪ In case of sending 1920x1200 no sync screen, the device did not notice the connection state changes ▪ Added Network HostName property (default: lightware-). on the inputs. Fixed. ▪ Added new ConnectedSource property for media output nodes. ▪ If the output was set to HDCP Always mode, the signal was sent out unencrypted, if the input port was disconnected and connected again. This issue only happened, if the input signal was also unencrypted. Bugfix: ▪ Poe enable wasn't saved. ▪ Fixed issue with tick counter when the device is continuously operating for a very long time. ▪ Cable diagnostics properties are moved to SYS/MB/TPS/REMOTE node. v1.4.0b8

11.10.2. WP- and FP-UMX-TPS-TX100 series Release date: 2019-07-23 New feature: v1.5.0b6 ▪ Added support for FP-UMX-TPS-TX120-GES, FP-UMX-TPS-TX130-GES product variants. Release date: 2021-06-30 ▪ Audio and video port names are changed: 'I' is used for inputs and 'O' is used for outputs, instead of 'P'. New feature: ▪ New EDID driver is used, the content of some factory EDID's are changed according to EDID 1.3 and ▪ Improved network compatibility with 10.x.x.x IP address range. 1.4 standard. ▪ Added property to indicate FeaturePackVersion (Advanced Control pack v3) ▪ TCP and UDP messages can be sent by the device to control projectors and any other devices. This feature can also be used with Event Manager. ▪ Added AND operator for Event Manager Conditions (Advanced Control pack v3) ▪ WP-UMX-TPS-TX100-WHITE products are now supported. ▪ Added Condition triggering for Event Manager (Advanced Control pack v3) for WP-UMX-TPS-TX130- Plus-US only! ▪ The method of storing device settings in EEPROM is upgraded, which may result in losing all the settings, logs and user EDID's after upgrading to 1.1.0. The LDU software contains a plug-in to help you ▪ Added Condition detect on property change to anything in Event Manager (Advanced Control pack v3) keep the actual settings after firmware upgrade. ▪ Added Variable handling for Event Manager (Advanced Control pack v3) for WP-UMX-TPS-TX130-Plus- ▪ New bootloader is used, which allows the connected TPS-RX95's to be upgraded remotely. US only! ▪ Added Permanent TCP clients with configurable target IP address, and Message recognizer for TCP ▪ Crosspoint properties and methods changed. Warning: If you are using an external controller for this clients (Advanced Control pack v3) for WP-UMX-TPS-TX130-Plus-US only! device via LW3 protocol, the recent changes in property and node names may result in difficulties to control the TPS device with the latest firmware. ▪ Added LW3 command-salvo over Http POST (protocol.lw3) (Advanced Control pack v3) for WP-UMX- TPS-TX130-Plus-US only! ▪ Event Manager configuration became more user friendly: actions can be triggered manually for testing and the user interface shows if any of the conditions are met. ▪ Added Http message sending with sendHttpPost and sendHttpPut (target server IP, target filepath, header, body) (Advanced Control pack v3) for WP-UMX-TPS-TX130-Plus-US only! ▪ Fan can be controlled manually with setFan() LW3 method. ▪ Added method to send Wake On LAN packet (Advanced Control pack v3) ▪ 3840x2160p60 YUV4:2:0 factory EDID added. ▪ Added cleartext login function (disabled by default) (Advanced Control pack v3) for WP-UMX-TPS- ▪ IR command injection is now supported: data received on a specific TCP port is transmitted as IR TX130-Plus-US only! signal, and the received IR frames are also sent to this TCP connection. ▪ Added MAC filtering (Advanced Control pack v3) for WP-UMX-TPS-TX130-Plus-US only! ▪ Event Manager upgraded: time delay can be configured between condition and action, a condition can trigger multiple actions at the same time, inverse condition can be used. ▪ Added IP port and services filtering (Advanced Control pack v3) for WP-UMX-TPS-TX130-Plus-US only! ▪ EDID node properties changed: PreferredResolution, MonitorName and AudioInfo properties are added ▪ Added Macro capability (running partial device preset with tags) (Advanced Control pack v3) for WP- UMX-TPS-TX130-Plus-US only! ▪ The device is able to identify IR commands on either the local or link IR input port. This feature can be connected to Event Manager, which means, that the device can be programmed to do various actions, ▪ Added new method for CEC control button sendClick (Advanced Control pack v3) for UWP-UMX-TPS- TX130-Plus-US only! if a specific IR command is detected. Autoselection connect and disconnect delay can be configured via LW3 methods. ▪ Added LMDMP (Lightware Multicast Device Management Protocol) feature. ▪ Added 'Disable default button function' option to support button customization in Event Manager ▪ Modified DeviceLabel property default text to LW__ ▪ Improved GPIO detection ▪ Added properties in root node: FirmwareVersion, PackageVersion, MacAddress. ▪ Use LDU2 v1.2.5 or later for the upgrade! ▪ Minor performance improvements and modifications. ▪

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 182

▪ Sending IR codes (SendProntoHex e.g. send max. 200 Byte IR code with Event Actions) for UMX-TPS- v1.3.0b1 TX140-Plus only! Release date: 2019-04-17 ▪ Added 'Forced button lock' function to lock buttons via protocol command New feature: ▪ Modified DP input driver to fix HDCP issue with MacBooks ▪ FP-UMX-TPS-TX100-MK products are now supported. ▪ LWROS integration compatible for LDU2 only! v1.2.0b1 ▪ CEC - sendCEC command (e.g. turn on the TV with Event Actions) for WP-UMX-TPS-TX130-Plus only! Release date: 2019-05-21 ▪ Added 'User replaceable miniweb slot' to support built-in control webpage New feature: ▪ Modified RS-232 modes ot support SendMessage in Control mode ▪ WP-UMX-TPS-TX100-WHITE products are now supported. ▪ RS232 Minimal Recognizer for Cisco compatibility (Cisco Login) for WP-UMX-TPS-TX130-Plus only! v1.1.1b1 ▪ Firmware platform library updated Release date: 2019-05-21 ▪ Added 'Dark mode' function to turn off front panel LEDs New feature: Bugfix: ▪ Autoselection connect and disconnect delay can be configured via LW3 methods. ▪ Compatibility issues with Gefen HDMI 1.3 HdBaseT extender fixed. Bugfix: ▪ In case of sending DVI signal on the output, the audio output port does not indicate signal present. ▪ Input video parameter measurement speed improved. ▪ In case of sending 1920x1200 no sync screen, the device did not notice the connection state changes on the inputs. Fixed. ▪ /SYS/MB/UMXDP node renamed to /SYS/MB/DP ▪ If no sync screen is active, the output resolution is now reported correctly by the output port. ▪ Event manager conditions did not work if DP input properties were selected. ▪ Reporting the resolution of signals in YUV 4:2:0 colorspace fixed. ▪ If the user switched to the currently selected port, the output was disconnected and connected again unnecessarily, which resulted in a picture drop. Fixed. ▪ Input video parameter measurement speed improved. ▪ Unsupported dual link DVI EDIDs removed from factory EDID list. ▪ /SYS/MB/UMXDP node renamed to /SYS/MB/DP v1.1.0b4 ▪ Event manager conditions did not work if DP input properties were selected. Release date: 2019-05-21 ▪ If the user switched to the currently selected port, the output was disconnected and connected again unnecessarily, which resulted in a picture drop. Fixed. New feature: ▪ Unsupported dual link DVI EDIDs removed from factory EDID list. ▪ Fan can be controlled manually with setFan() LW3 method. ▪ Poe enable state is now reloaded after reboot. ▪ The method of storing device settings in EEPROM is upgraded, which may result in losing all the ▪ If the output was set to HDCP Always mode, the signal was sent out unencrypted, if the input port was settings, logs and user EDID's after upgrading to 1.1.0. The LDU software contains a plug-in to help you disconnected and connected again. This issue only happened, if the input signal was also unencrypted. keep the actual settings after firmware upgrade. v1.3.1b1 ▪ New bootloader is used, which allows the connected TPS-RX95's to be upgraded remotely. Release date: 2019-05-21 ▪ Audio and video port names are changed: 'I' is used for inputs and 'O' is used for outputs, instead of 'P'. New feature: ▪ EDID node properties changed: PreferredResolution, MonitorName and AudioInfo properties are added ▪ The device is able to identify IR commands on either the local or link IR input port. This feature can be ▪ Added support for FP-UMX-TPS-TX120-GES, FP-UMX-TPS-TX130-GES product variants. connected to Event Manager, which means, that the device can be programmed to do various actions, if a specific IR command is detected. ▪ 3840x2160p60 YUV4:2:0 factory EDID added. ▪ IR command injection is now supported: data received on a specific TCP port is transmitted as IR signal, and the received IR frames are also sent to this TCP connection.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 183

▪ Crosspoint properties and methods changed. Warning: If you are using an external controller for this device via LW3 protocol, the recent changes in property and node names may result in difficulties to control the TPS device with the latest firmware. ▪ Event Manager configuration became more user friendly: actions can be triggered manually for testing and the user interface shows if any of the conditions are met. ▪ New EDID driver is used, the content of some factory EDID's are changed according to EDID 1.3 and 1.4 standard. ▪ TCP and UDP messages can be sent by the device to control projectors and any other devices. This feature can also be used with Event Manager. ▪ Event Manager upgraded: time delay can be configured between condition and action, a condition can trigger multiple actions at the same time, inverse condition can be used. Bugfix: ▪ Compatibility issues with Gefen HDMI 1.3 HdBaseT extender fixed. ▪ In case of sending DVI signal on the output, the audio output port does not indicate signal present. ▪ In case of sending 1920x1200 no sync screen, the device did not notice the connection state changes on the inputs. Fixed. ▪ If no sync screen is active, the output resolution is now reported correctly by the output port. ▪ Reporting the resolution of signals in YUV 4:2:0 colorspace fixed. ▪ Poe enable state is now reloaded after reboot. ▪ If the output was set to HDCP Always mode, the signal was sent out unencrypted, if the input port was disconnected and connected again. This issue only happened, if the input signal was also unencrypted.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 184

11.11. Hashtag Keyword List Hashtag Keyword  Description This user's manual contains keywords with hashtag (#) to help you to find the relevant information as quick #framedetector Frame detector in LDC/built-in web as possible. The format of the keywords is the following: #hdcp HDCP-encryption related setting # #http Http post and put messaging, salvo commands The usage of the keywords: use the Search function (Ctrl+F / Cmd+F) of your PDF reader application, type the #ipaddress IP address related settings # (hashtag) character and the wished keyword. The #new special keyword indicates a new feature/function or model that has just appeared in the latest firmware or software version. #identifyme Identify me Example #kvm USB data transmission #label Device label #dhcp #lock Port lock settings This keyword is placed at the DHCP (dynamic IP address) setting in the front panel operation, the Lightware #login Cleartext login feature Device Controller (LDC) and the LW3 programmer's reference section. The following list contains all hashtag keywords placed in the document with a short description belonging to them. The list is in alphabetical order #macfilter MAC filtering (IT security) by the hashtag keywords. #macro Macro-handling #mute Port mute setting Hashtag Keyword  Description #network Network (IP address) related settings Tag Description #nosyncscreen Test pattern (no sync screen) settings #advancedview Advanced view window #portblock IP port blocking (IT security) #analogaudio Analog audio related settings #power Power supply and redundancy related information #audio Audio related settings #reboot Restarting the device #backup Configuration cloning (backup) #reset Restarting the device #balance Balance (for analog audio) setting #restart Restarting the device #builtinweb; #miniweb; #web Built-in web #rs232 RS-232 related settings #button Front panel button operations #rs-232 RS-232 related settings #cablediagnostics Cable diagnostics #serial RS-232 related settings #cec CEC related settings #status Status query #commandinjection Command injection settings #switch Crosspoint switch setting #configurationcloning Configuration cloning (backup) #tcprecognizer TCP message recognizer-related settings #controllock Front panel control lock #terminal Advanced view window #controlprotocol Control protocol (LW2 / LW3) query #testpattern Test pattern (no sync screen) settings #crosspoint Crosspoint switch setting #tpsmode TPS (HDBaseT) mode setting #darkmode Dark mode setting #unlock Port unlock settings #devicelabel Device label #unmute Port unmute setting #dhcp Dynamic IP address (DHCP) setting #usbkvm USB data transmission #edid EDID related settings #variables Variable-management #factorydefault Restore factory default settings #volume Volume (for analog audio) setting #firmwareversion Firmware version query

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1

11. Appendix UMX-TPS-TX100 series – User's Manual 185

11.12. Further Information Document Revision History Limited Warranty Statement Rev. Release date Changes Editor 1. Lightware Visual Engineering LLC (Lightware) warrants to all trade and end user customers that any 1.0 26-09-2014 Initial version Laszlo Zsedenyi

Lightware product purchased will be free from manufacturing defects in both material and workmanship for ... three (3) years from purchase unless stated otherwise below. The warranty period will begin on the latest Added supplement in connection with WP-UMX-TPS- possible date where proof of purchase/delivery can be provided by the customer. In the event that no proof 2.3 22-08-2019 TX130-Plus-US model, added MKS mounting option for Tamas Forgacs can be provided (empty ‘Date of purchase’ field or a copy of invoice), the warranty period will begin from the FP-UMX-TPS-TX100 series models point of delivery from Lightware. Added supplement in connection with UMX-TPS-TX140K 2.4 25-02-2019 Judit Barsony 1.1. 25G and MODEX product series will be subject to a seven (7) year warranty period under the same terms model. as outlined in this document. Document re-structured and updated; Advanced Control 3.0 18-05-2021 Laszlo Zsedenyi 1.2. If during the first three (3) months of purchase, the customer is unhappy with any aspect of a Lightware Pack v3 features added; LDU2 CLI added product, Lightware will accept a return for full credit. Advanced Control Pack v3 features and LDU2 CLI 3.1 15-07-2021 Laszlo Zsedenyi 1.3. Any product that fails in the first six (6) months of the warranty period will automatically be eligible for support added to WP- and FP-UMX-TPS series. replacement and advanced replacement where available. Any replacements provided will be warranted for the remainder of the original unit’s warranty period. 1.4. Product failures from six (6) months to the end of the warranty period will either be repaired or replaced at the discretion of Lightware. If Lightware chooses to replace the product then the replacement will be warranted for the remainder of the original unit’s warranty period. 2. The above-stated warranty and procedures will not apply to any product that has been: 2.1. Modified, repaired or altered by anyone other than a certified Lightware engineer unless expressly agreed beforehand. 2.2. Used in any application other than that for which it was intended. 2.3. Subjected to any mechanical or electrical abuse or accidental damage. 2.4. Any costs incurred for repair/replacement of goods that fall into the above categories (2.1., 2.2., 2.3.) will be borne by the customer at a pre-agreed figure. 3. All products to be returned to Lightware require a return material authorization number (RMA) prior to shipment and this number must be clearly marked on the box. If an RMA number is not obtained or is not clearly marked on the box, Lightware will refuse the shipment. 3.1. The customer will be responsible for in-bound and Lightware will be responsible for out-bound shipping Contact Us costs. [email protected] 3.2. Newly repaired or replaced products will be warranted to the end of the originally purchased products warranty period. +36 1 255 3800 [email protected] +36 1 255 3810 Lightware Visual Engineering LLC. Peterdy 15, Budapest H-1071, Hungary www.lightware.com ©2021 Lightware Visual Engineering. All rights reserved. All trademarks mentioned are the property of their respective owners. Specifications subject to change without notice.

Applied firmware packages: (UMX-TPS): v1.5.0b4 | (WP-and FP-UMX-TPS): v1.5.0b6 | LDC software: v2.5.10b1