I've been trying for several weeks, and somehow just can't get the TourGuide function to work with my 560LMT. Does anybody know if the 560LMT actually WORKS with tourGuide files? Being a trucking GPSr, I'm wondering if that was left out.
Clovis, NM USA
I don't have the dezl 560 so I can not respond from experience. I did download the User Manual and found that it does not have any reference at all to "TourGuide".
My 765T has specific settings for how I might respond to TourGuides. The fact that your manual does not give any instructions seems to imply that your unit will not support them.
If so, this would be disappointing as having a "radius" is very helpful in certain situations.
I have a couple of files of skydiving drop zones, and I'm trying to get an alert when within about 25 miles of any DZ, whether on my route or not. I've tried several times this morning, and got pretty strange results.
I've copied the files, and the originals are strictly poi files, while the copies are set up as TourGuide files, with both .mp3 and .wav files (since the 560 doesn't include an .mp3 player), also .bmp and .jpg files (since I couldn't remember which one was actually needed). Just now, I got the alerts to set on the ORIGINAL files, but the ones set up to be TourGuide files show NO alert at all.
I even called Garmin, but they were no help at all, and "Coleen" actually ridiculed me for thinking I could get alerts more than 90 meters away.
As your unit doesn't have MP3, do you have SOX.exe in the same folder where POILoader.exe resides on your computer?
Also, 132,000 feet may be too large a number for a tourguide. 53,000 feet is 10 miles and it may work.
Yes, sox.exe is in the same directory as the poi loader executable.
As for 132,000 feet -- I originally tried 265,000 feet, and got a warning to use something between 1 and 200,000!
If my memory serves me correctly, TourGuide will operate up to 200,000 feet (~38miles)
A reminder that all versions of 'sox.exe' don't work with POILoader. I am still using v 14.0.1 which serves me well.
Garmin Tricks & Tips website
OK, I re-downloaded sox.exe, getting the 14.0.1 version -- and unfortunately, no change.
I'm saying the TourGuide isn't working, because when I use my "Where to?" menu, and go to "Extras" and then "Custom POIs", I can click on any POI that I try to set up as a TourGuide point, and there is no proximity alert distance shown, and if I then go into the "Settings", "Navigation", ..."Proximity Points", all I see is "Alerts" and "Audio". There is no option to set up TourGuide.
When you use TourGuide in the file name it will not show the alert distance when you click on a poi like other custom pois you set up for alerts..Do a simulation to the custom Tourguide waypoint to see if it works.
If you have never done a simulation (and I agree with charlesd45 that this would be a good way to check whether TourGuide will alert as you hope), then this might help
Thanks, y'all. I'm doing the sim right now -- the nearest Drop Zone to me in in Belen, New Mexico, so I set my location to I-25 North, about 28 miles south of Belen, told the GPS to take me to Los Lunas, and it's simulating 75 MPH now. Funny, my truck doesn't accelerate that fast in real life! LOL!
I'm really starting to suspect that the 560 doesn't support TourGuide.
At this link
TourGuide® Data Sources
With the help of Garmin's free POI Loader software, you can upload TourGuide files to your compatible Garmin device*. Below are links to several free and subscription services on the Internet that provide these custom TourGuide files.
Our POI Loader supports the TourGuide feature in GPX format only. This means you must upload TourGuide files saved in this file format. Many of the TourGuide sources listed below provide points of interest saved in the above format. Please contact the companies below for further information on how to use their TourGuide files with your Garmin unit.
I wonder is there is a difference between a real "Tourguide" (complete with pictures and tour audio) and what we use for "radius" alerts?
You should not have a problem doing TourGuide see http://www.poi-factory.com/node/25730 The trick is to make sure they are named the same except for the extensions.Example
TourGuide Cracker Barrel.csv
TourGuide Cracker Barrel.wav
TourGuide Cracker Barrel.bmp
Make sure the sox.exe is in the correct location on your computer.Example XP with latest poiloader.My Computer,Local Disk (c),Program files,Click on Garmin folder and you will see Poiloader folder .Click on it and put sox.exe in that folder.
IT FINALLY WORKED!
But not at 25 miles, it only ever alerted me at 9.1 miles away. More investigation to follow, but I have to get in the truck and go to Durango, Colorado in a few minutes. Thanks for all the help.
This is the max http://www.poi-factory.com/node/28650
A lot has to do with where the coordinates are located in the radius.
Twenty-five miles is well within the quoted maximum. All I can figure is something to do with the actual location -- can you tel me a bit more, or give me a link?
Oops, load is ready, gotta run. Hope to be back tomorrow night!
If you search the forum you can find all kind of discussions on this.This one has been on the web for a while.Scroll down to TourGuide http://brillharts.com/GarminAlerts/
You can ALWAYS know the alert distance set for any Custom POI if you adopt the convention that I suggested in several of my articles on the subject on the Garmin Trick and Tips website -- http://bit.ly/garmin_gps_tricks
For example if your .csv file was titled 'TexasEmuFarmsD5000TourGuide.csv' and when you used the 'Manual' mode of POI Loader you set the distance to 5000 feet, then the accessed 'Where To? / Extras / Custom POI screen on your nuvi would include the listing of 'TexasEmuFarmsD5000TourGuide' and immediately you would know that you set the alert distance at 5000 feet just by reading the file name. ['D' in the file name stands for 'distance']
The only caveat is that the number in the file name has to be a whole number between 125 and 200000; no less and no more [Feet/MPH system; 200 and 65000 for the Meters/KPH system]
Some reference articles which discuss or include the technique, all which are located in the Custom POI section of the site are:
--THE SECRET (?) SPEED NUMBERS THEY DIDN'T TELL YOU ABOUT - Surprise Settings and How To Take Advantage of Them
--THE 'PROXEMICS' OF THE TourGuide - Hakuna Matata! The Circle Of ... Alert
--MY WATERING HOLE AT THE STRIP CLUB - Hiding A Custom POI
--CRACKING THE CRACKER BARREL CODE - The TourGuide Sez It's Lunchtime
That's very handy info, Gary, and I've read it a good bit. The problem, however, is that, even though I set the alert distance out as far as 200,000 feet -- just over 37 miles -- I actually only get alerts when I am MUCH closer -- on the order of 10 miles.
I'm sure some of my problems are the result of having incorrect expectations, but something about the selected distance just isn't doing what I think it should be.
Please rest assured that the long distance alert does work. I just developed a test for you that will prove it, unless, of course, something is wrong with your unit or your settings. Of course, as alway, I test everything first before writing (no guessing or assuming) -- doesn't everyone? I used my 3790LMT.
This test is a 'Nebraska' adaptation of my new article
SALINA, ZOOM OUT FAR AND STILL SEE A CUSTOM POI - You May Be Able To Zoom Out More (or Less) Than You Think
which uses the 'TourGuide' keyword in the .csv file name -- for a different purpose, but relies on a long distance alert such as you are desiring.
[One can read it by going to my website and clicking on 'Recent Additions' and selecting it. It is an informative article re: a variety of nuvi techniques.]
It looks as if you have quite a bit of experience with this so I won't go into too much detail. You can find step by step instructions in the referenced article or write me. We won't use the 'TourGuide', .bmp, or .wav for your experiment -- we are making it quite simple and quick.
(1) Create a Favorite using coordinates 40.42316,-97.86230 and name it 'NEBRASKA START'
(2) Create a Favorite using coordinates 40.42317,-97.84321 and name it 'NEBRASKA ALERT POINT'
(3) Create a Favorite using coordinates 40.42254,-97.17899 and name it 'NEBRASKA END'
(4) Prepare a one line file with NotePad or other text editor
-97.17899, 40.42254, Nebraska Test,
(please put a comma at the end like I did)
Save the file as a .csv file (you may have to adjust the Type pull down box to either .csv or All Files) with a file name of 'Nebraska Test.csv' and place it in a NEW FOLDER named 'Nebraska Test
(5) Connect your nuvi to your computer, Start POILoader, Point to that Folder, use Manual Mode, and set the distance to be 184000 feet. Send the file to your nuvi. It will be a .gpi file and will be found in the Garmin/POI folder (if you want to later delete it.)
(6) After disconnecting your nuvi from your computer, in the Tools section, (A) make sure your alerts are enabled, (B) temporarily set your alert sounds to Continuous and (C) place your nuvi in GPS Simulator mode.
(7) Move your vehicle to Nebraska Start by selecting Where To? > Favorites > (spell Nebraska Start) > Edit > Set Location (Don't 'Go', just Back out) [depending upon your unit the instructions may be slightly different -- but the aim is to set your vehicle at Nebraska Start.]
(8) Now do a Where To? > Favorites > (spell Nebraska End) and, this time, 'Go' there. When asked if you want to simulate driving route, say, Yes.
You will be traveling on road 74. In about a mile you will see 'Nebraska Alert' appear. Just after you pass that spot your 'bing' alert sound will happen -- over and over. You may even have a balloon appear on your screen saying 'Alert: Nebraska End'.
You are traveling East. The alert sounded at a point about 34.8 miles (184,000 feet) West of Nebraska End. You will have proven that you can have an alert sound that far in advance -- actually up to 200,000 feet.
Try it and please report back re: your success (my fingers are crossed for you, hoping that you really aren't having some internal nuvi problem.)
Remember later to change your alert from Continuous to Single Tone
Garmin Tricks & Tips
Yep, that works. The alerts started at ~35 miles.
But what I'm not "getting" --
I'd like my alerts to be a CIRCLE, and not simply straight ahead on the route I'm driving. If there's something off to the side of my route -- my actual application is Skydiving Drop Zones -- say, 30 miles -- I'd like an alert to tell me that, so if I have time, I might alter my course and stop there. As it is, I'm not getting alerts in time to do this.
But that is exactly what my article tells you.
I guess you haven't had the chance to read it and try it out yet. It too has been tested and works.
It is the same ideas as I wrote a few messages ago except you use the keyword 'TourGuide' in the .csv file and also use a .bmp icon and a .wav file.
Do the Kansas one -- exactly as written -- and you will see that it works for you too.
My suspicion is that perhaps you are not making your .wav file loud enough and you are missing it. Is the TourGuide message appearing on the screen. Another thing that might be happening in your GPS Simulator Testing is that the message is played but before it is allowed to go to your speaker. You can overcome this by making your wave file much longer, either by recording a longer message, recording your message several times in the same .wav file or putting a two or three second prefix of silence before your message (I use Audacity for that).
This is a good exercise and I recommend that everyone should follow it.
I have a 765T , so there were some minor changes in my testing. I needed to have a sound file in the "Nebraska Test" folder (which I named "Nebraska Test.wav" to match my "Nebraska Test.csv" file). My 765T does not have anything like a continuous tone.
Another difference (perhaps) is that in number (7), I press "Map" rether than "Edit" to "Set Loc.".
I followed Gary's instructions and got the alert as expected, but not exactly where I expected. When I changed the distance to 185000, it occurred right at the NEBRASKA ALERT POINT.
Note that your simulation will drive over a mile before the alert sounds so do not be too anxious. 185,000 ft. is right at 35 miles. I was simulating driving at only 36 MPG so I had to go a minute and a half.
Thanks Gary - that was a fun way to prove that alerts can be way out there "along the route". It also works for TourGuide
No, I'm getting the alerts just fine, just not at the point I'm wanting them to be.
As an example -- I have a particular point near Belen, NM that I want an alert for -- it's at the Alexander Municipal Airport, at N34.64494 W106.83341. When I load it as a TourGuide POI, and set the alert distance all the way out at 200000, I'm thinking I should get an alert at 200,000-foot (37+ miles) radius from that point. Instead, when driving north on I-25 from Lemitar (N34.15700 W106.92124) to Albuquerque, I get an alert at just under 10 miles.
What am I missing here? I MUST be expecting something that won't happen, due to my "newness" with TourGuide -- but what???
And I have to leave for San Antonio in a few minutes, so probably won't be back for a couple of days.
I have a 765T , so there were some minor changes in my testing. I needed to have a sound file in the "Nebraska Test" folder (which I named "Nebraska Test.wav" to match my "Nebraska Test.csv" file). My 765T does not have anything like a continuous tone.-- snip --
While you were out last night watching the fireworks in Tennessee, I was able to add something special to your 765T.
If you will go to your Tools > Settings > Proximity Points > Promixity Alerts [Change] > Press 'Audio' at the bottom of the page, you can NOW choose between Single Tone and Continuous Tone.
No thanks necessary -- just a Virtual service on my part.
Thank you for furnishing those coordinates. After examining and testing them in my nüvi I may have some answers to your problems with your TourGuide alert 'not sounding' where you thought it should.
First, I going to assume that you have a .wav or .mp3 (for some users with that capability) correctly associated with your .csv file and that the word 'TourGuide' appears in the file name.
You CAN'T use the default sounds of your GPSr for a TourGuide alert sound.
That file name prefixes all match EXACTLY.
Also, if you are using a .wav file, that a working version of 'sox.exe' (v 14.0.1 is good) is in the same folder as the POI Loader that you are using.
As a slight aside, when you have trouble with a particular Custom POI it is sometimes best to remove all other Custom POIs from your unit so that there can be no interference and you can test with a clean slate.
OK -- Now The Stuff
The Letimar NM point on I-25 that you provided [N34.15700 W106.92124] is ALREADY WITHIN the 200,000 foot distance circle of radius that you have set for the Alexander Airport location [N34.64494 W106.83341]. That is NOT what you really want. You want your start point to be OUTSIDE the 200,000 radial distance.
My calculations say that your ROAD MILEAGE would be > 38 miles but your actual STRAIGHT LINE mileage is only 34.01 miles (~179,573 feet), which is less than the 200,000 ft. you had set. Thus, you were already in the 'zone' when you started. In this case, you don't want to be 'In The Zone'.
Please start OUTSIDE the zone by either reducing the zone to 174,240 (33 miles) or, if you still want to use '200000', start your I-25 run to Albuquerque NM from very slightly North of Socorro NM -- such as [N34.09095 W106.89770] which is 38.36 STRAIGHT LINE miles or 202,541 feet away from the airport and OUTSIDE the 200,000 foot radius.
In both cases you would have a rolling start of less than one minute before the alert sounded when you are simulating the drive.
You said your alert did sound at 10 miles. Of course, that is strange; you setting an alert for 38 miles and it doesn't sound until 10 miles. This leads me to think that the 10 mile alert was from SOME OTHER set Custom POI that is in your GPSr. That is why I suggest, for a TRUE TEST, remove all other Custom POIs and then none can influence what you are doing.
By the way, I tested the settings and they work fine with my 3790LMT.
Another point you might consider is the fact that the TourGuide alert WILL ONLY SOUND ONCE and you might have missed it when placing your vehicle when doing your 'Set Loc/Set Location'. I would suggest that you use a sound file for your alert that has a little LENGTH to it. [The original design for the TourGuide was to play a description of a point that you were approaching.] Perhaps something repeated that will get your attention such as, "TEST POINT TEST POINT TEST POINT."
In addition, some units tend to swallow up the beginning of .wav or .mp3 announcements (it has happened to me with earlier units that I owned.) The fix, that many have used in the past, was to place a 'silent lead' in front of the announcement. This can be done with such programs as Sound Recorder or Audacity. If your device swallows up a portion of your announcement, then this will help as it will be swallowing up the silence before your announcement begins.
Try the above and I think you will be pleased with the results.
Please report back with your results. A waiting POI Factory audience wants to know.
You can also look at my article
DECENT DOCENT DISCUSSION OF THE TOURGUIDE
- A Short Scrutiny With Advice
for some similar help.
OK, just got home. They kept me on the road for a WEEK! !@#$#@!!!
"First, I going to assume that you have a .wav or .mp3 (for some users with that capability) correctly associated with your .csv file and that the word 'TourGuide' appears in the file name. "
Yes, once again, I'm getting the audio I expect, and the balloon on the screen, including the words "TourGuide", just not at the RANGE I expect. My particular alert file is my voice saying,"DROP ZONE! DROP ZONE!" I intend to change it to say,"THERE'S the drop zone!", as we used to call out when looking out the door to find the correct exit point.
OK, so I have removed all POI's from my 560, and re-installed ONLY skydiving drop zones.
So I set my location to the northern edge of Socorro, just about where I-25-BL cuts off of I-25 -- N34.07830 W106.89416. Checking the list (Where to?", "Extras", "Custom POI's", "All Categories" for nearby POI's, I see Skydive NM at 39 miles. Command the GPS to route me to the Kirtland AFB BX (in Albuquerque) and simulate driving the route. This takes me north on I-25 and about 3 miles form Skydive New Mexico, at the closest point.
I'm now at 36 miles, headed north in I25 at 75 MPH, with the 200000-foot distance set in the POI, and no alarm.
So I've now set my location to the northbound lanes of I-25, adjacent to the Socorro Municipal Airport -- N34.01791 W106.89429. Distance to Skydive New Mexico is now 44 miles. Headed again to the Kirtland AFB BX at 75 MPH. (BTW, that's the speed limit on I-25.)
Passing Lemitar, still no alert...
FINALLY! At about 9.5 miles, I got the alert.
I have the following files in my subdirectory (c:\Programs\Garmin\POI files\Skydiving:
I can email these if it would help.
Any ideas just what I'm doing wrong here???
What is a .gdb file?
Why a jpg and a bmp?
Why mp3 and wav?
as you load your skydiving POI file.
Are there any distances set in the .gpx file?
Can you open the gpx file with a text editor and read the Proximity Distance for the first POI? It should look like the following for 132,000 feet.
EDIT: the site is not displaying the line as I have pasted it. all the words have the <> before and after the them
gpxx:Proximity 40233.6 /gpxx:Proximity
What version of EPE are you using?
It should be
If you are using Extra Poi Editor check your settings see http://www.poi-factory.com/node/28521 and make sure to set the 3 as listed. For example using ft for input. Under units you will see editor, select Imperial/US. For Field Read select metric and Field save select Metric.Or you will not get the distance you want.
If the coordinates for Skydive NM are Lat: 34.6451978 Lng: -106.8336958 and the distance is set to 200000 feet, the radius circle from those coordinates should intersect I-25 north of Exit 152 and south of Exit 231.
If you are entering the distance into POI Loader and it's set for feet/miles, that's where the alert should trigger. If you are entering 200000 as a value in the file to be read by Extra POI Editor, the radius is 124 miles as EPE expects distances in a file to be in meters.
9.5 miles is approximately 15,000 meters while 200000 feet is 60,900 meters.
What is a .gdb file?
It's a MapSource file that I saved in the same directory. I would have thought the POI Loader would just ignore it, but I have deleted it.
Can you open the gpx file with a text editor and read the Proximity Distance for the first POI? It should look like the following for 132,000 feet.
What version of EPE are you using?
Now THAT's interesting -- every one of the drop zones has a proximity line in it, and they're all the same.
"<"gpxx:Proximity 40233.6 /gpxx:Proximity">"
(minus the ")
Does that line need to come out?
And, I'm using the Garmin POI loader, straight from their web site. Looks like file version 22.214.171.124 dated 9/17/2009.
I just did a single POI TourGuide file with that number, it is the meters for 132000 feet. That part is normal since EPE and all other programs save the distance info in metric for POILoader.
With that number my distance is exactly 25 miles away when I get the TourGuide alert on my zumo. So your file is good. Now we need to figure out why it doesn't compile right.
POILoader version 126.96.36.199 was known as a very stable version but, I don't know that anyone ever set a distance that far with it. Try downloading version 188.8.131.52, it works real well and is what I used to compile the POI file.
Is the POILoader setting for "What units should be used for distance and speed?" set to "Feet and MPH"?
Yes, set to feet & MPH. I changed the number in the proximity line to 60900 and then did NOT set any proximity in POI loader. Running now while downloading the 2.6.1.
If the coordinates for Skydive NM are Lat: 34.6451978 Lng: -106.8336958
I have "34.644533302634954" lon="-106.82829997502267"
OK, I have figured out some of what I did to get that number in there. I originally downloaded the file, and when I couldn't get the proximity alarm to work as I wanted, I opened it in MapSource and set the proximity in there to 25 miles.
I just got 2.6.1 downloaded, installed, and tried again. No change. Well, other than the fact that 2.6.1 INSISTS on being installed in the Program Files directory -- I couldn't find any option to install it elsewhere.
I think I shall re-download the .gpx and start from scratch.
email me your gpx as it is to email@example.com
email the gpx, bmp and wav files
I already deleted the .gpx and replaced it with new. I'll send you the three files anyway.
AND NOW IT'S WORKING AT 37+ MILES!
I got my alert at 37.8 miles.
Goto Options/Preferences/Units and set -
-> Editor as "Imperial"
-> Csv Write and Read as "Metric"
Load your GPX into EPE
Goto Edit/Replace all...
-> Select Proximity in the Fieldname dropdown field
-> enter 200000 in the New filed valve box
-> Select Replace All command button
Save the file now and then close EPE
Run POILoader in Express mode
- or -
I can just email the Dropzones TourGuide.gpi file to you. Let me know either way.
Edit - you beat me.
Perhaps it was something MapSource had done to the .gpx?
Curious, I wish I could have seen the old file to see what was wrong. Or maybe the new POILoader did the trick.
Off topic -
can you post the internal mem size of the Dezl 560 in this post for me. Either right click the drive when connected to the PC and select Properties or from the "Where to? screen press and hold the battery icon for 8-10 seconds and a diagnostic screen should display with the info on the top banner if its like many other Garmins.
The entire line is:
SW Ver 2.50 dezl 560 A2 V5 8GB 128MB
Or maybe the new POILoader did the trick.
The new loader does at least one thing quite differently. If I load a file form one directory -- like c:/programs/garmin/POI files/skydiving -- then the .poi file is named skydiving.poi .
you can change the name to anything you want, can you not?
Yep, no problem to use Windows Explorer to change the name. It's just different -- last version of the poi loader just called it the same name no matter what. This new way makes it easier to use multiple files.
I like that feature. I individually name some files while I compile others in groups in folders. I maintain 4 different GPSs and everyone wants/needs something a little. I also compile all files to my hard drive and just drag and drop needed files when I get the different GPSs connected to my PC.
And it remembers your last folders used. I like this too!
I'm headed to Belen in the morning -- 200+ miles! And just to make ONE jump! Made my first jump in 15 years last weekend, and I can't let it go! Skydiving is seductive, alluring, intoxicating, ADDICTIVE!
terms | privacy | contactCopyright © 2006-2020