Lighting
ETC Element 2 troubleshooting
The ETC Element 2 problems live-event techs bring to Ask Roadie most (also called Element, Element2). 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 Element 2 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 →
After a Gadget/High-Speed I/O board firmware update the console will not boot — black screen with a blinking white cursor
Likely cause: A half-flashed I/O board sits in bootloader and blocks boot; a full power-down (not just restart) clears its state so the firmware update can complete cleanly.
- Step-by-step fixGet the fix →
Confusion about tracking, single cue list, and HTP vs LTP behaviour on Element 2
Likely cause: Most 'unexpected level' calls on Element 2 are really the tracking + HTP/LTP model working as designed; understanding the single-cue-list limit prevents workflows that assume multi-list playback.
- Step-by-step fixGet the fix →
Console appears to run fine but no lights come on / no DMX output
Likely cause: Eos outputs only when masters are up, addresses are patched, the network protocol is enabled in the Shell, and the port's universe matches where the fixtures actually live — the four things that account for nearly all 'no output' calls.
- Step-by-step fixGet the fix →
Fixtures respond but at the wrong addresses / universe — sACN universes on the rig don't match the console patch
Likely cause: The offset shifts the console's logical universes onto the rig's actual sACN universe numbers, so you keep a clean 1-based patch without renumbering every address.
- Step-by-step fixGet the fix →
How do I update software on an Element 2 / what is the current version
Likely cause: Eos updates are single-installer packages run from the Shell; keeping console and any networked gateways/RPUs on the same version avoids protocol mismatches.
- Step-by-step fixGet the fix →
How to connect Element 2 to gateways, dimmers and other show gear / what protocols it speaks
Likely cause: Getting console, gateways and fixtures on one subnet with a matching, enabled protocol and correct universe map is what makes multi-box ETC systems talk; termination prevents reflections on long DMX cable.
- Step-by-step fixGet the fix →
I/O board shows as 'in Bootloader mode' / not recognized after an interrupted update
Likely cause: An interrupted flash leaves the I/O micro in bootloader; re-running the flash from a clean boot completes it, and the mandatory restart re-initializes DMX output.
- Step-by-step fixGet the fix →
Newly patched LED / multi-parameter fixture only controls intensity or behaves oddly
Likely cause: The console can only drive the parameters its patched personality expects; matching the fixture's physical DMX mode to the library profile and start address makes every attribute land on the right slot.
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 Element 2
- 1. Pick the ETC Element 2. 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.