Re: [Gpsbabel-misc] MacOS X - GPSBabel+ does not do anything
Brought to you by:
robertl
From: Dan W. <yg...@co...> - 2007-04-22 18:26:28
|
FWIW, I have no problem talking to my Magellan eXplorist 500 via USB -- I can see and swap files. It seems to me to be the 1.3.3 GUI wrapper that is the source of the problem. I need to try the command line part of that distro to see if the problem extends to it -- I kinda doubt it as the Quick Window worked. The Advanced Window is the problem. Please feel free to ask me to help with the testing. I'm happy to contribute effort to such projects. On Apr 22, 2007, at 8:23 AM, Gavin Treadgold wrote: > OK, I've run a few more tests. > > All these are done with a Garmin 60CSX so I could test USB as well (my > previously problems have been with my 76S). I have used both USB and a > Keyspan USA-19HS serial adapter. All were downloading waypoints and > tracks and saving to GPX. All used the matching versions of gpsbabel > and GPSBabel+. All these were done using the Quick GPSBabel window > (note that this runs counter to the previously reported problem of > Advanced GPSBabel). > > 1. USB download using GPSBabel+ > 1.3.0 downloaded OK > 1.3.2a downloaded OK > 1.3.3 downloaded OK > > 2. Serial download using GPSBabel+ > 1.3.0 downloaded OK (note that this actually displays the command run) > 1.3.2a failed "EXECUTE-> -NO ERROR" (note no command displayed) > 1.3.3 failed "EXECUTE-> -NO ERROR" (note no command displayed) > > 3. Serial download using gpsbabel commandline (./gpsbabel -w -t -i > garmin -f /dev/cu.USA19H3b1P1.1 -o gpx -F test.gpx) > 1.3.0 downloaded OK > 1.3.2a downloaded OK > 1.3.3 downloaded OK > > So, the commandline versions of gpsbabel seem to be working > wonderfully whichever of the recent versions are used. The failures > I'm experiencing only occur when using GPSBabel+ 1.3.2a or 1.3.3. The > same versions of the commandline work perfectly. > > According to the log window - the gpsbabel command to be executed is > not being passed properly. > > So, I'm still convinced that in this case - there is nothing wrong > with the Keyspan as it works perfectly on the commandline. The only > problems occur with GPSBabel+ 1.3.2a and 1.3.3. The fact that the log > in GPSBabel+ does not display the command when it fails suggests to me > that maybe there is an error in building the gpsbabel command to be > run in 1.3.2a and 1.3.3. When it works, this command appears to be > built properly. The bundled gpsbabel commandline works fine. > > I hope that this is able to point someone in the right direction. > > Cheers Gav > > > > > > On 17/04/2007, at 14:48, Robert Lipe wrote: > >>> get the commandline transfers to work then that would support my >>> contention that the fault I am seeing lies with GPSBabel+ and not >>> with the commandline gpsbabel. I think this is already partly >> >> The "advanced window does nothing" is definitely the GUI and not the >> underlying GPSBabel. >> >> The "received data, but it's not a DLE and the first byte I see from >> a Garmin >> *has* to be a DLE" error is definitely not the GUI. It might be >> GPSBabel; it >> might be the Keyspan driver. > |