Quantcast

Problem reading tracks from eTrex Legend via USB-to-serial interface

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Problem reading tracks from eTrex Legend via USB-to-serial interface

Marco van Leeuwen
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.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Gary Turner-6

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.gpsbabel.org
[hidden email]
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
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Marco van Leeuwen
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 <[hidden email]> 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.gpsbabel.org
[hidden email]
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
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Robert Lipe-4
In reply to this post by Marco van Leeuwen
Hi, and welcome.

Yes, it's the right list. Unfortunately, when you have the intersection of minority configurations, finding someone with experience witht hat combination can be difficult, so hopefully someone else with a 15 y/o device using Linux can share their experience.

Do we have any Linux users that can confirm success with serial Garmins?


USB serial adapters are pretty well known in the industry to be annoying and on Linux, even more so. However, your configuration is not working in a way that's not common.  As you can deduce from the debug info (thank you for finding that and including it...) Garmin serial packets start with "10 something" and end with "10 3". There may be exceptions, but that's the basic rule here.

Garmin serial protocol starts with a handshake that's much like a human introduction.

You "Tell me about yourself" (PRDREQ)
GPS "OK. [ details ] ] (ACK + PRDAT)
You "Thank you" (ACK)
You "Oh, I see you have type 108 waypoints. Those are lovely. Give me a list, please."
GPSS "OK. [ details ]" (ACK + WPTDAT)

Garmin protocol is a conversation: the host asks questions and gives instructions and the device acknowledges them and responds. It's not like a lot of the logger products where it's basically a unidirectional dump of memory.


Your "conversations" are working too well for the serial driver place to be totally broken, but there is some evidence that the GPS isn't getting all the data we're actually sending.  For example:

Tx Data:10 fe 00 02 10 03 : ...(PRDREQ  )
Rx Data:10 15 02 02 00 e7 10 03  .. (NAK     )

Here, we've sent a very simple command (the "tell me about yourself") but instead of "OK", it said "I don't understand".  (Arguably, we probably should try again and in some cases we might, but here, we clearly don't.)  So in the process of sending those six bytes, the device said "I saw something that looked Garmin protocol-ish, but I don't know what it is."   So it's very likely that the data we sent isn't actually what went over the wire. There are other cases where the connection is corrupt - see the NAK or No DLE cases. 

I don't think we have a lot of serial Garmin users these days and surely even fewer on Linux.  If you have another USB/Serial adapter that uses a different chip (that one is using Prolific, try one with FTDI or maybe even just a different Prolific device - PL2303's are often reverse-engineered and cloned by other companies) If you have access to another computer/OS, try it there, too. The symptoms could be noise on the serial data lines, so be sure everythings plugged solidly on the RS-232 path.

If this is a one-shot need and not a recurring issue there are escalations we can try, but let's try the easier things first.  If you repeat the same command several times in a row, does it stop in the same place every time?

A borrowed Legend and Vista were some of the first Garmins that I added, so they did work at one point. Of course, there have been firmware updates, GPSBabel's changed, and the state of USB/serial drivers have all changed over the last 15 years.

Confirm that the unit is not set for NMEA. It doesn't look like it is, since it's clearly responding to Garmin conversations, but NMEA makes the device spit up position data every two (?) seconds and interrupt other conversations. 


On Sat, Dec 17, 2016 at 10:19 AM, Marco van Leeuwen <[hidden email]> 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.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Robert Lipe-4
Oh, it's worth saying that once it's failed, you should probably reset the device. Once the conversation has jumped the rails, it will sometimes get stuck.

