Lightware MX-FR17, Руководство пользователя

Страница: 141 / 190

7. Programmer’s Reference MX-FR Series Modular Matrix Frames – User's Manual 141
Applied CPU2 firmware: v3.5.7b8 | LDC software: v2.5.17b2
7.12. RS-232 over Fiber Commands
ATTENTION! The control interfaces on the router (USB, IP, and RS232) have 57600 bit/sec maximum
bandwidth, so heavy traffic should be avoided. Try to reduce the responses and status messages coming
from the end point to avoid the overload of the data transmission (e.g. see the
SERIAL
command in the
Setting the Serial Parameters section).
ATTENTION! If the endpoint (the controlled device) sends more than 1 kbyte/sec without at least 600ms
break between the data packets, then the sent data could be lost.
Important Notices
▪ The data rate can be 9600, 14400, 19200, 38400, 57600 baud. There is one stop bit and no parity bit.
▪ Maximum 64 bytes of data can be sent and 54 bytes of data can be received at once.
▪ There are two methods for sending data: ASCII and binary modes.
▪ HDMI-OPT-TX100R, HDMI-OPT-TX200R, MX-HDMI-OPT-IB: the baud rate can be set on the HDMI-OPT
transmitter unit via a rotary switch.
▪ MX-HDMI-OPT-OB, HDMI-OPT-RX100R, HDMI-OPT-RX200R: the baud rate can be set on the router via
protocol command or from the LCD menu. The baud rate can be set independently on each port.
7.12.1. Sending Data in Text Format
Sends the data from the matrix’s input or output port in text format, which is after the equation mark.
Command and Response
ȩ
{:S# <in2/out2> @ <S> I/O= <ascii_text> }
Ȩ
No response by the matrix
Example
ȩ
{:s#17@so=Blind text\r\n}
Ȩ
No response by the matrix
‘Blind text’ with CrLf is sent out on the 17th output. The matrix does not respond. If the remote controlled
device responds, the matrix is able to receive and show it.
Parameters
Identifier Parameter Description Parameter Values
< in2 >/< out2 > Input or output port number Output number in 1- or 2-digit ASCII format (01, 3, 04 etc.)
< I/O > Input or output port type I = input, O = output
< ascii_text > ASCII text Text to be sent
Important Notices about the Escape Characters
The text may contain any characters except "{" and "}", which are used for command framing. The following
escape sequences are supported: \r (carriage return); \n (new line); \t (bs); \x [hex code].
Example
Send the {power on}\r\n string to the second output:
ȩ
{:S#2@SO=\x7Bpower on\x7D\r\n}
It is possible to send the real characters (new line-carriage return) instead of \r\n , but curly brackets must
be escaped. Other characters can also be escaped if it is preferred:
ȩ
{:S#1@SO=\x7Bpower\x20on\x7D\r\n}
7.12.2. Sending Data in Binary Format
Sends the data from the matrix’s input or output port in binary format, which is after the equation mark.
Command and Response
ȩ
{:B# <in2/out2> @ <S> I/O= <hex_string> }
Ȩ
No response by the matrix
Example
ȩ
{:b#17@so=0d0aad}
Ȩ
No response by the matrix
"0D0AAD" is sent out on the 17th output. The matrix does not respond. If the remote controlled device
responds, the matrix is able to receive and show it.
Parameters
Identifier Parameter Description Parameter Values
< in2/out2 > Input or output port number Output number in 1- or 2-digit ASCII format (01, 3, 04 etc.)
< I/O > Input or output port type I = input, O = output
< hex_string > HEX string String to be sent
Every 2 characters represent a hexadecimal code. The maximum length of the data is 64 characters, so the
max length of the string is 128 char; any special character can be sent.
Receiving Data from the Far Endpoint
Every port can operate either in ASCII or Binary mode. The mode can be set up with the :SERIAL command,
see the next section. Depending on the selected mode, different messages are sent by the router when it
receives data from the far endpoint. These messages arrive from the router asynchronously without any
query command. (The router sends out the message immediately when it receives the data). Therefore it
may happen that this message is inserted between another command from the controller and the response
from the router. The controller must be able to handle this case. See example below:
▪
Controller:
2@3} //sending a switch command
▪
Router:
S#I3=Powered on) //asynchrony serial message
▪
Router:
O03 I02) //response to the switch command
   