Developers
Control EDC loudspeakers from your own software.
Our loudspeakers are network-controlled, we publish the full protocol specification, and you need no licence or NDA to implement it. This section covers what that control path does, what it does not do, and the terms for building on it.
What we publish
A documented protocol, and permission to use it.
- No licence, fee or NDA to build EDC control into your product
- Twelve months' notice before any breaking change
- UDP on port 12128, broadcast discovery, 4-byte ASCII commands
- Control over inputs, levels, mutes, EQ, processing and presets
- Every transducer reports pass or fail — up to 90 per cabinet
- Amplifier, thermal, supply-rail and DSP health in one request
- Two channels of Dante or AES67, assignable to any of the four beams
The full packet-level specification, ungated: EDC Speakers Network API (PDF) — field tables, CRC source, object definitions, EEPROM map and FIR deployment.
What we do not publish
Being straight about this saves you a wasted afternoon.
- No SDKs or sample code
- No Q-SYS, Crestron, Companion or Node-RED modules
- No REST or OSC interface — our cabinets speak the binary protocol only
- No AES70/OCA implementation
- No device simulator — you will need hardware to test against
- Beam aiming is not in the protocol. Coverage is designed in our Pro app and recalled as a preset
Building one of these? Tell us — it is how you get told before anything changes, and it is how we learn what integrators actually need.
Documentation
01
Protocol reference
The network control protocol our loudspeakers speak — UDP transport, discovery, packet framing, the command set, per-transducer telemetry, and a straight account of what your software can and cannot change.
02
Licence & trademark
You need no licence to build EDC support into your product, and we give twelve months' notice before any breaking change. What that covers and how to describe compatibility.
03
Dante & AES67 channel mapping
The question we are asked most often, answered once — how many network-audio channels a cabinet receives, how they map to the beams, and whether control and Dante share the RJ45.
Firmware
Firmware is updated over UDP with our own Windows utility — not through this protocol, and not by third parties. We have never issued a firmware update in the product's life to date, so the version a cabinet reports is stable in practice.
If something you need is missing, ask us — we would rather hear the requirement than have you guess.
Next step
Building something on EDC?
The specification is published and there is nothing to sign. Tell us what you are building anyway — it is how you get told before anything changes.