Thread: Re: [Gpsbabel-misc] Garmin 12xl download issue
Brought to you by:
robertl
From: <uru...@ix...> - 2004-05-05 16:55:30
|
[snip] { bashes head against wall, begins bleeding Garmin-colored blood... } Sorry.... +++++++++++++++++++++ What version did it last work with? Actually, I just started to work with this. The first version I used was 1= .2.2 supplied with GSAK. That version failed too. I have no experience wi= th earlier versions. +++++++++++++++++++++ [snip] Turn on debugging for a waypoint transfer and show us what you see =09gpsbabel -D9 -i garmin -f com1: Here is what I get: Tx Data:10 fe 00 02 10 03 : ... Rx Data:10 06 02 fe 00 fa 10 03=20 Rx Data:10 ff 3e 60 00 90 01 47 50 53 20 31 32 58 4c 20 53 4f 46 54 57 41 5= 2 45 20 20 34 2e 30 30 20 00 56 45 52 42 4d 41 50 20 4e 20 41 6d 65 72 69 6= 3 61 20 43 69 74 79 20 44 61 74 61 20 32 2e 30 31 00 93 10 03=20 Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12XL SOFTWARE 4.00=20 ID:=09=0996 Version:=094.00 Rx Data:00=20 Tx Data:10 06 02 ff 00 f9 10 03 : .....Capability '`'. Type 36864 Capability '=01'. Type 20551 Capability 'S'. Type 12576 Capability '2'. Type 19544 Capability ' '. Type 20307 Capability 'F'. Type 22356 Capability 'A'. Type 17746 <--- At this point, the message "[ERROR] PROT= OCOL ERROR: Unknown tag/data [A/17746]" is displayed on the screen. Capability ' '. Type 13344 Capability '.'. Type 12336 Capability ' '. Type 22016 Capability 'E'. Type 16978 Capability 'M'. Type 20545 Capability ' '. Type 8270 Capability 'A'. Type 25965 <--- At this point, the message "[ERROR] PROTO= COL ERROR: Unknown tag/data [A/25965]" is displayed on the screen. Capability 'r'. Type 25449 Capability 'a'. Type 17184 Capability 'i'. Type 31092 Capability ' '. Type 24900 Capability 't'. Type 8289 Capability '2'. Type 12334 Tx Data:10 32 02 41 00 8b 10 03 : A.... Rx Data:10 06 02 32 00 c6 10 03=20 Rx Data:00 <--- At this point, the message "GPS_Pack= et_Read: No DLE" is displayed on the screen. <--- At this point, the message "GARMIN:Can't init COM1" is displayed on t= he screen. ++++++++++++++++++++++++++ Additionally, the invocation string that GASK generates (gpsbabel =96D9 -i = xcsv,style=3Dgsak.stl -f babel.txt -vs -o garmin -F COM1 <-- D9 added by m= e.) produces a similar error output. What does the =96vs switch do? =20 Jim |
From: <uru...@ix...> - 2004-05-06 14:54:46
|
In answer to the question "Is it consistant?" Yes. I tried it on an earlier firmware version (2.01) and also a read from the d= evice and a GASK write to the devive. See below: C:\bab>gpsbabel -D9 -i xcsv,style=3Dgsak.stl -f babel.txt -vs -o garmin -F = COM1 GPSBabel Version: 1.2.3 Tx Data:10 fe 00 02 10 03 : ... Rx Data:10 06 02 fe 00 fa 10 03 Rx Data:10 ff 13 4d 00 c9 00 47 50 53 20 31 32 20 20 20 32 2e 30 31 20 00 2= a 10 03 Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12 2.01 ID: 77 Version: 2.01 Rx Data:00 GPS_Packet_Read: No DLE Tx Data:10 06 02 ff 00 f9 10 03 : .....Capability 'M'. Type 51456 Capability ' Capability 'S'. Type 12576 Capability '2'. Type 8224 Capability ' '. Type 11826 Capability '0'. Type 8241 Tx Data:10 32 02 41 00 8b 10 03 : A.... Rx Data:10 06 02 32 00 c6 10 03 Rx Data:00 GPS_Packet_Read: No DLE GARMIN:Can't init COM1 C:\bab>gpsbabel -D9 -i garmin -f COM1 GPSBabel Version: 1.2.3 Tx Data:10 fe 00 02 10 03 : ... Rx Data:10 06 02 fe 00 fa 10 03 Rx Data:10 ff 13 4d 00 c9 00 47 50 53 20 31 32 20 20 20 32 2e 30 31 20 00 2= a 10 03 Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12 2.01 ID: 77 Version: 2.01 Rx Data:00 GPS_Packet_Read: No DLE Tx Data:10 06 02 ff 00 f9 10 03 : .....Capability 'M'. Type 51456 Capability ' Capability 'S'. Type 12576 Capability '2'. Type 8224 Capability ' '. Type 11826 Capability '0'. Type 8241 Tx Data:10 32 02 41 00 8b 10 03 : A.... Rx Data:10 06 02 32 00 c6 10 03 Rx Data:00 GPS_Packet_Read: No DLE GARMIN:Can't init COM1 Jim -----Original Message----- [snip] > Here is what I get: >=20 > Tx Data:10 fe 00 02 10 03 : ... > Rx Data:10 06 02 fe 00 fa 10 03=20 > Rx Data:10 ff 3e 60 00 90 01 47 50 53 20 31 32 58 4c 20 53 4f 46 54 57 41= 52 45 20 20 34 2e 30 30 20 00 56 45 52 42 4d 41 50 20 4e 20 41 6d 65 72 69= 63 61 20 43 69 74 79 20 44 61 74 61 20 32 2e 30 31 00 93 10 03=20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12XL SOFTWARE 4.00=20 > ID:=09=0996 >=20 > Version:=094.00 >=20 >=20 > Rx Data:00=20 Bwwwwoooop! Right here is where we go wrong. You absolutely should not be receiving a zero byte from the unit at this time. Is this consistent or intermittent? =20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....Capability '`'. Type 36864 > Capability '=01'. Type 20551 > Capability 'S'. Type 12576 > Capability '2'. Type 19544 > Capability ' '. Type 20307 > Capability 'F'. Type 22356 > Capability 'A'. Type 17746 <--- At this point, the message "[ERROR] PR= OTOCOL ERROR: Unknown tag/data [A/17746]" is displayed on the screen. > Capability ' '. Type 13344 > Capability '.'. Type 12336 > Capability ' '. Type 22016 > Capability 'E'. Type 16978 > Capability 'M'. Type 20545 Now that I can put it in context: > Rx Data:10 ff 3e 60 00 90 01 47 50 53 20 31 32 58 4c 20 53 4f 46 54 57 41= 52 45 20 20 34 2e 30 30 20 00 56 45 52 42 4d 41 50 20 4e 20 41 6d 65 72 69= 63 61 20 43 69 74 79 20 44 61 74 61 20 32 2e 30 31 00 93 10 03=20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12XL SOFTWARE 4.00=20 The control A is the first '01' in that buffer. Let's count along =09^AGPS 12XL SOFTWARE 4 +=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D See the pattern? When we got this packet starting with a zero (which I'm 95% sure we shouldn't get) we reused the previous packet. This is becuase the parser KNOWS all valid packets start with a DLE.... > Rx Data:10 06 02 32 00 c6 10 03=20 > Rx Data:00 <--- At this point, the message "GPS_Pa= cket_Read: No DLE" is displayed on the screen. But doesn't start fussing until after the comm link is up; after all, SOME of the packets came with DLEs so we were able to get off the ground. So I have to ask "are there any 12XL owners out there that are succeeding?" [snip] |
From: Robert L. <rob...@us...> - 2004-05-06 15:22:51
|
uru...@ix... wrote: > I tried it on an earlier firmware version (2.01) and also a read from the device and a GASK write to the devive. See below: It's croaking way before it ever makes the distinction between reading and writing. In every case you showed me, we are seeing a NUL where section 4.1.1 of Garmin's comm spec says there must not be one. > Rx Data:00 GPS_Packet_Read: No DLE > Rx Data:00 GPS_Packet_Read: No DLE > Rx Data:00 GPS_Packet_Read: No DLE > Rx Data:00 GPS_Packet_Read: No DLE Does anyone else have a 12xl that can share stories of success or failure? RJL |
From: Robert L. <rob...@us...> - 2004-05-05 20:44:45
|
> Actually, I just started to work with this. The first version I used was= 1.2.2 supplied with GSAK. That version failed too. I have no experience = with earlier versions. OK, so this isn't new breakage; you're a new user. That helps. > Here is what I get: >=20 > Tx Data:10 fe 00 02 10 03 : ... > Rx Data:10 06 02 fe 00 fa 10 03=20 > Rx Data:10 ff 3e 60 00 90 01 47 50 53 20 31 32 58 4c 20 53 4f 46 54 57 41= 52 45 20 20 34 2e 30 30 20 00 56 45 52 42 4d 41 50 20 4e 20 41 6d 65 72 69= 63 61 20 43 69 74 79 20 44 61 74 61 20 32 2e 30 31 00 93 10 03=20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12XL SOFTWARE 4.00=20 > ID: 96 >=20 > Version: 4.00 >=20 >=20 > Rx Data:00=20 Bwwwwoooop! Right here is where we go wrong. You absolutely should not be receiving a zero byte from the unit at this time. Is this consistent or intermittent? =20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....Capability '`'. Type 36864 > Capability '=01'. Type 20551 > Capability 'S'. Type 12576 > Capability '2'. Type 19544 > Capability ' '. Type 20307 > Capability 'F'. Type 22356 > Capability 'A'. Type 17746 <--- At this point, the message "[ERROR] PR= OTOCOL ERROR: Unknown tag/data [A/17746]" is displayed on the screen. > Capability ' '. Type 13344 > Capability '.'. Type 12336 > Capability ' '. Type 22016 > Capability 'E'. Type 16978 > Capability 'M'. Type 20545 Now that I can put it in context: > Rx Data:10 ff 3e 60 00 90 01 47 50 53 20 31 32 58 4c 20 53 4f 46 54 57 41= 52 45 20 20 34 2e 30 30 20 00 56 45 52 42 4d 41 50 20 4e 20 41 6d 65 72 69= 63 61 20 43 69 74 79 20 44 61 74 61 20 32 2e 30 31 00 93 10 03=20 > Tx Data:10 06 02 ff 00 f9 10 03 : .....GPS 12XL SOFTWARE 4.00=20 The control A is the first '01' in that buffer. Let's count along ^AGPS 12XL SOFTWARE 4 +=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D=3D+=3D See the pattern? When we got this packet starting with a zero (which I'm 95% sure we shouldn't get) we reused the previous packet. This is becuase the parser KNOWS all valid packets start with a DLE.... > Rx Data:10 06 02 32 00 c6 10 03=20 > Rx Data:00 <--- At this point, the message "GPS_Pa= cket_Read: No DLE" is displayed on the screen. But doesn't start fussing until after the comm link is up; after all, SOME of the packets came with DLEs so we were able to get off the ground. So I have to ask "are there any 12XL owners out there that are succeeding?" > What does the ?vs switch do? "Verbose status" It gives GSAK the realtime count of waypoints in flight so it can tick progress status bars. RJL |