TEST Utah RCP-3A protocol for router control is supported in Helm, RouteMaster and RouteMaster VR.
RouteMaster uses the protocol for both outgoing and incoming connections, allowing third-party systems using RCP-3A to control RouteMaster. Helm uses it for outgoing connections to control routers.
Use over TCP/IP
RCP-3A over IP frequently uses TCP port 50001, but is not fixed.
Supported and Required Commands
This table details the commands used for outgoing connections, and the commands supported for incoming connections.
| Command | Outgoing | Incoming | Notes |
| PING | Yes | Yes | |
| VERBOSITY | Yes | Yes | RouteMaster always sends unsolicited tallies |
| TAKE | No | Yes | Helm and RouteMaster always send TAKE WITH NODE ID |
| GET MATRIX | Yes | Yes | |
| SET LOCK | Yes | Yes | ThePanelID property below determines which ‘user’ is protecting a destination |
| GET LOCK | Yes | Yes | |
| CLEAR LOCK | Yes | Yes | |
| TAKE WITH NODE ID | Yes | Yes | |
| DEVICE TABLE REQUEST | Yes | Yes | Only 8-character names are supported by RCP-3A protocol |
Special Properties
For outgoing connections, the following properties can be set directly in Helm Designer, or in the RouteMaster configuration file.
PanelID |
1-253 | AKA Node ID. Used for protecting destinations. Only panels with the same PanelID as the protecting panel can TAKE a source to a protected destination. |