QSC Q-SYS Parameter Controllable Device

QSC Q-SYS Parameter Controllable Device

Minimum hi Version: v2.7.6

Overview

hi uses the QSC^® Q-SYS^® External Control Protocol (ECP) over TCP. It reads and writes named controls and uses change groups for efficient updates.

Network Requirements

• Connection Model: hi initiates a persistent TCP connection to the Q-SYS Core.

• Multicast / Unicast: Unicast only.

• VLAN / IGMP: No multicast configuration is required.

• Bandwidth: Control traffic only.

• IP Version: IPv4.

• Firewall: Allow outbound TCP from hi to the Q-SYS Core, Port 1702 by default.

Standards Conformance

Operator Workflow

• UI Surface in hi: Inventory, Parameter Control, and Control Panel

• Parameter Semantics: Q-SYS controls exposed by the configured design appear under the device Node in Inventory.

• Device Administration: Use Q-SYS Designer for DSP design, component configuration, and named-control exposure.

Connection Details

Required Configuration

Device-Side Setup

Follow QSC Q-SYS Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

This integration supports the QSC Q-SYS Core range.

Supported Product Range

The Q-SYS Core range includes these processors:

• Core Nano

• Core 8 Flex

• Core 24f

• Core 110c

• Core 110f

• Core 510c

• Core 510i

• Core 610

• Core 5200

• Core 6000 CXR

• Server Core X10

• Server Core X20r

• Server Core X50r

Potentially Compatible (Not Yet Verified)

• Q-SYS vCore software processors that run a design with ECP Named Controls.

Known Limitations

• Confirm the Core model, installed version, access policy, and required controls during commissioning.

• Available controls depend on the design running on the connected Q-SYS Core.

• Q-SYS closes an ECP connection that has no traffic for 60 seconds.

• Q-SYS allows four change groups on each ECP connection and 512 change groups across the system. hi uses two change groups on its connection.

• The standby Core of a redundant pair ignores control changes. Connect hi to the active Core.

• If a control is absent, confirm that the running design exposes it as an ECP named control.

• A TCP connection alone does not establish authorized control access. Verify a named-control read and a safe write against the commissioned Core.

• hi lists the controls in a Named Controls folder and names each Parameter with its Control ID. Controls that report true/false or muted/unmuted appear as Boolean Parameters. All other controls appear as numeric Parameters with a fixed range of -1000 to 1000, independent of the range set in the design.

• hi requests a 10 ms poll period for the change group of pinned controls and 100 ms for the change group of other visible controls. Q-SYS changes a poll period below 30 ms to 30 ms. hi requests Core status every 50 seconds, which keeps the connection inside the 60-second idle timeout.

• hi combines rapid position changes, such as a fader move, and sends the latest position after a pause of 600 ms, or after 1 second while the changes continue. Value changes are sent at once.

What's Not Supported

• Q-SYS QRC, which uses JSON-RPC on TCP 1710, is not implemented by this integration.

• ECP credential configuration and login to a Core that requires ECP authentication.

• Firmware updates, DSP design, and controls not exposed as ECP named controls.

• Snapshot Load and Snapshot Save.

• Control Trigger, Control Set String, ramped value and position changes, and vector controls.

• Automatic failover between the Cores of a redundant pair. hi connects only to the configured Core address.

Trademarks