Test the device, its own application and the simulator connection as separate stages so you can find where shot data stops.
Prove one link at a time
A device shown as “connected” has not necessarily completed every step needed to send a shot into a course application. Work through three stages: device readiness → a shot in the manufacturer’s application → the same shot reaching the simulator.
If the manufacturer’s own application never records the shot, begin with Launch monitor not reading shots. Reinstalling a course application will not fix a misplaced ball or a blocked sensor.
Establish the supported combination
Write down the hardware model, firmware, device application, simulator application and any required connector or subscription. Confirm the combination in the manufacturers’ current compatibility guidance. Similar models can have different software access or connection requirements.
Do not assume a successful connection described for one Uneekor, Trackman, Voice Caddie or other device applies to every product from that brand. The catalog’s hardware package and the purchased software entitlement both matter.
Run a clean connection test
- Start the device using its normal connection method and wait for its ready state.
- Open its supported device application and capture a straightforward test shot in a safely assembled bay.
- Record whether the shot appears and whether the expected measurements are present.
- Follow the documented launch order for the supported connector and simulator. Some integrations need another application running; others have different requirements.
- Select the exact tracking system where the simulator asks for one. Start a practice session and compare with the device application.
- Change one setting at a time. Record the original value so you can restore it.
Interpret the result
| Test result | Where to investigate |
|---|---|
| Device is not ready | Power, placement, calibration and the model’s connection steps. |
| Device range reads; course application does not | Supported integration, entitlement, application selection and connector status. |
| First shot arrives, later shots stop | Readiness after each shot, connection stability and any repeating error. |
| Shots arrive but numbers differ | Units, selected club, environmental settings and whether the applications show the same metric. |
Carry distance and total distance are not interchangeable. Likewise, an estimated field in one application should not be compared as if it were a directly measured field in another.
Resolve security prompts narrowly
Use the publisher’s documented application-specific network permissions. Do not disable the computer’s firewall or security software as a general troubleshooting method. If an update preceded the problem, record the versions and exact error before changing the working configuration further.
Send support the result of each stage. “Reads in the device range, but not in the course application” immediately narrows the investigation.
Related guides
Need a hand?
Tell us your model and what is happening. Include a photo if it helps, or your order number for a delivery question.