Specification
RIO A

A. General
i.	The RIO A (“Remote Device”) shall be a microprocessor-based system specifically designed as an input/output interface for integration with lighting and audio visual controllers in an architectural or entertainment application. A personal computer running emulation software shall not be acceptable.
ii.	The Remote Device shall be configured by a controller over an Ethernet connection.
iii.	The Operating Software of the Remote Device shall be stored in a dedicated non-removable non-volatile solid-state memory. It shall be possible to update the Operating Software by download from a remote personal computer over an Ethernet connection.
iv.	The Remote Device shall automatically connect to a controller over an Ethernet connection on receiving power without additional external inputs.
v.	There shall be visual indicators on the Remote Device showing status of the Remote Device and its interfaces.
vi.	The Remote Device shall support a stereo balanced line level audio input.
vii.	The Remote Device shall support a MIDI input and a MIDI output interface.
viii.	The Remote Device shall perform up to 30 band spectrum analysis on each audio input channel and for combined channels. Data shall be transmitted over Ethernet to controllers for use as triggers.
ix.	The Remote Device shall perform peak analysis for each audio frequency band and transmit the data over Ethernet to controllers for use as triggers.
x.	The Remote Device shall allow the audio input gain to be adjusted by controllers over Ethernet.
xi.	The Remote Device shall support linear timecode via either audio channel and transmit the data over Ethernet to controllers. Formats supported shall include 24fps (film), 25fps (EBU), 29.97fps (NTSC) and 30fps (SMPTE).
xii.	The Remote Device shall support a software flywheel, error correction routines and jump support for linear timecode.
xiii.	The Remote Device shall support MIDI timecode and transmit the data over Ethernet to controllers.
xiv.	The Remote Device shall support MIDI input and transmit the data over Ethernet to controllers for use in triggers.
xv.	The Remote Device shall support MIDI output and receive the data to be transmitted over Ethernet from controllers.
xvi.	The Remote Device shall have an address wheel to aid simple addressing up to 15 remote devices, with a setting to allow additional addressing based on the serial number of the Remote Device.
xvii.	The Remote Device shall have a recessed switch for resetting the unit without removal of power.
xviii.	The Remote Device shall have an internal watchdog feature that will restart the unit in the event of program failure.
xix.	The Remote Device shall be provided with a 5 year manufacturer warranty.

B. Physical
i.	Enclosure and mounting shall comply with DIN43880 and EN60715(35/7.5) respectively.
ii.	The unit shall be an 4 unit DIN enclosure (71.5mm x 90.0mm x 58.0mm).
iii.	The unit shall be entirely solid-state with no moving parts, fans nor hard disc drives.
iv.	The unit shall operate in a temperature range from 0°C to 50°C (32°F to 122°F).
v.	The unit shall be CE compliant.
vi.	The unit shall be ETL/cETL listed.

C. Electrical
i.	The Remote Device shall be designed to support the following wire terminations (Camden Electronics CTB9208 5.08mm plug-in rising clamp terminals):
a.	6-pin stereo balanced line level analogue audio input
and the plug-in rising clamp terminals shall be provided.
ii.	In addition there shall be the following standard connectors:
a.	RJ45 socket for 10/100Base-TX Ethernet
b.	5-pin DIN socket for MIDI In
c.	5-pin DIN socket for MIDI Out
iii.	The Remote Device shall be able to receive power over Ethernet (IEEE 802.3af PoE powered device).

D. Software
i.	The Remote Device and associated controllers shall be supported by programming software running on either a PC or Mac platform.  Programming features shall include:
a.	Comprehensive architectural and automated fixture library 
b.	Drag and drop placement of fixtures on plan
c.	Drag and drop patching of fixtures to output addresses
d.	Import of any media for mapping to fixture arrays
e.	Timeline-based programming and playback
f.	Extensive range of editable effect presets
g.	Drag and drop placement of effect presets and media on timeline
h.	Variety of triggering options for firing system-wide events
i.	Each trigger event may be configured to initiate one or more lighting or show control action
j.	Each trigger event may be configured to test one or more conditions before executing its actions
k.	Simulation of individual timelines, and entire project with triggers
l.	Live output from software for programming verification purposes
m.	Controller, Remote Device and network management tools 
n.	Export TSV reports for all aspects of programming
o.	Tools for remote management of content and show programming