Run.GPS Online Shop

Download-Korb

Inhalt: 0

Einloggen | Registrieren

GPS-Sport Foren

Run.GPS Software

18km training being logged as 48km?

Bitte einloggen, um neue Kommentare zu erstellen

Foren durchsuchen

Erste Seite

Seite

von

Letzte Seite

ErwinB

21.07.2010 20:49:20 UTC

All time low

Today both my rides had errors again. The second one managed to list my 18 km commute as a ridiculous 233159.38km!!!

It seems as if there is an error in the algorithms or as if the gps messages crc's are not used.
In the first track there is again nothing to be seen on the map display but if you use the training simulator to play back the training you can see that about halfway a few meters before the roundabout there is a sudden jump in distance covered. As if there was a faulty gps point that is not shown in the graph but is taken along in the (distance) calculation.
http://www.gps-sport.net/trainings/cycling_346846
Only the trouble with that is that I recently bought a different logging gps (Qstarz BT-Q1000EX) The software that came with this gps , qsports, that for as far as I know does not filter any driftpoints by default (it is a seperate option) does not show any strange spike or drift point. Which I think moves the issue away from the gps to the bluetooth communication and/or the rungps software.

This afternoon things really became ridiculous. http://www.gps-sport.net/trainings/cycling_347304
I will remove this training in a couple of days because it is messing up my statistics, but it has several very very large spikes or driftpoints resulting in a training distance of more then 233000 Km in 45 minutes, a average speed of 326529Km/h and an also impossible max speed of (considering the distance) 95.2Km/h. The simple explanation would be that the gps made a few severe errors but again qsports the software that came with the gps does not in any way show such spike or better put, it does not show any spikes.
Even if the errors were in the gps data shouldn't the application ignore or filter out such obvious errors?

ErwinB

12.07.2010 20:13:25 UTC

And again with v2.3.7 b2070

And sure enough it happened again on the way back after upgrading to the latest version.
Same magnitude of error, but now the training data is considered plausible...
http://www.gps-sport.net/trainings/cycling_338898

I would like to go back to v2.3.5 b1916. Does somebody have a download link for this version?

@Stiophan: Please keep us informed if you solved your problems with the older version and if so, which version did you use?

Stiophan

12.07.2010 17:11:01 UTC

Same problem here

I think it is the version of Run.Gps that causes the problem.. I have all sort of strange problems with the latest version i downloaded.. I have by this hour downgraded to an older version

ErwinB

12.07.2010 09:07:27 UTC

And it happened again

http://www.gps-sport.net/trainings/cycling_338466#

My 12Km commute has been logged as 21Km.
And again there is nothing strange to be seen in the track.
Am I really the only one this is happening to?
This has been happening with two different gps units now. Both where on version 2.3.6.b B1956. I'm now going to upgrade to the latest version.

Maybe this is a "leftover bug" from the 0m altitude crossing bug?

ErwinB

22.06.2010 11:57:52 UTC

What went wrong with this training?

I have a route I cycle almost everyday of 18.3km. Yesterday the strangest thing happened, when I got home I saw that it was logged as almost 48km with an average speed of more then 60km/h. See http://www.gps-sport.net/trainings/cycling_320188
I expected to see some crazy spike in my trace that sometimes was there in previous version. You know to Moscow and back in 2 seconds :-). But visually I can't find anything wrong.
Is there something I can do to avoid or correct this?
Or is a wrong gps coordinate filtered out on the screen but is it still being used in the calculations?
Also strange is that the graphs do end at around 18km. Where does the 48km come from then?

Erste Seite

Seite

von

Letzte Seite