Skip to content

LED Volume — Unreal PC Must Be on Different Subnet from Robot; Secondary IP Assignment

Summary

On LED volume sets, the Unreal Engine PC is typically on the same LAN as the LED wall processor and other production gear — often on a subnet like 192.168.2.x or 10.0.0.x. The Flair robot network is on a different subnet (commonly 192.168.1.x). To receive camera tracking data from Flair while remaining on the LED wall network, assign a secondary IP address to the Unreal PC's network adapter that matches the Flair tracking data subnet. The Unreal PC then has two IPs — one for the LED wall network, one for the Flair data — and can communicate with both without the robot's network traffic touching the LED wall network.

Community Guidance

[RESOLVED] Assign a Secondary IP to the Unreal PC's Network Adapter

Community consensus

Windows allows multiple IP addresses on a single network adapter. To add a secondary IP:

  1. Open Control Panel → Network and Internet → Network Connections.
  2. Right-click the Unreal PC's network adapter → Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
  4. Click Advanced.
  5. Under the IP Settings tab, click Add under IP addresses.
  6. Enter an IP address on the Flair tracking subnet (e.g., 192.168.1.50 if Flair is at 192.168.1.x) and the appropriate subnet mask.
  7. Click OK to save.
  8. In Flair, set the output destination IP to this secondary address.
  9. The Unreal PC can now receive Flair tracking data while maintaining its primary LED wall network connection.

confidence_score: 0.92

[RESOLVED] Flair PC Also Needs a Secondary NIC for Rendering Network

Community

For the reverse direction (Flair PC talking to the Unreal PC on the rendering network), the Flair PC itself may need a secondary NIC or secondary IP address configured for the rendering subnet. The primary NIC stays on the InTime/EtherCAT network; the secondary connects to the LED wall production LAN.

See CRITICAL: Unreal Network Broadcast Traffic Warning — the secondary NIC on the Flair PC must be firewall-isolated so that rendering network broadcast traffic cannot reach the InTime side.

confidence_score: 0.90

[INFORMATIONAL] Reserved IP Ranges — Avoid Conflicts

Community — see NET-ip-reserved-addresses.md

Flair's InTime network uses specific IP ranges for its hardware nodes. Ensure the secondary IP address assigned to the Unreal PC does not fall within the reserved InTime/robot address range. Typical safe addresses for the secondary IP are in the upper range of the subnet (e.g., .50–.99) away from hardware node addresses.

confidence_score: 0.88