Martin P3 controllers & VDO fixtures troubleshooting

Common P3 controllers & VDO fixtures 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.

• What is the current P3 software / firmware version?

  Likely cause: The controller software and the fixture personality/firmware package are released as a matched set; running them at the same version avoids incompatibility.

  Step-by-step fixGet the fix →

• Can I use P3 without buying a hardware controller / as an Art-Net-to-P3 bridge?

  Likely cause: P3-PC exposes the same mapping/addressing engine as the hardware, so you can prep a show or bridge console data without a physical controller.

  Step-by-step fixGet the fix →

• How do I address VDO fixtures without touching each one?

  Likely cause: P3 (and RDM) address fixtures over the data network, so a large run is configured from the controller instead of by hand at height.

  Step-by-step fixGet the fix →

• How do I read a VDO Sceptron's status in the field with no console?

  Likely cause: The onboard magnetic sensor reports power/data/error state locally, so you can isolate a fixture-level fault from a controller/cabling fault without a desk.

  Step-by-step fixGet the fix →

• How do I update P3 software and fixture firmware?

  Likely cause: Clearing old user personalities first prevents stale files overriding the new package; importing the matched package is what actually gives the controller the current fixture firmware to push.

  Step-by-step fixGet the fix →

• P3 controller network ports — P3 data vs Art-Net/sACN in

  Likely cause: The two networks are separate: mixing them means the console can't reach the controller and fixtures get no video, which looks like a dead run.

  Step-by-step fixGet the fix →

• Can I pre-viz a P3 rig in 3D visualization software?

  Likely cause: The Visualizer Protocol exports the mapped fixture output to a viz engine, letting you program and check content offline.

  Step-by-step fixGet the fix →

• VDO Sceptron — DMX vs P3 video: which mode, and does it switch automatically?

  Likely cause: The fixture arbitrates its input by signal type, so a wrong/direct-DMX-only personality is a common reason content won't display even though the fixture is lit.

  Step-by-step fixGet the fix →

• VDO Sceptron acting up / stuck — how to reset it at the fixture

  Likely cause: The magnet-triggered reset reboots the fixture's onboard controller, clearing a hung state without removing power to the whole run.

  Step-by-step fixGet the fix →

• VDO fixtures dark / not taking content

  Likely cause: P3 carries pixel-mapped video over the same cabling infrastructure; fixtures ignore console DMX for pixel content when P3-mapped.

  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