|
From: Marco v. L. <mas...@gm...> - 2016-12-20 08:20:31
|
Hi Gary, all, The protocol on the device is set to 'GARMIN'. There is a second protocol garmin - something (GPC?), which has some additional options, such as baud rate etc. I can try that one, but it did not look promising on the device side (some of the option boxes stayed blank). Best regards, Marco. On Sun, Dec 18, 2016 at 11:46 PM, Gary Turner <g...@el...> wrote: > What protocol is your Garmin set to? > > On 18/12/2016 05:19, Marco van Leeuwen wrote: > > Dear all, > > I hope this is the right place to post my question. I have an old Garmin > eTrex legend device and am trying to retrieve some (old) tracks from it. > The device is connected to my PC via a serial-to-USB device. I am running > Ubuntu 16.04. The device shows up as /dev/ttyUSB0. > (from dmesg: > > [ 960.747772] usb 3-1: new full-speed USB device number 3 using xhci_hcd > [ 960.876241] usb 3-1: New USB device found, idVendor=067b, idProduct=2303 > [ 960.876246] usb 3-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 960.876702] pl2303 3-1:1.0: pl2303 converter detected > [ 960.877388] usb 3-1: pl2303 converter now attached to ttyUSB0 > > ) > > When I do: > > gpsbabel -t -i garmin -f /dev/ttyUSB0 -o gpx -F track.gpx > > I get: > > [ERROR] A800_Off: Not acknowledged > GPS_Packet_Read: No DLE. Data received, but probably not a garmin packet. > > I've read that retrying sometimes helps, but I get: > > gpsbabel -t -i garmin -f /dev/ttyUSB0 -o gpx -F track.gpx > GARMIN:Can't init /dev/ttyUSB0 > > I can unplug the USB-to-serial device and try again, but it only gives me > one show and always the same error. > > I've also tried with the debug options: > > gpsbabel -D9 -i garmin -f /dev/ttyUSB0 -o gpx -F track.gpx > > GPSBabel Version: 1.5.2 > GPS Serial Open at 9600 > Tx Data:10 fe 00 02 10 03 : ...(PRDREQ ) > Rx Data:10 15 02 02 00 e7 10 03 .. (NAK ) > GARMIN:Can't init /dev/ttyUSB0 > [AliEnv] mvl@multatuli:~$ gpsbabel -D9 -i garmin -f /dev/ttyUSB0 -o gpx > -F track.gpx > GPSBabel Version: 1.5.2 > GPS Serial Open at 9600 > Tx Data:10 fe 00 02 10 03 : ...(PRDREQ ) > Rx Data:10 06 02 fe 00 fa 10 03 .. (ACK ) > Rx Data:10 ff 85 b3 00 86 01 65 54 72 65 78 20 4c 65 67 65 6e 64 20 53 6f > 66 74 77 61 72 65 20 56 65 72 73 69 6f 6e 20 33 2e 39 30 00 56 45 52 42 4d > 41 50 20 41 74 6c 61 6e 74 69 63 20 48 69 67 68 77 61 79 20 31 2e 30 30 00 > 56 45 52 53 4d 41 50 20 43 41 4d 45 52 4f 4e 2c 20 41 5a 20 28 57 45 53 54 > 29 2c 20 47 4c 45 4e 20 43 41 4e 59 4f 4e 20 44 41 4d 2c 20 41 5a 20 28 57 > 45 53 54 29 2c 20 47 52 20 30 2e 30 30 00 bb 10 03 > ....eTrex.Legend.Software.Version.3.90.VERBMAP.Atlantic. > Highway.1.00.VERSMAP.CAMERON..AZ..WEST...GLEN.CANYON.DAM..AZ..WEST...GR.0.00. > (PRDDAT ) > Tx Data:10 06 02 ff 00 f9 10 03 : .....(ACK ) > Unit: eTrex Legend Software Version 3.90 > ID: 179 > Version: 3.90Rx Data:10 fd 4b 50 00 00 4c 01 00 41 0a 00 41 64 00 44 6c > 00 41 c9 00 44 ca 00 44 6c 00 44 d2 00 41 2d 01 44 36 01 44 2d 01 41 f4 01 > 44 f5 01 41 58 02 44 58 02 41 bc 02 44 bc 02 41 20 03 44 20 03 41 22 03 44 > 22 03 41 84 03 41 86 03 41 87 03 a0 10 03 P..L..A..Ad.Dl.A..D..Dl.D..A. > .D6.D..A..D..AX.DX.A..D..A..D..A..D..A..A..A.. (UNKNOWN ) > Tx Data:10 06 02 fd 00 fb 10 03 : .....(SESACK ) > > Capability A10: > Capability A100: D108 > Capability A201: D202 D108 D210 > Capability A301: D310 D301 > Capability A500: D501 > Capability A600: D600 > Capability A700: D700 > Capability A800: D800 > Capability A802: D802 > Capability A900: > Capability A902: > Capability A903: > Link_type 1 Device_command 0 > Waypoint: Transfer 100 Type 108 > Route: Transfer 201 Header 202 Type 108 > Track: Transfer 301 Type 301 > Tx Data:10 0a 02 32 00 c2 10 03 : 2....(CMDDAT Xfer PVT Stop) > Rx Data:10 63 0c 00 ff 30 31 2d 41 55 47 2d 31 31 00 98 10 03 > ..01.AUG.11. (TRKHDR ) > [ERROR] A800_Off: Not acknowledged > GPS Serial Open at 9600 > Tx Data:10 0a 02 05 00 ef 10 03 : .....(CMDDAT Xfer Time) > Rx Data:10 06 02 0a 00 ee 10 03 .. (ACK ) > Rx Data:10 0e 08 02 0a dc 07 08 00 20 09 ca 10 03 ........ (DATTIM ) > Tx Data:10 06 02 0e 00 ea 10 03 : .....(ACK ) > GPS Serial Open at 9600 > Tx Data:10 0a 02 02 00 f2 10 03 : .....(CMDDAT Xfer Posn) > Rx Data:10 06 02 0a 00 ee 10 03 .. (ACK ) > Rx Data:10 11 10 10 dd 1b 32 e2 3a 34 e9 3f d4 c5 93 7c 4f 89 bf 3f bf 10 > 03 ..2..4......O... (POS ) > Tx Data:10 06 02 11 00 e7 10 03 : .....(ACK ) > Waypoint type: 108 > Chosen waypoint length 10 > GPS Serial Open at 9600 > Tx Data:10 0a 02 07 00 ed 10 03 : .....(CMDDAT Xfer Wpt) > GPS_Packet_Read: No DLE. Data received, but probably not a garmin packet. > [ERROR] A100_Get: No acknowledge > GARMIN:Can't get waypoint from /dev/ttyUSB0 > > or with -t: > > gpsbabel -D9 -t -i garmin -f /dev/ttyUSB0 -o gpx -F track.gpx > GPSBabel Version: 1.5.2 > GPS Serial Open at 9600 > Tx Data:10 fe 00 02 10 03 : ...(PRDREQ ) > Rx Data:10 15 02 02 00 e7 10 03 .. (NAK ) > GARMIN:Can't init /dev/ttyUSB0 > [AliEnv] mvl@multatuli:~$ gpsbabel -D9 -t -i garmin -f /dev/ttyUSB0 -o > gpx -F track.gpx > GPSBabel Version: 1.5.2 > GPS Serial Open at 9600 > Tx Data:10 fe 00 02 10 03 : ...(PRDREQ ) > Rx Data:10 06 02 fe 00 fa 10 03 .. (ACK ) > Rx Data:10 ff 85 b3 00 86 01 65 54 72 65 78 20 4c 65 67 65 6e 64 20 53 6f > 66 74 77 61 72 65 20 56 65 72 73 69 6f 6e 20 33 2e 39 30 00 56 45 52 42 4d > 41 50 20 41 74 6c 61 6e 74 69 63 20 48 69 67 68 77 61 79 20 31 2e 30 30 00 > 56 45 52 53 4d 41 50 20 43 41 4d 45 52 4f 4e 2c 20 41 5a 20 28 57 45 53 54 > 29 2c 20 47 4c 45 4e 20 43 41 4e 59 4f 4e 20 44 41 4d 2c 20 41 5a 20 28 57 > 45 53 54 29 2c 20 47 52 20 30 2e 30 30 00 bb 10 03 > ....eTrex.Legend.Software.Version.3.90.VERBMAP.Atlantic. > Highway.1.00.VERSMAP.CAMERON..AZ..WEST...GLEN.CANYON.DAM..AZ..WEST...GR.0.00. > (PRDDAT ) > Tx Data:10 06 02 ff 00 f9 10 03 : .....(ACK ) > Unit: eTrex Legend Software Version 3.90 > ID: 179 > Version: 3.90Rx Data:10 fd 4b 50 00 00 4c 01 00 41 0a 00 41 64 00 44 6c > 00 41 c9 00 44 ca 00 44 6c 00 44 d2 00 41 2d 01 44 36 01 44 2d 01 41 f4 01 > 44 f5 01 41 58 02 44 58 02 41 bc 02 44 bc 02 41 20 03 44 20 03 41 22 03 44 > 22 03 41 84 03 41 86 03 41 87 03 a0 10 03 P..L..A..Ad.Dl.A..D..Dl.D..A. > .D6.D..A..D..AX.DX.A..D..A..D..A..D..A..A..A.. (UNKNOWN ) > Tx Data:10 06 02 fd 00 fb 10 03 : .....(SESACK ) > > Capability A10: > Capability A100: D108 > Capability A201: D202 D108 D210 > Capability A301: D310 D301 > Capability A500: D501 > Capability A600: D600 > Capability A700: D700 > Capability A800: D800 > Capability A802: D802 > Capability A900: > Capability A902: > Capability A903: > Link_type 1 Device_command 0 > Waypoint: Transfer 100 Type 108 > Route: Transfer 201 Header 202 Type 108 > Track: Transfer 301 Type 301 > Tx Data:10 0a 02 32 00 c2 10 03 : 2....(CMDDAT Xfer PVT Stop) > Rx Data:10 23 39 00 ff 00 60 12 00 00 00 00 00 00 00 ff ff ff ff ff ff ff > ff ff ff ff ff 98 af 1b 25 02 b3 b8 03 c0 58 bf 41 51 59 04 69 51 59 04 69 > 20 20 20 20 30 32 39 00 00 00 00 00 00 e7 10 03 > .................................X.AQY.iQY.i....029...... (WPTDAT ) > [ERROR] A800_Off: Not acknowledged > GPS Serial Open at 9600 > Tx Data:10 0a 02 05 00 ef 10 03 : .....(CMDDAT Xfer Time) > Rx Data:10 15 02 02 00 e7 10 03 .. (NAK ) > GPS Serial Open at 9600 > Tx Data:10 0a 02 02 00 f2 10 03 : .....(CMDDAT Xfer Posn) > Rx Data:10 06 02 0a 00 ee 10 03 .. (ACK ) > Rx Data:10 11 10 10 dd 1b 32 e2 3a 34 e9 3f d4 c5 93 7c 4f 89 bf 3f bf 10 > 03 ..2..4......O... (POS ) > Tx Data:10 06 02 11 00 e7 10 03 : .....(ACK ) > Waypoint type: 108 > Chosen waypoint length 10 > GPS Serial Open at 9600 > Tx Data:10 0a 02 06 00 ee 10 03 : .....(CMDDAT Xfer Trk) > Rx Data:10 23 39 00 ff 00 60 12 00 00 00 00 00 00 00 ff ff ff ff ff ff ff > ff ff ff ff ff 0e 3a 13 25 08 56 b3 03 00 48 8f 41 51 59 04 69 51 59 04 69 > 20 20 20 20 30 33 31 00 00 00 00 00 00 51 10 03 > .............................V...H.AQY.iQY.i....031...... (WPTDAT ) > cet_util: Converting from "US-ASCII" to "UTF-8", done. > options: module/option=value: gpx/snlen="32" (=default) > > ------------ > > Let me know if there is anything I can try to fix this; if needed, I would > be happy to play a bit with the code, but pointers to where to start > looking would be helpful. It could be that the UDB-to-serial device is > flaky; it's definitely old, but has worked in the past. > > Best regards, > > Marco. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Gpsbabel-misc mailing list http://www.gp...@li... > To unsubscribe, change list options, or see archives, visit:https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > |
