Explanation: Factory default settings reloaded for crosspoint and I/O card configurations
and emulated EDIDs.
Info:
The response may contain additional messages as the router makes the configurations.
These responses can be omitted.
Info:
After resetting the needed parameters, the matrix restarts.
7.5.2. Count HDCP keys
Description: If there is an HDCP source on any input of the matrix, the matrix can ask the
source whether it can handle <num> piece of sink devices.
Command {:HDCPTEST<in>@<num>}
Response (HDCPTEST=SUCCESS)CrLf
Legend:
Explanation: The source on the 2
7.5.3. Clear HDCP key cache
Description: The matrix stores the HDCP keys from the connected devices. These cached
keys can be cleared with this command.
Command {:HDCPRESET}
Response (Done)CrLf
Explanation: HDCP key cache is cleared.
Info:
This function is useful when too many keys were cached and a connected source device
cannot accept so many keys.
7.5.4. Restart matrix router
Description: The matrix router can be restarted without unplugging power.
Command {RST}
Response (Booting...)CrLf
Legend:
Explanation: The matrix reboots and sends a message when it is ready.
Info:
The response can be seen only if the connection to the router is still alive.
Page 86 / 129
Format
<in>
input port where the key counting will be executed
<num>
the number of the HDCP keys
nd
Format
Format
(<name>●Ready!)CrLf
<name>
is the type of the matrix
→ {:hdcptest2@8}
← (HDCPTEST=SUCCESS)CrLf
input can handle 8 HDCP sink devices.
→ {:hdcpreset}
← (Done)CrLf
→ {rst}
←
(Booting...)CrLf
←
(UMX4x4 Ready!)
Section 7. Programmers reference
Example
Example
Example
Need help?
Do you have a question about the UMX4x4-Pro and is the answer not in the manual?