Proximity Alerts Issue - (Driving me mad)

[festeringlog]

I'm at my wits end with this one.

I have for a long time had the PGPSW speed cam database on my Nuvi 250. It loads in from the CSV, for a while I had the additional voices, then I got bored of them so I created a new folder without the nice scottish lady's WAV files in and it works fine just the red banner and the standard garmin bonging noise. You get the 2 alerts , if you're over speed limit intially and then the proximity one, both just a bonging noise. I assume the bong noise file is located somewhere within the Sat Nav's voice files and is activated that way as theres no sound files in the POI upload folder.

The above is more to demonstrate I know pretty much how the CSV POI files work on Nuvi's through POI loader, not the problem.

Here's the problem, Im off on holiday to France soon so I downloaded a french speed camera database (from GPSpassion), again a CSV file. I notice that the PGPSW database uses the actual speed cam names in the CSV file (S-GATSO:364@20) etc and activates it's proximity alert that way. The french one I have instead uses wording like "RF0010@090"
to set the alert the last integer being the relevant soeed alert (in KPH).

So I have installed the second file onto the sat nav, as per other posts on here I have used POI loader to create seperate files named UK.gpi and france.gpi, and copied both across to the Garmin unit. I know the french camera are in there becuse they show up on the map with icons, and I know the alerts are set correctly because if you look one up as a destination in the satnav it provides the alert info on the screen as being 56mph or whatever and also procides a disance alert detail in a not round number metres.

BUT the proximity alerts on the french ones do not work, I have tested this by turning the GPS simulator on and setting the location to somewhere close to a camera and telling it to simulate a route past it, and it doesnt bong, I know the speed bong might not work but the proxmity bong should, if I do the same exercise with a UK speed camera I get the bonging even in the simulated route.

Can anyone offer any explanation or fix this is driving me mad and I would like to know before I hit the autoroute I will get a bong and not just an icon on the screen seconds before I rush towards a camera at or around 130km/h!!

[Kremmen]

Just checking, but you are using 'KPH and Metres' instead of 'MPH and Feet' within the POI Loader ?

I know the Alert limit in MPH is 125, anything more and it gets ignored.
_________________
DashCam:
Viofo A119 V3

[Allan_whoops]

What file are you loading from GPSPassion? I am just doing that as well and there are no @ signs in mine. An example is

-0.78673 44.80839 "RM00277-050km/h"

I import the two files (for fixed and mobile) into two noddy databases and then extract each speed limit as csv files. I then use GeePeeEx editor to create a gpi file with time and distance alerts. On the 765 and 1690, I use the warning files from here for each speed. That works fine.

Hope this helps

Allan

[festeringlog]

Yes definitely loaded in as KPH not MPH

I actually spent some more time testing his again last night, in the end I managed to get it to bong by altering the data in the CSV file to @10 a specific camera repackaging a *.gpi test file and simulating a french test route past that camera so it effectively triggered at 10km/h (or 6mph as my device stated) which was being exceeded by the simulated route.

Hopefully this means that in the unlikely event I am in excess of the speed limit as I approach a radar camera it will bong me.

I can't for the life of me understand why the proximity alerts dont work unless it's over the indicated speed but hopefully this will be OK.

[festeringlog]

[Kremmen]

What you've done sounds perfectly OK to me. I can only assume the POI Loader or the unit isn't playing ball with your @*** entries when loaded as KPH.

I understand from other posts that Garmin units can ignore these if your travelling under the Alert limit. In my app I'm doing the same as Ash10 did and I'm producing 2 lines, one with say @70 and another with #70. This seems to force the unit to always produce the Alert.
_________________
DashCam:
Viofo A119 V3

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!