Mevo plus 0.20 firmware - distances low on E6 since update

[johnnoco]

Hi all. The 0.20 firmware for the Mevo+ (Jan 26) created some issues with distance calculation being super low. Flightscope seemed to have fixed it in the FS Golf app updated on Feb 1st, but when I try on E6 Connect to play a course the same shot is going about 60-90yards less distance. Is this a known issue and is there going to be an update of E6 to fix this? Anyone else experiencing it? Using Ios version that comes with the Mevo+.

[bubbtubbs]

I haven't tried it myself yet since I primarily use the Flightscope app. They released an update for Fusion tracking for E6, are you on that version?

[johnnoco]

I havent seen an E6 update for Fusion tracking - the most recent says something about Accugolf flight tracking which seems unrelated to Mevo+. I have seen a FS Golf update (Flightscope app) and things seem good using that new app. So I can hit the range but not the course.

[bubbtubbs]

Ah, I didn't see the Accugolf part in that post that Mirek showed in the other thread. Nice catch.

Sorry that it means you're still waiting for the problem to be resolved, though.

[johnnoco]

I can still play it just takes me about 6 shots to reach the greens. .

[PapaChips]

I can't even get E6 to talk to Mevo+ since the Pro Package update, so I'm no help here. But I'm interested in the answers you get.

[johnnoco]

Make sure to kill the FS Golf app in IOS before attempting to use E6 - if one app "owns" the connection to the device the other app tends not to connect to it.

[johnnoco]

I find even the range distances are low in FS Golf app, unless you set the ball type to RANGE. Its not far off so perhaps its my environment, but its registering much lower distances than when I ran the 0.19 firmware. Im using a ProV1 with metal dots on it, but my yardage on FS Golf is off from the real driving range and course. Typical driver carry - 240yards in real life. 200yards on FS Golf. 7 iron is about right (155yards) but longer clubs seem low on distance.

[johnnoco]

Thanks for the suggestion - yes Ive taken it down to 10 and up to 18. No real effect.

[BJP1]

This has been my experience today as well. Anything beyond 7i reads a max of 160+ yards (6i thru 20* hybrid). Tried adjusting the tilt, still no change in readings beyond the 7i.

[Darren W]

Same here. Low smothered hooks. Son is a lefty and he was hitting smothered hooks in the other direction. E6 was much better. Launch angle seems really low in FS Golf. Will have to play around with setup to see if I can fix it.

[Bubba22]

I am seeing low distances post update on all software.

[Targuy]

I had a look to my PW spin average in a session several months ago and yesterday with the new firmware and the pro package activated. I have lost 800 RPM.
For distances, it is very cold outside here with low pressure so i am not sure that it is relevant to validate a loss of a couple of yards.

To be totally honest an average lower spin could have several causes :
- Me : With the pro package i am focused to make everyshot a draw ( Club path, FTT, FTP are lethal weapons ! Waooh it works so well for me to know if i must adjust the club head or the club path) when before i made a lot of fade.
- Them : Introducing somehow new datas like Dynamic loft in the calculation to complete the spin recorded most likely for indoor short setup.

[Bbabber23]

I am seeing low distances post update on all software.

I am seeing the same. It's really noticeable on driver.

[dwilson]

Hi all. Experiencing the same issues here. Significant drops in carry distance since updating to latest firmware 0.20 and installing the Pro Package. PW loss of 20yds & 8i loss of 25yds on the FS Golf app. Wouldn’t even register a swing on E6. I’ve sent Flightscope support a message and will post their response.

[Clubrepair]

Hi all. Experiencing the same issues here. Significant drops in carry distance since updating to latest firmware 0.20 and installing the Pro Package. PW loss of 20yds & 8i loss of 25yds on the FS Golf app. Wouldn’t even register a swing on E6. I’ve sent Flightscope support a message and will post their response.

I just installed my sim and seeing shots about 20% short testing with a PW and 7i. I called FS support yesterday and they had me move the M+ closer/further away from ball plus hit some shots while they were collecting data. I'm hoping they respond soon with a fix because I'm itching to play TGC 2019.

[dwilson]

I just installed my sim and seeing shots about 20% short testing with a PW and 7i. I called FS support yesterday and they had me move the M+ closer/further away from ball plus hit some shots while they were collecting data. I'm hoping they respond soon with a fix because I'm itching to play TGC 2019.

Just got a reply via Instagram to contact support. Still haven’t heard back from support. Hit balls in my net without any tracking today. Weird! Ha

[Bubba22]

I am not sure how to revert back to 0.19. I am not sure its recommended if you have the pro package. That would be a good question for Flightscope tech support.

[SPApex]

I have sent a support email to Flightscope with my concerns and waiting for a response. I do not have Pro package but I believe the .20 firmware performance is not right in my case.

[Bubba22]

Perfect SPA. Keep us posted.

[dwilson]

Update.

I received a response to my request for support email and also called the Support Team and spoke with someone this morning. I’m not convinced that Flightscope understand my issue clearly or that it’s FS Golf that’s the problem. The emailed response spoke about E6 needing an update and didn’t acknowledge the FS Golf issue I’d reported. My phone call at least gave me a pathway to move forward - asking me to update E6, and to collect data from both FS Golf and E6 and report back. I’ll do that, I’m not filled with confidence given the early interactions though.

Without sounding like a dickhead, I’ve played for 30 years and know how far I hit the ball and the numbers since 0.20 are well off. PW down 16m on a pure strike. Before 0.20 they were pretty bang on.

[Bubba22]

That's interesting. Thanks dwilson. What is strange is that I am seeing lower distances with the FS app and TGC2019 wheras the distances are too long with E6 Connect. The previous firmware was very good. I would hope they can correct things with a new firmware update.

[johnnoco]

Agree with 0.19 they were spot on. At least FS knows what to do - just compare the results to that version. Try setting to Range balls for now - that seems to get it closer.

[dwilson]

Update. Got the E6 app on iPad updated and recorded carry distances for comparison. E6 140m and FS Golf 119m. Have responded to my Flightscope support ticket, see where we go from here.

[SPApex]

I have the same problem dwilson. My short yardages are with FS App. I am not using E6 or TGC. I had very good yardages and parameters in FS app with .19 firmware. My problems started with .20. No response from FS on my support email yet.

[wildcatfan9698]

please check weather setting in FS, mine reverted from sea level to local

[johnnoco]

Update - E6 have an ios update - its fixed the low distances, but a bit too much as now I seem to be able to hit a PW 150yards. Its closer but has overcorrected to the long side. Fun to play again though! FS Golf is almost right when using Range balls, too low when using the real ball setting. They seem to be closing in on the issue - ball and club speeds seem about right but the calculation of carry and total distance seems to be off.

[Bubba22]

Exactly what I am seeing johnnoco.

[SPApex]

I have data comparison between camera based launch monitor and Mevo+ with .2 firmware. I was trying to look for outliers in data to figure out why Mevo+ is eratic. I set weather to "Standard Sea Level" and followed all setup guidelines for Mevo+ placement. I have 8Ft from Mevo+ to ball and 13ft to screen, hitting "Short Indoor" setting. My data confirms that Mevo+ does compute carry lower in all shots but also I have found a problem with Spin RPM. One shot was 2x spin rate higher and caused carry to be more than 16 yards shorter. I would still like to go back to .19 and confirm its accuracy vs .2.