Scott Miller wrote: > $PGRMW is a supplemental sentence - the waypoint creation is still done > through the $GPWPL sentence. Every time the T2 sends a waypoint, it > does both. Plus a few others if you've got them enabled. > > Scott >
Thanks for that, but I still can't see how sending a $GPWPL followed by a $PGRMW for every waypoint sent avoids the duplicate waypoint situation caused by Garmin's more recent philosophy for handling of duplicate $GPWPL sentences. I'm referring to the situation where old waypoints get an appended sequence number added. Does the T2 avoid that somehow? And is that only with the Oregon/Colorado series? Barry N4MSJ > Barry L. Lankford wrote: >> >> >> Scott Miller wrote: >> > That's right. Works very well. >> > >> > Scott >> > >> Scott, >> >> I'm confused about how this works. As I read the info in the Garmin blog >> link given in the original post, you can only use the $PGRMW sentence to >> update the altitude, symbol and comment of an already existing waypoint. >> Unless I've missed something, it does not say you can update the latitude >> and longitude, and the Garmin proprietary NMEA document seems to confirm >> that. So, how can you "move" an existing waypoints with the $PGRMW >> sentence without creating duplicates? >> >> Also, unless you can use the $PGRMW sentence to create new waypoints as >> well as update existing ones, that would seem to indicate that to use the >> $PGRMW sentence in a tracker would require you to maintain a list of >> already created waypoints in the tracker's memory (so you'd know whether to >> send an initial $GPWPL or a modifying $PGRMW), and I doubt even recent >> trackers have that much memory to spare. So, how does that work? >> >> Is the lat/long update capability only available with the Oregon and >> Colorado series? I have a vague recollection that the $PGRMW sentence may >> have been extended to include lat and long in those units, but I haven't >> been able to locate any posts on any of the forums I read, or any Garmin >> documents, to confirm that. >> >> Barry N4MSJ >> >> > Edward wrote: >> >> >> >> >> >> Is it true that you wont get the duplicate waypoints? >> >> >> >> --- In [email protected] <mailto:tracker2%40yahoogroups.com>, >> >> Scott Miller <sc...@...> wrote: >> >> > >> >> > I think the Garmin blog covers most of it. $PGRMW support has been >> >> > there in the Tracker2 since slightly before Garmin rolled out the >> >> > firmware update. You'll need to buy one of their serial interface >> >> > cables, unless you want to build your own with a voltage regulator and >> >> > level shifter. >> >> > >> >> > Scott >> >> > >> >> > Edward wrote: >> >> > > >> >> > > >> >> > > I saw this recently on the Garmin website and don't know quite >> what to >> >> > > make of it. They seem to say they have APRS compatible units. I >> >> searched >> >> > > the forum but didn't see any mention of it. >> >> > > >> >> > > http://garmin.blogs.com/softwareupdates/2009/06/index.html >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html> >> >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html>> >> >> > > <http://garmin.blogs.com/softwareupdates/2009/06/index.html >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html> >> >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html >> <http://garmin.blogs.com/softwareupdates/2009/06/index.html>>> >> >> > > >> >> > > Ed >> >> > > KE7MWY >> >> > > >> >> > > >> >> >
