Arch Linux

kabads

Member

Registered: 2012-09-22

Posts: 271

Website

[Solved] serial to usb not working - gpsbabel with garmin etrex

I'm trying to transfer some data from an old garmin etrex gps via a serial cable (Startech.com 1 Port FTDI USB to Serial RS232 Adapter Cable with COM Retention) which claims to work with linux.

However, I try:

$ sudo gpsbabel -i garmin  -f /dev/ttyUSB0 -o gpx -F /home/adam/mygpx.gpx  

and get -

GPS_Packet_Read: No DLE.  Data received, but probably not a garmin packet.
GARMIN:Can't init /dev/ttyUSB0

I seem to remember that this unit held garmin data, but instead I try -i gpx and the whole thing seems to hang for a very long time.

$ dmesg shows:

[ 2103.214817] usb 1-3: new full-speed USB device number 6 using xhci_hcd
[ 2103.441386] usbcore: registered new interface driver usbserial
[ 2103.441397] usbcore: registered new interface driver usbserial_generic
[ 2103.441405] usbserial: USB Serial support registered for generic
[ 2103.444029] usbcore: registered new interface driver ftdi_sio
[ 2103.444039] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 2103.444095] ftdi_sio 1-3:1.0: FTDI USB Serial Device converter detected
[ 2103.444119] usb 1-3: Detected FT232RL
[ 2103.444293] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0

Is there anyway I can start trying to read data from this device, or any tips to see what I can get out from this?

TIA

Last edited by kabads (2015-05-02 10:39:06)

nomorewindows

Member

Registered: 2010-04-03

Posts: 3,371

Re: [Solved] serial to usb not working - gpsbabel with garmin etrex

Try it without -i garmin and just let it autodetect.  Or use another gps program such as gpsman.

---

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

kabads

Member

Registered: 2012-09-22

Posts: 271

Website

Re: [Solved] serial to usb not working - gpsbabel with garmin etrex

OK - worked this one out in the end. Changed the type of data on the garmin etrex itself to 'garmin' and then gpsbabel worked fine.