7. Programmer’s Reference
MX-FR Series Modular Matrix Frames – User's Manual
115
Applied CPU2 firmware: v3.5.7b8 | LDC software: v2.5.17b2
7.8.2.
Changing the EDID on All Inputs
Copy an EDID from memory location
<source>
to all inputs.
Command and Response
ȩ
{EA:
<source>
}
Ȩ
(E_SW_OK)CrLf
…delay…
Ȩ
(E_S_C) CrLf
Parameters
Location
<source>
can be ‘Fxx’ or ‘Uxx’ for static routing and ‘Dxx’ for dynamic routing. See the details in the
previous section.
Example
ȩ
{pwr_off}
Ȩ
(Powered off)CrLf
User EDID #2 is copied to all inputs.
ATTENTION!
This operation can take several seconds depending on the frame size.
7.8.3.
Saving an EDID to the User Memory
Learn EDID from
<source>
memory location to
<destination>
.
Command and Response
ȩ
{
<destination>
:
<source>
}
Ȩ
(E_SW_OK)CrLf
Ȩ
(E_S_C) CrLf
Parameters
Location
<destination>
must be 'Uxx',
<source>
can be ‘Fxx’, ‘Uxx’, Dxx or Exx. See the details in the
Example
ȩ
{u4:d3}
Ȩ
(E_SW_OK)CrLf
Ȩ
(E_S_C) CrLf
EDID from Output 3 is saved to user EDID #4.
7.8.4. Querying the EDID Validity Table
Shows EDID validity table, which contains information about the EDID memory states.
Command and Response
ȩ
{WV
<type>
}
•
<val_table>
)CrLf
Ȩ
(E_SW_OK)CrLf
Parameters
Identifier
Parameter description
Parameter values
<
type
>
Type of the EDID memory
D:
Dynamic EDIDs *
E:
Emulated EDIDs *
F:
Factory preset EDIDs
U:
User saved EDIDs (max 50)
<
val_table
>
The EDID validity for the memory
locations from 1 to max value
0:
invalid EDID
1:
valid EDID
2:
deleted EDID
3:
changed EDID
* the highest value depends on the frame size.
Example
ȩ
{wv*}
Ȩ
(EVU 00000000000000000000000000000000000000000000000000)CrLf
Ȩ
(EVD 10001001000000000)CrLf
Ȩ
(EVE 13111111111111111)CrLf
There is a ‘3’ on the second position of the emulated EDID table. This means that the emulated EDID on Input
2 has been changed since the last EDID query on that port.
INFO:
If a changed EDID is queried by the {WH} command (see the next section), its value returns to ‘1’.
The status of a deleted EDID returns to ‘0’ after query.
