Skip to content

Tracker App Live Control — Complete Windows Setup

[FLAIR_7] [WINDOWS] This guide covers the complete process shown in 43A — Tracker App Setup (Windows): creating the INtime-to-Windows virtual network bridge, configuring a dedicated Wi-Fi access point, connecting the iPad or iPhone, and confirming that Flair receives live Tracker data.

Do not test Live Tracker with Flair 7.7.3

A community-confirmed bug in Flair 7.7.3 caused dangerously fast and erratic robot motion from very small iPad movements. Update to 7.7.10 or newer, keep the physical E-stop within reach, clear the robot envelope, and verify incoming values before enabling live motion.

Windows and INtime only

These bridge steps apply to a Windows Flair computer using INtime. Linux systems do not require the INtime-to-Windows bridge. Flair Bridge systems use their own network arrangement.

What You Need

  • A Windows Flair computer with INtime running.
  • A supported iPad or iPhone with the MRMC Tracker App.
  • A small dedicated Wi-Fi router or access point. Do not connect unrelated phones or computers to it.
  • One Ethernet cable long enough to reach from the access point to the Flair equipment switch.
  • Administrator access to Windows and the router configuration page.
  • Three unused addresses on the 192.168.1.xxx/24 network: one for INtime ven0, one for the Windows TenAsys adapter, and one for the router/access point.

The three boxes referred to in this guide

  • Access point: the small box that creates the Wi-Fi network for the iPad or iPhone. Some manufacturers call it a router or smart hub.
  • Flair equipment switch: the Ethernet box already used by real-time Flair equipment such as the RT-14, UltiBox, OctoBox, turntable, or robot network. This is also called the root network or INtime network.
  • Flair computer: the Windows PC running Flair. It can have several identical-looking Ethernet sockets with different jobs, so do not choose a socket by appearance alone.

If you only need to know where the cable goes, read Where Exactly to Plug In the Ethernet Cable before continuing.

What the IP addresses mean

An IP address is simply a device's number on the network. In this setup, every number must begin with 192.168.1, and the last number must be different for every device. The video uses the following examples:

Device/interface Example Purpose
INtime virtual Ethernet (ven0) 192.168.1.199 Real-time side of the bridge
TenAsys Virtual Ethernet Adapter 192.168.1.200 Windows side of the bridge
Wi-Fi router/access point 192.168.1.5 Router management and iOS gateway in the video
iPad 192.168.1.115 Example client address shown in the video
Subnet mask 255.255.255.0 Tells the devices that all 192.168.1.xxx addresses belong to this local network

Examples are not reservations

Confirm that every address is unused on your rig before assigning it. Two devices using the same address can stop parts of the robot network working. Community guidance often uses 192.168.1.1 for the access point, while the video uses .5. Do not copy either address blindly. If you do not know which addresses are free, stop and ask the person responsible for your Flair network. See Reserved IP Address Reference.

Network Layout

iPad / iPhone
     │ Wi-Fi
     ▼
Dedicated access point ─── Ethernet ─── Flair equipment switch
                                              │
                                  INtime ven0 (.199)
                                              │ bridge0
                              TenAsys adapter (.200)
                                              │
                                      Windows / Flair

Where Exactly to Plug In the Ethernet Cable

  1. On the access point, use the socket specified by its manufacturer for Access Point mode. This is usually labelled LAN. On some models, the WAN/Internet socket becomes the uplink in Access Point mode, so check that device's instructions if the sockets are unclear.
  2. Follow the existing robot-network cables to find the Flair equipment switch. It is the Ethernet switch already connected to equipment such as the RT-14, UltiBox, OctoBox, turntable, or other Flair-controlled hardware.
  3. Plug the other end of the cable into a spare socket on that switch.

Do not plug it into a socket just because it fits

Do not plug the access point into the Flair computer's ordinary office, studio, or internet Ethernet socket. Do not plug it into the EtherCAT socket or directly into the robot pedestal. Flair computers can have several identical-looking Ethernet sockets with different purposes.

If there is no spare socket on the Flair equipment switch, or you cannot identify the switch confidently, stop and ask your system technician or MRMC support. Do not unplug existing robot equipment to make room.

The reason for this cable location is simple: the iPad sends live control data through the access point, and that data must arrive on the same real-time network as the robot. A phone may still answer an ordinary network test, called a ping, when the cable is in the wrong place; that does not prove that Flair can receive its control data.

1. Create the Virtual Interface in INtime

Watch this section at 01:18

This step creates the INtime end of a software connection between the robot's real-time network and Windows. You are adding a virtual interface named ven0; you are not moving any physical cables.

  1. Close Flair if it is open.
  2. Confirm that INtime is running.
  3. Right-click the INtime system-tray icon and open INtime Configuration.
  4. Open Node Management, then select the Network tab.
  5. Under NIC configuration, write down the exact name of the existing physical interface. The official QSG shows rtl1g0, but your computer may show a different name. You will need this name in step 3.
  6. Edit the NIC list or click Add if ven0 does not exist.
  7. Select Virtual Ethernet (ven) as the NIC type.
  8. Assign the virtual interface an unused address. The documented example is:
IP address: 192.168.1.199
Subnet mask: 255.255.255.0
  1. Save the node configuration and allow INtime to restart when prompted.

2. Configure the Windows Side of the Bridge

Watch this section at 02:57

This step gives Windows its own end of the software connection. Look specifically for TenAsys Virtual Ethernet Adapter; do not alter the settings of another Ethernet adapter.

  1. Open Windows Network Connections.
  2. Find TenAsys Virtual Ethernet Adapter.
  3. Open its properties and select Internet Protocol Version 4 (TCP/IPv4).
  4. Choose Use the following IP address and enter an unused address on the same subnet:
IP address: 192.168.1.200
Subnet mask: 255.255.255.0
  1. Save and close the adapter properties.

The .199 and .200 values are the documented examples for the two ends of the same software bridge. They cannot be the same number, and neither number may already be used by another device.

3. Edit netuser.cfg

Watch this section at 03:32

This step tells INtime to join the virtual ven0 interface to the physical real-time network interface whose name you wrote down in step 1.

  1. Open Notepad as Administrator.
  2. Open:
C:\ProgramData\TenAsys\INtime\NodeA\etc\netuser.cfg
  1. If ProgramData is not visible, enable View → Hidden items in File Explorer. In Notepad’s Open dialog, select All files.
  2. Find the following three lines. If a line begins with #, remove only that leading # so the instruction becomes active:
ifconfig.rta -q bridge create
ifconfig.rta bridge0 addm ven0 addm rtl1g0 up
ifconfig.rta ven0 up
  1. Replace rtl1g0 with the physical INtime interface name recorded in step 1 if yours is different.
  2. Save the file and restart INtime Node A.

Do not guess the physical interface name

The QSG requires the actual interface name shown in INtime Node Management. Copying rtl1g0 when your computer shows another name will create a non-working bridge. If you did not record the name, return to step 1 rather than guessing.

4. Configure the Dedicated Wi-Fi Access Point

Watch this section at 05:09

This small box creates a private Wi-Fi network between the iPad and Flair. It should pass data onto the existing Flair equipment network, not create a second routed network.

  1. Before connecting it to Flair, connect a separate laptop directly to the access point if that is how its manufacturer says to configure it.
  2. In the laptop's browser, open the setup address printed on the access point or supplied in its instructions, then sign in.
  3. Set the device to Access Point mode, not normal router/NAT mode.
  4. Give the access point an unused static address in 192.168.1.xxx. The video uses 192.168.1.5; community guidance commonly uses .1.
  5. Set the subnet mask to 255.255.255.0.
  6. Configure the Wi-Fi network name and password.
  7. Apply the changes. Disconnect the setup laptop if required.
  8. Connect the access point to the Flair equipment switch by following Where Exactly to Plug In the Ethernet Cable.

Flair’s defaults are:

SSID: MocoWifi
Password: Moco1234

If you use another SSID or password, add or update these fields in the active Flair INI file:

*FlairSsid: <your SSID>
*FlairSsidPassword: <your password>

A successful ping is not sufficient proof

In a July 2024 community case, the phone answered a ping but Live Tracker still failed. The final fix was unplugging the access point from the assumed PC connection and plugging it into the Flair equipment switch on the root network.

5. Connect and Prepare the iPad or iPhone

Watch this section at 09:12

The iPad or iPhone must join the private Wi-Fi created by the access point, not the venue, office, or studio Wi-Fi.

  1. Join the dedicated Tracker Wi-Fi network.
  2. Open the network’s information panel in iOS.
  3. Turn off Private Wi-Fi Address for this dedicated control network.
  4. Turn off Limit IP Address Tracking.
  5. In the same information panel, find IP Address. Confirm that it begins with 192.168.1. Its final number must be different from the access point, .199, .200, and every other device.
  6. Open the Tracker App.

These privacy settings are shown disabled in the video. They prevent iOS from changing its network identity or trying to redirect this local connection through another privacy service.

6. Configure Tracker in Flair

Watch this section at 10:13

This step tells Flair where to receive the iPad's data, then uses a QR code to copy the matching settings into the Tracker App.

  1. Start Flair.
  2. Open Setups → External Devices.
  3. Under Data Input, select Tracker.
  4. Enter the iPad/iPhone IP address shown in iOS.
  5. Set the Tracker port to 55535, as specified by the official QSG.
  6. Save and apply the External Devices setup.
  7. Open SFX → Tracker → Connection.
  8. Check the displayed values. In plain language, they mean:
  9. Root IP: the INtime/root address used for Tracker control.
  10. Port: the Tracker data port.
  11. Flair 7 IP: the Windows side of the INtime bridge, such as .200.
  12. Wi-Fi: the SSID and password expected by Flair.
  13. In the Tracker App, open Settings → Network Settings → Read QR for network settings.
  14. Scan Flair’s Combined QR code to load the Wi-Fi, root/port, and live-view settings, or scan the appropriate individual QR code when the device is already connected.

Move the iPad gently without enabling robot motion. The numbers in Flair's Tracker window should change as the iPad moves. This proves that the data has reached Flair; it does not yet prove that moving the robot is safe.

