JW Diner Q-SYS Programming Portal

0 Quick read: the 3 Cores (decide this first)

Hardware on order: 3x Core 8 Flex (CN8699), 1x QIO-ML4i, 1x QIO-L4o, QIO-IR1x4 (confirm on site whether it is present), TSC-50-G3 touch screens (count the TSC panels installed: plan shows 4, orders show 5), 3x Lab Gruppen E 5:4, 5x RDL DD-BN31 Dante plates, 1+ Netgear M4250-26G4F-PoE+, and 1 iPad Air.

Recommendation (simplest valid setup): ONE design on ONE Core.

JWDC-CORE-1 stays in Core mode and runs the whole design: all 3 zones, all QIOs, all TSCs, the iPad, Dante, fire-alarm mute and the 4 AM reset. Cores 2 and 3 stay out of the design today. Either unplug them from the AV switch, or leave them in Core mode with unique names and no design pushed. They are spares. Phase 2 option: if you run out of analog outputs (12 amp channels vs 4 QIO-L4o outs + the Core's 8 Flex channels), switch Core 2 to Peripheral mode. It then becomes an "I/O-Core 8 Flex" with 8 more Flex channels plus GPIO, controlled by Core 1. (Core 8 Flex – Switching Modes)

Why not 3 separate Cores, one per zone? It would be valid Q-SYS, but it's the wrong fit here:

Each Core runs its own design, and only one design can run on a Core at a time (Getting Started). That means 3 files and 3 sets of UCIs. Each TSC and each QIO can only belong to one Core's design. The Spec's system-wide master on/off, fire-alarm mute and 4:00 AM reset (Spec 2.4.A.3.3 / .11) would have to be built 3 times or cross-linked. We only bought one QIO-ML4i and one QIO-L4o. The Plan (§1.3, §3) already assumes one primary Core.

Why not a redundant pair today? Core 8 Flex does support Core redundancy (set Is Redundant = Yes and name the Backup Core). However, Flex outputs cannot be wired redundantly, both Cores must be online during install, and the Core Redundancy network service has to be enabled on both. (Core Redundancy) That's extra complexity we don't need to get sound working today. Revisit only if EMD or Dana asks for it.

How to tell which mode each unit is in:

In Designer, open Tools > Show Q-SYS Configurator. A unit in Core mode lists as a Core ("Core 8 Flex"). Clicking its link opens Core Manager. A unit in Peripheral mode lists under I/O Devices as "I/O-Core 8 Flex". Clicking it opens Peripheral Manager. To confirm or change the mode: Core Manager > Utilities > Mode (Core / Peripheral) > Switch, which reboots the unit. From Peripheral back to Core: Peripheral Manager > Utilities > Mode = Core > Switch. (Core Manager Utilities) Switching to Peripheral turns off LAN B and clears its settings (same page).

A Before you start (10-minute checklist)

Open questions (JWDC Diner Q-SYS: Questions only Lorenzo can answer on site)

From open-questions.md. Tick each once you have the answer; these ticks don't count toward progress.

Type your answers and send them (section J)

(Ask these first. Each answer changes a step in playbook.md.)

1. What exactly is failing? (pick the step)

Can't see the Cores/devices in Tools > Show Q-SYS Configurator? Are they green, red or blue? F5 sticks on "Discovering Core…"? Firmware update prompt failing or stuck on "Initializing"? Devices show Missing in the design? Design runs but no audio at the amps or speakers? Can't build the signal flow (which components to use)? UCIs won't show on the TSCs ("No UCI assigned"/license) or on the iPad? Exact error text or a screenshot: ____________

2. Versions

Q-SYS Designer version on the laptop: ______ Core firmware (front panel Next, or Core Manager): ______ (9.x or 10.x? This decides the UCI license question.) Laptop is Windows? Y/N. Anyone set a Core Manager login (Access Control)? Who has it?

3. The 3 Core 8 Flex units

Hostname, IP and mode (Core vs Peripheral "I/O-Core 8 Flex" in Configurator) for each: 1 ____ 2 ____ 3 ____ Which one(s) are cabled to the AV switch (LAN A)? Is anything plugged into LAN B? What is landed on each Core's Flex 1–8 and GPIO pins? Did anyone wire amp feeds to Cores 2 or 3 expecting one Core per zone? Is any design already running on any Core? (Back it up with Load from Core & Connect before F5.)

4. Speakers and amps

Which zones do the 18–20 installed Phase 1 speakers serve? (Diner & Bar / Private Dining / Restaurant & Lounge.) TBD in Plan §1.2. Don't assume 16+4. Per amp channel: which speakers and which tap (W @ 70 V)? Is the amp set to 70 V mode? Attenuator positions? Which QIO-L4o or Core Flex output is cabled to which E 5:4 input (AMP-1/2/3, ch 1–4)? How many speaker home-runs are actually landed (Plan says 11)?

5. Inputs and sources

BGM source make and model; analog to Core Flex 1–2, or network/Dante? (TBD Plan §11 #8) What's on QIO-ML4i ch 1–4 (mic or line)? Which need phantom power? Which DD-BN31 plates are installed and where? (TBD Plan §5.5/§11 #7.) Is Dante Controller on the laptop?

6. Touch screens, iPad, IR

How many TSC-50-G3 are on site: 4 or 5? Hostname and wall location for each (TBD Plan §9.3). Portrait or landscape mount? iPad: which Wi-Fi network, and can it reach the Core IP? (Hotel IT, TBD Plan §4.) Is the QIO-IR1x4 physically on site? (Order status unconfirmed.) TV make and model?

7. Network

How many Netgear M4250 switches are on site (Plan says 1 of 2 seen)? Was the "Audio – Q-SYS" profile applied? Any uplink to hotel IT? IP plan from hotel IT, or an isolated subnet we pick? (All IPs TBD, Plan §4.)

8. Fire alarm

Where does the FA contact land (Core GPIO pin #, and/or E 5:4 GPI)? Is it dry contact or TTL? Normally open or normally closed? Who from the FA vendor can test it with us?

9. Still TBD in our Plan (not Lorenzo's problem today)

Owner logo artwork Final IPs/VLAN from hotel IT 5th DD-BN31 Dante channel count/license Phase 2 speaker order (~33) Core strategy confirmation from Dana/EMD (playbook recommends one primary Core) Cost-sheet "QIO-L4i" vs ordered QIO-ML4i

Windows laptop with Q-SYS Designer installed. It's a free download (Q-SYS Designer). Disable or pause antivirus if Designer behaves oddly, since the docs note antivirus "can impact some Q-SYS Designer Software operations" (Installing & Updating). Designer version = Core firmware version. They are the same number: "The Q-SYS firmware version and QDS version are the same" (Updating Firmware KB). To check the Core's version: Front panel: press Next until the firmware version shows, or Configurator > select the Core > its Core Manager page shows the version (CHECK ON SITE: write it down: ________). If Designer is newer, Save to Core & Run will offer to update the Core. That's fine on a new system (see B5). You can install more than one Designer version: rename C:\Program Files\QSC\Q-SYS Designer before installing the second (Installing). Free Q-SYS account for training videos and support cases (Create account). Plug the laptop into the Netgear AV switch on the same VLAN/subnet as the Cores' LAN A. Start the laptop NIC on DHCP ("Obtain an IP address automatically"). With no DHCP server, Q-SYS gear falls back to 169.254.x.x link-local and the laptop will too (Initial Discovery). Turn off laptop Wi-Fi so discovery goes out the right NIC. Do not plug the laptop directly into a QIO or TSC. "Direct connection with Q-SYS peripherals is not supported." A direct laptop-to-Core LAN B cable only reaches the Core, not the peripherals (Initial Discovery). Netgear M4250 switch settings: Easiest: in the M4250 AV UI, go to Configure > Network Profiles and apply the preconfigured "Audio – Q-SYS" profile to the AV ports (Netgear KB 000062313, KB 000062308). Since Dante (DD-BN31) is also on this network, check whether the M4250 offers a combined Q-SYS + Dante profile. CHECK ON SITE. If configuring by hand, this is what Q-SYS requires (Network Switches & Infrastructure): Gigabit, non-blocking. QoS by DSCP, Strict Priority: PTPv2 EF (46) in the highest queue, Q-LAN audio AF41 (34) in the second highest. Auto-QoS is not correct. IGMPv2 snooping plus exactly one IGMPv2 querier. Energy Efficient Ethernet (EEE) OFF. STP off on access ports, or use portfast/RSTP. No VLAN tagging on device ports (access ports only). Jumbo frames off. No traffic shaping/policing. Flow control helps Gen 1/Gen 2 TSCs only. No Q-LAN over Wi-Fi or through a firewall. The iPad's control traffic over Wi-Fi is fine; real-time audio is not. Know the UCI license rule for your firmware: Q-SYS 10.0 and later: Scripting and UCI are free on any Core (FAQ). 9.x: UCI deployment needs a feature license (Level 1 "UCI Deployment" video). If the Core is on 9.x and the UCIs won't deploy, upgrading to 10.x is the easy fix. Grab the Plan (I/O map §5, amp map §6, signal flow §7, UCIs §9) and a label maker.

B Find the hardware (Configurator + Core Manager)

Open Designer, then Tools > Show Q-SYS Configurator. Every Q-SYS device on the network appears on the left (Configurator). Green square: OK. Blue: initializing. Red: discovered, but your PC can't talk to it. Put the laptop on that device's subnet. Use Group By Category/Model and the Search box. Make a device list with name, model, IP, mode and firmware for each unit: Core x3 QIO-ML4i, QIO-L4o, QIO-IR1x4 (if present) Each TSC-50-G3 (count the TSC panels installed: plan shows 4, orders show 5) Use the ID buttons (on the device, or in Core Manager/Peripheral Manager) to match each name to a physical unit. A flashing icon means ID was pressed. On a TSC, swipe up from the bottom to open its Inventory Status screen, which shows Name, LAN A IP, Design and UCI (TSC Inventory Status). Name and address the Core: in Configurator, click the Core's Configuration Page link to open Core Manager (accept the browser certificate warning; it's your own device). Go to Network > Basic (Network Settings tab) > Edit. Set Hostname to JWDC-CORE-1 (Plan §3). Names can use letters, digits and hyphens only, can't start or end with a hyphen, and must be unique. LAN A: Auto (DHCP) or Static per hotel IT. Use the IP assigned by the building/Whiting-Turner IT; write it here: ____. (Plan §4) LAN B: set to Off if there's no redundant network. LAN A and LAN B must never be on the same subnet. Then Save. If you went static, move the laptop onto that subnet. (Initial Discovery, Core Manager Network > Basic) Name and address the peripherals (QIOs, TSCs): in Configurator, click the device to open Peripheral Manager > Network Settings, then set the hostname and Static/Auto (Peripheral Manager Network Settings). Suggested names: JWDC-QIO-ML4i-1, JWDC-QIO-L4o-1, JWDC-QIO-IR-1, JWDC-TSC-1…-n. These are suggestions: use what's already on the units if they've been named. If you lock yourself out of a QIO: a short reset (hold Reset about 10 s until the Power LED flashes slowly, release before 20 s) restores DHCP and keeps the hostname (QIO-L4o). Firmware: you don't update peripherals one by one. With matching names in your design, File > Save to Core & Run (F5). If versions differ, Designer prompts you; click Update. The Core updates and reboots (about 2–5 min), then pushes the firmware to every peripheral in the design, and each one reboots. Watch progress in each Status component. The system can't be used while this runs. (Installing & Updating, Updating Firmware KB) On firmware 9.10 or later you can't downgrade straight to below 9.1.0 (same KB). Spare Cores 2 and 3: give each a unique hostname (e.g. JWDC-CORE-2, -3), then either unplug them from the AV switch or leave them idle. An unconfigured Core with an "Idle" design does not route audio.

C Build the design (this job)

Build the full 3-zone design now and enable Phase 1 speakers only. Pre-build the Phase 2 chains (including AMP-3) and keep the Phase 2 UCI controls hidden or disabled (Plan §1.2 / §8).
Zones (Proposal §2.1): Diner & Bar (16 spk design), Private Dining (4), Restaurant & Lounge (33).
Which zones the 18–20 installed Phase 1 speakers serve is TBD (Plan §1.2). Ask yourself first, and do not assume 16+4=20.

C1. Inventory

File > New Design (Ctrl+N), then File > Save As JWDC_Diner_v01_2026-11-11.qsys. Left pane Inventory: select the default Core (named "Core-1"). In Core Properties on the right: Name = JWDC-CORE-1, the exact Core Manager hostname. Model = Core 8 Flex. Set Location. Designer only connects to a Core of the same model and name (Level Zero: Connecting to the Core). Leave Is Redundant = No (see section 0). Click + at the top of Inventory and add each device once per unit. A single click adds one; a double-click adds two (Level Zero: Inventory Panel). QIO-ML4i x1. Its components are the 4x Mic/Line In (QIO Series) and Status (QIO-ML4i). QIO-L4o x1. Components are the 4x Line Out (QIO Series) and Status (QIO-L4o). QIO-IR1x4 x1, only if it's physically on site (QIO-IR1x4). TSC-50-G3 xN, where N = the count on site. Components are Status/Control (Touch Screen) and Sensors (TSC-50-G3). Make sure you pick the G3 model, because "The TSC components are not interchangeable" (Status/Control (Touch Screen)). Status/Control (UCI Viewer) x1 for the iPad, named e.g. JWDC-iPad-1 (UCI Viewer component). Software Dante RX (Inventory > Streaming I/O) for the DD-BN31 plates. Base Core 8 Flex Dante is 8x8 (expandable to 32x32 with a license) (Core 8 Flex, Software Dante TX). For every device, set Name to the exact hostname from step B2/B4, and a Location (Diner & Bar / Private Dining / Restaurant & Lounge / Rack). Drag each device's Status component onto a schematic page called "Status". This is always recommended (Inventory Panel). Core 8 Flex Flex channels: each of the 8 is either an input or an output. Drag Flex In and Flex Out (Core 8 Flex) into the design and enable each channel in the direction you need (Flex Input Enable / Flex Output Enable) (Flex Out (Core 8 Flex)). Plan §5.1 (ASSUMPTION): Flex 1–2 In = BGM L/R, Flex 3–4 In = spare, Flex 5–8 Out = spare or amp feeds. CHECK ON SITE what is actually landed on each Flex pin. Dante setup (if using DD-BN31): In Core Manager, Network > Services: enable mDNS/Bonjour discovery on the Dante LAN. In File > Design Properties, pick the Dante interface. Set External Config/Control = Yes on the Software Dante RX if you'll route in Dante Controller. (Software Dante TX, KB Software Dante won't start) 5 plates vs 8 included channels: if each plate uses 2 channels, the 5th plate needs a license or a different plan (Plan §5.5 TBD).

C2. Schematic per zone (repeat x3)

Make one schematic page per zone (left pane Schematic Pages). Components come from the Schematic Library on the right; use its search box. Connect output pins to input pins by dragging wires. Use Signal Names to link between pages (Getting Started).

Chain per zone (Plan §7):

Sources: BGM L/R (Core Flex In 1–2, or a Dante RX if the BGM player is network). Local line/mic from Dante RX (DD-BN31) and/or QIO-ML4i Mic/Line In ch1–4. On QIO-ML4i, set mic vs line per input and turn phantom power on only where needed. What's landed on ML4i ch1–4 is TBD (Plan §5.2): CHECK ON SITE. Source select: a Router (one output per zone) or a Matrix Mixer (sources x 3 zones). A Router gives you clean "BGM / Local / Mic / Off" buttons for the UCI (Plan §9.1). The Spec wants any source routable to each space. Optional mic ducking over BGM (Plan §7 #3, ASSUMPTION). Parametric EQ, then a light Compressor, then a Limiter (amp protection). Delay at 0 ms until measured. Zone Gain (this is the UCI volume) with its Mute. Outputs: QIO-L4o Line Out 1–4, plus Core Flex Out if needed, wired by cable to the Lab Gruppen E 5:4 inputs. Plan §5.3/§6.3 (ASSUMPTION): L4o Out1 = AMP-1 Ch1 Private Dining; Out2 = AMP-1 Ch2 Diner & Bar; Out3 = AMP-1 Ch3 Diner & Bar; Out4 = AMP-1 Ch4 Diner & Bar sub. AMP-2 Ch1–3 Restaurant & Lounge needs Core Flex Out 5–8, because the L4o only has 4 outs. AMP-3 = Phase 2: pre-build it, nothing wired yet. Confirm the actual cable from each output to each amp channel on site and write it in the Plan. The Lab Gruppen E 5:4 is an analog amp and does NOT appear in Inventory. Q-SYS only sees the QIO/Flex output feeding it. Level and mute for the UCI: besides the zone Gain knob and Mute button, add a meter so the UCI can show an LED bar. The Spec requires "level (with led bar graph)" (Spec 2.4.A.3.2).

C3. Fire-alarm input to system mute

Per the Q-SYS KB (Fire Alarm Relay with Digital TTL) and GPIO In (Core 8 Flex):

Drag GPIO In (Core 8 Flex…) from the Core's Inventory into the design. In Properties, set the pin you wired to the right GPIO Type: Contact Closure Input for a dry contact. The pin sits at about 9–10 VDC open; the LED comes on when the pin is shorted to ground. Digital Input (TTL 3.3V) only if the FA panel supplies 3.3/5 V. CHECK ON SITE which pin and which contact type the FA vendor gave you (Plan §11 #13). Add a System Mute component (search "System Mute" in the Schematic Library). Its Mute control pin is Input/Output, and it mutes all system outputs at the Core (System Mute). Wire the GPIO pin's Contact Closure / Digital Input control pin to System Mute > Mute. If the FA contact is normally closed (closed = no alarm, which is common for fail-safe), put a Logic NOT / Position Invert between them so an open contact mutes (amp GPIO fire-panel KB). Test both states. Amp standby (the Plan's hardwired path, Plan §5.1/§6.3): per the Lab Gruppen E-Series data, the rear GPI is a contact-closure input and closing it turns the amp ON. That means a contact that opens on alarm puts the amps in standby. Verify on the E 5:4 rear panel and in the manual before wiring (E 5:4 datasheet, E-Series manual). Fire-code interpretation varies by AHJ (KB note), so coordinate with the FA vendor.

C4. Master on/off and 4:00 AM reset (Spec 2.4.A.3.3 and .11)

Put every zone Gain, Mute and source select into a Snapshot Bank: left pane Snapshots, then drop a Snapshot Controller (Snapshot Controller). Make Snapshot 1 = "Nominal" (Spec: 70% UI ≈ 76 dBC, set in section F) and Snapshot 2 = "System Off" (all zones muted). Add a When component: Time = 04:00 (24-hour format). All days on. Length 0–10 s. Wire Active to the Snapshot Controller's Load for "Nominal". Zones that should be off at 4 AM need to be off in that snapshot. (When) Check that the Core's clock and time zone are right (Core Manager; CHECK ON SITE).

C5. QIO-IR1x4 (only if it's on site)

Add an IR Driver (or an IR Receiver to learn codes from the TV remotes). Wire the IR Receiver's IR Source to the QIO-IR1x4 IR Input, run the design, press the remote buttons, then save and label each code (IR Receiver, IR Driver, IR1x4 learning FAQ). Plan §5.4 (ASSUMPTION): IR1 = TV-1 Diner & Bar, IR2 = TV-2 Diner & Bar, IR3 = TV-3, IR4 = spare. The TV make and model are TBD. This is not needed for sound today, so skip it if time is short.

C6. Check it

File > Check Design shows DSP usage and network audio/bandwidth. Keep each link under 80%.

D UCIs (touch screens + iPad)

Left pane User Control Interfaces: click + for a new UCI. ("Inventory Status" is built in and can't be edited.) (Level 1: UCI Creation) Set Panel Type FIRST (select the UCI name > Properties > Panel Type = TSC-50-G3, Portrait or Landscape to match the wall mount). Changing it later doesn't rescale anything you've placed. Plan §9.1 says portrait (TA5.01 Detail 1). Build each zone UCI (one per zone; which panel goes where is TBD (Plan §9.3)): Home page with the Owner logo (artwork TBD). Zone page with source select buttons (BGM / Local / Mic / Off), the Gain fader with the meter/LED bar, Mute, and System Off (snapshot load). TV page with IR buttons, only if IR is in. Admin page behind its own PIN. To add a control: open the component's control panel, select the control, Ctrl+C, then Ctrl+V onto the UCI. You can also drag the UCI tab to a split screen and drag controls across. Add pages with + > Add Page. Use Navigation Buttons (Schematic Library > Layout > UCI) and set Tabs to None / Swipe Disabled to keep users off the Admin page. iPad UCI: make a separate UCI with Panel Type = iPad (Air size/orientation as listed). Put all 3 zones on one Overview page plus System Off (Plan §9.2). Hide or disable the Phase 2 zone controls for now. Assign UCIs to the TSCs: Select each TSC in Inventory (or its Status/Control (Touch Screen) component). Set UCI Assignment = Static and pick the UCI in UCI. Set orientation (Portrait/Landscape/Flipped). The Name must match the TSC hostname from Core Manager or Peripheral Manager. A blank UCI field causes "Fault – No UCI assigned". (Status/Control (Touch Screen), Level 1: UCI Deployment, KB No UCI assigned) Passcode (Spec 2.4.A.3.10): after deploying, open Core Manager > User Control Interfaces > Edit PINs > + New PIN (up to 8 digits). Then select the UCI > PIN Protection tab > Edit, tick the users, and Save. Make a separate admin PIN for the Admin page/UCI. By default, UCI access is open (Core Manager: User Control Interfaces). iPad setup (Q-SYS UCI Viewer (iOS)): Install Q-SYS UCI Viewer (Q-SYS Control) from the App Store. It's free and needs iPadOS 15.6+ (App Store). In Core Manager > Network > Services, enable "Q-SYS UCI Viewers – Windows and iOS". Put the iPad on a Wi-Fi network that can route to the Core's control IP (CHECK ON SITE with hotel IT; Plan §4). Go to iPad Settings > Q-Sys Control: Turn on Local Network. Hard Link IP Addresses > IP 1 = the Core LAN A IP. Do this by default. On iOS 14+ the app often can't discover Cores by multicast (KB iOS not connecting). UCI Viewer Mode ON and UCI Viewer Name = JWDC-iPad-1, exactly matching the Status/Control (UCI Viewer) component. That lets the Core control the iPad (4 AM reset). Leave Design/UCI Filters blank. Open the app and tap the UCI or UCI Viewer name. Still nothing? Delete the app, reboot the iPad, reinstall, and re-add the Hard Link (KB iPad won't deploy). Mark the UCIs you don't want on the iPad list as Private = Yes.

E Deploy, test, and back up

Emulate (F6): runs the UCIs and logic with no Core and no audio. Use it to click through every button and page before going live. You don't need a UCI license for this. Exit with Disconnect (F7). Deploy quietly: While in Emulate, set System Mute ON. Press F7. Press F5 = File > Save to Core & Run. The system comes up muted. Unmute once the gains look sane; unmute ramps from −20 to 0 dB over 3 s (System Mute). If it sticks on "Discovering Core…", the design's Core name or model doesn't match the network, or your status isn't green (Connecting to the Core). F5 overwrites whatever design is on the Core, and that design can't be retrieved afterwards. Back up first (step 4). Back up the running design: File > Load from Core & Connect. Pick the Core by name/design/IP; it opens in a new Designer instance in Run mode without restarting the Core. Then File > Save As a dated copy. The docs we read list no hotkey for this command; F8 is not documented in Getting Started. (Getting Started, Saving to a Core) Caution: don't have the same-named file open from the PC and the Core at the same time. Save often (Ctrl+S), with version names like _v02, _v03. Turn on File > Preferences > File Recovery Save. Control settings changed at least 30 s before a power loss are kept on the Core. Archive the final .qsys and send it to Dana for the job Drive Field folder (Plan §8 #10). Also keep the firmware version and a device list (name, IP, mode).

F Test & commission (per zone, against Spec 2.4)

Run all of this per zone: Diner & Bar / Private Dining / Restaurant & Lounge. Phase 2 zones: only the UCI behavior can be checked.

G Troubleshooting

Core not in Configurator

Likely cause Laptop on the wrong port/VLAN, Wi-Fi taking the route, or multicast blocked

Fix (doc) Plug into the AV switch, NIC on DHCP, Wi-Fi off. Still missing: add a Hard Link to the Core IP. Note that Hard Links only help Designer and UCI Viewer; the Core still needs multicast to reach its peripherals (Initial Discovery, Hard links FAQ)

Core shows RED in Configurator

Likely cause Laptop not on the Core's subnet (static IP elsewhere)

Fix (doc) Read the IP on the front panel (Next) and set the laptop to a free IP in that subnet (Configurator)

Devices appear, then disappear

Likely cause IGMP snooping without a querier, or querier/snooping timers mismatched

Fix (doc) Apply the Netgear Q-SYS profile, or set exactly one IGMPv2 querier. As a test, disable IGMP snooping (Configurator troubleshooting, Switches)

F5 stuck on "Discovering Core…"

Likely cause Design Core Name/Model ≠ physical Core

Fix (doc) Copy the exact hostname from Core Manager; Model = Core 8 Flex (Connecting to the Core)

Peripheral "Missing" (red) in Inventory/Status

Likely cause Name in design ≠ hostname, wrong model component, device offline, or an I/O-Core 8 Flex that is still in Core mode

Fix (doc) Match names exactly (ID button to confirm). Check PoE/link. Check the mode (section 0). "Missing = device cannot be discovered" (Status I/O-Core 8 Flex)

"Not Present"

Likely cause Is Required = No and device not found, or Dynamic Pairing unassigned

Fix (doc) Same as above. Set Is Required = Yes so faults show

"Initializing" for a long time

Likely cause Firmware update in progress after F5

Fix (doc) Wait, it can take a while. Don't power-cycle mid-update (Installing & Updating)

Firmware mismatch prompt

Likely cause Designer ≠ Core firmware

Fix (doc) Click Update, or install the Designer version that matches the Core (Updating Firmware KB)

Can't Save to Core / Load from Core: credentials

Likely cause Core Manager Access Control is on

Fix (doc) Log in with an Administrator or Technician role (who set it? CHECK ON SITE) (8.4 release notes)

No audio out of an amp

Likely cause System Mute on, zone mute, Router on "Off", Flex channel set as input not output, cable to the wrong amp input, amp attenuator down, amp in standby (GPI open, or the E-Series auto-standby after about 20 min with no signal per its manual: verify), amp mode not 70 V, idle design

Fix (doc) Work along the chain: meter at the QIO/Flex out → amp input LED → amp output. Check the Status page. Use a Noise Generator. The E 5:4 doesn't show in Q-SYS, so check it at the amp

Audio "Compromised – Packet Missing / Too Late" on Q-LAN/AES67 receivers

Likely cause QoS/PTP problem, cabling or CRC errors, EEE on

Fix (doc) DSCP: EF 46 highest, AF41 34 second, Strict Priority. EEE off. Check port error counters (Switches, KB Packet Missing)

Dante plates not heard

Likely cause Software Dante not started or not routed, mDNS service off, channel count over 8

Fix (doc) Enable the Core Manager Network Services discovery, set External Config/Control = Yes, route in Dante Controller (Software Dante TX)

TSC shows "Fault – No UCI assigned" or the Inventory Status page

Likely cause UCI field blank, TSC name mismatch

Fix (doc) Assign the UCI (Static), match the hostname, F5 again (KB)

UCIs won't deploy (license)

Likely cause Core on 9.x without a UCI Deployment license

Fix (doc) Upgrade the design/Core to 10.x, where UCI is free on any Core (FAQ)

iPad can't find the Core/UCI

Likely cause iOS multicast limits, UCI Viewers service off, Local Network permission off, filters set, iPad Wi-Fi can't route to the Core

Fix (doc) Add a Hard Link IP, enable the "Q-SYS UCI Viewers – Windows and iOS" service, check iPad Settings > Q-Sys Control (UCI Viewer iOS)

iPad shows the UCI but touches don't respond

Likely cause App bug reported by users on 10.4

Fix (doc) Try toggling UCI Viewer Mode, test from Core Manager > UCI View, call support (App Store review, not official)

QIO unreachable after a bad IP setting

Likely cause Static IP typo

Fix (doc) QIO short reset: about 10 s, release before 20 s (QIO-L4o)

H Escalation (call early; it's free)

Superior Connects office: (253) 234-5040, info@superiorconnects.com Q-SYS Technical Support (North America): Mon–Fri 6:00 AM–5:00 PM Pacific (verified 11/11/2026 on support.qsys.com/contact-us). Toll-free +1-833-480-QSYS (7797) +1-657-660-6300 Lorenzo is in DC (ET), so that's 9:00 AM–8:00 PM Eastern. Remote session: A remote session is not arranged yet. If you want one, call the Superior Connects office. Support case: Create a Q-SYS Support Case (needs the free account). Attach the .qsys file, firmware version, Configurator screenshot, and a Core log: Core Manager > Utilities > Download log (.qsyslog) (Utilities). Supplier: Creation Networks, Dimitri Kritikos, 925-488-9850 (programming referral or quote; Dana decides).

I Q-SYS Training pages (read only what you need)

These are Q-SYS Training pages, not videos. Some may need a free Q-SYS account sign-in.

Level Zero – Software Basics

Length short

Covers Workspace, panes, modes

Link view

Level Zero – The Inventory Panel

Length ~7 min

Covers Core name/model, adding QIOs/TSCs, Status components

Link view · print transcript

Level Zero – Connecting to the Core

Length ~7.5 min

Covers Configurator, Core Manager naming, F5, "Discovering Core…"

Link view · print

Level 1 – UCI Creation and Management

Length ~10 min

Covers New UCI, Panel Type, pages, navigation, Private, PIN logon

Link view · print

Level 1 – UCI Deployment

Length ~7 min

Covers Assigning a UCI to a TSC, Static/Dynamic, iPad/Windows viewers, UCI Viewer component

Link view · print

Fire alarm GPIO example (KB)

Length read

Covers GPIO in → System Mute, Logic NOT

Link KB

J Answer these on site

Don't enter passwords or logins here.

Tapping Send answers emails everything below (and your photos) to Superior Connects at info@superiorconnects.com through FormSubmit. Your typing is also saved on this phone until you clear it.

Your name (optional)What's failing right now? (error text / screenshot)Choose photos or screenshots (up to 10 MB total)Or take a photo now (phone camera)

1. What exactly is failing? (pick the step)Can't see the Cores/devices in Tools > Show Q-SYS Configurator? Are they green, red or blue?F5 sticks on "Discovering Core…"?Firmware update prompt failing or stuck on "Initializing"?Devices show Missing in the design?Design runs but no audio at the amps or speakers?Can't build the signal flow (which components to use)?UCIs won't show on the TSCs ("No UCI assigned"/license) or on the iPad?Exact error text or a screenshot: ____________

2. VersionsQ-SYS Designer version on the laptop: ______Core firmware (front panel Next, or Core Manager): ______ (9.x or 10.x? This decides the UCI license question.)Laptop is Windows? Y/N. Anyone set a Core Manager login (Access Control)? Who has it?

3. The 3 Core 8 Flex unitsHostname, IP and mode (Core vs Peripheral "I/O-Core 8 Flex" in Configurator) for each: 1 ____ 2 ____ 3 ____Which one(s) are cabled to the AV switch (LAN A)? Is anything plugged into LAN B?What is landed on each Core's Flex 1–8 and GPIO pins? Did anyone wire amp feeds to Cores 2 or 3 expecting one Core per zone?Is any design already running on any Core? (Back it up with Load from Core & Connect before F5.)

4. Speakers and ampsWhich zones do the 18–20 installed Phase 1 speakers serve? (Diner & Bar / Private Dining / Restaurant & Lounge.) TBD in Plan §1.2. Don't assume 16+4.Per amp channel: which speakers and which tap (W @ 70 V)? Is the amp set to 70 V mode? Attenuator positions?Which QIO-L4o or Core Flex output is cabled to which E 5:4 input (AMP-1/2/3, ch 1–4)?How many speaker home-runs are actually landed (Plan says 11)?

5. Inputs and sourcesBGM source make and model; analog to Core Flex 1–2, or network/Dante? (TBD Plan §11 #8)What's on QIO-ML4i ch 1–4 (mic or line)? Which need phantom power?Which DD-BN31 plates are installed and where? (TBD Plan §5.5/§11 #7.) Is Dante Controller on the laptop?

6. Touch screens, iPad, IRHow many TSC-50-G3 are on site: 4 or 5? Hostname and wall location for each (TBD Plan §9.3).Portrait or landscape mount?iPad: which Wi-Fi network, and can it reach the Core IP? (Hotel IT, TBD Plan §4.)Is the QIO-IR1x4 physically on site? (Order status unconfirmed.) TV make and model?

7. NetworkHow many Netgear M4250 switches are on site (Plan says 1 of 2 seen)? Was the "Audio – Q-SYS" profile applied? Any uplink to hotel IT?IP plan from hotel IT, or an isolated subnet we pick? (All IPs TBD, Plan §4.)

8. Fire alarmWhere does the FA contact land (Core GPIO pin #, and/or E 5:4 GPI)? Is it dry contact or TTL? Normally open or normally closed? Who from the FA vendor can test it with us?

Don't enter passwords or logins here.

JW Marriott DC Diner: Q-SYS Field Programming Playbook

1. What exactly is failing? (pick the step)

2. Versions

3. The 3 Core 8 Flex units

4. Speakers and amps

5. Inputs and sources

6. Touch screens, iPad, IR

7. Network

8. Fire alarm

9. Still TBD in our Plan (not Lorenzo's problem today)

C1. Inventory

C2. Schematic per zone (repeat x3)

C3. Fire-alarm input to system mute

C4. Master on/off and 4:00 AM reset (Spec 2.4.A.3.3 and .11)

C5. QIO-IR1x4 (only if it's on site)

C6. Check it