Garmin R10 Does NOT work with Outdoor Nets

I waited so long and wanted this to work sooooooo badly, but sadly the R10 does not work with outdoor nets. Yes, I have the correct distances. 9 feet ball to net. Yes, I have more than 8ft behind. Yes, I've calibrated it, yes. I've messed with levels. But NOTHING works. It is RIDCULOUSLY SHORT on distances. When I hit in to the outdoor net, its 50-70 yards short per club. My longest 7 iron I can hit is 112 yards, lol. I suck at golf, but not that badly! My 7 is usually at 155-160 club. Driver is worse. It wont even get past 200 yards when I smash it. Driver usually goes 240-260 in real life. 

But here is the kicker, it worked perfectly on the range. The numbers and shot shapes looked good on the range. 

But I did not buy it for the range, I bought it for my backyard set up. And with the backyard set up, its unusable. Its so bad on the outdoor net its straight up laughable. Did Garmin even test this thing on outdoor nets, based on the results they did not. And I'm not the only one having this issue, there are lots of forums like this for people suffering like me. 

Long story short, it does not work on outdoor nets. If you are buying this for an outdoor (or indoor) sim set up, save your money and buy something else that works. 

  • I have had a similar experience with the garmin software, with very short readings hitting into a net. I have now managed to get more realistic readings with absolute golf (got 7 iron reading up to around 170yds which is about as expected), although after 14 days you have to pay a hefty subscription for that, and driver still seems to be reading about 20 yards shorter than I'd expect even on that. I think based on my experience though that it's a problem with the garmin software rather than the unit, I hope they fix it soon..

  • I have had a similar experience with the garmin software, with very short readings hitting into a net. I have now managed to get more realistic readings with absolute golf (got 7 iron reading up to around 170yds which is about as expected), although after 14 days you have to pay a hefty subscription for that, and driver still seems to be reading about 20 yards shorter than I'd expect even on that. I think based on my experience though that it's a problem with the garmin software rather than the unit, I hope they fix it soon..

  • ughhhh yeah, I mean it works well on the range. Question is, do I wait for the software update or just return it and cut my losses. All the videos online it "works" in to nets, unless they are just fake promo videos, which they might be. Not sure what to do...

  • I tried it today with the E6 software. Read a tip to change to 10K elevation in the app. That actually seemed to help and give me pretty close numbers. So, it works, kinda. Glad I was able to use E6 but still frusturated that its not playing nice out of the gate with E6, and its still not usable with Garmin Range or HTH. ;(

  • There's pretty much a new post every week about this. Nobody at Garmin seems to know how to fix it. It doesn't like Nets I've tried three different ones indoors basement and garage. Same issues as yourself HTH, Awesome Golf and Garmin range all short. E6 w/elevation changed is pretty accurate. Though sometimes I feel like there generous with the directions. Works fine at outdoor range which I used today. Also worked fine at a public sim with a screen.

    Outdoor Avg drive was 221yds.

    Indoor net Avg Drive 177yds.  

  • Is Garmin Rob able to provide a reply for those of us using outdoor nets? I just bought my R10 and am using it outdoors into a net, 8’ from unit, 8’ to net, and my irons are consistently about 30 yards short. Any news? Lots of posts from 5 and 7 months ago, but what’s new for those of us still suffering this inaccuracy plague?

  • Well, unfortunately I have 2 say welcome to the club. This is absolutely an issue that Garmin are clearly simply ignoring and referring people to the usual 'set up' guides etc etc etc. Return it, cos it's never gonna work properly. I'm gonna do the same. Garmin don't care and the unit is not cheap. Yeah, yeah I know it's a quarter of the price of the skytrak or whatever, but at least that unit works as intended. False advertising at best from Garmin for those of us amateurs hitting into a net!!? So annoying.

  • Hello, if yardage is 20+ yards shorter than expected and your R10 is running the latest software version 4.00, please review the following support articles for guidance in setting up and troubleshooting accuracy issues as follows:

    Troubleshooting Radar Features of the Approach R10

    Tips for Indoor or Outdoor Approach R10 Placement

    Try adjusting the height of the R10 (Raise 1-2" or 25-50 mm higher than current set up) and increasing the distance both forward and behind the ball may improve metrics. 8 feet should be considered the minimum ideal distance. A calibration can be performed if following the set up tips do not improve metrics, and you are also experiencing accuracy issues outdoors on a range.

    If issues persist, please reach out to the Golf Product Support team directly. They will likely need to look at pictures of your individual setup, screenshots of your metrics (ball speed, launch angle, backspin) and possibly a short video of your swing to further investigate.

    Approach® R10 | Garmin Customer Support

  • But surely it's not to do with placement of the device, if awesome golf is giving relatively accurate readings (at least for irons) with the unit in a particular position and then the garmin software is giving much shorter readings with the unit in the same position? It's not the positioning that's a problem, it's the garmin software, but we shouldn't have to subscribe to awesome golf to be able to get accurate distance readings..

    • Can nobody even confirm that garmin is working on a fix for this? It's obviously a general problem that needs sorting, and it can't be that everyone experiencing the same issues is just positioning the unit incorrectly (especially when the distance stats in other programmes suggest otherwise)..
  • I actually asked garmin support that question last week via web chat and was told that they are not aware of any fix being worked on.