Epic 2 GPS 2.32 problems

Yes, me too.

speed and distance are bad, GPS is fault

____________________________________

Before 2.32:

Distance 52.1 Km

AV Spped: 22 Km/h

Time: 2 h 22 minutes

____________________________________

With 2.32 (Same route):

Distance: 42,45 Km

Av Speed: 14,9 Km/h

Time: 2 h 24 minutes

___________________

GPS ver 2.32 is (Edited for language choice.)

With gps 2.27 the data was better for me, and for you?

Yes, 2.27 better than 2.32.

I have a e-bike with speed limitation to 25 Km/h, with GPS 2.27 electrical controller cut me on 24,7 Km/h, now, with GPS 2.32 electrical controller cut me on 19-20 Km/h....

______________________________________________

GPS 2.32 is fault in 20%!!!!!

#GPS ver 2.32 is...

you're absolutely right!!!

version 2.27 was too much better. garmin come back please

Is this on a standard or saphire model, and what GPS settings are used? I'm sick atm so have only done a walk since the upgrade but saw no difference on my track with an Epix standard version, standard GPS setting and 1 sec recording interval.

Epix 2 sapphire. Same setting as version 2.27 (multi GNSS). But also all system same problem

Just checked a whole slew of my activities where I do the same route and no discernible difference. Distances are all within 0.3 of each other. Zoomed all the way in on the map using satellite layer (easier to see where it is clipping stuff), and all the tracks look very similar and are within 1m of of my actual course (most of the time were within 0.5m). No change from 1month ago when on 7.35 to now on 8.18.

One thing I did not that is the second day after I knew I had been upgraded to 8.18 my watch took around 45-90s to get a fix (was starting to think something was wrong with it as the fix is usually done within 15s) - so I wonder if there is a CPE that you need to update or something like that and the watch just hasn't done it. Unfortunately I can't really check the track prior to that as it was a one off (not a usual route), but when I zoom into it, it doesn't look like there are any issues with it and Strava correction has it within 0.02km distance across 5km.

max peace with the run is ok for you? and the max speed with the bike? 

haven't been on a bike yet. But yes for run its working fine. But then it would be as my distance is good and there are no spikes or erroneous errors on the GPS track.

Max pace is basically a formula based off distance and time. So if distance is out/wrong i.e. track loses connection and puts you off actual track, then yes it would give you incorrect max pace. 

Had issues like that in the past on different watches, some suunto, some wear os and even on my older garmins on the odd occasion when a bad GPS fix has given me a very unrealistic fix. Once had one that so bad (think it was one of my wear os watches - that it had my max run pace at around 3m/km (so somehow I managed to run at 20km/hr along the tracked route - yeah right I believe you watch).

Would check your track to see where it went wonky. Probably easiest in the connect web, as you have the 3 charts with the map above and if you hover over the spike/drop in pace it will show you the position on the map, so you can then zoom into that area to see if you can spot a reason for the wonky pace.