Firmware update 8.83 bugs | Bug Reporting | Forums

Avatar
Please consider registering
guest
Advanced Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
sp_TopicIcon
Firmware update 8.83 bugs
May 16, 2011
2:24 pm
Avatar
pprass
Member
Members
Forum Posts: 264
Member Since:
November 12, 2010
sp_UserOfflineSmall Offline
2931sp_Permalink sp_Print

* The proximity alarm sometimes works, sometimes it doesn't. Not sure if it is related to the speed I am traveling in the vehicle. ie if I am doing more than say 50kmp/h I am pretty sure that it has never worked, but if I am walking it sometimes does? Haven't tested it fully and kept record.

I have determined that unless the distance set is actually detected by the GPS, then the proximity alarm won't go off.

So if you are doing 50kms per hour it is unlikely that the GPS will detect that you are 75 metres from GZ and set the alarm off. However if you are walking at 4 kms per hour, the GPs will certainly detect when you are 75 metres from GZ and will go off.

May 14, 2011
1:32 am
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2898sp_Permalink sp_Print

I used GSAK to download 500 caches from a PQ just now, and ended up with the ERROR! on every one of them and every waypoint.

So, I deleted everything in /USR and it's OK again. There are still some warts, but at least I can use the thing!

---
San Francisco, CA

May 14, 2011
1:13 am
Avatar
pprass
Member
Members
Forum Posts: 264
Member Since:
November 12, 2010
sp_UserOfflineSmall Offline
2897sp_Permalink sp_Print

I have been working my 610 with 4.82 hard for the last 5 days and I find that the electronic compass stalls for a minute or two and what is more frustrating - it will not calibrate no matter what I do. It just says "fail" every time. New batteries won't do it either.

Recapping my little issues in case Magellan are interested:
* Electronic compass stalls
* Compass won't calibrate
* After uploading caches into the GPS I have to remove the UGDS.BIN file otherwise I get an error on all of them.
* Can't Search by Name for caches that are more than 50 kms away. (There must be something I am doing wrong here)
* The proximity alarm sometimes works, sometimes it doesn't. Not sure if it is related to the speed I am traveling in the vehicle. ie if I am doing more than say 50kmp/h I am pretty sure that it has never worked, but if I am walking it sometimes does? Haven't tested it fully and kept record.
* With the heavy caching work that I am doing, a quick start up is sorely missed - especially when I have to replace batteries and I am trying to work out which track to take at a junction.
* Background colour of map (Aus map) is far too dark - dark olive green and it is difficult to pick up cache icons against that background.
* Position indicator is far too large and just gets in the way of detailed navigation.
* Next nearest cache function doesn't work.

I am able to put up and get used to most of the above issues as they don't really interfere with caching, but the compass stalling/calibration is really an issue for me - after all that is the whole point of a GPS isn't it? All of the other stuff is nice to have add-ons!

ps: I no longer demonstrate my GPS to people who ask about it. Also my wife's eXplorist 500 is finding caches quicker than I can due to the compass issue.

May 14, 2011
12:17 am
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2896sp_Permalink sp_Print

Not all is rosy I guess.

I tried to upload the field notes to geocaching.com and the logs.txt file has disappeared, although it was there when I got home and VP hasn't been anywhere near the GPS. The Magellan_Geocache_Extention.gpx file is still there though.

So that's still an issue.

---
San Francisco, CA

May 14, 2011
12:12 am
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2895sp_Permalink sp_Print

Forgot to mention, it even showed me an icon of a picture I had taken at a geocache (which it never showed me before) and I clicked on it and it showed me the picture, which I guess is exactly what it is supposed to do.

I'm pretty pleased!

🙂 🙂 🙂 🙂

---
San Francisco, CA

May 13, 2011
11:57 pm
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2894sp_Permalink sp_Print

Good News, Guys!

I noticed that all of the files in the /USR directory are dated today. I figured "What do I have to lose... the thing is just a $550 paperweight for me right now anyway".

So, I deleted ALL of the files in that directory, not just the UGDS.BIN file... I also deleted barhistory.sav, PrevDest.abx, Trips.cum, and Trips.trp.

I let it restart... most of those were regenerated on restart. Not all though. But what the heck, I decided to take it for a walk.

First thing I noticed is that now the map is updating smoothly. The map is not spinning in Track Up mode. I chose one of the WP I saved early this morning and walked to it. The distance counted down smoothly and it took me all the way to it without stalling. The prox alarm came on, and I was there.

I set it for a nearby geocache and it took me right to it with no stalling of the display. I marked it found, and everything still works (although it did not ask me if I wanted to go to the next nearest cache).

