Audio
Yamaha CL5 troubleshooting
The Yamaha CL5 problems live-event techs bring to Ask Roadie most. 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 CL5 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 →
What is the current CL5 firmware version and the correct update path?
Likely cause: Matches the official V5.91 update instructions.
- Step-by-step fixGet the fix →
After firmware update a dialog says the NAME SUB CPU is old
Likely cause: The console has a secondary CPU for the channel-name strip that updates independently of the main firmware.
- Step-by-step fixGet the fix →
Console froze or shows "kernel sysdwn" and is unresponsive
Likely cause: Yamaha lists "kernel sysdwn" as a known fault requiring restart with full settings initialization; pre-emptive backups and pulling the redundant cable prevent a bad-state Dante reconfigure.
- Step-by-step fixGet the fix →
Dante dropouts or poor clock sync through a network switch
Likely cause: EEE powers ports down during low traffic; faulty negotiation starves the tightly clocked Dante stream.
- Step-by-step fixGet the fix →
Firmware update best practices and the C-MD1.BIN trap
Likely cause: Same filename across two product lines is the classic failure; a mid-write power loss corrupts the boot image.
- Step-by-step fixGet the fix →
Newer Shure wireless mics or Rio-D3 stageboxes are not recognized / cannot be HA-controlled from the CL5
Likely cause: The device support tables are baked into firmware; older firmware simply has no descriptor for newer Shure/Rio-D3 hardware.
- Step-by-step fixGet the fix →
Set up Dante redundancy — changed Rio from Daisy Chain to Redundant and now it errors
Likely cause: The console caches Dante topology at boot; changing redundancy mode requires a restart to re-enumerate primary/secondary paths.
- Step-by-step fixGet the fix →
After a firmware update, console and Rio disagree / SYSTEM-SYNC inconsistency (Dante latency 0.25 or 0.5 ms)
Likely cause: The latency change triggers a full Dante re-negotiation that clears the stale post-update state.
- Step-by-step fixGet the fix →
FOH and monitor consoles share the same Rio — one engineer changing gain wrecks the other mix
Likely cause: Analog HA gain is a single shared physical setting per Rio input; gain comp decouples each console's working level from it digitally.
- Step-by-step fixGet the fix →
StageMix iPad won't connect to the console
Likely cause: StageMix rides on the console's network port over Wi-Fi; wrong subnet, old firmware, or a captive-portal AP are the usual blockers.
- Step-by-step fixGet the fix →
Console shows DANTE SETTING MISMATCH but Dante looks fine
Likely cause: A firmware bug mapped a PSU-redundancy fault to the wrong on-screen message; the underlying issue is often power, not Dante.
- Step-by-step fixGet the fix →
Dante Controller shows a device's channels greyed out / won't route
Likely cause: Dante only allows subscriptions between transmitters and receivers with identical media formats.
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 CL5
- 1. Pick the Yamaha CL5. 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.