This document describes the Roku Control Protocol (RCP). RCP is a control protocol implemented by the Roku SoundBridge line of digital audio players with software version 2.3 or later, and the Roku Wi-Fi Media Module (WMM), a drop- in hardware solution for implementing digital audio functionality targeted for OEMs.
RCP-capable device and the client controller. Any communication medium that can transmit full-duplex byte stream data could be utilized. In practice, Roku devices expose RCP via the following types of connections: 1. Serial (RS232 or I2S) – The Wi-Fi Media Module (WMM) exposes RS232...
When this document refers to the RCP host, it refers to the device that exposes the RCP interface and processes RCP commands. The RCP host can be any Roku SoundBridge device running software version 2.3 or later, or it can be a Roku Wi-Fi Media Module (WMM).
These capabilities are constant and don’t change. (Although note that Roku may for example add a searching capability to the Internet Radio server in a future software release, so even this is not a hard and fast rule.) But the capabilities of servers from the local network are hard to...
Planned Server Description RCP Support To alleviate these problems, Roku plans on adding new commands to provide the name and content selection capabilities of the current active server. This will most likely be with the addition of a single command like GetActiveServerInfo.
But for WMM users these setup commands will be necessary. Planned Host Configuration RCP Support Roku will add RCP commands to allow the setting of the wi-fi region, the user- interface language, the wi-fi SSID and password, and manual IP configuration.
RCP support for socket commands only supports simple TCP sockets at present. See the section “Socket Commands for Generalized Network Communication”. Roku plans on adding full socket support including datagram (UDP) sockets and listening stream (TCP) sockets. RCP is planned to offer support for drawing on the display using drawing primitive commands.