Re: [Gpsbabel-misc] Another miniHomer question, accessing data
Brought to you by:
robertl
From: Josep D. <ly...@ym...> - 2012-03-28 16:24:37
|
Thanks for the quick replies, Roland and Josef! I set baud=38400 and tried sudo stty -F /dev/ttyUSB0 sane clocal -crtscts (the option -clocal caused it to hang). It looks to be communicating now, except I get the error: "skytraq: Too many read errors on serial port". I tried to follow a suggestion from the archives here: http://sourceforge.net/mailarchive/forum.php?thread_name=4DD3A008.7020301%40aol.com&forum_name=gpsbabel-misc However, thisstill didn't produce any output for me. > sudo /usr/sbin/gpsd /dev/ttyUSB0 > sudo stty -F /dev/ttyUSB0 sane clocal -crtscts > sudo gpsbabel -D 5 -i miniHomer,baud=38400 -f /dev/ttyUSB0 -o gpx -F out.gpx GPSBabel Version: 1.4.3 options: module/option=value: miniHomer/baud="38400" options: module/option=value: miniHomer/erase="0" (=default) options: module/option=value: miniHomer/first-sector="0" (=default) options: module/option=value: miniHomer/initbaud="38400" (=default) options: module/option=value: miniHomer/last-sector="-1" (=default) options: module/option=value: miniHomer/no-output="0" (=default) options: module/option=value: miniHomer/read-at-once="255" (=default) gbser_init("/dev/ttyUSB0") skytraq: Probing SkyTraq Venus at 38400baud... Sending: a0 '.' Sending: a1 '.' Sending: 00 '.' Sending: 02 '.' Sending: 02 '.' Sending: 01 '.' Sending: 03 '.' Sending: 0d '.' Sending: 0a '.' skytraq: rd_char(): Got error: -1 skytraq: rd_char(): Got error: -1 skytraq: rd_char(): Got error: -1 skytraq: rd_char(): Got error: -1 skytraq: rd_char(): Got error: -1 skytraq: Too many read errors on serial port > ^C > sudo stty -F /dev/ttyUSB0 115200 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C > sudo stty -F /dev/ttyUSB0 57600 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C > sudo stty -F /dev/ttyUSB0 38400 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C > sudo stty -F /dev/ttyUSB0 9600 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C > sudo stty -F /dev/ttyUSB0 19200 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C > sudo stty -F /dev/ttyUSB0 230400 sane clocal -crtscts > sudo cat /dev/ttyUSB0 ^C Additionally, in case there was gpsd interference, I tried: # killall gpsd # /usr/sbin/gpsd /dev/ttyUSB0 # stty -F /dev/ttyUSB0 38400 sane clocal -crtscts # gpsbabel -D 5 -i miniHomer,baud=38400 -f /dev/ttyUSB0 -o gpx -F out.gpx ... (same as before) skytraq: Too many read errors on serial port I tried using different usb ports, and can track down another cable if this seems a potential issue. The miniHomer is brand new, so I wanted to make sure it was functional in the period I could still return it. >________________________________ > From: Josef Reisinger <dat...@ao...> >To: gps...@li...; ly...@ym...; rol...@gm... >Sent: Wednesday, March 28, 2012 2:13 AM >Subject: Re: [Gpsbabel-misc] Another miniHomer question, accessing data > >The pl2303 driver on Linux sometimes behaves very "peculiar" ... > >I a client program cannot open /dev/ttyUSB[0-9], I usually issue a 'stty -F /dev/ttyUSB0 sane clocal -crtscts' which most of the time sorts the things our for me. Sometimes I even switch between >'stty -F /dev/ttyUSB0 sane -clocal -crtscts' and 'stty -F /dev/ttyUSB0 sane clocal -crtscts' (the difference is the '-' before clocal!). > >The might be interference with a running gpsd - or issues with the USB port and/or cable. Sounds all not very logical, I know, but experience has shown it helps to look after all these items. > >Hope that helps. > >Roland, you mentioned there are other miniHomer posts - I just returned from vacation (where I logged ~4 weeks of tracks on the miniHomer with a 97% fill level) and I did not follow the list. If it does not create too much effort, could you point me to these entries or sketch what time of issue where mentioned ? > >Kind regards > >Josef Reisinger > >On 28.03.2012 07:48, Roland Wirth wrote: >> Hi, >> I think you have to use baud=38400, >> baudrate 115200 is a wrong default! >> >> Roland >> >> Am 28.03.2012 02:53, schrieb roidemai: >>> Hi, >>> >>> I saw a couple of other miniHomer posts, but I didn't seem to get as far as >>> those users. Using gpsbabel 1.4.3, I'm unable to access the gps logs, and it >>> just hangs whenever I try. Here's some more info and the things I attempted: >>> >>>> uname -a >>> Linux linux-8nxi.site 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 >>> 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux >>> >>>> dmesg >>> [32651.277608] usb 2-1.1: new full speed USB device using ehci_hcd and >>> address 3 >>> [32651.363135] usb 2-1.1: New USB device found, idVendor=067b, >>> idProduct=2303 >>> [32651.363138] usb 2-1.1: New USB device strings: Mfr=1, Product=2, >>> SerialNumber=0 >>> [32651.363141] usb 2-1.1: Product: USB-Serial Controller D >>> [32651.363143] usb 2-1.1: Manufacturer: Prolific Technology Inc. >>> [32651.530552] usbcore: registered new interface driver usbserial >>> [32651.530565] USB Serial support registered for generic >>> [32651.530597] usbcore: registered new interface driver usbserial_generic >>> [32651.530599] usbserial: USB Serial Driver core >>> [32651.540700] USB Serial support registered for pl2303 >>> [32651.540734] pl2303 2-1.1:1.0: pl2303 converter detected >>> [32651.542331] usb 2-1.1: pl2303 converter now attached to ttyUSB0 >>> [32651.542351] usbcore: registered new interface driver pl2303 >>> [32651.542353] pl2303: Prolific PL2303 USB to serial adaptor driver >>>> sudo /usr/sbin/gpsd /dev/ttyUSB0 >>>> sudo gpsbabel -D 5 -i miniHomer,erase -f /dev/ttyUSB0 -o gpx -F out.gpx >>> root's password: >>> GPSBabel Version: 1.4.3 >>> options: module/option=value: miniHomer/baud="115200" (=default) >>> options: module/option=value: miniHomer/erase="1" >>> options: module/option=value: miniHomer/first-sector="0" (=default) >>> options: module/option=value: miniHomer/initbaud="38400" (=default) >>> options: module/option=value: miniHomer/last-sector="-1" (=default) >>> options: module/option=value: miniHomer/no-output="0" (=default) >>> options: module/option=value: miniHomer/read-at-once="255" (=default) >>> gbser_init("/dev/ttyUSB0") >>> ^C >>> >>> # rmmod pl2303 usbserial >>> # modprobe pl2303 >>> # stty -F /dev/ttyUSB0 38400 >>> # cat /dev/ttyUSB0 >>> ^C >>> >>> Any ideas as to what is happening or what I'm doing incorrectly? Thanks in >>> advance. >>> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Gpsbabel-misc mailing list http://www.gpsbabel.org >> Gps...@li... >> To unsubscribe, change list options, or see archives, visit: >> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > > > |