Any way to adjust the initial warning for a speed/proximity POI?

 

On a Garmin you can set a speed POI with a proximity setting. E.G.: Set a 2 km proximity for a 100 km/hour speed warning.

In use, the GPS will 'double boing' when you are within the incoming 2 km POI proximity zone *IF* you are at 10 km/hr under the limit (in this example at 90 kmh). Then it will 'chime' as you exceed the set limit (in this example at 100 kmh).

I am looking for a way to change that 10 km/hr limit setting or to remove the double boing entirely.

The reason is - the speed limit might be 90 km/hour and my driving might see my speed fluctuating from 88 to 92 km/hour then back down to 88 and so on. Every time I exceed 90 I get the 'double boing'. I would rather not have it do that at all - or be able to adjust it so it would 'double boing' only when I was near the 100 km/hour set point.

Anyone know how to do this - if not on a Garmin then perhaps on some other brand of GPS?

Manually Update...

When you run POI Loader, choose "Manual" rather than "Automatic". It will take you through each POI that you are uploading, and for any with a proximity/speed alert, you can change the default setting. I think the speed alerts default to 0 mph/kph over the programmed speed, and you can simply enter something like "10" in that field. That should give you an alert if you are 10 above the programmed speed. The same works for proximity alerts - for RLCs, I think it defaults to 1320 feet (1/4 mile) but I usually change it to 500 feet.

--
The Moose Is Loose! nuvi 760

Adjusting the initial warning v/s the OVERSPEED setttings

"Manual" mode allows me to set an OVERSPEED setting for a given file that does not already have individual POI overspeed settings for the POIs in it.

My .gpx file already has OVERSPEED set for every POI in it so Manual does not help me as my need is to be able to adjust the 'initial warning' speed - which is lower by 10 km/hr (about 6 mph) than the OVERSPEED setting.

e.g. - If you set a single POI (or an entire file) to OVERSPEED warn at '100' km/h (60 mph) it will 'initial warn' at 90 km/hr (54 mph) with the 'double boing' every time you go over 90 km/hr. So if you are driving at 89 - everything is fine - hit 90 - you get a 'double boing' and the screen top goes red. Drop back to 89 - the screen top goes green - go back to 90 - you get one 'double boing' and the screen top goes red again.

If you continue accelerating to 100 or over then it will do the 'chime once every 5 seconds' OVERSPEED warning.

What I want is to remove the initial 'double boing' as it gets to be a pain if my speed is fluctuating back and forth across the 90 km/hr 'initial warning' speed point - or - to be able to adjust that speed point closer to the 100 km/hr 'chime' OVERSPEED warning.

Meaning - in an ideal situation I could set the OVERSPEED warning (the chime) to be 100 km/hr and the initial warning to be 98 km/hr. As I would drive from 89 to 92 and back again - nothing would happen. *IF* I went up to 98 I would get the 'double boing' and if I then went over 100 I would get the 'chime'.

Hope this explains what I am looking for.

Moose135 wrote:

When you run POI Loader, choose "Manual" rather than "Automatic". It will take you through each POI that you are uploading, and for any with a proximity/speed alert, you can change the default setting. I think the speed alerts default to 0 mph/kph over the programmed speed, and you can simply enter something like "10" in that field. That should give you an alert if you are 10 above the programmed speed. The same works for proximity alerts - for RLCs, I think it defaults to 1320 feet (1/4 mile) but I usually change it to 500 feet.

Setting Speed Threshold

Isn't it true that the speed indicator for individual POIs is just the @## MPH or @### KPH in the POI name? If so, any text editor can replace one speed for another. If you edit from the highest speed down by increments, you could change each POI speed warning threshold, making the warning and alarm at a more reasonable upper limit.

GVim text editor is free and fairly easy to program a set of edit comands in a file, such as:\
:%s/@100 KPH/@110 KPH/
:%s/@90 KPH/@100 KPH/
etc.

That way, each time you receive an updated speed POI file, it takes just a minute to change the limits to your personal preferences.

--
Zumo 550 & Zumo 665 My alarm clock is sunshine on chrome.

Speed warning

Yes I can change the speed setting using a variety of programs. The issue here is the initial warning comes at 10 km/hr (6 mph) before the speed setting.

e.g. - You set a POI speed setting for 100 km/hr (60 mph) and a proximity of 2 km. As you drive into the POI proximity range of the POI - the GPS will 'double boing' as soon as you exceed 90 km/hr (56 mph).

What I want to do is eliminate that doulbe boing at 90 km/hr (56 mph) ..or.. adjust it upward closer to the 100 km/hr (60 mph) setting.

I know I can adjust the 100 km/hr (60 mph) setting up to some higher amount - such as 115 km/hr (70 mph) but that is too fast.

dave817 wrote:

Isn't it true that the speed indicator for individual POIs is just the @## MPH or @### KPH in the POI name? If so, any text editor can replace one speed for another. If you edit from the highest speed down by increments, you could change each POI speed warning threshold, making the warning and alarm at a more reasonable upper limit.

GVim text editor is free and fairly easy to program a set of edit comands in a file, such as:\
:%s/@100 KPH/@110 KPH/
:%s/@90 KPH/@100 KPH/
etc.

That way, each time you receive an updated speed POI file, it takes just a minute to change the limits to your personal preferences.