Dragonframe Cannot Connect Over InTime Network — Requires Secondary NIC¶
Networking / InTime Resolved All rigs (InTime-based)
Summary¶
Dragonframe stop-motion software can connect to Flair using the "Flair Interface" option, but it cannot communicate over the InTime network. InTime takes exclusive control of the NIC used for robot communication, and Dragonframe communicates via the standard Windows TCP/IP stack — which InTime's NIC is not part of.
A secondary network port (NIC) on the Flair PC that is not under InTime control is required to connect Dragonframe.
Symptoms¶
- Dragonframe Flair Interface configured with InTime IP (192.168.1.10) — no connection
- Dragonframe shows "no connection" or times out despite Flair running normally
- Robot operates correctly; only Dragonframe connectivity is the issue
Root Cause¶
InTime places the Hilscher cifX network card (or Ethernet adapter) into real-time mode, bypassing the Windows network stack entirely. Standard Windows applications — including Dragonframe — cannot communicate over an InTime-controlled NIC. Dragonframe uses Windows sockets (standard TCP/IP), which only work on NICs managed by Windows, not InTime.
Resolution¶
- Install a second NIC on the Flair PC that is NOT assigned to InTime.
- On a tower PC: a USB network adapter or a second PCIe NIC.
- On a laptop: a USB-to-Ethernet adapter.
- Connect the Dragonframe computer to this second NIC via a direct cable or a separate switch.
- Assign IP addresses on a different subnet (e.g., 192.168.2.xxx) for this secondary connection.
- In Dragonframe's connection settings, use the IP address on this secondary NIC/subnet.
Official MRMC documentation
MRMC Support pointed to this forum thread as the reference: Connecting Dragonframe to Flair - updated
OSC also affected
The same limitation applies to OSC and other non-InTime protocols: you cannot send OSC to 127.0.0.1 (localhost) or from Flair to another app on the same PC over the InTime NIC. A secondary NIC (or TouchDesigner as a bridge on the InTime subnet) is required for Flair → same-PC application communication.
WhatsApp Excerpts¶
"Dragonframe cannot connect over the InTime network. You will need to use a secondary network port that's not under InTime." — MRMC Support (2025-12-17)
"When trying to send OSC to 127.0.0.1 — no go. Wired up via switch to another PC just to get this shoot done, but I wonder if there is a way to set up Flair to communicate with its own Windows PC in External Devices." — Marc Srour (2025-07-29)
"Needs to be on same 192.168.x.x." — Tom D (2025-07-29)
See Also¶
- NET freed unreal setup — Similar InTime subnet restriction for FreeD/UE
- NET ip reserved addresses — IP assignment on InTime and secondary networks