First, I want to thank you for making so much progress here! But, of course, I am having a few problems.

I have two Trimble GPS receivers here and your application works with one, just fine (an old ScoutMaster) but the other(SV6 core module a la BGMicro) doesn't seem to put out a compatible form of NMEA.

The ScoutMaster puts out GGA sentances that look like this:

$GPGGA,190423,3716.920,N,12202.023,W,1,04,2.4,108.6,M,25.9,M,*78
$GPGGA,190426,3716.920,N,12202.023,W,1,04,2.4,108.6,M,25.9,M,*7D
$GPGGA,190429,3716.920,N,12202.023,W,1,04,2.4,108.6,M,25.9,M,*72
$GPGGA,190431,3716.920,N,12202.023,W,1,04,2.4,108.6,M,25.9,M, *7B

The SV6 output looks like this:

$GPGGA,190441.0,3716.915,N,12202.080,W,1, 6,001.3,124,M,-026,M,,*68
$GPVTG,000,T,344,M,00.0,N,00.0,K*4D
$GPGGA,190442.0,3716.915,N,12202.079,W,1,6,001.3,125,M,-026,M,,*6C
$GPVTG,000,T,344,M,00.0,N,00.0,K*4D
$GPGGA,190443.0,3716.915,N,12202.079,W,1,6,001.3,125,M,-026,M,,*6D


As far as I can tell the NMEA output is hard coded and the VTG is included. Also, note the decimal content of the time stamp and other differences. It seems the SV6 has added some fields for DGPS status at the end and uses different formats for Time of Fix, HDOP and a sign difference for the Geoid offset.

I am looking forward to trying the TSIP binary protocol as it is far more flexible and useful for troubleshooting.

On another subject, could you give a little more detail on running the Python script. I have not succeeded in getting it to find the raw route file or perhaps I didn't save it in the coorrect format. See attached "raw route" (html).

Thanks,

Lynn