Chapter: Networking and InTime¶
Overview¶
Almost every MRMC motion control rig running Flair on Windows depends on InTime — a real-time OS extension from TenAsys that runs inside Windows and provides the deterministic timing required for robot motion control. Understanding how InTime works, what can break it, and how the network is structured is essential for diagnosing the most common category of field failures.
The Flair Bridge (introduced late 2025) replaces InTime for many rigs, but the majority of rigs in the field still use InTime as of 2026.
The InTime Network¶
What InTime Does¶
InTime places one network card (the Hilscher cifX card for EtherCAT-based Bolts, or a compatible Ethernet NIC for Ethernet-based robots) into real-time control mode. This NIC is taken out of the Windows networking stack entirely — Windows cannot see it, cannot route traffic over it, and cannot send or receive standard TCP/IP packets through it.
Any application that wants to communicate over the InTime-controlled NIC must go through InTime, not Windows. Applications using the standard Windows network stack (Dragonframe, OSC to localhost, web browsers) cannot use the InTime NIC and require a second, Windows-managed NIC.
Network Topology¶
[Flair PC]
└── cifX card (InTime NIC)
└── InTime switch
├── RT14 (192.168.1.234)
├── Ultiboard (192.168.1.236)
├── QuadBox / UltiBox
├── Ethernet Trigger Box (Cinebot RIC node)
└── VP machine (e.g. 192.168.1.99)
Reserved IP Addresses¶
| Device | IP | Notes |
|---|---|---|
| InTime | 192.168.1.10 | Fixed — do not change |
| RT14 | 192.168.1.234 | Fixed |
| Ultiboard | 192.168.1.236 | Fixed |
| Hyperdeck | 192.168.1.50 or .150 | Configurable via front panel |
| Reserved by MRMC | 192.168.1.20 | Do not use |
Never change the 192.168.1.xxx subnet range.
See: Reserved IP Addresses and Conflict Troubleshooting
InTime Startup Sequence¶
Order matters. Deviating from this sequence is the #1 cause of "robot not found" calls.
- Power on the robot controller (CS8 or equivalent). Wait 3–5 minutes for full boot.
- CS8 display shows
A(ready) or8(E-stop) when boot complete. - Boot the Flair PC. Let Windows reach the desktop fully.
- Wait for the InTime icon in the taskbar to be coloured (not grey).
- EtherCAT systems: wait for 2 green lights on the cifX card.
- Open Flair only after both above steps are confirmed.
See: InTime Not Starting or Robot Not Found After Boot
Transport / Vibration False Contacts¶
If a network, EtherCAT, node, or engagement fault appears immediately after transport, rolling a controller case, or a violent move, check physical connectors before assuming a software problem. The WhatsApp archive contains repeated field reports of internal CS8 cards, robot fibre links, amplifier connectors, Ethernet cables, axis-box headers, and sync-box connectors working loose from vibration or transport.
See: Transport Vibration / Rolling Cases Rattle Internal Connectors Loose
InTime Dongle and Licensing¶
The InTime licence is tied to the Windows OS installation, not just the USB dongle. Both the dongle and the OS drive must move together when swapping PCs. Plugging the dongle into a different PC without the matching OS produces a licence failure.
If only the dongle stops responding: try a different USB port first.
See: InTime Dongle Is Licensed to the OS Drive
The Flair Bridge (Replaces InTime)¶
Announced November 2025, shipping with Cinebot Nano first and rolling out to other rigs. The Flair Bridge is a small hardware device that:
- Runs robot real-time control internally (no InTime, no cifX card needed)
- Connects to the Flair PC via standard Ethernet
- Supports Mac, Windows, and Linux
- Requires no special BIOS settings or OS-level driver installation
- Eliminates all InTime-related issues (Windows Update, CMOS battery, version mismatches, dongle binding)
Flair Classic supported (EtherCAT still in testing as of early 2026). Flair for macOS supported on M-series Macs.
Focus Timing Settings (NWD Buffer / Robot Delay / Position Delay)¶
Three settings compensate for timing lag between robot motion and lens/accessory control:
| Setting | Location | Purpose |
|---|---|---|
| NWD buffer | Network Setup | Synchronises focus data across network |
| Robot Delay | Miscellaneous Setup | Compensates EtherCAT vs Ethernet comms lag (~4ms) |
| Position Delay | Miscellaneous Setup | Corrects Bolt X / Yaskawa controller processing delay |
Where to enter them:
| Value | Flair location |
|---|---|
| NWD / Network Buffer | Setups -> Network Setup |
| Robot Delay | Setups -> Miscellaneous Setup |
| Position Delay | Setups -> Miscellaneous Setup |
Reported MRMC/community values:
| Robot / Use case | NWD Buffer | Position Delay | Robot Delay | Notes |
|---|---|---|---|---|
| Bolt (EtherCAT/Staubli) + MRMC Focus/Zoom motors | 1 | 0 | 0.7 | Official relation quoted for focus/zoom timing |
| Bolt (EtherCAT/Staubli), older timing note | 1 | 0 | ~50 ticks / ~4ms | Earlier comms-lag reference; verify units/version |
| Bolt X (Yaskawa) | 4–6 | ~3 | As required | Position Delay is the correct setting now (not NWD buffer) |
| Bolt Jr+ (Mitsubishi) | 4–6 | As required | As required | Same principle as Bolt X |
See: NWD Buffer, Robot Delay, and Position Delay
FreeD / OSC to Virtual Production Software¶
Flair sends camera position data (FreeD over UDP) to Unreal Engine, Aximmetry, Disguise, and similar VP systems.
Critical requirement: the receiving machine must be on the 192.168.1.xxx subnet (connected to the InTime switch). FreeD data exits via the InTime NIC.
Setup in Flair:
Setups -> External Devices -> Data Output -> FreeD -> UDP
IP: [VP machine, 192.168.1.xxx]
Port: 55535
In Unreal Engine: set listening address to 0.0.0.0 (not the Flair PC's IP). Disable Windows Firewall on the VP machine. Use a wired connection.
If the VP machine cannot use 192.168.1.xxx: use TouchDesigner as a bridge (FreeD In CHOP → FreeD Out CHOP).
VP broadcast traffic can cause robot dropouts
Unreal Engine and Disguise generate significant UDP broadcast traffic. On an unmanaged switch, this can saturate the InTime network and cause robot disconnections. Use a managed switch with broadcast storm control when VP equipment shares the InTime switch.
See: FreeD / OSC Data to Unreal / Aximmetry — Setup and Pitfalls
Windows and InTime — Common Failure Modes¶
Windows Updates¶
Windows updates regularly break InTime. Keep the Flair PC offline and disable Windows Update (use ShutUp10). A PC left on a facility network can receive pushed updates silently.
See: Windows Updates Break InTime
Windows 11 Compatibility¶
Newer Windows 11 builds require InTime 7. Flair 7.5 requires at minimum InTime 6.4.
See: Windows 11 and Flair 7.5 Require InTime 6.4+ / 7
Windows Smart App Control (Flair 7 Only)¶
Windows SAC blocks filmbox.dll and libcurl.dll after an update, preventing Flair 7 from starting. Classic is unaffected. Fix: disable SAC in Windows Security.
See: Windows Smart App Control Blocks Flair 7
Flair Bridge / Mac Routing¶
When using Flair Bridge on macOS, keep Wi-Fi disabled while connecting and running unless explicitly needed. Simultaneous Wi-Fi and robot Ethernet can create routing problems.
See: Flair Bridge On Mac - Wi-Fi / Routing Node Dropouts
BIOS CMOS Battery¶
A dead CMOS battery resets BIOS to defaults. If this changes UEFI/Legacy mode, Windows will not boot. Replace the CR2032 battery annually on all Flair PCs.
See: BIOS CMOS Battery Death Resets InTime Configuration
Applications That Cannot Use the InTime Network¶
| Application | Workaround |
|---|---|
| Dragonframe | Secondary NIC not under InTime |
| OSC to localhost (127.0.0.1) | Secondary NIC or TouchDesigner bridge |
| Standard web/TCP apps | Secondary NIC |
See: Dragonframe Requires Secondary NIC
Dragonframe stepper speed values also need translation through real axis scaling before they can be used as Flair axis velocity/acceleration values.
See: Dragonframe Stepper Speed To Flair Axis Velocity / Acceleration
Running Flair Without a Robot (Offline Mode)¶
Comment out these lines in flair.ini:
See: Running Flair Without Hardware (Offline Mode)
Issue Index¶
Official Documentation References¶
| Document | Notes |
|---|---|
| InTime Product Guide (TenAsys) | InTime installation, licensing, node management |
| Flair INI Setup Guide | flair.ini parameters including InTime, RemoteRobot, NetworkDirect |
| Flair Bridge Setup Guide | New bridge device — replaces InTime |
| MRMC Forum: Reserved IP Addresses | talk.mrmoco.com/t/reserved-ip-addresses-for-flair-robots-accessories/1379 |
| MRMC Forum: InTime Node A Disappears (Win11) | talk.mrmoco.com/t/intime-nodea-disappears-in-windows-11/1827 |
| MRMC Forum: Connecting Dragonframe to Flair | talk.mrmoco.com/t/connecting-dragonframe-to-flair-updated/145 |