Select to expand quote
Roo said..
Some postings on GPSSS, Coros vertix showing 45.37kts for 500m, event GPS timing from Luderitz only showing 43.94kts!
Locosys GW60 recording 46.09kts event GPS with 46.89kts.
Another GW60 48.42kts for 500m event GPS 47.87kts.
The older COROS watches (APEX Pro and VERTIX) are horribly broken at the moment, since the Aug firmware. The 2s is particularly untrustworthy with the Aug F/W, often reporting several knots too high.
I guess the GW-60 reading 0.55 kts higher than the event GPS is mainly due to the GW-60 not knowing about the start + finish lines. 9 times out of 10 when I investigate a query during WSW or POS it is due to that reason. i.e. Fast start + slow finish or vice-versa.
The GW-60 under-reading by 0.8 knots is more interesting, assuming the event GPS was correct. I've also seen under-reading a couple of times on UBX devices during WSW and POS, but the issue is always glaringly obvious in the sAcc values.
The event GPS will sometimes over-read as several riders will attest, and unfortunately the case for Antoine yesterday. Jenna's records were only downgraded by 0.05 (47.41 -> 47.36 and 47.53 -> 47.48) knots which shows how well they can perform.