Thread: [Gpsbabel-misc] GPSbabel via cmd - proximity alarm problem
Brought to you by:
robertl
From: <wol...@gm...> - 2010-02-27 10:14:15
|
Hi, I want to generate a Garmin POI file with GPSbabel from cmd. This works pretty fine, BUT I do not get any alarm when I have a distance of 220meters or less to the waypoint. What am I doing wrong ? I first used the latest stable version of GPSbabel and I also tried the actual beta. When I generate a GPX file which one I upload with the POIloader from Garmin all is working fine. I use a zumo 550 but I guess this is here not important. Here the syntax I tried: gpsbabel.exe -p "" -w -i csv -f "D:\input.csv" -o garmin_gpi,alerts=1,bitmap="D:\icon.bmp",category="Test",proximity=220m,unique=0 -F "D:\output.gpi" Cheers Wolle -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser |
From: Terry B. <ter...@ya...> - 2010-02-27 14:09:26
|
On Sat, 27 Feb 2010 11:14:02 +0100 wol...@gm... wrote: > I want to generate a Garmin POI file with GPSbabel from cmd. This works pretty fine, BUT I do not get any alarm when I have a distance of 220meters or less to the waypoint. What am I doing wrong Me too. I've tried with and without 1 km/h speed setting. I was attempting to set 100 m prox. alarm on a set of several thousand POIs, not sure if there's a limit in that respect. The on GPSr info. display for the POI says something like: Alarm distance: 100m Alarm speed: 1kmh (or unknown) Prox. alarms on waypoints (created on the GPSr) are working. Cheers -Terry |
From: Robert L. <rob...@gp...> - 2010-02-27 18:21:57
|
I just made a file with a single waypoint and wrote it with -o garmin_gpi,proximity=220m and -o garmin_gpi,proximity=221m. Other than the timestamp, the only difference was the 220 and the 221 in the file. We don't have any kind of special case for 220m and it's not like we have any obvious overflow/underflow/sign extension types of problems. As this is a reverse engineered format, perhaps Garmin does something goofy like using a different encoding for small values or perhaps Zumo does something different than Nuvi, where most of this work was done. Does the proximity value show on the unit and just not fire or does it not show at all? I won't be shocked if there's some nuance here. It's a pretty complicated format. On Sat, Feb 27, 2010 at 8:05 AM, Terry Brown <ter...@ya...>wrote: > On Sat, 27 Feb 2010 11:14:02 +0100 > wol...@gm... wrote: > > > I want to generate a Garmin POI file with GPSbabel from cmd. This works > pretty fine, BUT I do not get any alarm when I have a distance of 220meters > or less to the waypoint. What am I doing wrong > > Me too. I've tried with and without 1 km/h speed setting. I was > attempting to set 100 m prox. alarm on a set of several thousand POIs, not > sure if there's a limit in that respect. > > The on GPSr info. display for the POI says something like: > > Alarm distance: 100m > Alarm speed: 1kmh (or unknown) > > Prox. alarms on waypoints (created on the GPSr) are working. > > Cheers -Terry > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Stefan M. <mu...@we...> - 2010-02-27 18:46:29
|
Hello! Am Samstag, 27. Februar 2010 schrieb Robert Lipe: > I just made a file with a single waypoint and wrote it with -o > garmin_gpi,proximity=220m and -o garmin_gpi,proximity=221m. Other > than the timestamp, the only difference was the 220 and the 221 in > the file. We don't have any kind of special case for 220m and it's > not like we have any obvious overflow/underflow/sign extension types > of problems. I don't think that this is with the format of the file. > As this is a reverse engineered format, perhaps Garmin > does something goofy like using a different encoding for small values > or perhaps Zumo does something different than Nuvi, where most of > this work was done. Maybe it's the place where the information (proxim. alerts or gpi file) lives. I'm using a Etrex Legend HCx with an extra memory card where I can stores maps or poi files. I've also tested creating a gpi with proxim. alert. But without luck... If one is creating a proxim. alert with the GPSr you can see a circle with the given radius at the given point. But this information isn't on the memory card, it is in the device memory... So I think at least in my case the question is, how to transfer the gpi to the device memory instead of the memory card. No, device memory isn't availiable, neither using mount nor using MapSource. > Does the proximity value show on the unit and > just not fire or does it not show at all? > > I won't be shocked if there's some nuance here. It's a pretty > complicated format. > > On Sat, Feb 27, 2010 at 8:05 AM, Terry Brown <ter...@ya...>wrote: > > On Sat, 27 Feb 2010 11:14:02 +0100 > > > > wol...@gm... wrote: > > > I want to generate a Garmin POI file with GPSbabel from cmd. This > > > works > > > > pretty fine, BUT I do not get any alarm when I have a distance of > > 220meters or less to the waypoint. What am I doing wrong > > > > Me too. I've tried with and without 1 km/h speed setting. I was > > attempting to set 100 m prox. alarm on a set of several thousand > > POIs, not sure if there's a limit in that respect. > > > > The on GPSr info. display for the POI says something like: > > > > Alarm distance: 100m > > Alarm speed: 1kmh (or unknown) > > > > Prox. alarms on waypoints (created on the GPSr) are working. > > > > Cheers -Terry > > > > > > ------------------------------------------------------------------- > >----------- Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Gpsbabel-misc mailing list http://www.gpsbabel.org > > Gps...@li... > > To unsubscribe, change list options, or see archives, visit: > > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc |
From: Robert L. <rob...@gp...> - 2010-02-27 19:08:21
|
On Sat, Feb 27, 2010 at 12:46 PM, Stefan Munder <mu...@we...> wrote: > > If one is creating a proxim. alert with the GPSr you can see a circle > with the given radius at the given point. But this information isn't on > the memory card, it is in the device memory... > > So I think at least in my case the question is, how to transfer the gpi > to the device memory instead of the memory card. No, device memory > isn't availiable, neither using mount nor using MapSource. > POIs and waypoints are completely different. Waypoints are editable on the handset and are always in internal memory. POIs are not editable on any of the Garmins I've seen. I don't think custom POIs are ever in internal memory; certainly there's no documented protocol for putting them there, though Garmin's POI loader may be able to do it. |
From: Robert L. <rob...@gp...> - 2010-02-27 19:13:29
|
On Sat, Feb 27, 2010 at 12:55 PM, Terry Brown <ter...@ya...>wrote: > On Sat, 27 Feb 2010 12:21:48 -0600 > Robert Lipe <rob...@gp...> wrote: > > > perhaps Zumo does something different > > than Nuvi, where most of this work was done. > > I'm using GPSmap 76CSx > > > Does the proximity value show > > on the unit and just not fire or does it not show at all? > > Shows, but doesn't fire. Well, shows in the textual description of the POI > on the GPSr (Alarm distance: 100m, Alarm speed: 1kmh), it doesn't show a > ring around the POI as it does for a Waypoint prox. alarm. > Is that similarly true with points written by POI Loader? It sure sounds like we're putting it in the file in the right place and it's recognizing it. It's not like we write a textual description of that data in the gpi file. So there me be some other nuance that we're missing. But I really don't understand the magic about 220m. Can someone affected by this prepare a single point from CSV (providing that CSV) with both POI Loader and GPSBabel at both 220 and 221m and confirm that the only one that fails is GPSBabel at 220 and then provide all five files? RJL |
From: Terry B. <ter...@ya...> - 2010-02-27 20:15:26
|
On Sat, 27 Feb 2010 12:21:48 -0600 Robert Lipe <rob...@gp...> wrote: > Other than the > timestamp, the only difference was the 220 and the 221 in the file. gpsbabel -i gpx -o garmin_gpi,descr,bitmap=../icons/gccom/O.bmp,proximity=221m,sleep=2,category=test e40.gpx e40.gpi This gpi and another at 220 m (non-overlapping) both failed to alarm as I walked by, while a waypoint prox. alarm created on the GPSr (GPSmap 60CSx) did alarm. pois display the text: Alarm Range: 22[01]m Alarm Speed Unknown Cheers -Terry |
From: Robert L. <rob...@gp...> - 2010-02-27 20:31:46
|
On Sat, Feb 27, 2010 at 2:14 PM, Terry Brown <ter...@ya...>wrote: > On Sat, 27 Feb 2010 12:21:48 -0600 > Robert Lipe <rob...@gp...> wrote: > > > Other than the > > timestamp, the only difference was the 220 and the 221 in the file. > > gpsbabel -i gpx -o > garmin_gpi,descr,bitmap=../icons/gccom/O.bmp,proximity=221m,sleep=2,category=test > e40.gpx e40.gpi > > This gpi and another at 220 m (non-overlapping) both failed to alarm as I > walked by, while a waypoint prox. alarm created on the GPSr (GPSmap 60CSx) > did alarm. > Waypoints and POIs are completely different. Your tests don't test the opening theory that there's a breaking point at 220m. From your test, it may be that our proximity support is totally broken. If you feed that same gpx file to POI loader, does the handset react differently? If so, submit the simplest possible input (single point, no icon, etc....) that can be given to both POI LOader and to us that causes the handset to fail. Include both GPI files as well. RJL > pois display the text: > > Alarm Range: 22[01]m > Alarm Speed Unknown > > Cheers -Terry > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > |
From: Terry B. <ter...@ya...> - 2010-02-27 20:39:19
|
On Sat, 27 Feb 2010 14:31:39 -0600 Robert Lipe <rob...@gp...> wrote: > Waypoints and POIs are completely different. I understand that, I only mention the wpt prox. alarm to indicate I don't have prox. alarms turned off, or mute turned on, or other sound setting errors, on the unit. > Your tests don't test the opening theory that there's a breaking point at > 220m. From your test, it may be that our proximity support is totally > broken. Indeed. > If you feed that same gpx file to POI loader, does the handset react > differently? If so, submit the simplest possible input (single point, no > icon, etc....) that can be given to both POI LOader and to us that causes > the handset to fail. Include both GPI files as well. ok, I'll have to install poi loader somewhere, don't usually use Windows. Cheers -Terry |
From: Håkon S. <ha...@st...> - 2010-02-27 21:00:17
Attachments:
gpsbabel-1.3.7-beta20100215_fix_alerts.diff
|
wol...@gm... writes: > I want to generate a Garmin POI file with GPSbabel from cmd. This > works pretty fine, BUT I do not get any alarm when I have a distance > of 220meters or less to the waypoint. What am I doing wrong ? I first > used the latest stable version of GPSbabel and I also tried the actual > beta. Hello. I've had the same experience, but if I remember correctly alarms where never triggered regardless of the proximity distance. However, applying the following simple patch against the latest beta appears to fix the problem with alarms not being triggered. It's according to a suggestion in a post by Øyvind Jonsson on gpsbabel-code on 2009-08-15. The post includes much information on the GPI format, but unfortunately I've only had the chance to have a brief look at it. |
From: Robert L. <rob...@gp...> - 2010-02-27 21:27:44
|
On Sat, Feb 27, 2010 at 1:53 PM, Håkon Stordahl <ha...@st...> wrote: > wol...@gm... writes: > > > I want to generate a Garmin POI file with GPSbabel from cmd. This > > works pretty fine, BUT I do not get any alarm when I have a distance > > of 220meters or less to the waypoint. What am I doing wrong ? I first > > used the latest stable version of GPSbabel and I also tried the actual > > beta. > > Hello. I've had the same experience, but if I remember correctly alarms > where never triggered regardless of the proximity distance. > > However, applying the following simple patch against the latest beta > appears to fix the problem with alarms not being triggered. It's > according to a suggestion in a post by Øyvind Jonsson on gpsbabel-code > on 2009-08-15. The post includes much information on the GPI format, but > unfortunately I've only had the chance to have a brief look at it. > Cool. I've applied this. "Totally broken" is a rather different search domain than "do not get any alarm when I have a distance of 220meters or less". I'd missed what was essentially a bugreport in Jonsson's message which seemed to be otherwise additional analysis of the file format. Thanx, guys. RJL > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Gpsbabel-misc mailing list http://www.gpsbabel.org > Gps...@li... > To unsubscribe, change list options, or see archives, visit: > https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc > > |
From: Terry B. <ter...@ya...> - 2010-02-27 21:54:17
|
On Sat, 27 Feb 2010 15:27:36 -0600 Robert Lipe <rob...@gp...> wrote: > Cool. I've applied this. Oh, of course this arrived after I finished making POIs and wandering around the neighborhood :-) So you can ignore the .zip of demo broken POIs I sent. Cheers -Terry |
From: Håkon S. <ha...@st...> - 2010-02-27 23:06:22
|
Terry Brown <ter...@ya...> writes: > On Sat, 27 Feb 2010 15:27:36 -0600 > Robert Lipe <rob...@gp...> wrote: > >> Cool. I've applied this. > > Oh, of course this arrived after I finished making POIs and wandering > around the neighborhood :-) I'm sorry about that.. Anyhow, although also a bit late now, a useful trick I discovered when trying to figure this out is to use the GPS receiver with simulation of auto-routing in demo mode, and possibly also first setting the current location to be near the POI in question. It requires a map that supports auto-routing. Even though the process is somewhat involved, it'll avoid the need to actually visit the POI to be tested. This at least worked with a Garmin GPSmap 76CSx. (Demo mode can be enabled in the System Setup menu on 76CSx.) |