Two alerts at same time?

Are you sure the 'Chipotle' alert sounds? I'd suggest temporarily disabling the 'Peets' alert and check for the 'Chipotle' alert. If the POIs are csv files, you can disable 'Peets' by putting @60 after the 'Peets' name (3rd field) that is sounding the alert; making sure you drive below that speed.

RT

Thanks for the suggestion. After I got home and was able to connect the GPS to my PC, I turned off the Peets alert and tested again in simulation mode. This time, I did hear the alert for Chipotle. Although it's only simulation, I think it indicates that the alert was set up correctly. I'll try again tomorrow in real driving.

this morning with the "Peets" alert turned off. The GPS alerted for Chipotle exactly as it was supposed to. I guess it picks up only one alert at a time.

You got me curious, so I created a Red-Light csv POI and a Speed csv POI, both with the same coordinates. Both audio alerts sounded (Red light alway first), but only one visual alert displayed.

I then created two csv POI files with 1000 ft manual alerts and again with the same coordinates. Both audio alerts sounded, and either one or both visual alerts would display ... depending on which direction I was driving from.

I don't know if this is normal, but this is what happens with my nuvi 350. Hope this helps.

RT

Yesterday when I had both proximity alerts enabled, I had the GPS in continuous-tone mode, and maybe some of the dings belonged to Peets and the rest belonged to Chipotle. I have a 255W without mp3, so I can't customize audio alerts for each store and all the dings sound the same. But I was sure that I got the visual alert only for Peets.

I will put the unit into single-tone mode later, and see if I get two dings when I approach the stores. I hope they don't arrest me for driving back and forth through that intersection ten times

Thanks for all the time you put into this.

Although the 2xx series can't use mp3 alerts, you apparently can use wav alerts. Check out this article http://home.comcast.net/~ghayman3/garmin.gps/pagepoi.02.htm#...

I drove by the stores today with both alerts enabled, and got two dings almost back to back, one for each store. Yay! Only the first store (Peets in this case) showed a visual alert. I believe that you don't get a second one until the first one has expired. I also found that the simulation mode is very representative of real life driving - the only difference being that you cannot set the speed in simulation.

Yes, I tried that. I created a wav file with the same name as the POI file in the POI folder, but when I tried to load using POI Loader, it said something about not recognizing a sox format, or something like that. I think I have to do a few more things to make it work, but haven't had time to dig into it.

To load .wav files with POI Loader, you need the right version of a file called SOX.EXE. Read here:

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

Download the .zip file and extract the file inside. Make sure you extract it to the program folder where the POI Loader program is installed.

It's not working for me. I have the POI Loader on the desktop, so I extracted the sox.exe file to the desktop also. Is that incorrect? Thanks.

No, you need to extract the sox.exe file to the actual folder where the POI Loader program is installed. Right click on the POI Loader icon on your desktop, select Properties, and you should see a shortcut tab. Look for the line that says "Start In:" That is the location you need to extract the sox.exe file to.

I put the sox.exe file in the right folder, and was able to upload the .wav file using POI LOader. But the proximity alert still remains a "ding ding." I've checked the file names and file locations, and played the .wav file on my PC, and everything looks OK. It just won't play on the GPS. Maybe my model, a nuvi 255W, doesn't handle .wav files.

Thanks RetiredTechnician, Gadget Guy and Gary A, for your help. I am happy with the ding ding alerts.

Recheck the parameters of your wav file. It may be it wasn't saved in the proper format even though you set the parameters in your conversion program... it should be 16 bit, mono, and 44 kHz

census 1940

I used a program called "Switch" to convert a Peets alert which I downloaded from POI Factory, from mp3 to wav. I used the encoder settings PCM 44.100 kHz 16-bit mono.

Just now I rechecked the properties of the resulting wav file, and it showed: bit rate 705 kbps, 16 bit, mono, 44 kHz, PCM.

The only thing that might be suspect is the bit rate, but I don't know how to set that in "Switch" - there is no such option.

Remember that you will need to re-send BOTH the poi file and the wave file, with identical names except for the extension, at the SAME TIME. Go back and send the files again. You can't add one in later and have it work.

Yes, I did. Each time I modified it, I upload the entire folder, which includes a csv file, a bmp file and a wav file for Peets. Nothing else related to Peets. I've gone back, typed and retyped the name in case there is a hidden error, but still no dice. I wonder if perhaps the 255 doesn't handle wav.

I tested this in simulation mode. That shouldn't matter, right? It did alert with a ding sound.

My guess is the bit rate is too high. Maybe try converting your mp3 using using Audacity. http://audacity.sourceforge.net/

My .wav files play fine in simulation mode. I took a look at my .wav file format just to compare, they are:

Bit Rate: 256kbps
Audio sample size: 16bit
Channels: 1(mono)
Audio sample rate: 16kHz
Audio format: PCM

It still doesn't work after I converted the .mp3 to .wav using audacity. I think it's enough work for this I can live with the tone alert which, coupled with the visual indication, is good enough for me. Thanks everyone for your help.

If you want to try one more thing, use the Contact tab on my Profile page and send me a message. When I respond via email you can send the .wav file to me and I can try loading it on my 660, where I know .wav files work. Up to you.

Do now give up. I have a 255 and the same .WAV alerts that I used on my 200 work fine.

Since the 255 is TTS capable, I assumed it would work with MP3 alerts, even though it doesn't have an MP3 player. I was wrong. I had to go back to WAVs.

.wav alerts work like a charm on my 255W.

Thanks Gary for the offer, and everyone for the advice. I am now on a road trip for a month, and don't have access to my alert file which is on my PC at home. I'll give it another try when I get back. Glad to know that .wav works with the 255W.