Atlona Help Center

AT-UHD-PRO3 matrices: “Randomly losing one or more HDBaseT outputs, and a power cycle temporarily resolves the challenge.”

AT-UHD-PRO3 matrices: “Randomly losing one or more HDBaseT outputs, and a power cycle temporarily resolves the challenge.”

Independent of any source, display, HDMI cable, control system, network connectivity, etc., compromised HDBaseT connections may cause some AT-UHD-PRO3 matrices to be randomly losing one or more HDBaseT outputs, and a power cycle temporarily resolves the challenge. It may only occur at certain job-sites, but potentially across multiple job-sites, and it may seem unrelated to a specific port #.

Once your matrix is updated to the latest firmware:

  • UI: 16.1.0
  • HDMI: 1.8.0
  • FP: 1.8.5
  • FPGA: 1.0
    • Power Cycle (10 seconds)
  • HDBaseT TX VS100: 13136110
  • HDBaseT TX VS10: 23136110
    • Power Cycle (10 seconds)

Perform HDBaseT quality tests for every HDBaseT run in your installation to confirm whether a compromised HDBaseT connection is the cause of your challenge. An indication that this challenge has manifested itself on a given PRO3 matrix is if one or more known-working HDBaseT outputs’ quality test appears totally negative:

Upon power cycling the matrix, a good HDBaseT connection should change from these failures to something like this:

Running the HDBT test on a compromised/intermittent HDBaseT connection may result in an “HDBT Board Monitor Fail”, and potentially all HDBaseT outputs may fail until the next power cycle.

While our engineering group is currently running the final tests on a promising firmware that addresses this challenge, you can identify such compromised HDBaseT connections in the following way:

  1. Disconnect your HDBT connections at the matrix.
  2. Power cycle the matrix (10 seconds)
  3. Run the HDBT test on each output one-by-one.
  4. As soon as the HDBT Board Monitor Fail occurs, note that the associated HDBaseT run may be compromised and disconnect it from the system.
  5. Power cycle the matrix (10 seconds)
  6. Continue running the HDBT test on the remaining outputs one-by-one, noting the associated runs that may be compromised and disconnecting them from the system.

For all HDBaseT Receivers that were associated with outputs that manifested this challenge:

  1. Remove the HDBaseT Receiver from the display and take it to the matrix.
  2. Using a short factory-made category cable, temporarily test using a known working HDBaseT output. If this HDBaseT receiver experiences any challenges, it may need be compromised and require replacement.
  3. Continue testing each remaining HDBaseT Receiver.
  4. For each compromised HDBaseT receiver, capture the serial numbers and prepare them for replacement.
  5. Using a known working HDBaseT Receiver with the short factory-made category cable, test each HDBaseT output that resulted in an HDBT Board Monitor Failure.
    1. If the matrix experiences another HDBT Board Monitor Failure, then this port may be compromised due to a compromised HDBaseT cable requiring retermination or replacement.
    2. If the matrix does not experience another HDBT Board Monitor Failure, then only the HDBaseT cable is compromised and requires retermination or replacement.
  6. If the matrix experiences HDBT Board Monitor Failures, document the ports at which these failures occur and process a replacement.
  7. If the matrix does not experience other HDBT Board Monitor Failures, then advise the customer to reterminate or replace the compromised HDBaseT cables.

Once our engineering group has a finalized firmware which address these challenges, we will forward this firmware to you so that identifying compromised HDBaseT cables no longer presents this challenge.

This level of troubleshooting will likely be a time consuming process that will be easier if you have 2 or more techs on site.

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Contact Us