IMPORTANT: READ PROGRAMMING INFORMATION SECTION BELOW IN REGARD TO UPGRADING OLDER FIRMWARE VERSIONs

DXLink HDMI Receiver Module Firmware v1.9.28

Last Updated: Sep 28

 

Prerequisites

  • DXLink RX v1.9.10 (or later) must be loaded on the DXLink Receiver to upgrade
  • DXLink TX v1.6.7 (or later) must be loaded on the DXLink Transmitters to get the most benefit from this RX version
  • Enova DGX enclosures should ideally have the following:
    • DGX 8/16/32 (NI Master) v4.2.395 & DGX kit 2.0.0.11
    • DGX 8/16/32/32 (NX Master) v1.2.312 & DGX kit 2.0.0.11
  • Enova DVX 315X and 215X should ideally have the following:
    • Master v4.8.316
    • Switcher Firmware v1.6.31
  • NetLinx Studio V3.4 (4.0 if using NX master)

Features added in this release:

  • Added additional HDCP renegotiations during hot plug event
  • Added an "Offline Recovery Mechanism." In a telnet session, type "WD ON" to enable or "WD OFF" to disable this feature. A reboot is required after enabling or disabling the state for it to take effect. This also monitors conditions when:
    • A DXLink device processor becomes unstable
    • The DXLink device’s exceeds it's minimum memory threshold

Fixes in this release

  • Fixed issue where DVX switches from HDCP to non-HDCP inputs cause the sink to randomly display a black screen instead of the no input logo
  • Fixed a memory leak in ICSP that could negatively impact device's network stability

Notable Points

  • If a send command "FACTORYAV" or telent command "RESET FACTORY" is sent, a reboot of the RX will be required.
  • PLEASE READ the documentation in regard to the DIP switches located on the bottom of the Tx/Rx modules before attempting to connect to the network
  • The RX module uses a solid ORANGE screen to indicate an HDCP authentication failure with the connected device
  • If using a hostname in the USB_HID_ROUTE command, the hostname length is limited to 50 characters

Programming Information

!!****Important – Two downloads of this kit file may be required if upgrading from a version earlier than 1.5.12. A reboot of the Rx is needed in between kits. Please follow the following steps to complete this upgrade on the DXLink RX device****

  1. Transfer v1.9.28 kit file to the RX. If upgrading from a version earlier than 1.5.12, the upgrade will be aborted due to memory error. If so, complete steps 2 & 3.
  2. Reboot the RX device so v1.9.28 application can run.
  3. Transfer v1.9.28 kit file again so it can complete the firmware transfer of the other components.
  • PLEASE reference Appendix A (Upgrading the Firmware) in the DXLink Instruction Manual for more information.

Hot Fix for the DXLink HDMI Receiver Module Firmware (v.1.9.53 Available from AMX Technical Support)

Prerequisites:

  • DXLink RX v1.9.10 (or later) should be loaded on the DXLink Receiver prior to upgrade
  • DXLink TX v1.6.7 (or later) should be loaded on the DXLink Transmitters to get the most benefit from this RX version
  • Enova DGX enclosures should at least have the following:
    • DGX 8/16/32 (NI Master) v4.2.395 & DGX kit 2.0.0.12
    • DGX 8/16/32/32 (NX Master) v1.2.312 & DGX kit 2.0.0.12
  • Enova DVX 315X and 215X should at least have the following:
    • Master v4.8.316
    • Switcher Firmware v1.6.31
  • NetLinx Studio V3.4 (4.0 if using NX master)

Features added in this release:
No new features

  • Previously released in v1.9.52
    • Added a watchdog for point to point setups. In a telnet session, type "wdp2p on x.x.x.x" to enable. The x.x.x.x is the ip address of the opposite device. To disable, in a telnet session type "wdp2p off". A reboot is required after enabling or disabling the state for it to take effect. Leave the RX and MFTX in static ip mode. Once the devices ping each other the watchdog will be armed. If they fail to ping each other for 1 minute the watchdog will fire.
  • Previously released in v1.9.49
    • Added an offline recovery mechanism if a master connection is expected. In a telnet session, type "wdurlsocket on" to enable or "wdurlsocket off" to disable this feature. WARNING! - Do not use this feature if the DX-RX is not configured to connect to a Master.
  • Previously released in v1.9.38
    • Added manual resolution 1920x1080p@50Hz to supported res/ref list (VIDOUT_RES_REF-1920x1080p,50)
    • Added manual resolution 1280x800@120Hz to supported res/ref list (VIDOUT_RES_REF-1280x800,120)

