Multiple Robots / Multiple Flair Systems - Trigger, Timecode, and API Options¶
Summary¶
For dual-robot or multi-robot jobs, each robot normally needs its own individual Flair system. Do not connect the robot/InTime networks together as if one Flair instance will directly own both robots. The common field workflows are: use the camera robot as the primary system and send an output trigger to the input trigger of the secondary system; use split timecode for the strongest timing reference; or use the Multi / Quad Flair API controller on a normal Windows network for browsing and non-frame-critical control.
Symptoms / Questions¶
- Operator asks how to physically connect dual systems with a Bolt pedestal and Bolt X track.
- Operator asks whether to connect Ethernet between the robot network switches.
- Operator expects to program two moves on two robots and browse them together from one Flair instance.
- Operator asks about
sync with other Flairs. - Operator asks how to start two Flair sequences in time.
- Operator asks whether the latest Flair has an input trigger to start the moco move.
- Operator wants one robot to trigger a second robot, model mover, or additional Flair system.
- Operator wants to control multiple Flairs with API Control.
Setup Options¶
| Method | Best for | Accuracy / caveat |
|---|---|---|
| Output trigger from primary robot to input trigger on secondary robot | Starting multiple robot moves consistently | Usually a few frames of consistent delay; use opto-isolation / noise protection |
| Split LTC timecode feed | Frame-aligned music, show, or multi-system timing | Strongest repeatable timing if all systems are configured correctly |
| Multi / Quad Flair API controller | Browsing multiple systems together, setup, non-frame-critical control | API latency can be inconsistent; not the preferred shoot trigger for frame-critical work |
| OSC / custom keypress bridge | Custom workflows when hardware trigger is unavailable | Experimental; predictable latency may be possible but must be tested |
Settings Location¶
| Task | Flair location |
|---|---|
| Hardware output trigger | Setups -> Outputs |
| Hardware input trigger / move input bit | Setups -> Inputs Setup and RT-14 / trigger-box input wiring |
| Timecode triggering | Setups -> Timecode Setup, Serial Devices Setup, Inputs Setup |
| API browsing / Multi API | Flair API tools / QuadFlairApi.exe in API folder |
| Normal Windows network for API | Secondary NIC / USB NIC / standard TCP/IP network, not InTime |
Community Solutions¶
[CONFIRMED] Each Robot Needs Its Own Flair System¶
Experienced operators stated that each robot needs its own individual Flair system. The systems can then be coordinated by triggers, timecode, or API, but one Flair instance does not simply own two independent robots over the InTime network.
Confidence: 0.88
[CONFIRMED] Do Not Join The InTime Networks For API Browsing¶
The API / Multi API connection uses a standard Windows-level network connection, not the robot/InTime network. Operators suggested inexpensive USB NICs and a simple TCP/IP network between machines.
Confidence: 0.84
[CONFIRMED] Use Output Trigger To Input Trigger For Reliable Multi-Robot Starts¶
For production runs, the common approach is to set the camera robot as the primary system and wire an output trigger to the input trigger of the secondary robot or additional systems. Dan described this as reliable and consistent, usually with a slight delay of a few frames.
Confidence: 0.84
[LIKELY] Use Split Timecode For Stronger Frame Alignment¶
Simon noted that a split timecode feed is another way to trigger one or more Flair systems. Use this when frame timing matters more than simple start coordination.
Confidence: 0.76
[LIKELY] Use API For Browsing, Not Frame-Critical Shooting¶
The Multi / Quad Flair API controller can browse systems together, but operators still preferred wired triggers for the actual shoot because API control is not guaranteed frame accurate.
Confidence: 0.78
Evidence¶
| Timestamp | User | Evidence |
|---|---|---|
| 2021-08-17 | Riley / Simon / Josh / Dan | Dual-system physical connection discussed; no InTime link between robot systems; each robot needs its own Flair system; API uses normal Windows network. |
| 2021-10-25 | Peter / Dan / Simon | Input trigger can start a move through RT-14 + trigger box; output of one rig can wire to input of another; Multi API and split timecode are alternatives. |
| 2025-06-25 | Niko / Dan / Heiko / Simon | Multi Flair API controller / QuadFlairApi discussed; RT-14 input/output trigger was considered most accurate and consistent; API browsing works but not frame accurate. |
| 2025-07-03 | Marc Srour | Custom OSC bridge from master Flair run-state output to slave Flair keypress described as a predictable-latency workaround. |
| 2025-12-17 | Dan Gottesman | For more than one robot, camera robot is generally primary and sends output trigger to input trigger of secondary and additional systems; delay around 4-5 frames, reliable and consistent. |
WhatsApp Excerpts¶
- 2021-08-17 04:20 - Riley Morgan: I'm looking to run dual systems with a Bolt ped & boltx track, I haven't done this before and can't find much info on dual systems.
- 2021-08-17 04:39 - Simon Wakley: No connection between the systems other than trigger cable and maybe linked estops.
- 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: It's a network connection at windows level. 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. If it's just the two, you don't even need a switch.
- 2021-10-25 10:49 - Dan Gottesman: You can use an input trigger to start a move directly through the RT-14 + triggers box.
- 2021-10-25 10:49 - Dan Gottesman: Just wire the output of one rig to the input of the other, then set the "move input bit" to whichever input you're using.
- 2021-10-25 13:23 - Simon Wakley: You can trigger one Flair from another either using the input output triggers or using the Multi Api. Just can't be absolutely sure about frame accurate. You could use a split timecode feed.
- 2025-06-25 21:18 - Dan Gottesman: the most accurate / consistent way (IMHO) is to use the RT-14 with input & output triggers on both rigs. typically the delay is a few frames, which is very consistent.
- 2025-12-17 22:37 - Dan Gottesman: sometimes we'll use more than one robot on a job, so we'll generally use the camera robot as the primary system, which will send an output trigger to the input trigger of the secondary (and any additional) system.