Separate ball detection, shot capture and software delivery so you can test the right part of your setup.
Describe the failure precisely
“Not reading” can mean three different things: the device cannot see the ball, it sees the ball but does not record the strike, or it records the shot but the simulator does not receive it. Start with the manufacturer’s own practice or diagnostic application when your model provides one. This separates hardware capture from the connection to third-party course software.
Test one stage at a time
- Power and connection: confirm the normal power state and the connection method specified for that model. Note whether the manufacturer’s application identifies the unit.
- Ball-ready state: place the required ball inside the documented hitting zone. Keep the mat, tee and unit at the heights shown in the installation guide. Confirm the ready indicator before swinging.
- Shot capture: make a controlled test shot only after the bay and screen are ready for use. Look for shot data in the native application or device display.
- Simulator delivery: if the native system captures the shot, check the integration, selected device, license and launch sequence for the simulator.
Use the symptom to narrow the cause
| Symptom | Useful next check |
|---|---|
| Unit is not detected | Power, data cable or approved wireless connection, then the device-specific software. |
| Unit connects but never shows ball ready | Hitting zone, height, alignment, ball requirements and obstructions. |
| Ball is ready but a shot is missed | Model-specific lighting, club/ball requirements and capture diagnostics. |
| Native range works but course play does not | Integration setup, device selection and license entitlement. |
| Problem began after changing the mat | Finished ball height and calibration geometry. |
| Problem begins after the PC sleeps | Restore the device connection and restart the documented software sequence. |
Do not mix setup rules between devices
An overhead camera, a side-mounted camera and a radar unit behind the golfer have different geometry. Ball markings and club stickers can also serve different purposes. Missing club data does not automatically mean ball tracking has failed. Use the requirements for the measurement you expect from your exact model.
Record a small repeatable test
Use the same ball and club, the same ball position and the same application for several shots. Note which shots register and what changes when you move the ball within the approved zone. Do not change calibration, lighting and network settings simultaneously; you would lose the evidence of which change helped.
Send the model, software versions, connection method, room/setup photos and the failed stage to IGK. For native-range success but integration failure, use Software connection troubleshooting.
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.