You: "What books have you read"
GPS [starts list ]
You: repeat that, please? (or the GPS doesn't understand the "repeat that" or a crash or whatever) and then walks away.

Someone else then comes along and asks what movies you've seen, but the GPS is still listing books. 


I think that's what's happening in case 3 above: we've asked for a list of trackpoints, but the device is still babbling waypoints from an earlier failed conversation.

On Tue, Dec 20, 2016 at 11:12 AM, Robert Lipe <[hidden email]> wrote:
Hi, and welcome.

Yes, it's the right list. Unfortunately, when you have the intersection of minority configurations, finding someone with experience witht hat combination can be difficult, so hopefully someone else with a 15 y/o device using Linux can share their experience.

Do we have any Linux users that can confirm success with serial Garmins?


USB serial adapters are pretty well known in the industry to be annoying and on Linux, even more so. However, your configuration is not working in a way that's not common.  As you can deduce from the debug info (thank you for finding that and including it...) Garmin serial packets start with "10 something" and end with "10 3". There may be exceptions, but that's the basic rule here.

Garmin serial protocol starts with a handshake that's much like a human introduction.

You "Tell me about yourself" (PRDREQ)
GPS "OK. [ details ] ] (ACK + PRDAT)
You "Thank you" (ACK)
You "Oh, I see you have type 108 waypoints. Those are lovely. Give me a list, please."
GPSS "OK. [ details ]" (ACK + WPTDAT)

Garmin protocol is a conversation: the host asks questions and gives instructions and the device acknowledges them and responds. It's not like a lot of the logger products where it's basically a unidirectional dump of memory.


Your "conversations" are working too well for the serial driver place to be totally broken, but there is some evidence that the GPS isn't getting all the data we're actually sending.  For example:

Tx Data:10 fe 00 02 10 03 : ...(PRDREQ  )
Rx Data:10 15 02 02 00 e7 10 03  .. (NAK     )

Here, we've sent a very simple command (the "tell me about yourself") but instead of "OK", it said "I don't understand".  (Arguably, we probably should try again and in some cases we might, but here, we clearly don't.)  So in the process of sending those six bytes, the device said "I saw something that looked Garmin protocol-ish, but I don't know what it is."   So it's very likely that the data we sent isn't actually what went over the wire. There are other cases where the connection is corrupt - see the NAK or No DLE cases. 

I don't think we have a lot of serial Garmin users these days and surely even fewer on Linux.  If you have another USB/Serial adapter that uses a different chip (that one is using Prolific, try one with FTDI or maybe even just a different Prolific device - PL2303's are often reverse-engineered and cloned by other companies) If you have access to another computer/OS, try it there, too. The symptoms could be noise on the serial data lines, so be sure everythings plugged solidly on the RS-232 path.

If this is a one-shot need and not a recurring issue there are escalations we can try, but let's try the easier things first.  If you repeat the same command several times in a row, does it stop in the same place every time?

A borrowed Legend and Vista were some of the first Garmins that I added, so they did work at one point. Of course, there have been firmware updates, GPSBabel's changed, and the state of USB/serial drivers have all changed over the last 15 years.

Confirm that the unit is not set for NMEA. It doesn't look like it is, since it's clearly responding to Garmin conversations, but NMEA makes the device spit up position data every two (?) seconds and interrupt other conversations. 


On Sat, Dec 17, 2016 at 10:19 AM, Marco van Leeuwen <[hidden email]> 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.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc




------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Jakob Mühldorfer

I have an eTrex Vista from ~2003, and managed to upload tracks with a USB Serial adapter under Arch Linux:

gpsbabel -i gpx -f /tmp/to.gpx -x simplify,count=750 -o garmin -F /dev/ttyUSB0
Have not tested downloading them again.
When interacting with serial, the device shows some kind of on-screen message.
If you need me to test anything or that helps, let me know

Jakob

Am 20.12.2016 um 18:16 schrieb Robert Lipe:
Oh, it's worth saying that once it's failed, you should probably reset the device. Once the conversation has jumped the rails, it will sometimes get stuck.

You: "What books have you read"
GPS [starts list ]
You: repeat that, please? (or the GPS doesn't understand the "repeat that" or a crash or whatever) and then walks away.

Someone else then comes along and asks what movies you've seen, but the GPS is still listing books. 


I think that's what's happening in case 3 above: we've asked for a list of trackpoints, but the device is still babbling waypoints from an earlier failed conversation.

On Tue, Dec 20, 2016 at 11:12 AM, Robert Lipe <[hidden email]> wrote:
Hi, and welcome.

Yes, it's the right list. Unfortunately, when you have the intersection of minority configurations, finding someone with experience witht hat combination can be difficult, so hopefully someone else with a 15 y/o device using Linux can share their experience.

Do we have any Linux users that can confirm success with serial Garmins?


USB serial adapters are pretty well known in the industry to be annoying and on Linux, even more so. However, your configuration is not working in a way that's not common.  As you can deduce from the debug info (thank you for finding that and including it...) Garmin serial packets start with "10 something" and end with "10 3". There may be exceptions, but that's the basic rule here.

Garmin serial protocol starts with a handshake that's much like a human introduction.

You "Tell me about yourself" (PRDREQ)
GPS "OK. [ details ] ] (ACK + PRDAT)
You "Thank you" (ACK)
You "Oh, I see you have type 108 waypoints. Those are lovely. Give me a list, please."
GPSS "OK. [ details ]" (ACK + WPTDAT)

Garmin protocol is a conversation: the host asks questions and gives instructions and the device acknowledges them and responds. It's not like a lot of the logger products where it's basically a unidirectional dump of memory.


Your "conversations" are working too well for the serial driver place to be totally broken, but there is some evidence that the GPS isn't getting all the data we're actually sending.  For example:

Tx Data:10 fe 00 02 10 03 : ...(PRDREQ  )
Rx Data:10 15 02 02 00 e7 10 03  .. (NAK     )

Here, we've sent a very simple command (the "tell me about yourself") but instead of "OK", it said "I don't understand".  (Arguably, we probably should try again and in some cases we might, but here, we clearly don't.)  So in the process of sending those six bytes, the device said "I saw something that looked Garmin protocol-ish, but I don't know what it is."   So it's very likely that the data we sent isn't actually what went over the wire. There are other cases where the connection is corrupt - see the NAK or No DLE cases. 

I don't think we have a lot of serial Garmin users these days and surely even fewer on Linux.  If you have another USB/Serial adapter that uses a different chip (that one is using Prolific, try one with FTDI or maybe even just a different Prolific device - PL2303's are often reverse-engineered and cloned by other companies) If you have access to another computer/OS, try it there, too. The symptoms could be noise on the serial data lines, so be sure everythings plugged solidly on the RS-232 path.

If this is a one-shot need and not a recurring issue there are escalations we can try, but let's try the easier things first.  If you repeat the same command several times in a row, does it stop in the same place every time?

A borrowed Legend and Vista were some of the first Garmins that I added, so they did work at one point. Of course, there have been firmware updates, GPSBabel's changed, and the state of USB/serial drivers have all changed over the last 15 years.

Confirm that the unit is not set for NMEA. It doesn't look like it is, since it's clearly responding to Garmin conversations, but NMEA makes the device spit up position data every two (?) seconds and interrupt other conversations. 


On Sat, Dec 17, 2016 at 10:19 AM, Marco van Leeuwen <[hidden email]> 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.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc





------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel


_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Ralf Horstmann
In reply to this post by Marco van Leeuwen
I tried to reproduce on Fedora 25, with a GPSMap 60CSx set to "GARMIN" protocol
for the serial port. An FTDI USB serial adapter works pretty reliable, while my
Prolific adapter works or fails depending on the USB port being used.

My laptop has one USB port that attaches to a xhci controller like yours. With
that, the transmission fails with similar symptoms like you have seen. When I
either disable USB 3.0 support in BIOS setup or use a port that attaches to
ehci-hcd, the Prolific adapter tends to work.

If you have an option to use an USB 2.0 port, maybe that's worth a try.

