Skip to content

Troubleshooting

Start with the Dashboard: a warning symbol marks the card where the problem is, and a click opens its page. The LEDs tell the rest without a computer.

The unit

The Power LED double-flashes
  • No Ethernet link: check the cable, and that the switch port is on.
The Power LED stays on or off, without blinking
  • The firmware has stopped: power-cycle the unit. If it happens again, write to support@miraxyz.com with the serial number (System page → Copy info).
The Ref and Timecode LEDs double-flash together
  • The sync card is not answering: power-cycle the unit. If it stays, contact support.

Finding the unit

Discovery doesn't list the unit
  • Check the Power LED: a slow heartbeat means the unit runs with its network link up (LED indicators).
  • Run Discovery on a computer cabled to the same switch, and allow it through the Windows firewall (UDP port 27000, Network → Ports).
Discovery lists the unit but the web app doesn't open
  • The computer is on another subnet: give it an address on the unit's subnet, or give the unit one on yours with Edit in Discovery (First connection).
  • Two units with the same address: every unit leaves the factory as 192.168.37.50. Give each its own (Network → Address).
The web app shows RigFX is open on another device

Sync

The Sync card doesn't read Locked
  • In External mode, check the Ref cable and that the sync generator sends Black Burst or Tri-Level (Genlock / Sync). The Ref LED is on when the reference is detected.
  • Check that the Target framerate is the reference's rate: the measured FPS under the timecode must match it.
  • The card says when the Sync card18 is missing or not answering, and what to check.
The timecode is wrong or frozen
  • With a timecode cable, check that the Timecode LED is on and that the timecode and the Genlock7 come from the same sync generator.
  • With OpenTrackIO11 as the timecode source, the status beside the selector says why it falls back to the hardware timecode (Sync → Timecode source).

Sources

A source stays at No Data
  • Network sources: the sender must send to the IP address of RigFX and to the port on the source card, from the same subnet.
  • Lens FIZ5: check the Mode and the connector (Lens FIZ source).
  • Each source page has its own troubleshooting section: Source.
OptiTrack: Motive is connected but the rigid body never comes (No rigid body with ID N in stream)
  • The Rigid Body ID must be the asset's Streaming ID in Motive.
  • With Motive 3.5, the unit needs firmware 1.13 or later (OptiTrack: Supported versions).
The camera stutters, or lags one frame behind now and then
  • Open the Phase View: packets drawn orange arrive after the phase offset and are used one frame late. Raise the Phase Offset until every source's packets land before the PHASE marker, with some margin for their jitter.
  • Two sources on one rig a frame apart (Cartoni encoders and a network PTZ, for example): raise the Buffer (frames delay) of the faster one by 1.

Rig

The rig doesn't move in the 3D view
  • A node card with an amber border and a warning is bound to a channel with no data: on Source, check that this input (or Cartoni channel) is enabled and reads Connected (Source).
The camera moves the wrong way in the 3D view
  • Toggle Negate on that field of the node card (Rig). Don't fix a direction with an offset or a negative scale.
The camera is in the wrong place, or drifts as the rig moves
  • Check the measurements on the node cards against your rig (Measuring your rig), and zero the encoders again with Set 0 at the reference position.
  • For a precise result, line the rig up with CalibFX Lineup: it solves the studio and sensor offsets and the chain in between.

Output

The render engine receives nothing
  • Check the output's IP and Port against the render engine's, and that the output is enabled (Output).
  • Check that a firewall on the render engine computer lets that UDP port in.
  • Check that the render engine reads the same protocol (FreeD6 or OpenTrackIO11).
The lens doesn't match in the render engine
  • With FreeD6, the render engine applies its own lens file to the zoom and focus encoders: check it has one for this lens (Lens pipeline 1).
  • With OpenTrackIO11, choose a lens file on the Lens page, or a lens source that sends a calibrated lens.
  • Aximmetry: see the Invert Cx and Legacy distortion order options (Output → OpenTrackIO options).