Skip to content

title: "Dragonframe Cannot Connect Over InTime Network — Requires Secondary NIC" category: Networking / InTime issue_status: RESOLVED hardware: All rigs (InTime-based) software: BOTH first_seen: 2021-01-01 date: 2021-01-01 search: boost: 0.8

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

  1. Install a second NIC on the Flair PC that is NOT assigned to InTime.
  2. On a tower PC: a USB network adapter or a second PCIe NIC.
  3. On a laptop: a USB-to-Ethernet adapter.
  4. Connect the Dragonframe computer to this second NIC via a direct cable or a separate switch.
  5. Assign IP addresses on a different subnet (e.g., 192.168.2.xxx) for this secondary connection.
  6. 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.

Dragonframe Connection Field Guide

The following steps were documented in a shared field guide ("HOW TO CONNECT to dragonframe.docx", posted by community member 2022-05-05). They expand on the basic secondary-NIC setup with exact INI keys and Scene settings.

INI Keys Required in the Flair INI File

Add these keys to the relevant section of the Flair INI file. Do not use the InTime port or robot-hub port.

*Dragon: TRUE
*Api: TCP
*ApiPort: 53025
*ApiAutoAccept: True
  • *Dragon: TRUE enables the Dragonframe interface in Flair.
  • *Api: TCP — must be TCP. Do not use UDP or COM port.
  • *ApiPort: 53025 — the Dragonframe API port. This is separate from the InTime port and the robot hub port.
  • *ApiAutoAccept: True — Flair will accept the Dragonframe connection without a manual prompt.

Dragonframe Scene Settings

In Dragonframe: Scene → Connections → Flair Interface

  • Enter the IP address of the secondary NIC on the Flair PC (e.g., 192.168.2.100:53025).
  • Do not use the InTime NIC IP (192.168.1.10) — Dragonframe cannot communicate via InTime.

Additional Settings

  • Miscellaneous → Auto Run Short Go-Tos → Yes — prevents Dragonframe from stopping between frames on short robot moves.
  • Run Job → Run From Dragon — ensures Dragonframe controls the job run, not the Flair play button.
  • Flair and Dragonframe must share the same start frame and move length. If they are out of sync, the robot move will not align with the stop-motion capture.

Addressing Notes

  • Use static IP addresses on the secondary NIC, not DHCP. DHCP can change IPs between sessions, breaking the connection.
  • Avoid subnet mask 255.255.255.255 — use a standard /24 mask (255.255.255.0).
  • For same-PC testing (Dragonframe and Flair on the same machine), use 127.0.0.1 with the API port.

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

Official Documentation

Bolt Quick Start Guide — p.41–42: Appendix 2 Network Layout — INtime NIC vs Windows NIC

Flair Classic Manual — Ch.4 Flair Systems: Network Direct — p.30

Flair Classic Manual — Ch.22 Network Direct — p.313

Flair 7 Manual — Ch.4 Flair Systems: Network Direct — p.16

Flair 7 Manual — Ch.19 Network Direct — p.263