Regards,
Ralf

* Marco van Leeuwen <[hidden email]> [2016-12-17 17:19]:

> 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.gpsbabel.org
> [hidden email]
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Marco van Leeuwen
Dear all,

Thanks for the responses and suggestions. I tried again with a different PC (am away from my main PC), which has only USB 2 ports, and Ubuntu 12.04, and there it works! 

So it seems that this was indeed an issue with USB3 and my USB-to-serial converter.

The retrieved tracks only have coordinates (longitude and latitude) and elevation information; I had hoped to retrieve also time information, but I guess that the eTrex Legends does not send this over serial; in fact, it may not even store it in tracks... I searched a bit for this and it seems to be a feature of the Garmin GPS, see e.g.: http://forums.gpsreview.net/discussion/12967/why-doesn-t-my-track-have-time-stamps

Best regards,

Marco.

On Tue, Dec 20, 2016 at 11:33 PM, Ralf Horstmann <[hidden email]> wrote:
I tried to reproduce on Fedora 25, with a GPSMap 60CSx set to "GARMIN" protocol
for the serial port. An FTDI USB serial adapter works pretty reliable, while my
Prolific adapter works or fails depending on the USB port being used.

My laptop has one USB port that attaches to a xhci controller like yours. With
that, the transmission fails with similar symptoms like you have seen. When I
either disable USB 3.0 support in BIOS setup or use a port that attaches to
ehci-hcd, the Prolific adapter tends to work.

If you have an option to use an USB 2.0 port, maybe that's worth a try.

Regards,
Ralf

* Marco van Leeuwen <[hidden email]> [2016-12-17 17:19]:
> 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.gpsbabel.org
> [hidden email]
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem reading tracks from eTrex Legend via USB-to-serial interface

Robert Lipe-4
Hooray for it being a bug that isn't ours. Hooray? :-)  Please do try to get the attention of whatever distro maintainers are involved that didn't let you get to your tracks.

It's true that Garmins of that decade famously compress "saved" tracks by throwing away time and the shape of most tracks. http://www.gpsfaqs.org/faqs/garmin/xseries/g60csx/tracks.html#notime touches on these issues, but the solutions for the USB era devices and yours are different and there is, unfortunately for you, nothing that can rescue them retroactively.

On Thu, Dec 22, 2016 at 3:04 AM, Marco van Leeuwen <[hidden email]> wrote:
Dear all,

Thanks for the responses and suggestions. I tried again with a different PC (am away from my main PC), which has only USB 2 ports, and Ubuntu 12.04, and there it works! 

So it seems that this was indeed an issue with USB3 and my USB-to-serial converter.

The retrieved tracks only have coordinates (longitude and latitude) and elevation information; I had hoped to retrieve also time information, but I guess that the eTrex Legends does not send this over serial; in fact, it may not even store it in tracks... I searched a bit for this and it seems to be a feature of the Garmin GPS, see e.g.: http://forums.gpsreview.net/discussion/12967/why-doesn-t-my-track-have-time-stamps

Best regards,

Marco.

On Tue, Dec 20, 2016 at 11:33 PM, Ralf Horstmann <[hidden email]> wrote:
I tried to reproduce on Fedora 25, with a GPSMap 60CSx set to "GARMIN" protocol
for the serial port. An FTDI USB serial adapter works pretty reliable, while my
Prolific adapter works or fails depending on the USB port being used.

My laptop has one USB port that attaches to a xhci controller like yours. With
that, the transmission fails with similar symptoms like you have seen. When I
either disable USB 3.0 support in BIOS setup or use a port that attaches to
ehci-hcd, the Prolific adapter tends to work.

If you have an option to use an USB 2.0 port, maybe that's worth a try.

Regards,
Ralf

* Marco van Leeuwen <[hidden email]> [2016-12-17 17:19]:
> 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.gpsbabel.org
> [hidden email]
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Loading...