Mevo Plus Spin/Carry Inaccuracies

[brown.kyle727@gmail.com]

Hi all, I've got a Mevo Plus that has been giving me inconsistent spin/carry numbers. Hoping someone on this forum has shared a similar experience and can offer advice or a solution.

I find that my Mevo is accurate until 1 in every 3 or so balls, it'll record a low spin shot that carries an addition ~25% distance. It's likely happening on my driver; however, its much more obvious on my irons. I hit in my garage which is 17' Mevo to screen. I created a level surface from the mevo to the hitting mat and have tried messing with the distances Mevo to the ball. Even with more/less ball flight adjjusting the ball location and Mevo to ball settings, I keep seeing the unrealistic spin/carry numbers every couple swings. My stock 9-iron carry is 150-160 yds with a club head speed of 95 mph. I've attached two examples showing near identical swings resulting in completely different outcomes on the distance and spin. I'll see 190 9-irons, 220 7 irons, 240 6-irons and so on... When its reading the spin correctly (60-70% of the swings), the numbers look great.

In this testing, I was playing on TGC 2019 driver range running on my PC. I was using ProV1 RCT balls and also tried other balls with the metallic stickers (same result). I've got the Mevo on short in-door, current alitude (~75 ft for Houston), 15 degrees angle, no height adjustment to tee, no moving objects like a fan, TV off, LED spotlight only (no florecent lighting). My hitting strip is FiberBuilt.

I emailed Flightscope to get their take on this. I'm also planning on testing this same test with the 9-iron on the Flightscope app on my Ipad. I'm not sure if that will yield different results. If it does, it doesn't help muich since I play all my simgolf on TGC.

Thanks for taking the time to read!

[OttawaP]

I had the same results when I had access to one last winter. I think all the stars have to align in a perfect room for it to be reliable. Outdoors I'm sure is where it really shines. I found drivers the worst with impossible spin numbers.
I did enjoy the range ball setting that got me over 300yrds on drives, I miss that even though i need to be on an elevated tee with a damn good wind behind me for that to happen.

[TheBurtonEus]

This is why I moved on from the Mevo+ and went with a GC2. Although it may appear as a "downgrade", it really isn't if you are the only one using your sim consistently. The inconsistency with the Mevo+ got to me over time. It was great for LH and RH simplicity, but I use the sim predominantly myself.

[brown.kyle727@gmail.com]

Quick update from small session with the Flightscope Sim running on my iPad. Spin numbers and distances were consistent and realistic. My 9 iron stock dropped to 145-150 carry with 7500-8500 RPM. I’d say this is accurate based on real course play. I used RCT balls and regular with metallic dot and had good results regardless. No 170+ 9 iron swings…

Guess we’ll see if it continues to be consistent in flightscope sim. Maybe I’ll try to update or reinstall TGC to see if it somehow fixes. If not, may be time to upgrade to GSPRO.

[southbay]

I have trouble with this too, and I've found that it only happens when I'm hitting higher ball speeds in a small area. The 8' recommendation is just a guess that should work for most people and most scenarios, but if I hit 170+ ball speed with 8' between the ball and my net the Mevo+ gives me strange numbers almost every time. If I hit that same shot outside, the numbers the monitor gives me are spot on.

This makes sense if you think about it. The monitor doesn't need to measure ball flight over a certain distance, it needs to measure it over a certain amount of time. For most shots, 8' from ball to screen gives enough time, but for high ball speed shots you need more distance before the ball hits something.

As it currently stands I can't get consistent measurements for 3w or driver using my indoor space, which is annoying.

[buggerman999]

Had the same issue. Spent hours on the phone with flight scope and they determined the data was being read and fed into TGC correctly. Doesn’t make sense. Just play longer courses and play the extra 15-20 yards.