Lighting
ROBE Spiider troubleshooting
The ROBE Spiider problems live-event techs bring to Ask Roadie most (also called Robin Spiider, Spider). 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 Spiider 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 →
Choosing the right DMX personality / patch count for the Spiider
Likely cause: Mismatched personality between console and fixture is the most common cause of "wrong channels doing wrong things"; matching the mode fixes mapping.
- Step-by-step fixGet the fix →
Clean Air Filters warning icon on display
Likely cause: The warning is a timer-based maintenance reminder; cleaning and resetting the counter clears it and keeps cooling effective.
- Step-by-step fixGet the fix →
EEprom Error on the display
Likely cause: An EEPROM fault is a memory-hardware error, not a user setting, so it is cleared only by service/replacement.
- Step-by-step fixGet the fix →
Fixture dims itself / LEDs shut off during a show (overheating)
Likely cause: Thermal fold-back and cut-off are intentional protections; restoring airflow and cleaning filters lets the head cool so it stops derating.
- Step-by-step fixGet the fix →
How to update Spiider firmware and confirm current version
Likely cause: Robe Uploader is the official update path and reads/writes version info via RDM/Ethernet, so it both flashes and confirms the running version.
- Step-by-step fixGet the fix →
On ETC Eos the Spiider has no intensity by default / pixels will not respond
Likely cause: The pixel-vs-master priority channel governs whether individual pixel RGB or the master RGB takes over; forcing it high gives predictable pixel output, and knowing the dual intensity structure prevents a dark fixture.
- Step-by-step fixGet the fix →
On grandMA3 the Spiider pixels/multi-instance behave wrongly (MA3 1.8 multi-instance bug)
Likely cause: The misbehavior originated in the console fixture library/software, not the luminaire, so a console update + fresh fixture type resolves it.
- Step-by-step fixGet the fix →
Pan Error 1 / Pan Error 2 (or Tilt Error 1/2) shown after reset; head or yoke lands off its home position
Likely cause: A P/T position error is raised only when the axis does not reach its default position after homing, which points to the indexing circuit or motor drive rather than DMX/control.
- Step-by-step fixGet the fix →
Pan/Tilt EMS Cal. Error or Pan/Tilt EMS Error
Likely cause: The two variants separate an un-calibrated state (fixable by recalibrating) from a communication failure (hardware/service).
- Step-by-step fixGet the fix →
Recharge The Battery / Battery faulty message; clock or settings lost
Likely cause: The display board uses a rechargeable backup cell; a long power-on recharges it, and an exhausted cell can no longer hold charge and must be swapped.
- Step-by-step fixGet the fix →
Rod Error after reset; flower/beam effect rod not working
Likely cause: This message is tied only to the flower-effect rod failing to home, so the fault is in that module, not the LED/control path.
- Step-by-step fixGet the fix →
Temper.Sensor Error message on the display
Likely cause: The message indicates a lost sensor-to-processor link; without a valid head temperature the fixture cannot self-protect against overheating.
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 Spiider
- 1. Pick the ROBE Spiider. 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.