Feature Request: Enhancing CT10 Functionality for Driving Range Use

COEZBAY 9 days ago

Hi Garmin Team,

I’m a passionate user of the Garmin CT10 sensors and greatly appreciate the detailed insights they provide during rounds of golf. However, I’d like to share a suggestion that could significantly enhance the usability of the sensors, especially for training sessions on the driving range.

Currently, the CT10 sensors face limitations on the driving range due to the lack of GPS data, making it impossible to calculate shot distances. To address this, I believe the following features would be highly beneficial:

Manual Entry of Club Distances: Introducing the ability to manually define maximum or average distances for each club and integrate them into the statistics. This would greatly improve the utility of the CT10 sensors on the driving range.
Driving Range Tracking Support: Adding a mode specifically designed for the driving range that allows users to track shots and analyze them separately from GPS-based rounds. This could simply involve club selection and shot counting.
Integration of Distances Without GPS: Allowing users to input shot distances manually or integrating data from a launch monitor (e.g., Garmin R10) would make the product more versatile and appealing.

These enhancements would provide immense value to golfers by improving both training sessions and club selection during rounds. I’m confident that many users would benefit from such features.

Thank you for your fantastic work with the CT10 sensors! I hope these suggestions can be considered in future updates.

Best regards,

COEZBAY

0 Owen 8 days ago

But while you're at the range how do you know your manual entry of distance is actually the correct distance for that shot? - you shouldn't rely on any markers the driving range may have placed in the landing area. Distance from a launch monitor like the R10 is calculated, not measured.

I use a different launch monitor SC300 by Voice Caddie which does calculate shot distance (similar to the R10) records data into the cloud and allows for post range analysis. While it's calculation might not exactly match an on-course distance measurement, it's consistent enough for me to say my driving range numbers typically differ from my on-course numbers by +/- X.

0 COEZBAY 6 days ago in reply to Owen

Hi Owen,

Thanks for your response! You bring up an excellent point about the accuracy of driving range distance markers and even launch monitors. I completely agree that the distances calculated by launch monitors like the R10 or SC300 might not perfectly align with on-course measurements. However, I believe the consistency they provide can still offer tremendous value for practice and analysis.

The idea behind manually entering distances in the Garmin system would primarily serve as a way to bridge the gap for those who don’t have access to a launch monitor or want to standardize their own practice data. For example, if someone consistently observes a certain carry distance on the range (even if it’s slightly off compared to on-course numbers), being able to input that data into Garmin could still help create a more personalized and useful training experience.

While fully integrating manually tracked data or driving range results into the Garmin Golf app would require Garmin to provide an open API or allow third-party data imports, it could significantly enhance the ecosystem by enabling users to bridge the gap between range practice and on-course performance analysis.

In your case, the SC300 sounds like a great solution, especially with the cloud data and post-range analysis features. I hope Garmin considers adding similar integration for their devices like the R10 and potentially allowing a mix of calculated (or even manually verified) data to enhance their ecosystem.

Best regards,

COEZBAY