Tracker App: Do NOT Import CSV as Mimic — Use Standard CGI Import¶
Summary¶
When importing a Tracker App CSV file into Flair, do not use the Import as Mimic option. Importing as Mimic produces a blank or mostly-empty move — the Mimic recording system expects real-time data from the Flair hardware axes, not an external CSV file. Instead, use the standard CGI Data import workflow in the Move Programming section: File → Import → Tracker CSV. This produces editable keyframes that correctly represent the phone's recorded motion. If you want to use the recorded move as a Mimic-type reference, you can convert the imported keyframe move to Mimic data afterwards.
Symptoms¶
- Importing a Tracker App CSV via the Mimic window produces a blank move with no keyframes.
- All axes show zero or missing data after a Mimic import of the Tracker CSV.
- The robot sits still or only moves on one axis after a Mimic import.
- The import completes without errors but nothing is in the move.
- Move data looks correct in the CSV file but disappears on import.
Community Guidance¶
[RESOLVED] Use the Standard CGI Import — Not Import as Mimic¶
2021-12-13 — Peter Constan-Tatos / Dan Gottesman / Jeremy Andrews
The Tracker App CSV export is a standard XYZ/rotation data file. It must be imported using the standard Tracker CSV import in Flair, not through the Mimic recording system:
Correct import workflow: 1. Copy the Tracker App CSV file to the Flair PC. 2. In Flair, go to File → Import (or use the CGI data import button in the Move Programming section). 3. Select the Tracker CSV file. 4. Set Translate to Current → Camera. 5. Set Rotate to Camera → Yes. 6. Set Granularity to 10–25 (not 1). 7. Ensure the robot is positioned approximately where you want the move to start. 8. Click Import.
The import creates editable keyframes in the move. You can then preview in the 3D rig view, adjust the granularity and reimport if needed, and smooth curves in the Cartesian Graphics view.
Why Mimic import fails: The Mimic system in Flair records the current positions of the hardware axes in real time — it is designed for physically operating the robot and capturing those movements. The Mimic import path does not read external CSV data. Sending a CSV through the Mimic path results in a blank recording because no hardware position data is coming in.
Dan Gottesman: "Try to be mindful to hit the 'home' icon on the app right before you start your move, to zero it. Once you've gotten the file to your computer, put the camera in the general area where you'd like the move to start. Then, set the granularity to like 10 or 15 or so. Then, switch the import settings to translate to the current camera and rotate to camera (set to 'yes')."
confidence_score: 0.91
[INFORMATIONAL] Mimic + Smoothing As a Post-Import Option¶
2022-10-22 — Timothy Heys Cerchio
Once a Tracker CSV has been correctly imported as keyframes via CGI import, it is possible to then use the Mimic system's Smoothing tools on the resulting Cartesian Graphics curves — but this is a post-import step, not the initial import method. Import as keyframes first, then optionally apply smoothing.
Timothy Heys Cerchio: "When you import as Mimic you lose your waypoints...but then you can apply some Smoothing on the Cartesian Graphics curves."
Note: this quotation describes a workflow where the operator chose Mimic import — but Timothy's workaround is importing first as keyframes, then optionally applying smoothing in Cartesian Graphics.
confidence_score: 0.85
WhatsApp Excerpts¶
[13/12/2021] ~ .: Need help to import a files from mrmc tracker. But not get good rig
[13/12/2021] Peter Constan-Tatos: Ebek where did you zero the tracker? It's best to put bolt into home position and hold the phone at the camera nodal when you zero it (using the house button on the tracker).
[13/12/2021] Dan Gottesman: try to be mindful to hit the "home" icon on the app right before you start your move, to zero it. once you've gotten the file to your computer, put the camera in the general area where you'd like the move to start. then, set the granularity to like 10 or 15 or so. then, switch the import settings to translate to the current camera and rotate to camera (set to "yes").
[13/12/2021] Jeremy Andrews: Sorry - just realised the problem. Your move is starting near the xyz origin (under the robot). Before you import the move, put the robot in the normal home position. Then import your move 'translate to current - camera'
Related Issues¶
- See also: Tracker App Import: Robot Move Completely Wrong — Zero at Home
- See also: Tracker App: Reducing Shakiness and Jitter
- See also: Tracker App: FPS Mismatch — 60fps Recording
- See also: Tracker App: Live Control — Recording Moves via Flair 7 Mimic Window