Integration
More relays and GPIO for a Q-SYS system
Add eight relays and eight inputs to a Q-SYS design with the RELO IO8. Trigger it over TCP from a Q-SYS script, or close Q-SYS GPIO inputs with its relays.
When a Q-SYS core runs out of GPIO
Q-SYS cores and peripherals have a limited number of GPIO pins, and the room always wants one more relay: a screen, a lift, an on-air light. The RELO IO8 adds eight relays and eight inputs per unit, on PoE+.
Two ways to connect
Over the network: a Q-SYS control script opens a TCP socket to the RELO IO8 on port 8081 and sends a string, and a flow switches the relay. The RELO IO8 can send TCP strings back to Q-SYS when one of its inputs changes.
Over wires: a RELO IO8 relay closes a contact on a Q-SYS GPIO input, with no scripting at all. In the other direction, use a Q-SYS relay output or another dry contact. RELO IO8 inputs take dry contacts to ground only, so never wire a Q-SYS GPIO output directly into one.
Q-SYS UCI and Cueva Interface Builder
Keep the Q-SYS UCI for what Q-SYS does best: audio, routing and room presets. Cueva Interface Builder, coming soon, covers the relays, contacts and devices Q-SYS does not reach, on its own touch panel for iPad, iPhone and Android. Use both in the same room, or bridge them with TCP strings so one press on the UCI also runs a RELO IO8 flow.
Questions
Common questions.
No plugin is needed. You connect with TCP strings from a Q-SYS script, or with contact closures between a RELO IO8 relay and a Q-SYS GPIO input.
Yes. Wire the button to a RELO IO8 input and send a TCP string to Q-SYS from the flow, or close a contact on a Q-SYS GPIO input with a RELO IO8 relay.
Start with one. Scale when you need to.
Order the RELO IO8 from our store, or talk to us about your project.