igotu2gpx team mailing list archive

[Michael Hofmann <question89253@xxxxxxxxxxxxxxxxxxxxx>]

Question #89253 on igotu2gpx changed:
https://answers.edge.launchpad.net/igotu2gpx/+question/89253

    Status: Open => Needs information

Michael Hofmann requested for more information:
Hi medconsulting,

in the first trace, the tracker was not found (Gerät '0df7:0900' konnte
nicht gefunden werden), so that is something where igotu2gpx can't do
anything about it (just unplug it, reconnect it as you have done).

in the second trace, it never makes successful communication with the
device (the response to 930101030000000000000000000000, which is the
first command, is already invalid). This may be as the device is in NMEA
mode normally, so for some reason it can't be switched to normal mode
(replug it, yes :-).

And in the third one, nothing happens at all (weird, I have no idea
why).

I fear you have to try again :-(. Things to look out for:
- put the IGOTU2GPX_(NO)WORKAROUND=1 on the same line as the call to igotu2gpx, or use "export IGOTU2GPX_(NO)WORKAROUND=1"
- what you want is some valid communication (some commands with responses, as seen in the first post). It should fail (or, if solved with one of the env variables, just work), at 930507100004030000000000000000 (as can be also seen in the first post)
- valid commands can be recognized by "Kommando: 93*" followed by "Ergebnis: *"

Michael

-- 
You received this question notification because you are a member of
MobileAction i-gotU USB GPS travel logger Mac/Linux developers, which is
an answer contact for igotu2gpx.