Skip to content

Cinebot Mini/Max/Nano — Adding Genlock and LTC via RT-14 Box

Summary

Cinebot Mini, Cinebot Max, and the Nanobot ship with an Ethernet Trigger Box as standard — not an RT-14. The Ethernet Trigger Box handles camera start/stop triggers but does not provide genlock video input or LTC timecode input. To add these capabilities (required for LED volume virtual production, genlock sync to a camera, or timecode-triggered moves), a spare RT-14 from another robot can be connected to the Cinebot network. Tom D confirmed RT-14 integration on Cinebot Mini/Max in May 2025. Peter Constan-Tatos confirmed it on Nanobot in May 2026.

Community Guidance

[RESOLVED] RT-14 Integration — What It Adds to Cinebot

Community — Tom D — May 2025

Tom D: "For anyone with a new Cinebot Mini or Max — I was able to plug in our spare RT-14 box successfully, which therefore enables the Cinebot to trigger from LTC timecode, as well as sync to genlock from a Sony or Blackmagic etc camera. (For those that don't have a Cinebot, LTC trigger and standard genlock is not possible with the standard kit.)"

What the RT-14 adds: - LTC timecode input — trigger moves from timecode (not available on Ethernet Trigger Box). - Genlock video input — lock Flair to an external sync generator or camera genlock signal. - Consolidated sync source for LED volume: Flair + LED processor + camera all genlocked from one device.

confidence_score: 0.88

[RESOLVED] Configuration — External Camera Setup Source

Community — Peter Constan-Tatos, Tom D — May 2026

When connecting an RT-14 to a Cinebot or Nanobot, the External Camera Setup source must be changed from its default:

Peter Constan-Tatos (after connecting RT-14 to Nanobot): "Ok so I had to reload network board 1 (the Nano's quad). Otherwise it works. I think the problem may have been the ext cam setup/sync/source was set to network and not rt14."

Steps:

  1. Connect the RT-14 to the Cinebot network (ensure it has a unique IP address — not conflicting with the Ethernet Trigger Box).
  2. In Flair, go to External Camera Setup → Sync → Source and change from Network to RT14.
  3. If the RT-14 doesn't appear, reload network board 1 (the Cinebot's quad node) via the Network Setup dialog.
  4. Verify genlock or LTC is being received in the External Camera Setup window.

confidence_score: 0.88

[RESOLVED] IP Address Conflict — RT-14 vs Ethernet Trigger Box

Community — Tom D — May 2026

Tom D: "You'll want to make sure the RT-14 is not sharing an IP address with the other hardware that would otherwise be driving sync or bloop light etc (like the Ethernet Trigger Box, for example)."

Both the RT-14 and the Ethernet Trigger Box sit on the InTime network. Assign them different IP addresses before connecting. Check the InTime network layout and the existing Cinebot IP schema before plugging in a spare RT-14 from another rig.

confidence_score: 0.88

[RESOLVED] RT-14 Serial Number — Timecode Connector Location Varies

Community — Dig, Tom D — May 2025

RT-14 units vary by serial number (series 2/3 vs series 4/5). The LTC timecode input connector location differs:

Dig: "Look for the label on the rear of the RT14 with 1188-[number]. If your RT14 is series 2 or 3, then you'll need to connect to the red RCA connector. If you have a series 4 or 5 then connect to the black side."

Tom D: "Also be aware that the old RT-14 and the 'new' RT-14 switched which connector in the headphone jack received the LTC timecode — i.e. the new RT-14 receives the LTC on the tip of the headphone jack."

Check the series number before wiring LTC to your RT-14.

confidence_score: 0.85

[INFORMATIONAL] Standard Kit Comparison

Community — Timothy Heys Cerchio, Ben Myers — 2024

Feature Bolt / Milo (standard) Cinebot Mini/Max (standard)
Sync hardware RT-14 Ethernet Trigger Box
LTC timecode input Yes No
Genlock video input Yes No
Camera sync (shutter) Yes (via RT-14) Yes (shutter-based)
LED wall genlock Yes Requires RT-14 add-on

Ben Myers: "I have a Cinebot Mini with no RT-14, so I can only sync off the shutter."

Timothy Heys Cerchio: "This function would only be available through an external Genlock source or other camera reference through BNC or a dedicated Sync port — therefore not possible with Cinebot — for the lack of RT-14."

confidence_score: 0.88

[RESOLVED] Only One RIC Can Be Loaded — RT-14 and Ethernet Trigger Box Cannot Run Together on One Flair Instance

Community — Gordon Eschke, Simon Wakley, Ben Myers — July 2026

Both the RT-14 and the Ethernet Trigger Box register with Flair as a RIC (Remote I/O Controller), and Flair can only load one RIC at a time — this is a deeper limitation than the IP-conflict issue above, and applies even if the two devices are on different IP addresses.

Gordon Eschke: "Unfortunately you cannot use the RT-14 and the Ethernet trigger box together. Because as far as Flair is concerned they are both RIC's and you can't have 2 RIC's."

If you need genlock (via RT-14) and independent Ethernet-triggered triggers at the same time — for example, genlocking a camera while also firing a separate trigger box output — the confirmed workaround is to run two networked Flair instances on two PCs: one machine with the RT-14 handling the robot, camera, and genlock; a second machine with the Ethernet Trigger Box, triggered by the first with a small, fixed (non-genlock-synced) delay.

Ben Myers: "I have Ethernet triggers and RT-14 with my Cinebot mini. Have a network switch routed with a jumper cable so that if I want to use the triggers box, I just connect the jumper cable on one end which connects the triggers box to the switch and if I want to run the RT-14, I disconnect the jumper on one end and connect the RT-14 instead." (a single-machine jumper-swap alternative if you don't need both live simultaneously — see caveat below)

Simon Wakley: "If you used the rt14 for genlock and the ethernet triggers on the separate machine for triggers then in theory it will work. The triggers are usually not critical for frame accuracy depends what you are using them for... 2 robots genlocked will not necessarily be perfectly in sync as the core internal timings are not locked. Theoretically it could work but also there might be a frame difference between them."

Important: treat any claim that RT-14 and the Ethernet Trigger Box can be used together simultaneously on one Flair instance with suspicion — it directly contradicts this RIC limitation as explained by MRMC/Multidyne support. If you see this claimed elsewhere, the setup being described is very likely two separate Flair instances (as above), not one instance driving both.

confidence_score: 0.85

[CRITICAL] Universal Sync Box Safety Warning

Community — Jeremy Andrews, Dig — March 2026

Dig: "With a Milo (or any system running camera sync to the RT14) — if you connect the sync through the triggers box while the sync emulator is on, the additional voltage on that circuit will blow the universal sync box."

Do not connect the Universal Sync Box to the Ethernet Trigger Box simultaneously if the sync emulator is active. This applies to Cinebots as well as Bolts.

confidence_score: 0.90

Official Documentation