guest
Home
10:41 pm
April 6, 2010
Offline
Well yeah, GSAK is the best way to load a bunch of caches and pocket queries but Communicator works perfectly for loading a few new caches.
When you see a cache (any cache) you want loaded on your GPSr just 'Send to GPS', it couldn't be easier!
Every morning I check my e-mail for new caches in my area, I'll just 'Send to GPS' each one as I look at them.
No time wasted & I'm out the door for a FTF run! 😛
Why go through any extra steps like downloading GPX files to GSAK then loading the 710 through GSAK for just a few new caches?
Or downloading GPX files to copy & paste to the GPSr?
Or downloading to VP & loading the GPSr through VP?
Or making a new PQ every time 6 or 7 new caches are posted?
We have many options to choose from to load caches to the GPSr, find what works for you and have fun.
When in trouble or in doubt, run in circles, scream and shout
5:18 pm
June 9, 2011
Offline
Personally I never use Magellan Communicator. Like Phil I us GSAK it is a great program. I load my PQ's in it and then deleted the caches I don't want, and with the puzzle caches I am able to edit the cords after solving the puzzle then load all the edited caches into my 710 from GSAK
8:00 am
April 6, 2010
Offline
I'm glad it's working for you now.
For myself I don't really care about the name or GC number in the files.
I always load my 710 with GSAK and "Send to GPS" on GC.com.
Usually I will clear everything from it at least every two weeks.
I have never deleted cache files a few at a time.
But it would make sense to have the names/gc# on the file.
When in trouble or in doubt, run in circles, scream and shout
5:53 am
March 17, 2010
Offline
Yup. Here's how it's done...
David -- Did you get this one ? It's a pretty good idea, and no-one will be against this change !
David is a Magellan user, who is also a contact with the Magellan team. Although not a Magellan employee, his efforts in improving the product are far above the average employee's. He deserves any positive recognition we can give him !
Denis Gionet, OGA Executive Member - Northern Ontario.
4:51 am
January 2, 2012
Offline
Well, great news! I did as suggested and cleared everything out, downloaded a new PQ, then chose a cache that had an update today after the PQ.....and it showed the new log entry! I can't thank you guys enough for this. Very much appreciated. Now if Magellan Communicator can just have the file names aligned with the GC code or name! Is there anyone that can pass this suggestion along to Magellan for consideration?
6:53 am
April 6, 2010
Offline
Your first PQs that are loaded now will be in GPX version 1.0
That may be screwing up the files and not allowing the list to update?
Try starting over, make some new pocket queries, clear the 710 of all geocaches and load the new PQs to it. Then try the "Send to GPS" to see what happens?
The UGDS.BIN file is generated by the unit every time you disconnect it from the computer.
Before the last update I repeatedly deleted it with no trouble.
With the latest firmware I have not had to delete it.
I would recommend the latest firmware for the 710, it cured most of the problems and didn't cause any new ones.
When in trouble or in doubt, run in circles, scream and shout
6:08 am
March 17, 2010
Offline
I've deleted mine with no ill effects. Of course you could save it to the hard drive, and just send it back to the unit if something goes wrong. The cache file problems the others have had I've never seen, I don't tend to follow the routines they've been using when marking a cache as Found, so the problems aren't necessarily global.
No harm in being conservative either. I found the last 2 updates added some nice functionality features to the unit and zero problems.
Denis Gionet, OGA Executive Member - Northern Ontario.
4:54 am
January 2, 2012
Offline
Thanks for the thoughts. I went to gc.com and checked the settings and sure enough I was on 1.0. I changed this to 1.0.1 and was very hopeful but it didn't do the trick. I then read some of the past posts about the bin file. To be honest, I'm a little nervous about deleting it. I'm probably just being over-conservative, but I've only had the unit for a few days and it came with version 5.83 on it and everything works great (except for this Communicator file issue). The compass, maps, geocaching filtering, log.txt, etc., all worked great out of the box. I am pretty reluctant to change anything after all I've read on here! I certainly haven't upgraded it to the new version on magellan's website. Is it a pretty sure bet that the bin file replacing itself won't result in any new problems? I saw where you guys were spending a lot of time on this several months ago and that you were having problems with cache files after you would mark one as "found"...and I just don't want to end up having some other problem show up if I do this!!! How certain are you that the deleting it will be okay? I really appreciate your time and efforts.
1:36 am
April 6, 2010
Offline
Yes I'm using 1.14.
I can think of two things to try.
First, the UGDS.BIN file under USR on the 710 would sometimes get corrupted & screw up several things on the unit.
If I delete the UGDS.BIN file from my 710 it would fix it.
The unit generates a new UGDS file when it indexes files when unplugged.
Second, it's unlikely to be wrong but on Geocaching.com 'Your account Details' - 'Your preferences' GPX Version should be GPX 1.0.1
When in trouble or in doubt, run in circles, scream and shout
11:29 pm
January 2, 2012
Offline
Thanks....good info. I'm using v1.14. Is that what you use, too? If so, why would mine be adding a completely new file with a new name and NOT updating the info in my geocaching list on the unit? If mine would do what you said below, I'd be good to go. I've tried it with both IE and Firefox and it didn't change anything.
10:57 pm
April 6, 2010
Offline
Yes, it would be better if the file had the cache name on it.
But when I "Send to GPS" on a cache that is already on the unit, it shows on the geocache list any new info, like new logs or updates, and does not show on the list any duplicates.
Yes, in the files it adds another file without a name.
Pocket Queries filters are too simple to do what I want, I have found the easiest way to update my cache files on the 710 is to use GSAK to filter the PQs, then load the 710 from GSAK.
In fact a new feature on GSAK lets you update a database with new GPX info without having to get a new PQ.
When in trouble or in doubt, run in circles, scream and shout
7:46 pm
March 17, 2010
Offline
I agree on this 100 %. There's no reason why Communicator can't just use the cache name as the file name, truncate it to 12 or 15 or 18 characters, or whatever, but put a name we can recognize. If we want to manually delete individual cache files from the unit, we don't know which is which from the file names given with Communicator.
Denis Gionet, OGA Executive Member - Northern Ontario.
4:36 pm
January 2, 2012
Offline
I have a new Explorist 710 and love it! I can put PQ files into it just fine. I can use "Send to GPS" okay, too, although the annoying "Would you like to update to the newest version" window comes up every time unnecessarily. But that is apparently being addressed (??). My issue is that I only have a limited number of caches in the area that I haven't found and I manage them and the new ones that come out by just sending individual caches via "Send to GPS" as they are published. I don't routinely update things with a PQ because there are caches that I don't want in there that don't come out with simple PQ filters. Anyway, the issue I have is that Magellan Communicator sends files to my unit with names that seem to make no sense. The file name doesn't use the cache name or even the GC code in it. It starts off with the year (i.e., 2012) and then has a long number after this. If I click on the same cache and "Send to GPS" again, it just adds another file with another number. This is pretty silly! It also doesn't result in the 710 showing the new info....it just continues to show the first file. I've been using a Delorme PN-40 for 3 years and the files make more sense. When "Send to GPS" is used for that unit, I can see the name of the cache on the unit...and when I resend it, it just overwrites it. This is as it should be and ensures that the file is up-to-date. I can't understand why Magellan Communicator would put files into the unit with names that have nothing to do with the cache itself. Any thoughts/input on this? If I have a cache in the unit which is downloaded after I see that it is published, I should be able to come back two or three weeks later and "Send to GPS" again and get all the new logs associated with that cache in the unit. I find the 710 to be a pretty impressive device now that the bugs are mostly worked out, but for the life of me I can't understand how they can take the easiest part (files) and overcomplicate it. Even when you click on the "GPX file" button for a cache, you get the gc # of the cache in the file! I'm just curious if there is any way to get Magellan Communicator to have the sent file name just be the geocache number or name. Thanks in advance for any feedback on this! :cheer:
1 Guest(s)
