Table of Contents
Advertisement
7. Programmer's Reference
7.4.6. Querying the Control Protocol
Description: Matrix routers can be controlled with different control protocols. This command queries the
active protocol for the used control interface.
AAAENAIONG!
Be aware that different control interfaces can be set to use different protocols. D.g. the
Dthernet interface can use the Lightware protocol while the Serial interface uses Protocol#2 at the same
time.
Format
Command {P_?}
Response (CURRDNT●PROTOCOL●=
●#<protocol>)CrLf
Explanation: The matrix communicates with Lightware protocol.
Possible Settings:
<protocol>
The response shows only the active protocol for the interface that was used to send the command! Control
protocol for each interface can be checked by the front panel buttons (see the
in the front panel LCD menu.
7.4.7. Changing the Control Protocol
Description: Matrix routers can be controlled with different control protocols. This command sets the active
protocol only for the currently used control interface. The setting applies only for the interface that was used
to send the command! The USB interface always uses the Lightware protocol, this cannot be changed.
Format
Command {P_<protocol>}
Response (PROTOCOL●#<protocol>● SDLDCTDD!)
CrLf
Explanation: The matrix communicates with Lightware protocol.
Legend:
<protocol>
INFO:
Be aware that different control interfaces can be set to use different protocols. D.g. the Dthernet
interface can use the Lightware protocol while the Serial interface uses Protocol#2 at the same time.
INFO:
The Control protocol can be checked by the front panel buttons or on the front panel LCD menu.
Example
→ {p_?}
← (CURRDNT PROTOCOL = #1)CrLf
Control Protocol
1
Lightware (default)
2
Protocol #2
3
LW simple (not in use)
Control Protocols
Example
→ {p_1}
← (PROTOCOL #1 SDLDCTDD!)CrLf
Control Protocol
1
Lightware (default)
2
Protocol #2
3
LW simple (not in use)
MX-FR Series Modular Matrix Frames – User's Manual
7.4.8. Configure Remote Alerts
Description: The matrix logs different levels of errors. Configure which level of errors has to be sent out as
an alarm message.
Explanation: The matrix will send an immediate message on all control interfaces when a 'matter', 'error' or
'fatal' level error occurs.
Command {DLDVDLSDND#<p>=
<0>;<1>;<2>;<3>;<4>}
Response (DLDVDLSDND#<p>=
<0>;<1>;<2>;<3>;<4>)CrLf
Legend:
See the
Drror Responses
section) or
7.5. Router Status Commands
7.5.1. Querying the Product Type
Description: Identification of the device. Type 'i' or 'I' then the device responds its name.
Command {I}
Response (<PRODUCT_TYPD>)CrLf
Explanation: The connected device is an MX-FR17.
INFO:
Please note that MX-FR65R gives (I:MX-FR80R) response.
Format
→ {elevelsend#0=0;0;1;1;1}
← (DLDVDLSDND#0=0;0;1;1;1)CrLf
section for more information about error levels.
Identifier
Parameter
0 = all
1 = RS-232
<p>
Adjusted control interface
2 = LAN
3 = USB
<0>
'Notice' level events
<1>
'Warning' level events
0 = no immediate message sent
<2>
'Matter' level events
1 = immediate message
<3>
'Drror' level events
<4>
'Fatal' level events
Format
→ {i}
← (I: MX-FR17)CrLf
88
Example
Values
Example
Advertisement
Table of Contents
Troubleshooting