Fixes in this release:
Fixed a video issue where no video would be sent to certain sink devices (i.e. Polycom HDX8000)

Previously released in v1.9.49

ONLINE

  • Fixed issue where an DX-RX could generate multiple online/offline events during bootup of the system. This seemed to occur more frequently when the DX-RX's are configured with static IP address.
  • Improved the AMX master connection to reduce the number of offline events.
  • Fixed an issue with the TCP 3-way handshake process. This issue also caused offline events.

VIDEO

  • Fixed black screen issue seen with some Dell laptops as the source in point to point setups after unplugging the HDMI cable.
  • == Previously released in v1.9.38 ==
  • Hardened upstream video detection and monitoring
  • Improved HDCP authentication to prevent Orange Screen on certain HDCP compliant monitors
  • Corrected VIC (Video Info Code) reporting when manual CEA resolutions are used
  • Fixed video flicker issue due to audio changes from certain upstream devices (i.e. DGX SC Fiber TX)

AUDIO (RX.e and RX.c)

  • Corrected detection issues of various Surround Sound (Dolby/DTS) and HBR (High Bit Rate) Audio formats (Dolby TrueHD/DTS-HD Master Audio)
  • NOTE: HBR audio REQUIRES Hi-Def VIDEO with a pixel clock of 127MHz or higher, in order to effectively pass HBR content (i.e. 1280x720p,60 / 1920x1080p,60 / etc.)

Notable Points:

  • If a send command "FACTORYAV" or telnet "RESET FACTORY" is sent, a reboot of the RX will be required.
  • PLEASE READ the documentation in regard to the DIP switches located on the bottom of the Tx/Rx modules before attempting to connect to the network
  • The RX uses a solid ORANGE screen to indicate an HDCP authentication failure with the connected device
  • If using a hostname in the USB_HID_ROUTE command, the hostname length is limited to 50 characters

Programming Information

UPGRADING

Important–Due to a HWID change, this kit will FAIL on the first attempt of the kit transfer IF upgrading from firmware earlier than v1.9.32

  1. Transfer kit v1.9.53 to the RX. If upgrading from a version earlier than 1.9.32, it will abort: "Transfer Aborted Unsupported file type." If this happens, then proceed to step 2
  2. Reboot the RX (via telnet or power cycle) then check the firmware versions in the Online Tree:
    • g. 07001 - DXLINK-HDMI-RX.e (v1.9.53)
    • [OID=1] - MQX (v3.62)
    • [OID=2] - DXLINK Boot (v1.9.53)
    • [OID=3] - DXLINK App (v1.9.53)
    • [OID=5] - DXLINK Link (3.0.x.x)
    • [OID=6] - DXLINK FPGA (1.0.0.6)
  3. If the FPGA is still not up to date, then transfer kit v1.9.53 again to completele the transfer of the final component. If the FW is up to date then no other kit transfers are required.

DOWNGRADING

  • Also due to the HWID change, RX's with a factory firmware image of v1.9.32 or later will not be able to downgrade to versions earlier than v1.9.32. The loaded fw images can be seen in a telnet session to the RX by typing: fwimages
  • Example of RX that can be downgraded below 1.9.32: >fwimages
  • Available Firmware Images
  • Slot Boot App
    • 0 v1.9.17 v1.9.17 //0 is the factory image
    • 1 v1.9.38 v1.9.38 //upgraded to .38
    • *2 v1.9.28 v1.9.28 //then downgraded to .28
    • * - slot to use at next boot
  • Booted from slot 2 - v1.9.28 v1.9.28

Previous Versions


Related Products

  • DX-RX

    DX-RX

    DXLink™ HDMI Receiver Module

Previous Versions