User guide

External control user guide
March 27, 2015 Version 1.7.2.0 17
RATC does not echo data input from the client, so we advise that local echo is enabled on the
telnet client program, so that you can see what you are typing while you type it.
Notes:
 Although you can use a telnet style application to control MediaMatrix products with
RATC, we recommend using custom software for real world applications. Telnet is handy
for testing your RATC connection.
 The BEL character that precedes each error response from RATC may cause a bell sound
on your telnet client computer.
 RATC supports only the minimum telnet protocol, and thus will refuse all telnet option
requests from a telnet client program.
Allowing RATC to be used on a MediaMatrix node
1. Right-click the NioNode, nControl node or nTouch 180 node, and then click Device
Properties.
2. If you are using a serial connection, click RATC1 or RATC2 in the RS-232 Protocol
(COM port) list.
If you are using a TCP/IP connection, click RATC1 or RATC2 in the Network Control
Protocol list.
3. Deploy the project, and then specify settings on the Serial RATC or Net Ctl tab to match
your control system. For example:
Commands and Responses
Each RATC1 command is an ASCII text string terminated with an ASCII CR. Each command
results in a response from RATC1. Except during login, RATC1 will send no unsolicited data
to a client. Each response from RATC1 is an ASCII text string terminated with both an ASCII
CR and NL character. Each response that indicates an error in the input command line is
preceded by an ASCII BEL character.