[Gpsbabel-misc] MiniHomer: Problems downloading tracks
Brought to you by:
robertl
From: Olaf P. <ol...@la...> - 2011-12-06 18:10:11
|
Hi everyone, I am facing problems to download data from my MiniHomer logger, using GPSBabel ver. 1.4.3-beta20111112 on MS Windows 7 Home Premium SP1. The logger was updated to the FNAM Sports 4 - firmware and everything runs fine on nTrip 1.2.14 When I try to invoke GPSBabel with "gpsbabel -D3 -i miniHomer,baud=38400,read-at-once=0 -f com3 -x height,wgs84tomsl -x track,split=1h,title="TRACK" -o gtm -F c:\Users\olafpe\Documents\GPS\lasttrack.gtm" I get an error message "Error reading sector #0". Same if I try to dump-file. I have appended a full printout at the end of this message. Each time, GPSBabel pauses for a few moments after printing the line "Reading sector #0", on a higher debug-level it can be seen that the MiniHomer only sends NMEA-data meanwhile, so I do have the idea that a new binary command-set is used in the newer firmware-versions. When I experiment with first-sector and last-sector options, all I manage is to download the POIs when I force GPSBabel to read an empty sector by e.g. setting first-sector and last-sector to 2. Only then a GTM-file is created. It is no problem to delete the MiniHomer's log using GPSBabel. Should I return to a previous firmware version? FNAM Sports 3 won't do the job. Thank you in advance! Olaf Printout follows 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="0" Translated port name: "com3" skytraq: Probing SkyTraq Venus at 38400baud... Receiving message with 2 bytes of payload (expected >=2) Receiving message with 2 bytes of payload (expected >=2) Got ACK (id=0x02) Receiving message with 14 bytes of payload (expected >=14) skytraq: Venus device found: Kernel version = 1.4.42, ODM version = 1.4.41, revision (Y/M/D) = 11/03/23 Receiving message with 2 bytes of payload (expected >=2) Receiving message with 2 bytes of payload (expected >=2) Got ACK (id=0x17) Receiving message with 37 bytes of payload (expected >=9) skytraq: Device status: free sectors: 509 / total sectors: 509 / 0% used / write ptr: 10996 skytraq: Reading log data from device... skytraq: start=0 used=1 skytraq: opt_last_sector_val=-1 Reading sector #0... Receiving message with 2 bytes of payload (expected >=2) Receiving message with 2 bytes of payload (expected >=2) Got ACK (id=0x1b) skytraq: Didn't get sector end tag Reading sector #0... Receiving message with 2 bytes of payload (expected >=2) Receiving message with 2 bytes of payload (expected >=2) Got ACK (id=0x1b) skytraq: Didn't get sector end tag Reading sector #0... Receiving message with 2 bytes of payload (expected >=2) Receiving message with 2 bytes of payload (expected >=2) Got ACK (id=0x1b) skytraq: Didn't get sector end tag -- Olaf Petersen <ol...@la...> |