When I got home I put it back on the computer and all of the files that had been in /USR are now back. The Geocaches directory has a "logs.txt" and a Magellan_Geocache_Extention.gpx file too.

Near as I can tell, my unit seems to me to be substantially FIXED.

Not sure if the files in /USR had gotten corrupted, or if they will again, but at least I know a way now to get it working again!

---
San Francisco, CA

May 13, 2011
7:11 pm
Avatar
David
Member
Members
Forum Posts: 646
Member Since:
March 20, 2010
sp_UserOfflineSmall Offline
2893sp_Permalink sp_Print

Here you go Denis, just so you don't feel to left out!!!

I know that it is out of focus, but my little camera is a cheapo...

That was actually taken with new batteries, the compass was calibrated and the unit was sitting on a table. However, I will say that except for this minor issue the unit is totall usable even though the compass does show that it needs to be calibrated almost everytime I stop with it, if I'll just move the unit around a bit the compass drops right into calibration...

David


 

 

 

May 13, 2011
6:43 pm
Avatar
denisetdoris
Member
Members
Forum Posts: 400
Member Since:
March 17, 2010
sp_UserOfflineSmall Offline
2892sp_Permalink sp_Print

michaeln wrote:

phild31 wrote:

At 190 feet from the cache it stopped tracking.
I shut down the unit, restarted and it tracked to 50 feet and stopped.

I wonder why it doesn't happen to EVERYONE though. Perhaps it is some interaction between certain hardware units and the 4.83 firmware?

I've got a 610 Canada edition. Every time I use it, I do a field note, even if I just press Enter after seeing the keyboard, at least that much. Often I write a note (I'm getting better with the split-screen)... And EVERY time I mark a cache as Found, I get my notes when I log on GC or VP. I did delete the UGDS.bin file to test the compass spin theory, but I didn't have a bad case of compass/map spin like others have. I've also kept the MGE.GPX file intact.

Essentially, a 710 is a 610 with more memory and an extra map. My unit doesn't do any of the oddball things that others report, and it's not for the lack of using it. It's DEAD accurate, at least as accurate as my T-500, if not more. I am using the most recent firmware as well, and that change hasn't caused any issues.

Anxious to see what happens with all of you guys once the issues get fixed.

Denis Gionet, OGA Executive Member - Northern Ontario.

May 13, 2011
5:21 pm
Avatar
phild31
Nashua, New Hampshire USA
Member
Members
Forum Posts: 1479
Member Since:
April 6, 2010
sp_UserOfflineSmall Offline
2891sp_Permalink sp_Print

OK, I'll play around with it this Sunday and mark some caches as found to see what happens.
Until then I'll not mark any as found to see if any problems develop.

When in trouble or in doubt, run in circles, scream and shout

May 13, 2011
5:16 pm
Avatar
Caotix
Member
Members
Forum Posts: 143
Member Since:
December 3, 2010
sp_UserOfflineSmall Offline
2890sp_Permalink sp_Print

In short Version, the Magellan_Geocache_Extension.gpx
is the file where your founds are stored.

May 13, 2011
5:08 pm
Avatar
phild31
Nashua, New Hampshire USA
Member
Members
Forum Posts: 1479
Member Since:
April 6, 2010
sp_UserOfflineSmall Offline
2888sp_Permalink sp_Print

michaeln wrote:

My 710 doesn't have a Magellan_Geocache_Extension.gpx file.

After deleting it and all gpx files I loaded about 4,000 caches from GSAK.

My 710 doesn't have a Magellan_Geocache_Extension.gpx file now.
It did before I cleared the geocache file of all gpx files.
What is the Magellan_Geocache_Extension.gpx file?
Is it created when you log a cache?

When in trouble or in doubt, run in circles, scream and shout

May 13, 2011
4:33 pm
Avatar
David
Member
Members
Forum Posts: 646
Member Since:
March 20, 2010
sp_UserOfflineSmall Offline
2885sp_Permalink sp_Print

Maybe I'm insane! But I've been out cachine several times since the new firmware has come out and yes I'm seeing several of the reported issues like the spinning map screen and the compass not staying calibrated. However, my field notes work every time. Now I always use the same procedure in marking them, but they're always there... I'm going to have to play around with it this coming Monday and see if I can get it to drop some...

David


 

 

 

May 13, 2011
4:27 pm
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2884sp_Permalink sp_Print

My 710 doesn't have a Magellan_Geocache_Extension.gpx file.

---
San Francisco, CA

May 13, 2011
4:19 pm
Avatar
phild31
Nashua, New Hampshire USA
Member
Members
Forum Posts: 1479
Member Since:
April 6, 2010
sp_UserOfflineSmall Offline
2883sp_Permalink sp_Print

ShortcutHicksy wrote:

phild31 wrote:

Deleting the UGDS.BIN file cleared the problems every time but marking a cache as 'found' created the problems again every time I marked a cache as 'found'.
When I did not mark any caches as 'found' I had no problems.

Phil,

At any time did you try deleting the Magellan_Geocache_Extension.gpx file. I have been trying to work out how it, the UGDS.BIN and Logs.txt interact in looking at my problem, with no logs.txt file creation.

It would be easier with a copy of the software description.

Graham.

First, I don't know programing I just try different things to see what works and doesn't work.

I deleted the all geocache gpx files and the UGDS.BIN file then loaded a new batch of caches. When I did not mark any caches as 'found' I had no problems.

I have no idea why this happens and no hope of finding out why.
I'm just trying to find a consistent behavior to report to the people that can fix it.

For myself I can live without the field notes until it's fixed, the large arrow is a minor thing and the keyboard is even less of a problem for me.

The unit stopping tracking has only happened to me after I marked a cache as found, so I won't mark any caches as found until the firmware is fixed.

The 710 worked great for months before the 4.83 upgrade, I expect the people at Maggie to fix the problems fairly quickly. This is not the same Magellan that that never responded to user issues with the Tritons.

When in trouble or in doubt, run in circles, scream and shout

May 13, 2011
3:54 pm
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2882sp_Permalink sp_Print

Well, I'm more confused than ever.

I have no FOUNDS marked on my 710. I deleted that UGDS.BIN file, then used GSAK to load up 500 geocaches after clearing all waypoints, geocaches, photos and notes.

I booted the 710 and went for a walk around the neighborhood. I marked a waypoint at each street intersection as I walked. But I noticed as I walked that although the compass was showing as calibrated and all bars were lit up on the signal strength meter and it was showing from 16-20 feet accuracy, the map and / or compass display did not update smoothly.

For instance, the map would show me at a constant position on the road as I walked, although the smart arrow would detect the slightest directional change. Then suddenly the map would update and show me in a new position farther down the street.

On the way back, I set it to seek the waypoints I had laid down. So, I selected the closest one and it said something like 300 feet to go. I walked toward it, about 2/3 of a block before the map jumped and showed me farther down the block and distance to go now said about 160 feet. This behavior continued as I walked toward the corner, then as I got about 20 feet from it the prox alarm circle came on and it updated the map to show me about 20 feet from the waypoint. I continued walking on BY the waypoint and turned the corner and was 100 feet or more past the WP before the map updated again.

This is what makes this unit so useless to me. It seems to update the map every 140 feet or so, whether I am searching for something or just walking. Mind you, in TRACK UP mode it constantly updates the map display in terms of rotating it about the central axis of the arrow, but it does NOT update it except for every 140 feet or so in terms of showing my updated position.

It's like it needs a big squirt of DataLube(tm).

---
San Francisco, CA

May 13, 2011
3:27 pm
Avatar
Mr Walleye
Member
Members
Forum Posts: 4
Member Since:
April 23, 2011
sp_UserOfflineSmall Offline
2880sp_Permalink sp_Print

Count me in the EVERYONE group here.

I have had this happen at least four out of ten of my last caching runs.
The third time, the unit almost went swimming with the fishes in a nearby pond I was so frustrated.
On that trip, just for fun, I eventually put in fresh batteries even though the originals had two bars on the meter left due to another post I read.
Boom, the thing worked like a blue tick hound finding escaped cons the rest of the day.
On subsequent trips I have just removed and reinstalled (full power down reboot) the batteries and that did the trick.
This, coupled with my disappearing field notes, the goofy double keyboard, and giant catioon arrow in the middle that covers four square blocks in the quarter mile range, are really making me regret retiring my T2000.
Sure, it worked something awful the first year I owned it too!
But at the end of it's short life it was amazingly accurate and stable.

I have begun to accept the fact that although the display is telling me I have better than 15 foot accuracy and seven signals locked, I may need to have a 100 foot search circle.

By accept, I mean watch for a good deal on eBay soon!
Maybe I'll just put it in the drawer and wait until Maggie either fixes it or bails on it.

Life is to short to be this frustrated.

May 13, 2011
2:47 pm
Avatar
michaeln
Member
Members
Forum Posts: 61
Member Since:
May 5, 2011
sp_UserOfflineSmall Offline
2878sp_Permalink sp_Print

phild31 wrote:

At 190 feet from the cache it stopped tracking.
I shut down the unit, restarted and it tracked to 50 feet and stopped.

My 710 does that exact same thing, and it is the one thing that makes this device useless to me for geocaching (and geocaching is the reason I bought it).

