I've had an opposite experience with realspeed. My max display on my foretrex said 31.3 but once it was put into realspeed it ended up as 30.4. How come I didn't get an extra 4 knots like Troppo and Firie???

can anyone let me know what lap racig is in the new version of realspeed.?

cheers

It's good to see Mal has stepped up to the plate and started posting here. Who better to answer questions about the software and how it works other than the author. Hopefully Mal can explain all the parameters that need to be set in options to measure our speeds correctly and filter out the spikes in the data. It seems every update of the software has more parameters for filtering data but there is no guide to let us know how and what to set them at. I'm sure with the formal release due in a month or two a users guide will be included with the purchase price.

Sorry that should have read
"So .PTL.gpx and .PTL.NMEA files work OK," and not as I put in previous post
"So .PTL.ptx and .PTL.NMEA files work OK"

Hi Mineral.

If you are working with files with those endings you must be working with the files downloaded from the internal memory via Navilink.
Those files are not as good as the ones saved to the SD card. The SD card files contain more accuracy and a lot more information. They are the ones you need to use. You just copy them from the card with a card reader and the file extention should be .txt. (Well, it is for me.)
If you open it in a text program (like notepad) it should look like this small sample:

This is the data from 1 second from an SD card:

$GPRMC,034158.682,A,3850.7095,S,14609.5444,E,26.05,182.88,130407,,*2C
$GPVTG,182.88,T,,M,26.05,N,48.2,K*64
$GPGGA,034159.682,3850.7169,S,14609.5441,E,1,08,0.8,1.9,M,-4.7,M,0.0,0000*76
$GPGLL,3850.7169,S,14609.5441,E,034159.682,A*26
$GPGSA,A,3,28,09,04,08,29,17,26,11,,,,,1.9,0.8,1.7*32
$GPGSV,2,1,08,17,75,128,45,28,36,107,46,26,35,295,41,09,30,226,33*72
$GPGSV,2,2,08,29,29,313,43,04,23,023,38,08,19,043,41,11,10,137,41*7B

Note that there are 6 NMEA 'sentences'.



Here is what I just got from the internal memory:

$GPRMC,015045.000,A,3851.1783,S,14609.9631,E,24.84,112.00,110607,,*27
$GPGGA,015045,3851.1783,S,14609.9631,E,1,,,4.5,M,,,,*23

In this sample there is only 2 NMEA sentences, and it looks like the Doppler speed value is rounded off in some way in the files I just ran because the doppler speed graph is too blocky. The trackpoint data looks the same though.

The speed figure is in the RMC line. The seventh item (comma deliniated) In the above examples it is after the letter E and in the first it is 26.05 (knots) and in the second it is 24.84. (The two samples are not from the same run or even the same day).

The normal and encouraged proceedure is to use an SD card and analyse the data from that.

If I understand it correctly, there is firmware being tested now that can write the Sirf binary data to the internal memory as well as the SD card which should be quite an advantage because we may be able to have the same data twice. One set on the SD card and another duplicate set on the internal memory. There will be a backup built in. Since the binary data takes up much less space we should be able to get many more hours of data on the internal memory than we can now.

The gist of all this is: Use the SD card data.

I have fixed the File/Properties crash. It was an error in logic when processing the altitude. It only occured when the max altitude was less than zero.

This fix has been posted up in version 1.905 on my website with many other fixes (its been another big weekend of coding to stabilise RealSpeed...).

Also available on my website is a pair of example files (actually my best runs in March) so you can see how the multi-file calculation is working. Take a look at the merged doppler option in the speed graph by right clicking in the speed graph and select Graph Fields... to choose which speeds you want to see.

While you are there, take special note of how well the two doppler tracks (green lines) agree.

http://www.intellimass.com/RealSpeed/realspeed_beta.htm

In 1.901 the Nautical Mile and 1 hour calculations don't show up. Is this fixed in the latest update?

Hi Nebbian, the issue was that I tightened up the handling of invalid points when implementing all the new features in 1.900. Long runs like the nautical mile and one hour (and virtually any distance cycle or run) with a few invalid points will not produce a result so I need to fix this. My solution is to provide an option in the divisions to use a "Strict" method for short course speed competitions like on GPS-Speedsurfing, and a less strict option for all other divisions. I should have this done by the end of the week.

This will again raise the complexity of setting up divisions, so I will probably separate advanced settings from standard settings and default to not strict. For GPSSS we can produce a standard rsp file with all the correct settings so that should not be a problem either.

If you have any other suggestions then let me know.

Hardy and I went for a 1hr today, wind was light and gusty, my navi registered 27.something max speed. when I loaded the sd card .txt files into realspeed 1.804 and deleting invalid, it had a 32.something 2sec max. It was obviously wrong, as it was at the very beginning of the session while I was still in the carpark!!!! possibly caused by going to the car for something and getting in a satellite shadow. For some reason "delete invalid" didn't remove it.
However when I used 1.905 with the doppler file, that came up with a similar 27.something 2sc max.

Be nice if everybody used the doppler version for max speed, as it does seem much more accurate. But don't rely on it for alpha's at the moment, seems to miss one direction out of the calculations.

quote:

---

Originally posted by TimeMachine

Aplogies Decrepit, I missed your big post...

Could you send me the file at [email protected] so I can find out what is going wrong? Thanks!

---

No worries Mal.
I just clicked on your address link in firefox and replied in the email panel that appeared, I assumed it was part of thunderbird, but it doesn't seem to be, and I have no record of it in any "sent-box" So if you didn't get it, PM me.

quote:

---

Originally posted by nebbian

I may well be wrong, but doesn't the display use doppler speed, instead of 1 second distance between points?

So if you set up RealSpeed to use doppler, then it will always agree with the display.
Or am I missing something?

---

True. However, the logged data also contains extra information about HDOP, satellites, etc. so it is in a better position to determine whether the max speed was actually a valid max speed.

Trackpoints would need to be involved anyway, to calculate the distances wouldn't they?

The problem I experienced with 1.905 happened with the old alpha.rsp as well as the new Doppler.rsp.
Mal is working on the problem and will post a fix.

Thanks Mal, file received, I'll try tomorrow.

Hey GT,

I have searched high and low and no unanswered emails except a couple from the USA and Israel. Even checked my spam folders...

Send it to me again tonight and I'll send a reg Id post-haste!

quote:

---

Originally posted by TimeMachine

Hey GT,

I have searched high and low and no unanswered emails except a couple from the USA and Israel. Even checked my spam folders...

Send it to me again tonight and I'll send a reg Id post-haste!

---

Hi Mal,

Weird, I sent the email to [email protected] this is correct?

No worries, I will resend tonight.

Thanks heaps, GT.