Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[VanX]

Hi Geoffrey
Please send me this new X firmware
I like to try it out
Best regards VanX

mcmidtfyn  (@)  gmail.com

[TWG_TECH8]

Hi Geoffrey
Please send me this new X firmware
I like to try it out
Best regards VanX

mcmidtfyn  (@)  gmail.com

Done it!
Please check your email box.

Sincerely,

Geoffrey

[Longjog @ GS-Sport-Servicecenter]

Hi Geoffrey,

today I have done a Conconitest while I have had my GH625 with 200m auto-lap function.
Here are the results:
Lap# Trigger (200m) Lap dist  cumm error
01         200m            209m      +9m
02         191m            200m      +9m
03         200m            201m     +10m --> SET Trigger Value to 200-10 =190!

Ups, mistake! Please set Trigger Value for the 3rd lap to 200 - 9 = 191 instead of 190
Maybe I really was to tired yesterday evening 

Sincerely

Longjog

[ultrapetita]

The easiest way (quick and dirty) to improve this is to take 3rd decimal=meters into account; i.e. if the user could control the amount of the cumulative error.

(Actually I can not understand why the user can specify e.g. 0.997km lap, but this will be rounded to 0.99km.)

Regarding the pace1k: how is it possible that with very constant 5min/km pace the 1kpace can show numbers like 5min43s/km? If the 1kpace was working OK and updated once/100m, I guess this would be much better than the lap pace, which shows quite instabe numbers in the beginning of the laps.

[leonker]

Hi Geoffrey
Please send me this new X firmware
leonker@013.net.il

Thanks

[Longjog @ GS-Sport-Servicecenter]

The easiest way (quick and dirty) to improve this is to take 3rd decimal=meters into account; i.e. if the user could control the amount of the cumulative error.

But this means to know the average error exactly and there will be a statistical error which will grow up with the number of laps.

The solution of the globalsat engineers with the calculated variation of the trigger-value is much better because the cummulated error is limited to the "step-size", independent of the number of laps.
This is implemented already, only the actual cummulated step-error has to be used instead of singe step-error of the last lap!

I love my watch! 

Regards
Longjog

[erbschaft2]

Hi Geoffrey
Please send me this new X firmware too
horst@franken-online.de

Thanks

[Icehands]

Hello Geoffrey
Please, send me too
THX

[alfanut]

Hi Geoffrey

Please send me this new X firmware too:

alfanut@telefonica.net

Thanks

[Icehands]

sorry 
my email address: ismaelgph@euskalnet.net

[albert]

Hi Geoffrey,
the new FW sound great! I'm interested in testing the new one, please send it to my email address.
Many thanks in advance.

Hello Geoffrey,

I am back from a holiday, but i am interested in the new FW, can you please send it to my emailaccount? I did some Hiking with the watch, worked out very good, I did follow a route from the local people, made by a Garmin GPS, I think my end result of the track was much better then from them.
What was interesting, they had some kind of waypoints in the gpx track, but I was be able to load it into the watch. I think they did that with Oziexplorer, because I suggested that to them, after giving a digitized and calibrated card to them.
I hope you can release the FW with the slope % soon. But thanks for continuing the updates.

Best regards Albert     
 

[TWG_TECH8]

Hi Geoffrey,

today I have done a Conconitest while I have had my GH625 with 200m auto-lap function.
Here are the results:
Lap# Trigger (200m) Lap dist  cumm error
01         200m            209m      +9m
02         191m            200m      +9m
03         200m            201m     +10m --> SET Trigger Value to 200-10 =190!

Ups, mistake! Please set Trigger Value for the 3rd lap to 200 - 9 = 191 instead of 190
Maybe I really was to tired yesterday evening 

Sincerely

Longjog

Hi Longjog,

About the 3rd trigger, the alogrithm of firmware X was setting 200-9=191 m for trigger value. (Formula is: 200m- lap diff [n-1])

Regards

Geoffrey 

[TWG_TECH8]

Hi Longjog,

Yes, we adjust the trigger by "step-size", the variation of trggier value would be: (ex. the lap is set to 1000m)

