Thread: [Gpsbabel-misc] GPS data download issue with gpsbabel > 1.3.0 (Magellan, Mac OS X)
Brought to you by:
robertl
From: Antoine H. <ant...@if...> - 2008-01-07 17:04:46
|
Hello, A friend has some issue when downloading data from a Magellan Sportrak map under Mac IS X (10.4.11) on an iMac 20" (Intel core 2 Duo 2.16GHz ) with a serial to USB aten UC-232A (driver: prolific (ProlificUsbSerial.kext)) Problem appears from GPSBabel 1.3.1 and up. The error is: "MAGPROTO: Read error" No other details. Can we get a better debug trace ? Is this a known error ? Is there a workaround ? Thanks in advance, Antoine |
From: Robert L. <rob...@gm...> - 2008-01-07 17:20:36
|
Can we get a better debug trace ? > Adding a '-D9' to the transfer will show us byte-level detail of what's going over the wire. > Is this a known error ? The Prolific drivers are known to be problematic on Mac, but their failure case is one that generally doesn't affect the Magellans. It's not like we've had throngs of screaming Magellan/Mac users, so whatever's affecting you doesn't seem to be hammering everyone. If you have a different serial adapter, give that a shot. |
From: Antoine H. <ant...@if...> - 2008-01-27 19:35:24
Attachments:
gpsbabel1.3.0.log
gpsbabel1.3.4.log
|
Robert Lipe wrote: > > > Can we get a better debug trace ? > > > Adding a '-D9' to the transfer will show us byte-level detail of > what's going over the wire. > Hello Robert, Thank you very much for the quick answer. We have been tracing gpsbabel 1.3.0 and 1.3.4 reading the GPS using -D9 option -> attached It seems that 1.3.0 was a little more tolerant than newer versions: besides initial errors, transfer starts and gets completed OK. Would it be possible to add the missing code to go back to the 1.3.0 solution with the advantages of the newer code ? Antoine |
From: Robert L. <rob...@gm...> - 2008-01-28 06:07:42
|
It seems that 1.3.0 was a little more tolerant than newer versions: > besides initial errors, transfer starts and gets completed OK. > > Would it be possible to add the missing code to go back to the 1.3.0 > solution with the advantages of the newer code ? Actually, the 1.3.0 trace shows data corruption, too. The newer version is doing you a favor (in a governmental "we're here to help" kind of way :-) in reporting the error and stopping instead of letting it march on through an adapter that mangles data. There was packet that was lost and the GPS eventually gave up on that and resynced with the current one. If that had been in the middle of a data stream, it'd have been a lost point. These Prolific drivers are just a pain. Some people here have reported that the open source ones on sourceforge work better than Prolific's own. It's been a while (2+ years?) since I tried them on a G4 Mac, but at the time I looked at them, they tended to bring the system down with an alarming frequency. Hopefully they've fixed that... If you're happier with the 1.3.0 version's behaviour, please do feel free to use it. If you want want to graft 1.3.0's magproto.c into 1.3.4, that would be possible to do. |