SYSTEM INTEGRATION

BSS / Harman HiQnet

We two practical paths depending on which devices you’re talking to:

1) Soundweb London (BLU-80/BLU-160/BLU-100/BLU-3xx, etc.)

Use London Direct Inject (DI) over TCP. It’s the intended third-party control path and is simpler than raw HiQnet.

• Transport/ports: TCP 1023 for DI control; Telnet on 23 (handy for testing). HiQnet discovery/control also uses 3804 TCP/UDP (but you don’t need it for DI). help.harmanpro.com+1
• Doc: “Soundweb London Third-Party Control / London DI Kit” explains message framing and examples. help.harmanpro.com+1
• Quick sanity tools: Telnet login bssaudio / monkey, help shows commands. help.harmanpro.com

How to wire dMix → Soundweb (recommended)

1. Subscribes to your dMix events (e.g., a.N.mix, a.N.mute).
2. Opens a TCP socket to the Soundweb at port 1023.
3. Translates each event into the DI message for the specific parameter (gain/mute) using the object/parameter IDs you pull from your Audio Architect design. help.harmanpro.com+1

Tip: In Audio Architect, note the object instance and control IDs for the target blocks (gain, mute, router x-points). Those IDs map directly into the DI payloads you’ll send. The Harman DI guide shows exact byte layouts and examples. BSS Networked Audio Systems

2) Generic HiQnet (beyond Soundweb: Crown amps, JBL processors, etc.)

You can speak HiQnet directly on port 3804 (TCP/UDP). This is more involved but officially documented. help.harmanpro.com+2HiQnet Audio Architect+2

• Doc: “HiQnet Third-Party Programmer Documentation” (covers message formats, transports, command types, open/closed-loop control). HiQnet Audio Architect
• Ports/firewall: Ensure 3804 TCP/UDP is open (plus FTP during updates on some devices). help.harmanpro.com+1
• When to use: If you need to control non-Soundweb HiQnet devices (e.g., Crown amps) from dMix without Audio Architect.

Which should you pick?

• Controlling Soundweb London: Use London DI over TCP 1023. It’s straightforward and officially supported for third-party control. help.harmanpro.com+1
• Controlling other HiQnet gear: Implement HiQnet on 3804 using the Programmer’s Guide. Expect more framing/state management. HiQnet Audio Architect+1

Minimal bridge outline (concept)

• Input: dMix WebSocket JSON (e.g., {"cmd":"set","key":"a.0.mix","value":0.73})
• Output: DI frame to Soundweb gain object for Ch1
• Discovery: None needed; you already know the BLU device IP.
• Feedback: Optionally poll or subscribe to meters/params via DI and push back to dMix as {"evt":"update", ...}.

(Exact DI bytes depend on your design’s object/control IDs—grab them from Audio Architect; examples are in the DI Kit PDF.) BSS Networked Audio Systems

Network checklist

• Open 1023/TCP to each Soundweb for DI; 23/TCP optional for Telnet testing. help.harmanpro.com
• If you’ll also use HiQnet discovery/control, open 3804 TCP/UDP (and 21/49152-50152 TCP if you do firmware/FTP). help.harmanpro.com+1

Download:

Download: dmix_hiqnet_bridge_v1.zip

(Contains main.go, config.example.json, and a README.)

What it does

• Subscribes to your dMix WebSocket (evt:"update" messages like {"key":"a.0.mix","value":0.73}).
• For any mapped key, it builds a DI/HiQnet frame from a hex template and fires it over TCP to your BSS device.
• Auto-reconnects both the dMix WS and the BSS TCP session.

Configure it (keep IP generic or set later)

• In config.example.json, set:
• dmix_ws_url: e.g. ws://dmix.local:8080/ws
• bss_host: leave "127.0.0.1" for now; swap to your BLU device later
• bss_port: 1023 (typical for London DI; change if you target raw HiQnet)
• mappings: map dMix keys → frame templates (hex + tokens)

Template tokens supported:

• {{VAL_F32_LE}} → float32 little-endian
• {{VAL_U8}} → 0–255 byte
• {{VAL_I16_BE}}, {{VAL_I16_LE}} → 16-bit signed

Optional linear scaling per mapping:

"scale": {
  "mode": "linear",
  "in_min": 0.0, "in_max": 1.0,
  "out_min": -80.0, "out_max": 10.0
}

Example mapping (you’ll replace headers/IDs per your design)

{
  "key": "a.0.mix",
  "frame_template": "AA 55 12 34 56 {{VAL_F32_LE}} CC",
  "scale": {"mode":"linear","in_min":0.0,"in_max":1.0,"out_min":-80.0,"out_max":10.0}
},
{
  "key": "a.0.mute",
  "frame_template": "AA 55 12 34 57 {{VAL_U8}} CC"
}

The AA 55 ... CC bytes are placeholders—fill them using the London DI or HiQnet docs for your object/parameter.

Build & run

cd dmix_hiqnet_bridge_v1
go build -o bridge main.go
./bridge -config ./config.example.json

If you want, I can also provide:

• A DI checksum helper token (if your frame needs it).
• A BSS→dMix poller path for two-way sync (read back params and push evt:"update" to dMix).
• A pre-filled config if you share your object/parameter IDs for the target gain/mute blocks.

Here’s a breakdown of the most popular installed-sound ecosystems and how dMix can talk to them: