Excessive Speed Camera Ahead Announcements

Check for multiple installs of the camera POI, i.e. on the SD card or installed on the main unit.

It looks like you may have 3 instances, probably on the SD card since the installer doesn't erase the past files on the SD card like it does on the main mamory.

In addition to multiple installs, every time you stop the alert will be reissued when you start moving again.

Proximity alert and speed alert POIs are non-directional. Both eastbound and westbound cameras are alerting no matter which direction you are traveling. This probably can't be helped because a POI will alert if it is up to 100 feet off the track. It is possible to adjust the location of the POIs to off the road on one side and the other but these custom locations would have to be loaded every time you update the file from POI Factory.

See this recent thread -

http://www.poi-factory.com/node/34733

Why is each POI alerting three times for a proximity alert? This happens to me with the nuvi 760 but it does not happen with every nuvi. I would suggest trying to load it as a proximity alert as you have done, but remove the word "speed" from the filename. This could be causing it to load as a speed alert even though you selected proximity alert in POI Loader.

Another tactic would be to load it as a proximity alert as above, and specify a shorter alert distance such as 600 feet, but remember this will be the same for every speed camera. If some of them are on 55 mph roads, 600 feet may be too short.

dobs108

There are no GPI files on my SD card and only 1 speed file in main memory. I have now deleted the Garmin Trial files. I simulated the route through the speed cameras. I get 5 announcements of speed cameras ahead which was probably what I was getting all along. There is only 1 entry for both of these speed cameras in the downloaded speed file if I am reading the file correctly. It must be locating the midpoint between the cameras. Is this the properly method? I also replaced "speed" with "motion" in the file name on my Garmin. Also was already using 600 feet. Any other thoughts?

5 announcements is behavior associated with a speed alert. After replacing "speed" with "motion" you would have to run POI Loader again, preferably in manual, and specify "alert when you get close to a point."

"motion" should not cause a speed alert to be automatically loaded. Read through Garmin POI Loader help. There are other ways a speed alert could have loaded when you want a proximity alert.

dobs108

I usually get 2 (once approaching, once as you pass it). You might want to try removing all POIs and then re-installing. I've had my Nuvi get duplicates before and this just flushes it all out.

Do you maybe have "Continuous Alerts" enabled on the GPS? Look for the setting in the "Proximity Points" section of the GPS. On the 37xx series, it's under Tools>Settings>Navigation>Automobile>Proximity Points. Choices are Single Tone, Continuous Tone and Off. The actual menu setting's location may be different on your unit.

Look at the folder and subfolders on the PC you are browsing POI Loader to. Is the original "speed-cameras.csv" still there in addition to the "motion-cameras.csv"? You will get both speed and proximity alerts, a mess of alerts at the same time. Move "speed-cameras.csv" to a different folder where POI Loader is not looking.

dobs108

I used the loader in manual mode and set the distance at 600 feet.

No I renamed the speed file. Only 1 there.

It is set to single tone.

POI Loader Help (in part) -

Speed information can be included in the file name or in the names of individual POIs within the file.

POI Loader determines speed information based on the following information, listed from highest to lowest priority:

1 - Speed information included in the name of the individual Custom POI. For example, a POI named "SpeedZone@30" will have an alert speed of 30 regardless of the speed information specified in Manual mode or in the file name.

2 - Speed information entered in Manual mode.

3 - Speed information included in the file name. POI Loader interprets any numbers in the file name as speed information.

-----------------------

It appears since every POI in the file has a "@" before the speed, it will always load as a speed file. Use Excel or Notepad to batch delete all the "@s" and the problem will go away.

And never put numbers in the file name according to "3" above.

dobs108

I deleted all my custom POI files and just reloaded the same Speed file and now I get only 2 announcements which has corrected the problem of 5 announcements. Do you think this solved the problem? I will see after I reload the remaining POI files. Could other speed data be hidden in one of the other files?

Yes. An ordinary filename Like Motel 8 will cause a 8 mph speed alert. (If a Motel 8 is at the speed camera location!)

Or, as other posters have suggested, there could have been multiple speed camera files loaded. POI Loader should have deleted them with every load, but maybe it became confused?

dobs108

Thanks

Glad to hear that problem solved. Once in awhile I've had multiple alerts but it's always been a database problem or cross street distance problem.

Fred

Thanks Fred

See this thread for another instance of this problem.

http://www.poi-factory.com/node/34105

I think you are probably beating your head against the wall trying to fix something that can't be fixed.
Skip whether or not its a speed, red light or regular distance alert. Certain units just sound off with certain POIs until you are past it.

I have turned off all my alerts except the rest areas, speed and redlights because many of the POIs have multiple alerts. Though Garmin doesn't generally investigate custom POI alert problems I got them to investigate the closest one to my house that always went off continuously, even in simulator mode and with the exact same repeat pattern which is different for the 2 different directions. I had to make the single POI file, give them locations to drive from and to, etc. After a week they confirmed the problem on multiple GPS models they tested on and were forwarding it to R&D saying they would keep me informed. I have not heard a thing back in 3 months. I sent an email asking what is going on with no answer yet.

The only way to be sure your actual POI location is the problem is to remove absolutely everything off the GPS, confirm the proximity setting is set for single tone, make a single file with a single known bad POI location, skip the bmp and wav files, confirm the POI name and the filename do not have any numbers or keywords, then recompile with POILoader in manual mode, setting a distance alert (generally 1320 feet works well), sending it to the GPS. Then do a simulator test drive past the location. You will see the default dot on the screen and get the default BONG sound multiple times if it a bad location.

I did this with multiple POI locations and they all sounded multiple times. I think that is why Garmin said they would investigate it.

The previous post is what happens when there is a break while typing the response and being long winded, while the problem is being solved.

Oh, and being a slow typist.

Glad you got the problem fixed.

LDSNOW, we are glad the problem is solved!

dobs108