No of Lap   Trigger (1km)    Lap dist
----------   ---------------   -----------
0               1000m             1006m 
1               994m               999m
2               1001m             1004m             
3               992m               997m
4               1003m             1005m 
5               995m               1001m

So the total cumulative error is : 6-1+4-3+5+1=12m
Because GPS accuracy is +/-15m, the lap dist will always larger a little bit than trigger.

Please post your training file like the above format or send me the training ile, so that I can easier to find out the reason.

Have a nice day,

Geoffrey

Hi Geoffrey,

I think the algorithm shown above just needs a little modification to be almost perfect:

Currently you adjust the trigger value by a "step-size", which is calculated by the difference
from expected lap-distance to measured lap-distance. Example: When the expected lap-dist.
is 1000m and the measured distance is 1006m, the difference is +6m and so the next
trigger will be adjusted to 1000 - 6 = 994m.

As you could see from the examples by Longjog and others this still leads to a cumulative error !

When you modify the algorithm just a little bit, it will be much better:
You just don't have to calculate the difference between expected lap-distance and measured lap,
instead calculate the difference between (adjusted) trigger and measured lap !

Example:

No of Lap    Trigger (1km)    Lap dist      Diff. 
----------   -------------   ---------    -----
0               1000m             1006m        + 6 
1               994m               999m         + 5
2               995m               1004m        + 9     
3               991m               997m         + 6
4               994m               1005m        +11
5               989m               993m         + 4

Because of GPS inaccuracy there will always be an error and with this kind of algorithm
it will be always positive. But it will not cumulate !
As GPS error will be in a range from 0m to + 15m, also the final error for the last lap will
be in the range from 0 to 15m.

Please check my suggestion and discuss with you software team !

Regards, Hubert

Hi Hubert,

It seems no different than orginal after estiminated.

The last instance:
No of Lap   Trigger (1km)    Lap dist            GPS inaccuracy
----------   ---------------   -----------         -----------------
0               1000m             1006m                   +6
1               994m               999m                     +5
2               1001m             1004m                   +3
3               992m               997m                     +5
4               1003m             1005m                   +2
5               995m               1001m                   +6

Total comulatived error is 6-1+4-3+5+1=12m;

About yours:

No of Lap    Trigger              Lap dist (T+GPS inaccuracy)       
                 (T-GPS inaccuracy)          Diff
----------   -------------   ---------    -----
0               1000m             1006m        + 6 
1               994m               999m          -1
2               995m               998m          -2     
3               997m               1002m         +2
4               995m               997m           -3
5               998m               1004m         +4


Total comulatived error is +6-1-2+2-3+4=12m;

Needs to check more...

Regards

Geoffrey 

[TWG_TECH8]

Hi Geoffrey,
the new FW sound great! I'm interested in testing the new one, please send it to my email address.
Many thanks in advance.

Hello Geoffrey,

I am back from a holiday, but i am interested in the new FW, can you please send it to my emailaccount? I did some Hiking with the watch, worked out very good, I did follow a route from the local people, made by a Garmin GPS, I think my end result of the track was much better then from them.
What was interesting, they had some kind of waypoints in the gpx track, but I was be able to load it into the watch. I think they did that with Oziexplorer, because I suggested that to them, after giving a digitized and calibrated card to them.
I hope you can release the FW with the slope % soon. But thanks for continuing the updates.

Best regards Albert     

Hi Albert,

It is good to know the track of watch is better than Garmin.

Dear members,
About the firmwareX, we also put a suprising in that! Smart Track Back.
We are not only put arrow in 1/3 screen at right, but also it can guide you point by point instead of track routing!! You can trace with your taining files or you can download the file from PC to watch than perform it likes route navigation.
Map mode is the new but compass page still only shows the dircection to the destination as previous.

Enjoy your training!
Geoffrey

[alb]

Hi Geoffrey

Please send me the new X firmware
I like to try it out (Smart Track Back)
Thanks

Email: albert.hofmann@gmx.net

Best regards alb