I need help....POI files not working on Garmin 1250

 

I downloaded all the POI files into one folder on my computer....named my .csv files, BMP icons and sound files all the exact same name. I then used the Garmin loader to put them in to my GPS.....at first I got missing sox.exe errors and "could not convert wav file" errors on every single sound file. I then found a sox.exe download on here and put the file in the Garmin loader directory and when I loaded them again, they went in with no problems and show up in the Garmin unit as POIs. I then took a test drive by two Wal-marts and a Sonic and got nothing....no icons and no sounds....nada.

Could someone tell me what I am doing wrong?

Jeff

.

1. Did you download the sounds as WAV files?

2. Did you SET alerts for the Custom POIs for which you wish to be alerted? Regular POIs do not alert by default. You must SET an alert if you wish to be alerted.

As to the icons, are you zoomed in to at least 200 feet?

Did you

Did you use MANUAL mode in POIloader to load the POIs to your Nuvi? You need to do that and select "This file contains proximity alerts points and set the Alert Settings in order to get the .wav file to play.

The icon will probably show on the screen if you zoom the map in.

--
Nuvi 350, 760, 1695LM, 3790LMT, 2460LMT, 3597LMTHD, DriveLuxe 50LMTHD, DriveSmart 61, Garmin Drive 52, Garmin Backup Camera 40 and TomTom XXL540s.

I had no clue that each POI

I had no clue that each POI had to be activated through the manual setting on the loader. Yes each sound is a WAV file. The red light camera files were already set for like 1800 feet... I activated the other files to go off at about 5000 feet....do you think that is too far away?

Thanks again for the info....I was tearing my hair out trying to figure out why such an easy task was not working....

The distance you are setting

The distance you are setting in manual mode for poiloader is not a problem .If the alerts are not working and you are driving to them.Either you don't have them named the same except for the extensions or you have double extensions The best way to prevent double extensions is to go to your folder options in the control panel and click view then find hide extensions for known file types and remove the check mark. Click ok.This is for Windows XP.
See http://www.poi-factory.com/node/25730 and http://www.poi-factory.com/node/25721 .

--
Charlie. Nuvi 265 WT and Nuvi 2597 LMT. MapFactor Navigator - Offline Maps & GPS.

.

Jeff - keep in mind that you don't need to actually drive a route to test your poi files. You can use the simulation mode.

Really

GadgetGuy2008 wrote:

Jeff - keep in mind that you don't need to actually drive a route to test your poi files. You can use the simulation mode.

Never thought of that, I'll try it myself. Thanks

--
Always on the Road Knowing where I've Been

POI Files worked!!

GadgetGuy2008 wrote:

Jeff - keep in mind that you don't need to actually drive a route to test your poi files. You can use the simulation mode.

Good tip...will remember that one!
I went out again to test and was successful!
Went near Target and it came up...also Sonic and Wal-Mart! I did have a small issue....Sonic popped up on a alert near Target, but Target did not go off again, still showed the Sonic alert. When I got home I cut the alert distance from 5000 feet to 2000 feet for all my POI files....maybe that will fix the overlap issue.

Alert distance

I usually just take the default 1/4 mile (1320 feet).

--
Striving to make the NYC Metro area project the best.

Alert Distances for Red Light Cameras

Shorter alert distances for red light cameras will make it more obvious where each camera is. If your area is wide-open, with intersections far apart and high speed limits, try 1320 feet. If you have downtown areas where intersections are close together and low speed limits, use a shorter distance. It is easier to have all red light cameras you are loading use the same distance.

For downtown New York City, where intersections are usually 1/10th of a mile apart, I use 500 feet. This is needed because of areas where every intersection has a camera, to avoid overlapping alerts which will be confusing.

dobs108