Skip to content

Tracker App Import — Only Roll Axis Shows Data After Import; Other Axes Zero

Summary

Some operators report that after importing a Tracker App CSV, only the Roll axis has data — all other axes (pan, tilt, X, Y, Z) remain at zero. The move plays back as a pure roll motion regardless of what was recorded. The most likely causes are: incorrect Kinematics mode in Flair (must be TT/Roll Relative, not Camera Orbital), the phone being held with the wrong orientation during recording (vertical vs horizontal), or an import mode mismatch. Changing kinematics to TT with Roll Relative, re-importing with Translate to Current → Camera, and verifying the phone's orientation during recording resolves the issue in most documented cases.

Symptoms

  • After importing Tracker App CSV, only roll axis has non-zero keyframes.
  • Pan, tilt, X, Y, Z all remain at zero or at home position.
  • Move plays back as only a camera roll with no translation or pan/tilt.
  • The recording appeared to capture a full move (walk around, pan, etc.) but only roll comes through.
  • 3D rig view shows robot stationary with only roll axis animating.

Community Guidance

[WORKAROUND] Check Kinematics Mode — Must Be TT with Roll Relative

Community — see also TRACKER-import-origin-zeroing.md

The kinematics mode must be set to TT (Target Tracking) with Roll Relative for the Tracker App import to function correctly. Camera Orbital mode solves the robot motion differently and can produce incorrect or partial results — in some cases only producing roll data.

In Flair: Kinematics Setup → set to TT → Roll Relative (not Camera Orbital).

Alexandre Zahnn Ythen: "Found out my problem: needed to be in Roll Relative, and should be on TT. Mine was set on camera orbital changed it to TT and worked."

confidence_score: 0.90

[WORKAROUND] Phone Orientation During Recording

Community

The Tracker App assumes a specific phone orientation relative to the camera. If the phone was held vertically (portrait) instead of the expected horizontal (landscape) orientation when the move was recorded, the axis mapping can be incorrect — rotation around the phone's long axis (which would be roll in landscape) becomes the dominant recorded axis.

Hold the phone in landscape orientation during recording with the screen facing up and the camera facing in the same direction as the robot's camera lens.

confidence_score: 0.82

[WORKAROUND] Verify Zeroing and Reimport with Correct Settings

Community — see TRACKER-import-origin-zeroing.md for full procedure

Run through the complete import checklist: 1. Zero the app at the camera nodal point with robot at home (house icon in the app) 2. Import with Translate to Current → Camera (not "None") 3. Rotate to Camera → Yes 4. Granularity 10–25 5. Kinematics: TT, Roll Relative

If only roll data appears after following all steps correctly, contact MRMC support as this may indicate an app-specific issue with the recording file.

confidence_score: 0.85

Official Documentation

MRMC Forum — Mimic Tracker iOS App: Read Me First