Comment 4 for bug 135717

Revision history for this message
whamblen (whamblen) wrote :

I was messing around with this a little bit more last night and may have some more information. I don't really understand the code, but it looks to me like that index is out of range because the datapoint class (D1015?) associated with the lap class (A906) hasn't ever been defined but one is required. I'm guessing maybe your Edge uses a different datapoint class than my Forerunner. For sure self.datatypes = [] when the A906 getData call is made.

Here is the list of protocols returned by my forerunner.

whamblen@wake:~/garmin-sync-0.2$ ./garminsync.py
Get supported protocols
Try reading protocols using PCP
Got msg type 248, retrying...
Protocols reported by A001: ['P000', 'L001', 'A010', 'T001', 'A100', 'D110', 'A201', 'D202', 'D110', 'D210', 'A302', 'D311', 'D304', 'A500', 'D501', 'A600', 'D600', 'A601', 'D601', 'A700', 'D700', 'A800', 'D800', 'A801', 'D801', 'A902', 'A903', 'A907', 'D907', 'D908', 'D909', 'D910', 'A918', 'D918', 'A1000', 'D1009', 'A906', 'D1015', 'A1002', 'D1008', 'A1003', 'D1003', 'A1004', 'D1004', 'A1005', 'D1005', 'A1006', 'D1006', 'A1007', 'D1007', 'A1008', 'D1012', 'A1009', 'D1013', 'A1013', 'D1014']

D1015 immediately follows A906 and that appears (to me anyway) to mean that I need to create a class for it. Unfortunately I couldn't find any documentation from Garmin for that class. Somebody submitted a patch to gpsbabel that will download laps from my Forerunner (and only laps as I recall). Could the necessary info be gleaned from that? http://www.nabble.com/Re:-Lap:-How-to-get-from-a-device--t4014195.html

Anyway, I hope I'm not bothering you with all this. But I didn't want to keep potentially useful information hidden away either. :-)

 - Bill