Symptom:
Because E6 Connect relies on hardware-locked licenses, your TruGolf account profile must be specifically matched to your hardware vendor:
Launch E6 Connect on your PC. If your profile needs a refresh to view the license, go to Settings > Info & Help > Simulator Binding, click Unbind, log back in, and select your active GPRO / XSwing Standard License from the available slots.
Once your license structure is correct, you can configure the data connection within the software interface:
Power on your XSwing simulator unit or embedded floor sensors.
Ensure that any standalone XSwing calibration, diagnostic tools, or native play apps running on your Windows computer are completely closed. If a native diagnostic viewer has control over the system's data pipeline, E6 Connect will be locked out.
Launch E6 Connect and select Settings from the main dashboard interface.
Click on the Simulator tab.
Under the Tracking System dropdown menu, look for GPRO Xswing-G (or XSwing depending on your exact version path) and highlight it.
Click the Configure button immediately next to the dropdown selection.
Set Communication Port: Ensure your local communication port is mapped to the standard TruGolf data interface default, which is 2483. If your specific layout relies on an external hardware client bridge, make sure the IP targets your designated local host loopback address.
Click Accept. The status indicator box inside the menu should turn Green, confirming that the platform is reading your data.
If the connection indicator remains red or your swings register physically on the system but do not launch the ball inside the E6 virtual environment, you will need to tweak a couple of Windows security settings:
Windows Firewall Exceptions: Local cross-app transmissions are often flagged as potential security threats. Search your PC for "Allow an app through Windows Firewall" and make certain that E6Connect.exe has full checkmark allowances for Private networks.
Network Profile Check: If your computer is tied directly to the XSwing interface via an Ethernet cord or local network switch, check your Windows network properties. Ensure the connection profile is set to Private. If it states "Public," Windows will block incoming sensor data packets.