igotu2gpx 0.3.0 on Windows

Asked by hopet on 2009-11-07

I'm having problem with igotu2gpx 0.3.0 on Windows XP SP3 Czech - it can't open port created by the MobileAction driver.
The COM port numbers for the device are rather high (usually COM16 or higher) and says something like:
$ ./igotu2gpx.exe -d serial:16 dump
Downloading tracks...
Unable to download trackpoints from GPS tracker: Unable to open device 'COM16':
Systém nemůže nalézt uvedený soubor.
(the last message is a Czech version of "System can't find given file.")
The message is printed immediately. If I try to use low COM port numbers (real COM ports with no device attached),
it takes much longer and I get a different reply:
$ ./igotu2gpx.exe -d serial:3 dump
Downloading tracks...
Unable to download trackpoints from GPS tracker: Response too short: expected 3,
 got 0 bytes

It looks to me like there's some igotu2gpx compatibility problem with the higher COM port numbers.

Few observations:
- @trip works fine on the same machine (but I'd prefer using igotu2gpx for more complete export of data to GPX)
- igotu2gpx both versions 0.3.0 and trunk (see my previous question with patch) work on Ubuntu 8.04 LTS on the same machine

Question information

Language:
English Edit question
Status:
Solved
For:
igotu2gpx Edit question
Assignee:
No assignee Edit question
Last query:
2009-11-07
Last reply:
2010-02-14
Michael Hofmann (mh21) said : #1

Thanks for your question and sorry for the late answer.

Hmm, weird. Can you change the COM port somewhere in the configuration panel to sth lower and see whether it works then? If the serial port exists, then opening comXX is normally the way to go on WIndows.

hopet (hopet) said : #2

Michael, it will take some time as I've migrated to the Windows 7 64b in the meantime, where there's no working driver at all (there're two of them available through the a-trip forum, e.g. http://www.a-trip.com/forum/viewtopic.php?t=897, but both of them panic the final version of Windows 7 that I have once I try to access the device). I will be able to switch back to WinXP for the test, but it will be at least a week from now.

Launchpad Janitor (janitor) said : #3

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Hello. I have *exactly* the same problem on Windows Vista, with version 0.30 and a GT-120. I also tried to change port COM16 to COM1 using the Control Panel, but the result is the same.

Michael Hofmann (mh21) said : #6

I converted the question in a bug. There is a problem with port numbers greater 9.