Page 86 / 129
Section
7
.
Programmers
reference
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.
Format
Example
Command {:HDCPTEST<in>@<num>}
→ {:hdcptest2@8}
Response (HDCPTEST=SUCCESS)CrLf
← (HDCPTEST=SUCCESS)CrLf
Legend:
<in>
input port where the key counting will be executed
<num>
the number of the HDCP keys
Explanation:
The source on the 2
nd
input can handle 8 HDCP sink devices.
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.
Format
Example
Command {:HDCPRESET}
→ {:hdcpreset}
Response (Done)CrLf
← (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.
Format
Example
Command {RST}
→ {rst}
Response
(Booting…)CrLf
(<name>
●Ready!)CrLf
←
←
(
Booting…)CrLf
(UMX4x4 Ready!)
Legend:
<name>
is the type of the matrix
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.
