Hi,
Thanks for asking... but my week of riding probably wasn't anywhere near as thrilling as yours. The most exciting thing was what didn't happen.
Spent the week riding (and camping) the Katy trail across Missouri. The female companion (who is not into camping) is still speaking to me after the ride. It's some of the small victories that are important.
For TF and the beta 2.88B
SUCCESS!!!!!!!
YEAH!!!!
The download didn't die out part way through. I even tried it a few times to make sure.
Ohhh crud... it did just die during a download.
Okay, here are the starts and ends of the log,
------------------------------------------------------
Releasing other Surfaces
Creating Surfaces
BackBuffer: Width=1594, Height=963, was created in Video Memory
TileBuffer: Width=1994, Height=1363, was created in Video Memory
Creating Resource Tiles....
Creating Sprites
Successfully Created Surfaces
Unit type = EDGE305 Software Version 2.60
Supported protocols/data types:
P - 0
L - 1
A - 10
T - 1
A - 100
D - 110
A - 201
D - 202
D - 110
D - 210
A - 302
D - 311
D - 304
A - 500
D - 501
A - 600
D - 600
A - 601
D - 601
A - 700
D - 700
A - 800
D - 800
A - 801
D - 801
A - 902
A - 903
A - 907
D - 907
D - 908
D - 909
D - 910
A - 918
D - 918
A - 1000
D - 1009
A - 906
D - 1011
A - 1002
D - 1008
A - 1003
D - 1003
A - 1004
D - 1004
A - 1005
D - 1005
A - 1006
D - 1006
A - 1007
D - 1007
A - 1008
D - 1012
A - 1009
D - 1013
newTrackLoc = 22
Number of Records = 11967
Starting new track - header received, curTrack = 0
length = 24
Bogus Cadence or HR point? Lat = 180.000000
length = 24
Bogus Cadence or HR point? Lat = 180.000000
length = 24
Bogus Cadence or HR point? Lat = 180.000000
length = 24
Bogus Cadence or HR point? Lat = 180.000000
length = 24
packet[17] = 0
packet[18] = 0
packet[19] = 0
packet[20] = 0
packet[21] = 0
packet[22] = 0
packet[23] = 255
length = 24
packet[17] = 74
packet[18] = 0
packet[19] = 64
packet[20] = 0
packet[21] = 0
packet[22] = 0
packet[23] = 255
length = 24
packet[17] = 129
packet[18] = 227
packet[19] = 64
packet[20] = 0
packet[21] = 32
packet[22] = 0
packet[23] = 255
length = 24
(etc...etc...etc...)
length = 24
packet[17] = 7
packet[18] = 189
packet[19] = 70
packet[20] = 107
packet[21] = 66
packet[22] = 0
packet[23] = 255
length = 24
packet[17] = 67
packet[18] = 189
packet[19] = 70
packet[20] = 112
packet[21] = 79
packet[22] = 0
packet[23] = 255
Caught Exception:
Function: Unhandled
Exception: Access Violation
--# FV EIP----- RetAddr- FramePtr StackPtr Symbol
0 .V 1003cea5 1003cef3 0d71f554 0d71f4ec getPacketUSBGarmin +373 bytes Sig: ?getPacketUSBGarmin@@YAHPAEPAK_N@Z
Decl: int cdecl getPacket(unsigned char *,unsigned long *,bool)
Line: C:\GPSMaster\checkout\GPSMaster\serial.cpp(480) +17 bytes
Mod: GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
Sym: type: CV, file: C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX
2 .V 1003e479 1002b746 0d71fa9c 0d71f4ec downloadGarmin +1449 bytes Sig: ?downloadGarmin@@YAHFPAUlayer@@_N11@Z
Decl: int cdecl gpsComm(short,short,short,short,char *,bool,bool,bool)
Line: C:\GPSMaster\checkout\GPSMaster\master.cpp(3304) +17 bytes
Mod: GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
Sym: type: CV, file: C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX
4 .V 1002c233 100a6871 0d71ff14 0d71f4ec GPSThread +179 bytes Sig: ?GPSThread@@YAIPAX@Z
Decl: unsigned int stdcall _AfxThreadEntry(void *)
Line: thrdcore.cpp(112) +5 bytes
Mod: GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
Sym: type: CV, file: C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX
6 .V 1008d0d9 7c80b50b 0d71ffb4 0d71f4ec beginthreadex
Decl: __beginthreadex
Mod: GPSMAS~1[C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
Sym: type: CV, file: C:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX
7 .V 7c80b50b 00000000 0d71ffec 0d71f4ec GetModuleFileNameA +436 bytes Sig: GetModuleFileNameA
Decl: GetModuleFileNameA
Mod: kernel32[C:\WINDOWS\system32\kernel32.dll], base: 7c800000h
Sym: type: -exported-, file:
-------------------------------------------------
So there is the latest error... and it looks like the 180 lat is still showing up, are you just dumping it now? Now that I think about it... I do believe there are some 'unwanted points' that are thrown out in the download into Garmins programs. Hmmm.... I'll have to look into those logs.
Okay... I also tried download from the older 201. Seems to be working beautiful. Tried three downloads, no faults.
Looks like there was considerable progress on the last round. Muchas Gracias.
So where was your week of riding at?
TC
PS Now that all the tracks are on the download screen without me having to do a bunch of merge/deletes, I see that I exceeded the 10,000 points after three days of riding. So I guess it makes sense that it dumped the detail data of the previous 2 days rides. Course I'd rather see it cut it down to maybe the 250 ponts of the older series then just dump it all. Sigh.
