Garmin R10 — CSV export and free analysis
The Garmin Approach R10 is a single-Doppler-radar launch monitor priced around $599 MSRP, making it one of the most accessible ways to get real launch-monitor numbers off a home mat or range session. ContactCoach reads its CSV export directly and layers free analysis — including an estimated descent angle — on top of whatever the R10 measures.
How do I get a CSV off the R10?
The R10 itself doesn't produce a CSV — export happens through the Garmin Golf app. Open a saved Range or Driving Range session in the app, then use the share/export option in that session's menu to save the file. You can also pull the same session from connect.garmin.com under Activities if you'd rather export from a browser. Upload the resulting CSV at / and ContactCoach auto-detects the R10 format.
What does the R10 actually export?
The R10 is a single radar unit, and it's worth knowing which numbers come straight off that radar versus which ones Garmin calculates afterward. Directly measured: ball speed, clubhead speed, launch angle, launch direction, face angle (±2°), and apex height. Calculated from those measurements, not measured directly: spin rate, carry distance, total distance, club path, and face-to-path. Garmin's calculated club path — and values derived from it, like face-to-path — can differ from a dual-radar system like Trackman by 1–4°, since a single radar has to infer club delivery rather than track the clubhead directly. Ball flight numbers are generally reliable within a few percent of higher-end monitors; it's the calculated club-delivery numbers where the gap widens.
What does ContactCoach add on top?
The R10's CSV export doesn't appear to include descent angle, so ContactCoach estimates it. Everything else ContactCoach adds is really about turning a session's worth of shots into patterns, not adding new physics to a single shot.
| ContactCoach adds | Status | Guide |
|---|---|---|
| Descent angle | Estimated from carry + apex height | How it's estimated |
| Dispersion ellipses per club | Computed from your visible shots | Reading the ellipses |
| Gap analysis across your bag | Computed from carry percentiles | Reading gap analysis |
| Mishit flagging | Computed from per-club thresholds | How mishits are flagged |
Club path and face-to-path, when the R10's CSV includes them, are Garmin's own calculated values — ContactCoach passes those through as-is rather than re-deriving them, so the 1–4° caveat above still applies to those two fields specifically.
Measured or modeled — what should I trust?
Trust the R10's directly measured numbers — ball speed, clubhead speed, launch angle, launch direction, face angle, and apex height — as genuine radar measurements with tight, published error bars. Treat spin, carry, club path, and face-to-path as Garmin's best calculation from that same radar data, not independent measurements — useful for spotting trends over many shots, less reliable shot-to-shot. ContactCoach's descent angle is one more estimate on top of that, built from carry and apex height rather than a direct trajectory measurement, and it's always labeled "estimated" in the app so you know which numbers came off the radar and which came from a formula.
Try it
Upload your own R10 session at /, or click "Explore a sample session" on that page to see estimated descent angle, dispersion ellipses, and gap analysis running on real launch-monitor data before you upload anything of your own.