InTime Network — Reserved IP Addresses and Conflict Troubleshooting¶
Networking / InTime Resolved All rigs
Summary¶
The InTime robot control network always uses the 192.168.1.xxx subnet. Every device on this network has a fixed or semi-fixed IP address. Assigning a conflicting IP to any device — including a VP wall, external laptop, or new accessory — causes network failures that can appear as random robot disconnections, axis trip faults, or devices simply not being found.
Never change the InTime subnet range.
Symptoms of IP Conflict¶
- Robot disconnects randomly during a move
- Device (Ultiboard, QuadBox, Ethernet Trigger Box) appears in Network Setup but is unreliable
- EtherCAT faults that appear intermittently and resolve on reboot
- VP wall connected to the network causes robot dropouts
Reserved / Standard IP Addresses¶
| Device | IP Address | Notes |
|---|---|---|
| InTime (host PC) | 192.168.1.10 | Fixed; do not change |
| RT14 controller | 192.168.1.234 | Fixed; do not change |
| Ultiboard | 192.168.1.236 | Fixed; do not change |
| QuadBox / UltiBox | Varies | Check Network Setup |
| Ethernet Trigger Box (Cinebot RIC) | Varies | Check Network Setup |
| Hyperdeck | 192.168.1.50 or .150 | Configurable via front panel |
| VP / UE machine (added by operator) | 192.168.1.99 recommended | Must not conflict with above |
| Do not use .20 | 192.168.1.20 | MRMC reserved |
Do not change the InTime network range
The 192.168.1.xxx range is hardcoded into InTime and all MRMC hardware. Changing it requires factory-level reconfiguration and will break all robot communication.
Root Cause¶
Two devices sharing the same IP cause ARP conflicts. The switch forwards packets to whichever device last announced itself, producing intermittent failures. VP walls and LED systems (Unreal, Disguise) sometimes use DHCP or default to addresses that conflict with MRMC-reserved IPs.
Resolution¶
- Before connecting any new device to the InTime switch, check its IP address and confirm it does not conflict with any reserved address.
- Set the new device to a static IP in the 192.168.1.xxx range (avoid .10, .20, .50, .150, .234, .236 and any IPs already in use).
- If using a VP wall, connect it to a separate switch with a port connection to the InTime switch, and verify broadcast storm control is active.
- If conflict is suspected, use
ping.rta(the InTime ping utility) to identify duplicate responses.
Standard Windows ping will not work
You cannot ping InTime network devices using the standard Windows command prompt. Use the InTime-specific ping.rta application. Devices not visible to standard ping may still be reachable via InTime.
WhatsApp Excerpts¶
"Standard IPs: .10 = InTime, .234 = RT14, .236 = Ultiboard — never change this range." — Community member (multiple threads)
"Don't use .20" — MRMC Support (2025-06-13)
"There can be IP conflict issues from VP walls on a different network address." — Dig (2025-06-28)
"If you can ping it, it's in the wrong network. It must be in the InTime network and the only way to ping it is using the InTime ping.rta app. It should be plugged into the same switch as the RT14." — Simon Wakley (2025-07-28)
"The Hyperdeck address is usually .50 (or maybe .150) — you can check or configure it via the front controls." — Simon Wakley (2025-07-28)
See Also¶
- NET freed unreal setup — VP/UE IP configuration on InTime network
- NET intime not starting — Startup failures that can mimic IP conflict symptoms