Skip to main content
Top

Trackman is not triggering Swing Catalyst technical troubleshooting

Stian Eklund
  • Updated

Trackman connectivity issues troubleshooting guide.

You're having the following problem:

Trackman is connected and displays data in TPS but Swing Catalyst isn't triggered and no data is present within Swing Catalyst.

  1. Reboot the Trackman unit itself.
  2. Check if you are receiving data in TPS, if not double check the calibration.
  3. Verify that "Enable SDK Output" / "Legacy SDK" is enabled in TPS Settings.

 

In Swing Catalyst 9.7.8 and 9.7.9 this issue has been improved further. If you have followed these instructions without luck making sure that you are running 9.7.9 or newer can help mitigate the delay.

 

Swing Catalyst Launch Monitor delay compensation

If you are getting data but Swing Catalyst is not triggering a recording, try changing the "Trigger delay" value to 1400.

2021-11-25_14-21-29.png

 

 

Trackman 3e

You can also check if "legacy SDK" is enabled from the device's web interface. You can go to the web interface from TPS Settings, force operator and check under Setup.

If SDK output is set in TPS and on device and you're still not getting data, try to connect to the unit or SDK with a tool called Hercules.

 

Monitor the output from the unit / TPS software:

  1. Make sure TPS is running and receiving data from the unit.
  2. Download and run Hercules.
  3. Navigate to the TCP Client tab.
  4. Enter the IP and port below and click connect.

WiFi & USB IP Addresses

Trackman 4

  • Ethernet: Not supported.
  • USB address 169.254.0.1 port: 52950
  • WiFi address 172.30.20.1 port: 52950

Trackman 3e:

  • USB address 169.254.0.1 port: 52950
  • WiFi address 172.30.20.1 port: 52950

Trackman 2:

  • Connect directly to the TPS SDK server on 127.0.0.1 port: 52950

If connected properly in Hercules you should see the following output when you hit the connect button.

gvim_2018-08-01_13-41-00.png

If you do not, then try restarting the Trackman device itself, the Trackman Legacy SDK is not outputting data.

If you're able to connect you should receive data as well as shot data as soon as a shot is tracked. 

This is the same data Swing Catalyst receives, and is a good way of making sure that TPS and the Trackman is in fact sending data.

If you're unable to connect, check the firewall, if connected over WiFi the Trackman can be identified as a public network which could be an issue with certain firewalls; try turning the firewall off for public networks and check again, do you now get data? If so, make sure TPS and Swing / Motion Catalyst is allowed in the Windows Firewall.

 

Check Swing Catalyst's log file:

C:\ProgramData\Swing Catalyst\logs\log.txt

If you see the following message in the log, the TrackMan OEM Service is running, and needs to be disabled.

LaunchMonitorNetworkClientBase.OnTryConnectCompleted(): Successfully connected to [Trackman] on [127.0.0.1:8000].

 

Related articles