Thread: [Gpsbabel-misc] Magellan -> OSX revisited
Brought to you by:
robertl
From: Laurie B. <la...@br...> - 2002-12-22 16:43:49
|
> this just hangs when I connect the same (Keyspan) cable configuration to > a Magellan Meridian: > > gpsbabel -i magellan -f /dev/tty.USA28X213P1.1 > > Any advice on settings on the Meridian? In the OS X command line? Try: gpsbabel -i magellan -f /dev/cu.USA28X213P1.1 I believe that the tty port is blocking and that is why it doesn't work... but the above works great for getting the info FROM the magellan (I have a Magellan Meridian) but I can't get data TO the magellan ... in other words this does NOT work: gpsbabel -i gpx -f file.gpx -o magellan -F /dev/cu.USA28X213P1.1 When run with -D 2 I get the following output: W1P1.1 WRITE: $PMGNCMD,HANDON*70 WRITE: $PMGNCMD,VERSION*28 READ: $PMGNCSM,28*6F READ: $PMGNVER,033,VER 4 02,Meridian*0F WRITE: $PMGNCSM,0F*13 WRITE: $PMGNCMD,NMEAOFF*3A READ: $PMGNCSM,3A*17 WRITE: $PMGNWPL,4300.919,N,07131.206,W,0000000,M,GC6CD5,Piscatequog Paddle by Grampa C,a*5D WRITE: $PMGNCMD,HANDOFF*3E (I removed several lines of lat/lon locations - but left the relevent parts) Any ideas?? Laurie /*----------------------------------------------------------------*/ Homepage: http://www.brownfox.org PGP Fingerprint: C81B 0293 7041 14C4 2655 AE8A 5F9E 6D22 9BAC 144E |
From: Robert L. <rob...@us...> - 2002-12-31 06:00:29
|
[ I'm climbing out of an email backlog from holiday travels. ] Laurie Brown wrote: > gpsbabel -i gpx -f file.gpx -o magellan -F /dev/cu.USA28X213P1.1 > > When run with -D 2 I get the following output: > > W1P1.1 That line is curious. Can you tell us where that comes from? > WRITE: $PMGNCMD,HANDON*70 > WRITE: $PMGNCMD,VERSION*28 > READ: $PMGNCSM,28*6F > > READ: $PMGNVER,033,VER 4 02,Meridian*0F > > WRITE: $PMGNCSM,0F*13 > WRITE: $PMGNCMD,NMEAOFF*3A > READ: $PMGNCSM,3A*17 > > WRITE: $PMGNWPL,4300.919,N,07131.206,W,0000000,M,GC6CD5,Piscatequog Paddle > by Grampa C,a*5D > WRITE: $PMGNCMD,HANDOFF*3E > > (I removed several lines of lat/lon locations - but left the relevent > parts) Very odd. Did you delete the PNGNCSM that acked that WPL command? Is it some waypoints that are lost or all? Can you whack the input down to a single waypoint and include the entire session? Did it work with the 3.08/3.12 firmware on the Meridian or is this a new failure with 4.02? RJL |
From: Laurie B. <la...@br...> - 2002-12-31 14:51:55
|
--On Monday, December 30, 2002 23:59 -0600 Robert Lipe <rob...@us...> wrote: > [ I'm climbing out of an email backlog from holiday travels. ] > > Laurie Brown wrote: > >> gpsbabel -i gpx -f file.gpx -o magellan -F /dev/cu.USA28X213P1.1 >> >> When run with -D 2 I get the following output: >> >> W1P1.1 > > That line is curious. Can you tell us where that comes from? Not a clue - it could have been an unfortunate cut/paste accident (news at 11). > Very odd. Did you delete the PNGNCSM that acked that WPL command? Is > it some waypoints that are lost or all? Can you whack the input down to > a single waypoint and include the entire session? > > Did it work with the 3.08/3.12 firmware on the Meridian or is this a new > failure with 4.02? Don't know that either BUT I did try this with a Magellan 330 and got the same result. Here is the output: **** From the Magellan 330 [veronica:/Volumes/Download] laurie% gpsbabel -D 2 -i gpx -f one_wpt.gpx -o mage llan -F /dev/cu.USA19QW1P1.1 WRITE: $PMGNCMD,HANDON*70 WRITE: $PMGNCMD,VERSION*28 READ: $PMGNCSM,28*6F READ: $PMGNVER,030,VER 2 08, MAP 330*5D WRITE: $PMGNCSM,5D*14 WRITE: $PMGNCMD,NMEAOFF*3A READ: $PMGNCSM,3A*17 WRITE: $PMGNWPL,4300.919,N,07131.206,W,0000000,M,GC6CD5,Piscatequog Paddle by Gr ampa C,a*5D WRITE: $PMGNCMD,HANDOFF*3E [veronica:/Volumes/Download] laurie% **** From the Magellan Meridian [veronica:/Volumes/Download] laurie% gpsbabel -D 2 -i gpx -f one_wpt.gpx -o mage llan -F /dev/cu.USA19QW1P1.1 WRITE: $PMGNCMD,HANDON*70 WRITE: $PMGNCMD,VERSION*28 READ: $PMGNCSM,70*62 READ: $PMGNCSM,28*6F READ: $PMGNVER,033,VER 4 02,Meridian*0F WRITE: $PMGNCSM,0F*13 WRITE: $PMGNCMD,NMEAOFF*3A READ: $PMGNCSM,3A*17 WRITE: $PMGNWPL,4300.919,N,07131.206,W,0000000,M,GC6CD5,Piscatequog Paddle by Gr ampa C,a*5D WRITE: $PMGNCMD,HANDOFF*3E [veronica:/Volumes/Download] laurie% As someone else noted - if you use tty.USA19QW1P1.1 the connection hangs, the only way to get it back is to unplug the Keyspan plug - resulting in a bus error. Laurie |
From: Robert L. <rob...@us...> - 2003-01-07 04:28:31
|
This is on the mist list for closure. It turns out the problem in question wasn't really OSX specific at all. I've implemented a fix, Laurie confirmed it, and I've committed it so it'll be in the next version. Thanx, RJL > > Very odd. Did you delete the PNGNCSM that acked that WPL command? Is > > it some waypoints that are lost or all? Can you whack the input down to > > a single waypoint and include the entire session? > > > Don't know that either BUT I did try this with a Magellan 330 and got the > same result. Here is the output: [ munch ] |
From: Robert L. <rob...@us...> - 2002-12-31 17:31:44
|
> Don't know that either BUT I did try this with a Magellan 330 and got the > same result. Here is the output: A 330 (unlike a Mac) I own, so that does allow us to eliminate one variable. > WRITE: $PMGNWPL,4300.919,N,07131.206,W,0000000,M,GC6CD5,Piscatequog Paddle > by Gr > ampa C,a*5D > WRITE: $PMGNCMD,HANDOFF*3E This is interesting. We're sending down the HANDOFF command before we get the ack on the WRITE. I'm not sure that it's a protocol violation, but it's definitely in bad taste. Oh. There's even some code in there to handle this that's currently turned off. Let me tinker with that and propose a patch. So the problem is that the waypoint is being sprayed to the receiver, but it doesn't seem to "stick", right? RJL |
From: Laurie B. <la...@br...> - 2002-12-31 18:21:14
|
--On Tuesday, December 31, 2002 11:31 -0600 Robert Lipe <rob...@us...> wrote: > > So the problem is that the waypoint is being sprayed to the receiver, > but it doesn't seem to "stick", right? True - that seems to be the problem. Oddly enough (as stated previously) I can download waypoints from the Magellan. I also think that the tty.USA28X213P1.1 vs cu.USA28X213P1.1 is a bit suspicious. The difference is that the cu.USA28X213P1.1 does not need acknowledgement of the connection (from Keyspan's website) and tty.USA28X213P1.1 does. Let me know what I can do to help. Laurie |