Lighting
Obsidian ONYX troubleshooting
The Obsidian ONYX problems live-event techs bring to Ask Roadie most (also called Martin M-series successor, NX Touch, NX Wing, NX1). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common ONYX errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact unit is in Ask Roadie.
- Step-by-step fixGet the fix →
ONYX only runs in Free mode / drops to a low tier / license (dongle) not found
Likely cause: If the key/dongle drops off the USB bus the app reverts down a tier.
- Step-by-step fixGet the fix →
How does ONYX handle timecode / show integration (SMPTE, MIDI, Art-Net) and X-Net?
Likely cause: Timecode and X-Net are the backbone of automated and multi-node shows; knowing which surfaces expose LTC/MIDI and how NIC binding works prevents sync and routing failures.
- Step-by-step fixGet the fix →
License / dongle not recognized after a Windows Update (e.g. KB5074105 or KB5077181)
Likely cause: The Windows security updates changed driver/enforcement behavior that ONYX's license check relied on; the 4.32.1311 build restores compatibility.
- Step-by-step fixGet the fix →
How do I update ONYX software and NX hardware firmware safely?
Likely cause: ONYX bundles surface firmware with the app build; library changes between versions can shift fixture defaults, so verifying shows after an update prevents surprises on stage.
- Step-by-step fixGet the fix →
NX Touch (or NX Wing) freezes mid-show: faders/buttons unresponsive and its DMX output frozen while the PC and other universes keep running
Likely cause: The lockup was a firmware/USB handshake fault fixed in 4.10.1268; ending the Obsidian service forces a clean re-enumeration of the USB surface, and cable separation cuts EMI-induced USB drops.
- Step-by-step fixGet the fix →
NX Wing firmware update fails / Wing becomes unusable after a firmware update
Likely cause: A partial/interrupted flash leaves firmware in a bad state; re-flashing from the matching ONYX build or a support recovery image is the intended repair path.
- Step-by-step fixGet the fix →
NX Wing USB control surface specifications
Likely cause: The Wing doubles as the license key and DMX I/O, so its health directly sets the available universe count and playback control.
- Step-by-step fixGet the fix →
NX4 console specifications (spec-sheet reference)
Likely cause: Physical/electrical and I/O specs let techs plan rigging, power, monitor support and timecode integration for the flagship NX4.
- Step-by-step fixGet the fix →
NX2 console specifications (spec-sheet reference)
Likely cause: Compact 64-universe console specs for transport, power and monitor planning.
- Step-by-step fixGet the fix →
Some Art-Net nodes work, others get nothing
Likely cause: Unicast-to-detected relies on ArtPoll replies; nodes with quirky discovery never make the list.
- Step-by-step fixGet the fix →
No DMX output over Art-Net / sACN (fixtures dead from ONYX)
Likely cause: ONYX ships with all network DMX disabled so it never floods a network unasked — nothing leaves the console until you enable outputs per protocol, per interface, per universe.
- Step-by-step fixGet the fix →
Art-Net node never receives data
Likely cause: Art-Net convention uses the 2.x.x.x network; a node on 192.168.x.x never sees packets addressed to the 2.x range.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the ONYX
- 1. Pick the Obsidian ONYX. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.