FlightScope Mevo - Portable Launch Monitor for the Everyday Golfer

[iacas]

  On 2/11/2018 at 7:16 PM, b101 said:

Srixon range balls - whatever their standard is. 

Expand  

Then that's a big part of your problem (i.e. the 42° you were getting): urethane balls launch lower with more spin, firmer (cover) balls launch significantly higher, particularly off partial wedges.

This basically completely explains your issue. You're not hitting premium, urethane-covered balls.

[Lihu]

  On 2/11/2018 at 8:05 PM, b101 said:

Well, mine's normally pretty good and I can't get above 1.44. At my last fitting, I averaged 1.50.

Not sure whether this affects launch angle though? I also remember some early reviews saying that the Mevo over-stated launch though

Expand  

I saw the reviews as well, and with a sample of two Mevos I got pretty good results if it’s setup correctly.

I’m probably more skeptical of the many YouTube videos that tested the Mevo except for the one pro from UK who compared it to an X3.

The sensor technology is pretty accurate and is designed in Germany. I’ve run FMCW tests with it and it’s pretty good.

[nevets88]

Richie3jack is positive on the Mevo and recently posted this about yardage gapping.

http://3jack.blogspot.com/2018/03/yardage-gapping-test-with-flightscope.html

[FrankfurtDave]

I recently updated the Mevo App which wanted a new FW update of the Mevo. Since that I am not getting any shots registered.

Anyone else seen any issues. My app provides the following version information:

App Version 1.3.5

AVR Version 0.08 FSMevo BT

DSP Version 1.09

Do these versions match those used by others?

 

Thanks

Dave

 

[FrankfurtDave]

  On 3/25/2018 at 3:51 PM, FrankfurtDave said:

I recently updated the Mevo App which wanted a new FW update of the Mevo. Since that I am not getting any shots registered.

Anyone else seen any issues. My app provides the following version information:

App Version 1.3.5

AVR Version 0.08 FSMevo BT

DSP Version 1.09

Do these versions match those used by others?

 

Thanks

Dave

 

Expand  

Just to answer my own reply in case it helps anyone else. The versions that I mentioned above are correct. The issue I had is a known issue within Flightscope and there is a fix coming coming in the next days.

 

The workaround should you have this problem is to change the mode (Outdoor to Indoor and back again in the app) when connected to the Mevo.

After doing this everything working perfectly again.

As usual great support from Flightscope. They replied within hours and came up with a solution immediately.

[iacas]

  On 3/27/2018 at 3:13 PM, FrankfurtDave said:

Just to answer my own reply in case it helps anyone else. The versions that I mentioned above are correct. The issue I had is a known issue within Flightscope and there is a fix coming coming in the next days.

The workaround should you have this problem is to change the mode (Outdoor to Indoor and back again in the app) when connected to the Mevo.

After doing this everything working perfectly again.

As usual great support from Flightscope. They replied within hours and came up with a solution immediately.

Expand  

So is this true if you are already set on indoor mode?

Is it more an issue with the app?

Or does changing the mode just reset something so it can function (and you changing it back was just because you were outside)?

[FrankfurtDave]

  On 3/27/2018 at 11:18 PM, iacas said:

So is this true if you are already set on indoor mode?

Is it more an issue with the app?

Or does changing the mode just reset something so it can function (and you changing it back was just because you were outside)?

Expand  

I can not say anything about the actual error that they had, and hence what additional use cases there might be. I can only say that if anyone has the issue that their unit is not registering ANY shots that switching the mode to something else and back again when connected might help.

For me I only test "Outdoor" mode hence I went from Outdoor to Indoor and back again. Whether the same issue can occur for Indoors or Pitching I do not know.

[iacas]

Likely switching the mode once works then. Thanks.

[nevets88]

I read something on Golfwrx on a "sniper's sight", I assume that's referring to the notch to help you align the unit?

Also, there's an update to the Mevo (new model not firmware) in a year or two? What new features are anticipated?

[iacas]

  On 4/15/2018 at 3:06 PM, nevets88 said:

I read something on Golfwrx on a "sniper's sight", I assume that's referring to the notch to help you align the unit?

Expand  

Yep.

  On 4/15/2018 at 3:06 PM, nevets88 said:

Also, there's an update to the Mevo (new model not firmware) in a year or two? What new features are anticipated?

Expand  

I don't need anything more.

[nevets88]

Flightscope wins award for Mevo

https://flightscope.com/goldstevie2018/

[boogielicious]

I noticed something odd today. I was recording 7-4 irons and driver. My first driver session was 5 shots and had spin in the 2100 range. Then I did 6 iron and was around 5000. I went back to driver but forgot to switch the settings to driver. My distances were shorter and spin was around 5000 again. 

Im assuming the algorithm uses club selection to resolve the spin numbers verses what it is reading for the spin sample. 

[iacas]

  On 3/29/2019 at 4:42 PM, boogielicious said:

I noticed something odd today. I was recording 7-4 irons and driver. My first driver session was 5 shots and had spin in the 2100 range. Then I did 6 iron and was around 5000. I went back to driver but forgot to switch the settings to driver. My distances were shorter and spin was around 5000 again. 

Im assuming the algorithm uses club selection to resolve the spin numbers verses what it is reading for the spin sample. 

Expand  

No, but it might use the club to determine the range for spin. Especially if you don’t have dots on the balls.

[boogielicious]

  On 3/29/2019 at 4:47 PM, iacas said:

No, but it might use the club to determine the range for spin. Especially if you don’t have dots on the balls.

Expand  

I had the dot and was hitting into the net. One concern I have is the net is only 7 feet from the contact area. I’m not sure if that affects accuracy. 

[billchao]

  On 3/29/2019 at 4:49 PM, boogielicious said:

I had the dot and was hitting into the net. One concern I have is the net is only 7 feet from the contact area. I’m not sure if that affects accuracy. 

Expand  

Do you have it set to the pitching setting (or whatever the shortest flight setting is called)? I only have about 7' to my net as well and that's what I have it on. It says it needs 10' of flight but that's as good as it's going to get at home for me.

[boogielicious]

  On 3/29/2019 at 5:01 PM, billchao said:

Do you have it set to the pitching setting (or whatever the shortest flight setting is called)? I only have about 7' to my net as well and that's what I have it on. It says it needs 10' of flight but that's as good as it's going to get at home for me.

Expand  

I have it set at indoor and 5 feet. I was have trouble when I set it for pitching. I know Erik had more accurate results with driver at 7 feet, but my driveway is sloped and 7 feet will be too high above the level of the mat. 

[nevets88]

Why does this use a mini usb port? I lost the original charging cable and had to dig to find a mini usb cable, have a million micro usb cables. Guess it has something to do with rate of charging.

[nevets88]

Having trouble with it lately outside with 5-30 yards. Doesn't seem to be capturing a majority of the short game shots. Moved it front and back and it's on same level as mat. Will keep trying.