gps-guides

Manuel’s Tracks

Devices

Highlights

Fenix 7

The GT-31 and Fenix 5 Plus results are very comparable with the two generally within 0.1-0.2 knots for results across the various speed categories. However, the Fenix 7 is reporting much lower than the other two devices.

The image below shows the Fenix 5 Plus (left) vs Fenix 7 (right). I’ve displayed the tracks such that the “Doppler speeds” (n.b. we don’t know for sure what Garmin is recording) and non-Doppler speeds are overlaid. The speed data from the Fenix 5 looks typical of a working GPS device and the speed graphs closely match the GT-31, especially what I suspect to be the Doppler-derived speeds. n.b. I won’t go into why I think the speeds from the Fenix 5 Plus are Doppler-derived right now, since it’s a topic in its own right.

The Fenix 7 speed data (right image) looks very similar in nature to my friend’s Fenix 7 track. What should be the Doppler-derived data is shifted right by several seconds, it is heavily smoothed and has flattened peaks.

img

Aside from the heavy smoothing (likely a basic rolling average but without centring, plus some basic filtering when stationary) there are also some weird downward spikes in the speed data. The shifting to the right wasn’t present in tracks from an earlier version of the Fenix 7 firmware but the downward spikes were also present in tracks that I have seen from the earlier firmware.

img

Garmin are definitely doing something peculiar with the speed data received from the GNSS chip. So far as I know it’s the same chip as the COROS VERTIX 2 and that watch doesn’t have these issues.

I’d be sure to complain to Garmin if I owned a Fenix 7. They should definitely look to fix this issue!

Fenix 5

Comparing the Fenix 5 to the GT-31 in GPS Speedreader shows they are pretty comparable.

The Fenix 5 speeds are sometimes 0.1-0.3 higher than the GT-31 but either could actually be correct.

There are a few spikes evident in the Fenix 5 data when stationary (actually in the water) but during sailing time the data looks decent.

The spikes may be due to the use of GPSBabel to load make the FIT file usable. Need to re-check when the original FIT can be analysed.

img

Track Data

You can find all of the tracks on GitHub under sessions/contacts/zugm/tracks.