Specification
Express Control 6 universe (XPC 6)

A. General
i.	The Controller shall be a microprocessor-based system specifically designed for control of lighting in an architectural or entertainment application. A personal computer running emulation software shall not be acceptable. 
ii.	The Controller shall store show data in non-volatile solid-state memory. This memory shall be removable for purposes of backup or disaster-recovery.
iii.	Show data may be downloaded from a remote personal computer over an Ethernet connection.
iv.	The Operating Software of the Controller 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.
v.	The Controller shall commence lighting playback automatically on receiving power without additional external inputs.  
vi.	The Controller shall have an internal real-time clock that continues to operate when external power is removed for a short period. It shall be capable of adjusting for Daylight Savings Time automatically and can be updated over the Internet using the Simple Network Time Protocol (SNTP).
vii.	The Controller shall be able to calculate astronomical times based on longitude and latitude information and use this to adjust lighting output.
viii.	The Controller shall have a capacity of 3072 output control channels of either DMX512 with RDM or eDMX protocols, including Art-Net III, KiNet and sACN.
ix.	The Controller shall support a DALI bus interface for transmitting and receiving the DALI protocol, compliant with EN60929.
x.	The Controller shall support DALI standards EN 62386-101:2009, EN 62386-102:2009, EN 62386-202:2009, EN 62386-209:2011.
xi.	The Controller shall have a capacity of 64 DALI ballasts.
xii.	The Controller shall be able to output DMX512, multiple eDMX protocols and DALI simultaneously, up to the output control channel limit.
xiii.	The Controller shall be able to output eDMX protocols on a different IP network to its management IP network with optional VLAN tagging.
xiv.	There shall be visual indicators on the Controller showing status of the controller and its interfaces.
xv.	The Controller shall operate a web server on its Ethernet interface. This shall allow status information, control and configuration options to be accessed remotely.
xvi.	The Controller shall allow lighting to be programmed in separate spaces, with independent scene playback and override and mastering controls.
xvii.	The Controller shall support multiple scenes with different effects running concurrently over multiple spaces.
xviii.	The Controller shall support playback of video media with individual pixels mapped to lighting fixtures in an array.
xix.	The Controller shall support 2 local inputs capable of digital, analog or contact closure operating modes.
xx.	The Controller shall support 2 local relay outputs capable of switching up to 48V 250mA. 
xxi.	The Controller shall support multiple remote and virtual touch stations with automatically generated interfaces via Ethernet for adjusting lighting output and for user feedback.
xxii.	The Controller shall use a Rotary Dial and Push Button which can be used for lighting protocol line testing without additional programming being required.
xxiii.	The Controller shall support using a Rotary Dial and Push Button during programmed operation to adjust lighting output.
xxiv.	The Controller shall have a recessed switch for resetting the unit without removal of power.
xxv.	The Controller shall have an internal watchdog feature that will restart the unit in the event of program failure.
xxvi.	Controller shall have a configurable power up recovery system to bring light and/or DMX values back on to the desired state after power loss.
xxvii.	The Controller shall support remote management using outbound only connections.
xxviii.	The Controller shall support tags for simple programming of automated scene-based playback.
xxix.	The Controller shall support a calendar-based scheduler.
xxx.	The Controller shall be provided with a 5-year manufacturer warranty.

B. Physical
i.	The unit shall be a 6 unit DIN enclosure (107.5mm x 90.0mm x 40.0mm). 
ii.	Mounting shall comply with EN60715 (35/7.5 rail). 
iii.	The unit shall additionally have a keyhole bracket for alternate wall mounting. 
iv.	The unit shall be entirely solid-state with no moving parts, fans nor hard disc drives
v.	The unit shall operate in a temperature range from 0°C to 50°C (32°F to 122°F)
vi.	The unit shall be CE and UKCA compliant
vii.	The unit shall be UL/cUL listed.

C. Electrical
i.	The Controller shall be designed to support the following wire terminations with plug-in rising clamp terminals:
a.	3-pin 9V to 48V DC Power
b.	3-pin individually galvanically isolated DMX512 Out, RDM-compatible (2)
c.	3-pin DALI bus connection
d.	8-pin digital/analogue inputs/outputs (2 inputs, tri-mode for digital: active high, active low or contact closure; 2 outputs, individually isolated (1KV) relay outputs (48V 250mA))
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
iii.	The DMX512 ports shall be self-healing and withstand continuous AC voltage up to 277V
iv.	The Controller shall be able to receive power over Ethernet as an alternative to direct DC power (IEEE 802.3af PoE powered device).

D. Software
i.	The Controller shall be supported by programming software running on either a PC or Mac platform.  Programming features shall include:
a.	Comprehensive architectural fixture library 
b.	Placement of fixtures on plan
c.	Drag and drop patching of fixtures to output addresses
d.	Import of any media for mapping to fixtures
e.	Scene-based programming with Space dependant playback, using Static, Dynamic and Timeline Scenes
f.	Curated range of editable effect presets
g.	Placement of scenes on plan
h.	Lighting playback determined by editable tag sets or scheduled events
i.	Tagged scenes automatically start dependant on controller state
j.	Logical grouping of fixtures in hierarchical spaces
k.	Automatically generated user interfaces using project data 
l.	Simulation of individual scenes and entire project with tags and real-time generated clock
m.	Live output from software for programming verification purposes
n.	Controller and network management tools 
o.	Tools for remote management of content and lighting programming
p.	RDM discovery of fixture with auto-addressing and identification tools
q.	Graphical drawing tools for creating spaces of fixtures that then become the logical control group or areas for programming both static, dynamic and timelines scenes.