Sync With Other Flairs / Multi API Controller - Browsing Multiple Robots¶
Summary¶
Sync with other Flairs, Multi API, and QuadFlairApi.exe are used to browse or coordinate multiple Flair systems from a normal Windows network. This is separate from the InTime robot network. Operators report it can browse multiple rigs together, but browsing may be uneven, speed-mismatched, or "holterdipolter", and the API connection is not the preferred method for frame-accurate shooting.
Symptoms / Questions¶
- Operator wants to browse two robots together.
- Operator asks if there is a means of programming two moves on two robots and browsing them together from one Flair instance.
- Operator uses
sync with other Flairswith a Bolt and Cinebot but the Cinebot browses much faster. - HHB speed is the same, but different robot types browse at different speeds.
- Operator asks whether Multi Flair API Controller can control up to 4 Flair systems.
- Operator asks whether
API Masterworks or whether to useQuadFlairApi.exe. - Operator needs multiple systems visible on the same time scale during setup.
Settings Location¶
| Task | Location |
|---|---|
| Multi-Flair API tool | API folder, QuadFlairApi.exe |
| API network | Normal Windows TCP/IP network, not InTime |
| Two-PC direct link | Secondary NIC / USB NIC on each PC |
| Browse speed / damping | Multi API controller settings |
| Bolt real-time browsing workaround | *FastBypass in supported Classic versions, used with caution |
Community Solutions¶
[CONFIRMED] Use A Windows-Level Network, Not InTime¶
The Multi API connection runs over a normal Windows TCP/IP network. Use a secondary Ethernet port or inexpensive USB NICs. Do not join or repurpose the InTime robot network for API browsing.
Confidence: 0.84
[LIKELY] Use QuadFlairApi.exe For Up To Four Flairs¶
Operators referenced the Multi Flair API Controller and QuadFlairApi.exe for controlling or browsing up to four Flair systems. Heiko reported that QuadFlairApi.exe in the API folder was the tool he would use; API Master did not work for him when tried.
Confidence: 0.72
[LIKELY] Expect Browse-Speed Differences Between Robot Types¶
When browsing a Bolt and Cinebot together, the Cinebot may browse much faster because it tends to browse closer to full speed while the Bolt is slower. This may require workarounds and careful testing.
Confidence: 0.70
[FIELD GUIDANCE] Use Hardware Trigger For The Actual Shoot¶
The API connection can be useful for browsing and setup, but multiple operators advised using wired RT-14 input/output triggers for the real shoot because API control is not frame accurate.
Confidence: 0.80
[CAUTION] FastBypass Can Help Bolt Browsing But Requires Care¶
Dan noted that in Classic 7.29, *FastBypass can enable the safety bypass button in the control menu and allow a Bolt to browse in real time. This is a safety-sensitive feature and should be used carefully.
Confidence: 0.66
Evidence¶
| Timestamp | User | Evidence |
|---|---|---|
| 2021-08-17 | Josh / Simon / Dan | Each robot needs its own Flair system; API can browse robots together; API is Windows network, not InTime; USB NICs suggested. |
| 2025-06-25 | Niko | Multi Flair API Controller mentioned as an option, possibly up to 4 Flair systems from a master. |
| 2025-06-25 | Mike / Julian | sync with other Flairs with Bolt + Cinebot caused Cinebot to browse much faster; framerate factor workaround mentioned. |
| 2025-06-25 | Dan Gottesman | RT-14 triggers are most accurate/consistent; Multi API can work but with inconsistent latency; wired PC connection helps. |
| 2025-06-26 | Heiko Matting | Multi-Flair API works, browsing together can be uneven, damping and browse speed can help, sync button can realign, QuadFlairApi.exe in API folder recommended. |
WhatsApp Excerpts¶
- 2021-08-17 04:43 - Riley Morgan: I thought there was a means of programming two moves on two robots and browsing them together from one flair instance.
- 2021-08-17 04:45 - Josh T.: Each robot needs its own individual flair system. You can then use the Flair API to browse the two Robots together.
- 2021-08-17 04:47 - Simon Wakley: The multi api controller lets you browse the 2 systems together. It's NOT connected to the Intime network it's a standard windows network connection.
- 2021-08-17 05:13 - Dan Gottesman: best bet is to get some inexpensive USB NICs, and create a simple TCP/IP network between the two machines.
- 2025-06-25 17:11 - Niko: You have an option that is the Multi Flair API Controller.
- 2025-06-25 17:12 - Niko: if I'm not wrong you can control up to 4 Flair systems from a "master" one.
- 2025-06-25 20:33 - Mike Greenberg: For "sync with other Flairs"- If running a Bolt and a Cinebot together, when browsing the Cinebot always browses much faster, even when HHB speed is the same.
- 2025-06-25 21:18 - Dan Gottesman: the Multi API controller will also work, but there can be some inconsistent latency between the rigs. using a wired connection directly from one PC to the other should minimize that.
- 2025-06-26 02:40 - Heiko Matting: The Multi- Flair API Connection works great, but browsing together is a bit holterdipolter.
- 2025-06-26 02:40 - Heiko Matting: I would use the QuadFlairApi.exe, which is in the API folder (for up to 4 Flairs).
- 2025-06-26 02:40 - Heiko Matting: For the shoot I would use a wired trigger as well, since the API connection isn't frame accurate.