ROBE T1 Profile troubleshooting

Common T1 Profile 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.

• "Clean Air Filters" message / fixture running hot / fans loud

  Likely cause: Blocked filters or a dead fan starve the heatsink of airflow, raising junction temps and triggering thermal protection; resetting the maintenance counter clears the reminder after cleaning.

  Step-by-step fixGet the fix →

• "EEprom Error" on display

  Likely cause: The EEPROM stores fixture settings/counters; a hardware error there cannot be cleared by the user and indicates a failed memory chip.

  Step-by-step fixGet the fix →

• "Internal Error 1" or "Internal Error 2" (PCBs not communicating)

  Likely cause: The fixture's boards share a comms bus; the Software Versions screen enumerates every board, so an N/A entry pinpoints exactly which PCB dropped off.

  Step-by-step fixGet the fix →

• "Pan/Tilt EMS Cal. Error" or "Pan/Tilt EMS Error" on reset

  Likely cause: EMS is the gyro-based P/T stabiliser; a cal error is a stored-offset problem (fixable by recalibration) while a comms error is a wiring/board fault.

  Step-by-step fixGet the fix →

• "Recharge The battery" or "Battery Faulty. Replace it." message

  Likely cause: A backup cell on the display board holds the clock and lets the touchscreen power up untethered; low = rechargeable by running, dead = must swap.

  Step-by-step fixGet the fix →

• ETC Eos: T1 framing shutter action previews incorrectly in Encoder Display / Augment3D

  Likely cause: The preview error is in the console fixture profile mapping, not the fixture — a corrected library entry aligns the encoder/visualiser to the actual blade DMX values.

  Step-by-step fixGet the fix →

• Framing shutter errors after reset: "Fr. Shutters Rot. Error 1/2" or "Fr. Shutter 1/2/3/4 Error 1/2"

  Likely cause: The reset routine homes each blade against its index sensor; a repeatable error means the module never reached home, which is a sensor/motor/driver fault rather than a control error.

  Step-by-step fixGet the fix →

• How to read/see an error on the T1 Profile (yellow warning icon on display)

  Likely cause: The T1 uses a QVGA touch display that logs faults; the icon is the entry point to the human-readable message list, and the Software Versions screen isolates a dead PCB.

  Step-by-step fixGet the fix →

• LED "Short Error" messages: Blue/Green/Light Green/Amber/Red 1-4 Short Error

  Likely cause: The T1's multi-spectral engine is driven in colour channels; the driver detects an open/short per channel and names the colour and segment, which directly identifies the faulty emitter group.

  Step-by-step fixGet the fix →

• Setting DMX address and choosing a DMX mode/protocol

  Likely cause: Channel count must match between fixture personality and console; using the wrong mode shifts every parameter.

  Step-by-step fixGet the fix →

• Updating firmware / software on the T1 Profile

  Likely cause: Robe fixtures flash via their proprietary uploader over RDM/Ethernet or via the RUNIT DSU dongle; matching the process to whether the unit has RDM/Ethernet avoids a failed/partial flash.

  Step-by-step fixGet the fix →

• Wireless DMX (CRMX) will not receive / pairing the fixture

  Likely cause: CRMX must be bound to one transmitter at a time; a leftover pairing or the input being left on Wired are the usual reasons a linked fixture shows no data.

  Step-by-step fixGet the fix →

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.

More ROBE gear

Other lighting gear