First of all, I will try to picture here that GPSR shows exact numbers as KA72 if is setted correctly.
GPSR is a professional program, and have integration to GPSS, maybe nex ver will have integration to GTC :), time will tell
Main difference and allways problem is score of 2sec. 2sec is not max speed, then speed you hold for 2 sec, counting from 0, 1, 2 - so you need 3 points to have correct 2sec. KA72 in that case working fine, but what bothering users in gpsr ?
Maybe my test will clear this:
As Nebb said, KA72 is the best way and the easiest to post score, and Nebb also said that filter in GPSR must be on trapezoidal setting to be the same as ka72 reding 2sec.
If you have older version of GPSR that will don't work, so check this out:
1. Get latest version of GPSR v6.90
2. If you have payed licence for version 6.xx, just install over old one, key will work, becouse in gpsr you pay for all newer version. There is no need to do nothing, just reinstall it. (If you payed for versio 5, contact Manfred for new key before doing upgrade - this work only if you payed for 6.xx key)
3. Now you have v 6.90
4. I open one file in default setting and it looks like that:
You see that gpsr is setted in default on cubic spline and 2sec is calculated
from 2 points (grey colour in the point box) - 2sec is 36,282
Now, try to switch cubic to trapezoidal.
In that case you will got this:
Now you see that 2sec is calculated from 3 points (3 grey colour line in point box)
2 sec in that sample is
36,13 KT
When I uploaded that same file on KA72, here is a result:
As you see, KA72 shows
36,13 as correct setted gpsr, no any difference in decimals. So, I trying to say that correct setted gpsr show the same numbers as ka72, and there is no theory that 2sec is bigger then on ka72.
Sorry 4 my english, I hope you understand what I trying to say here.
Update:I also checked this same file with GPS Action Reply Pro, and in that case
2 sec is also
36,13 - so 3 times exact score, how more precise can be?