Magellan is going to swap my unit for a different one, but I am not optimistic a different unit is going to solve this problem, since it really appears to be a firmware issue.

I will experiment with it some today deleting the UGDS.BIN file and then using it without marking a FOUND and then trying it after marking a FOUND to see if it clearly triggers the misbehavior as on your unit. I bet it will. Right now I cleared it, loaded 500 caches from GSAK and have deleted that UGDS.BIN file so I can start testing.

I wonder why it doesn't happen to EVERYONE though. Perhaps it is some interaction between certain hardware units and the 4.83 firmware?

---
San Francisco, CA

May 13, 2011
11:12 am
Avatar
ShortcutHicksy
Member
Members
Forum Posts: 250
Member Since:
March 19, 2011
sp_UserOfflineSmall Offline
2877sp_Permalink sp_Print

phild31 wrote:

Deleting the UGDS.BIN file cleared the problems every time but marking a cache as 'found' created the problems again every time I marked a cache as 'found'.
When I did not mark any caches as 'found' I had no problems.

Phil,

At any time did you try deleting the Magellan_Geocache_Extension.gpx file. I have been trying to work out how it, the UGDS.BIN and Logs.txt interact in looking at my problem, with no logs.txt file creation.

It would be easier with a copy of the software description.

Graham.

May 13, 2011
9:19 am
Avatar
phild31
Nashua, New Hampshire USA
Member
Members
Forum Posts: 1479
Member Since:
April 6, 2010
sp_UserOfflineSmall Offline
2876sp_Permalink sp_Print

To continue reporting bugs in the update;

Today I went after a cache, found it with no trouble.
I marked it as found on the 710, did not make a comment, did not use the go to nearest list afterwards.

Then back at the truck, in vehicle profile I picked a cache to go to.
My settings had changed to default.
When I went to geocaching profile the electronic compass started to spin and rotate. I shut off the compass to stop the spinning and went after the cache. At 190 feet from the cache it stopped tracking.
I shut down the unit, restarted and it tracked to 50 feet and stopped.
I found the cache, shut the 710 down and went home.

After deleting the UGDS.BIN file everything worked properly.
So I did some tests, when I mark a cache as found the problems come back.
If I don't mark a cache as found no problems with 12 test runs to 12 local caches.
Then I marked one of them as found and all the problems came back.

I then spent about 4 hours doing this 4 or 5 times with different caches, first with over 3,000 caches loaded, then with 25 loaded, then with just 5 and got the same results every time.
I loaded caches from just GSAK, then just VP and then just straight from GC.com and got the same results no matter how the caches were loaded to the 710.

Deleting the UGDS.BIN file cleared the problems every time but marking a cache as 'found' created the problems again every time I marked a cache as 'found'.
When I did not mark any caches as 'found' I had no problems.

When in trouble or in doubt, run in circles, scream and shout

April 30, 2011
11:40 pm
Avatar
phild31
Nashua, New Hampshire USA
Member
Members
Forum Posts: 1479
Member Since:
April 6, 2010
sp_UserOfflineSmall Offline
2639sp_Permalink sp_Print

Caotix wrote:

For Point 3.
I had the same problem. After I changed Menue (left lower corner) Geocaches to all (before it was found only) the result was that my eX showes now the next 50 Caches after finding one.
It seems that there are different settings cause under quick button (left top corner) Geocaches i had a different setting.

I think I still have a long way to go to understand my eX. :blink:

For me I will sometimes get the list, sometimes get one cache, sometimes get a cache I already found and sometimes get nothing at all on the list.
It seemed random.
I no longer use that function, I set a side button for the nearest cache list/description.
The best thing about a side button for cache list/description is when you are on a route to a cache one button and the description page is up. Hit the button again and you are back to the map/compass page.

When in trouble or in doubt, run in circles, scream and shout

Forum Timezone: America/New_York
Most Users Ever Online: 99
Currently Online:
Guest(s) 3
Currently Browsing this Page:
1 Guest(s)
Top Posters:
phild31: 1479
David: 646
denisetdoris: 400
pprass: 264
S!G: 251
ShortcutHicksy: 250
jmebd: 184
Sockeye: 170
Caotix: 143
Paganel: 116
Member Stats:
Guest Posters: 5
Members: 804
Moderators: 0
Admins: 3
Forum Stats:
Groups: 14
Forums: 41
Topics: 921
Posts: 7328
Newest Members:
KHB3, ethanwetherspoon, EmilyAnges, cletachristie0, Robert Temple, OSS-SAS
Administrators: jg_the_Prophet: 27, mike_the_Enforcer: 0, OSS-SAS: 1

Leave a Reply