Lighting
ETC Eos Apex troubleshooting
The ETC Eos Apex problems live-event techs bring to Ask Roadie most (also called Apex, Apex 10, Apex 20, Apex 5). 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 Eos Apex 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 →
"Firmware Updates Available" message on boot
Likely cause: Console-module firmware is bundled with Eos software; the message just means the installed software is newer than the boards.
- Step-by-step fixGet the fix →
1-Port Gateway in Net2 mode stops outputting DMX after idle
Likely cause: A gateway firmware defect in Net2 mode drops output when idle; newer firmware / Net3 sACN operation removes the dependency on constant activity.
- Step-by-step fixGet the fix →
Apex Button Module OLED 1x10 target key stuck in Bootloader Mode / default boot image
Likely cause: A firmware-test defect left the module in bootloader state; a cold boot re-flashes the display, and the newer software removes the defect.
- Step-by-step fixGet the fix →
Apex fader-panel (FP) touchscreen not responding to touches
Likely cause: Distinguishes a software hang (fixed by reboot) from a failed touch digitizer (needs service); the face panel test isolates the fault.
- Step-by-step fixGet the fix →
Console not outputting DMX / not talking to lights
Likely cause: Output is gated by the grandmaster and by per-port universe mapping; the two most common 'no output' causes are a master fader down and a port/universe mismatch.
- Step-by-step fixGet the fix →
Faders dead or console misbehaves when a fader wing was powered before the console
Likely cause: The console assigns/enumerates attached wings at boot; a wing powered first can fail to register on the panel bus until reconnected after boot.
- Step-by-step fixGet the fix →
Faders or bump buttons become unresponsive mid-use
Likely cause: Unresponsive faders are usually a face-panel firmware/communication hang rather than dead hardware; updated module firmware and a reboot restore the panel bus.
- Step-by-step fixGet the fix →
LED fixtures flicker or are unresponsive
Likely cause: Many LED fixtures mis-read DMX sent at max refresh; slowing the port or disabling RDM restores stable data.
- Step-by-step fixGet the fix →
Need to factory reset / restore an Apex console
Likely cause: The recovery partition reimages the OS/software to a known-good state; it wipes local data, so a show backup and re-updating software are required around it.
- Step-by-step fixGet the fix →
Quick reference: Apex specs / power / I/O
Likely cause: Gives techs the load-in essentials (fader count, power/amperage for circuiting, network and local I/O options) at a glance.
- Step-by-step fixGet the fix →
SMPTE or MIDI timecode not being received
Likely cause: Timecode triggering requires the protocol configured as a show-control list and the correct input path; SMPTE has no local input on Eos, which is the usual gap.
- Step-by-step fixGet the fix →
Splotchy or dark backlight on Apex internal touch screens
Likely cause: Uneven backlight is a panel hardware fault, not a settable option; ETC handles it as a service item.
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 Eos Apex
- 1. Pick the ETC Eos Apex. 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.