Martin MAC Viper XIP troubleshooting

Common MAC Viper XIP 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.

• Extended framing shutters wont position correctly, or blades/curtain look misaligned across the beam

  Likely cause: Framing on the XIP is 16-bit and rotatable, so wrong coarse/fine mapping or a missed home cycle looks like a mechanical fault; re-homing and confirming the channel map resolves the non-hardware cases.

  Step-by-step fixGet the fix →

• Fan error on display (BASE FAN, HEAD FAN, or module fan ERR) and LED output drops or shuts off

  Likely cause: A stopped fan removes cooling headroom; the firmware kills output to protect the LED engine and latches the error until a reset confirms the fan is spinning again.

  Step-by-step fixGet the fix →

• Firmware upload failed: DMX UPLOAD ERROR (UPLD) or UPL ERR module (UEZF/UEEF/UEPT/UEUI/UECM); fixture will not finish init

  Likely cause: An interrupted or noisy transfer leaves a circuit without valid firmware so init cannot complete; a clean re-send over a reliable path (USB) writes it correctly.

  Step-by-step fixGet the fix →

• FIXTURE COLD (COLD) shown; effects sluggish or not working after cold-weather outdoor use

  Likely cause: Grease and mechanics stiffen in the cold and some effects are held until the head warms; self-heating from the engine brings the fixture into its operating band.

  Step-by-step fixGet the fix →

• Fixture wont strike / no light output and display holds LED engine off; CAL DATA error shown (CDZF, CDEF, CDCM, CDPT)

  Likely cause: The fixture stores per-effect calibration in EEPROM; if it is blank or corrupt the controller cannot guarantee optic position, so it disables output until valid data exists.

  Step-by-step fixGet the fix →

• GOBO WHEEL 1/2 error (G1ER/G2ER) or gobo rotation error (R1ER/R2ER); gobo mispositioned, will not index or rotate

  Likely cause: Gobo indexing uses the same magnetic-indexing + timeout scheme as the other wheels, so movement present vs absent isolates the fault to feedback vs motor drive.

  Step-by-step fixGet the fix →

• Need to set DMX address, mode or personality, or configure the fixture with power off

  Likely cause: The XIP has a battery-backed UI and NFC config, so address/mode can be set in the case before power; matching modes keeps each fixtures channel footprint consistent on the console patch.

  Step-by-step fixGet the fix →

• Setting up networked control (Art-Net / sACN / P3) or daisy-chaining fixtures over Ethernet

  Likely cause: The internal switch with relay bypass keeps downstream fixtures fed if one node drops, and P3 5.1.0+ is the minimum that recognizes the XIP profile.

  Step-by-step fixGet the fix →

• TEMP CUT OFF / TEMP HIGH warning (module, PSU or UI); LED shuts down and fans ramp to full

  Likely cause: The PCBs cut the LED engine when a temp sensor reads over the allowed limit for a sustained period; restoring airflow/ambient lets it drop below threshold, and a reset re-arms output.

  Step-by-step fixGet the fix →

• ZOOM ERROR (ZOER) or FOCUS ERROR (FOER) on display; beam soft, wont zoom or focus, or optic parks at mechanical stop

  Likely cause: These are magnetic/optical indexing timeouts: if the effect moves, the motor drive is fine and the fault is in position feedback (sensor/wiring); if it does not move, the motor circuit itself is the point of failure.

  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 Martin gear

Other lighting gear