7. Optional Camera Live View

This optional step shows the robot camera image in the Tracker App. Skip it until the Tracker values are working correctly. The INtime bridge allows the Windows-side Flair camera stream to reach the app.

In plain language, Serve RTSP Stream is Flair sending its live camera video out over the network to another device — in this case the Tracker App on the iPad/iPhone, so the operator can see what the camera sees on the handheld device as the rig moves, not just the numeric position data.

  1. Open the Flair Live View settings.
  2. Enable Serve RTSP Stream.
  3. Use the QR button beside the RTSP URL and scan it from the Tracker App’s Network Settings if it was not included in the Combined QR.
  4. If the video does not appear, clear and re-enable Serve RTSP Stream to refresh it.
YouTube 31 - Live View Display in Flair 7 & Focus Assist Flair 7

▶ 14:46 — Serve RTSP Stream explained: Flair sends its live camera video out over the network to another device, e.g. the Tracker App on an iPhone/iPad

8. Safe First Live-Control Test

  1. Confirm that Flair is not 7.7.3; use 7.7.10 or newer.
  2. Clear the robot’s full movement envelope and keep the E-stop in hand.
  3. Use the slowest available Tracker response mode for the first test.
  4. Confirm that incoming Tracker values change smoothly and proportionally before enabling motion.
  5. Begin with millimetres of device movement and be ready to stop immediately.
  6. Do not assume that a previously working setup remains safe after a Flair update; retest it in a clear area.

Troubleshooting Checklist

Flair receives no Tracker values

  • Confirm the Tracker input is selected under External Devices → Data Input, not another device type.
  • Confirm port 55535 and the current iPad address.
  • Confirm the access point is in Access Point mode.
  • Trace the access point cable with your hand and confirm that its other end is plugged into the Flair equipment switch used by the RT-14, UltiBox, OctoBox, turntable, or other robot-network equipment. Do not rely only on the socket label at the computer.
  • Allow every installed Flair.exe entry through Windows Defender Firewall on both Private and Public profiles.
  • Confirm SSID/password match the Flair INI values.
  • Confirm ven0, the TenAsys adapter, the access point, and iPad all use unique 192.168.1.xxx addresses.
  • Recheck the three uncommented netuser.cfg lines and the physical interface name.

QR code says it cannot connect to MocoWifi

  • Join the Wi-Fi network manually and confirm its SSID and password.
  • If using a custom network name, update *FlairSsid and *FlairSsidPassword.
  • Open the router’s IP in a browser to confirm the management page is reachable.
  • Restart the Tracker App after correcting the network. Community reports show an app restart can clear a stalled partial connection, though it is not a substitute for correct routing.

Connected, but the robot does not move

  • First verify that values change in SFX → Tracker.
  • Confirm the access point is plugged into the Flair equipment switch, not the computer's ordinary office/studio LAN socket.
  • Check Carts limits, the selected control mode, scale, and axis selection.
  • Treat stuttering, unexpectedly large movement, or non-proportional motion as unsafe: stop and verify the Flair version before continuing.

Linux or Flair Bridge system

  • Do not apply the Windows netuser.cfg procedure to Linux.
  • Community guidance says Linux does not need the INtime-to-Windows bridge, but the dedicated smart hub should still be on the same 192.168.1.xxx range.
  • Follow the relevant Flair Bridge or Linux network instructions for that system.

Evidence Added from the Transcript and Community Audit

The tutorial transcript is the only archived tutorial transcript containing the complete Windows bridge procedure. Other tutorial transcripts mention the Tracker App but do not add setup instructions. The full WhatsApp archive adds these field findings:

  • 11 November 2023 — Simon Wakley: Tracker must reach the root network for real-time data; either bridge Windows to INtime or provide wireless access on the INtime side.
  • 26 March 2024 — Gordon Eschke / Josh T.: verify the router dashboard by browsing to its IP; connect the Wi-Fi router by Ethernet to the INtime network; the iPad then joins that Wi-Fi.
  • 9 July 2024 — Gordon Eschke / Ben Myers: use access-point mode, allow Flair on both firewall profiles, verify SSID/password, and connect the access point to the root network. The root-network cable location was the final confirmed fix.
  • 4 September 2024 — Gordon Eschke: Linux does not require the INtime bridge, but a small hub on 192.168.1.xxx is still advisable.
  • 17 September 2024 — Gordon Eschke: an access point would normally use .1; a direct wired iPad connection has no router address. Restarting the app temporarily cleared one stalled connection.
  • 4 February 2026 — Marcin Biegunajtys: the procedure applies across robot types, not only the Cinebot shown in the tutorial.
  • 5 March 2026 — Mattm / Ben Myers: Flair 7.7.3 produced dangerously fast erratic live motion; update to 7.7.10 or newer.

Tutorial and Documentation

Sources: MRMC video tutorial 43A; Flair Tracker App Quick Start Guide MRMC-2278-00; Flair Community WhatsApp discussions dated 11 November 2023, 26 March 2024, 9 July 2024, 4 and 17 September 2024, 4 February 2026, and 5 March 2026.