A.T.Hiker

Hopefully this makes it to the OR x50 soon. Hopefully it works. I wonder if it will still draw the straight lines? That issue can at least be worked around by turning your track log off at the end of one segment, and then track on again once you've acquired a fix and started moving at your new location.

Upon eventual release of this unit, I'll be curious about these things: 1) Has the track and odometer recording method been modified to NOT include straight-line connections between power cycles? 2) Does the display have a night time option? 3) Can the master odometer be reset without a hard reset? 4) Can accumulated elevation and trip odometer be reset independently of one another? 5) Will wireless transfer work properly? 6) Will waypoint management work properly? Also does anyone know, will this new advertised display look like the i-Phone? If so, that will make for a nice image. I find the oregon 450 hard to read and not have a very responsive touch screen. Depending on these issues will determine if it's worth selling off the 450 for an upgrade.

I think there is an issue with the montana compass pointer. I have mine set to direct routing and it still does a dance. It's sort of helpful, but could be better in my opinion. Too much fluttering around.

Thank you to cacheoholic. I tried option 2 with success. Everything has been restored! Pesky little thing, the Montana can be.

I just add the individual geocaches right from the cache page on geocaching.com, by clicking on "send to GPS".

Hi folks- I apologize if this topic has already been addressed. I haven't had a chance to search the forums or the internet, but here's the problem. Yesterday, I loaded three new geocaches onto my Montana for some local caching. Upon powering up, I noticed all other geocaches were gone, except for the three i had just loaded. Also gone was every waypoint I had saved. What the heck?? Anyone know what would cause this?? I hate the thought of re-doing everything if this feature is subject to random failures. Is there some sequence I can put the GPS through to retrieve the lost waypoints and geocaches? Like power up ten times, master reset, run around the block, stand on my head, power up again? Seriously, any feedback is appreciated. This is quite a big problem if it can't be fixed somehow. FYI - latest software version (I think, if not, it's from the last month or two), running windows Vista on the computer. Thanks everyone. GPSN

Anyone had any other experiences / feedback for this since my initial post in July? I spoke to Garmin 3 times in regards to it - still no fix. Still happening, even following every step of track off, clear, archive. The straight line problem is avoidable this way, but the odometer is still piling on the mileage between power cycles on Montana and also add Oregon to the list, but only since the last couple of software updates.

Oh, but they do! I can confirm this myself. How so?

It is painful to see Garmin's ignorance to this issue -- I was esentially told the same thing by one Garmin rep, who was as useless as teets on a bull. The other acknowledged and listened, but obviously, nothing has been done. This is NOT the way prior units worked, and to make the claim that users who get the straight line tracks do not know how to operate their units is insulting, both from Garmin and on this forum. If it's intended to function this way, then Garmin should document that and help us understand the brains behind the unit a little bit better and why this happens. I could live with that. Although it might help, I still don't feel as though I should have to fiddle with track editing tools and stopwatches to perform a basic tracking function. Garmin has been good, but I wonder if my Montana will end up as my last Garmin because they just can't seem to work out all of the glitches, nor do they really seem to care to.

The save and clear workaround is valid, however not always convenient in my opinion. If you were involved with our mapping projects, you'd understand. Also of note, as I've stated, the save and clear workaround is valid. However, it doesn't solve the odometer problem. The excess mileage is still added even with a cleared track log. Furthermore, if you save and clear, and the unit has time to record one track point before you power it off and move, you STILL get the straight lines connecting previous end point to current start point. Best to clear at the START of your current journey. I've already made that mistake. The point here is Garmin needs to fix this. This is too much effin around out there, and then if you forget or mix up a step in the sequence your still screwed. I also expect better from units costing hundreds. Any others concerned about this may want to contact Garmin. I will (again) when I get the chance.

That should be Oregon.Beta@garmin.com for the Oregon series GPSr. He has a Montana, you clearly didn't read his message, TROLL. MtnHermit, anyone can read through this thread and see that in each post it is the Oregon x50 firmware being discussed. Have you read the TITLE of the Thread yet? "Oregon x50 software version 5.90 (WebUpdater)" - No mention of the Garmin Montana until you incorrectly gave the Montana Beta email for users to send bugs for the Oregon x50. You even mention firmware 5.50 for the Oregon x50 series one line above where you gave the Montana Beta email address in the same post! As for the UGLY troll remarks, I am going to assume you are having a very bad morning, and need more coffee or meds. Either way, I hope it all gets better for you. BTW, MtnHermit, I just checked your profile, and I can see you have been a member since 2007. In that time you have amassed a total of one hidden cache, and zero found caches. Who, I wonder, is the TROLL here? The name calling is silly since we are talking about GPS tracklogs, not world peace. In any event, to clairfy for those concerned, I own BOTH a Montana and an Oregon. The odometer/track issue has plagued the Montana since launch, and was just introduced on the Oregon post version 5.50. Thanks to user grasscatcher for the tips -- when time permits I plan to try it. Thanks Mtn hermit for your feedback also. As for the issue, I feel Garmin should fix it and we shouldn't have to rely on work arounds and time consuming data mining. This track logging / odometer counting defies logic to me. But, just my 2 cents.

I'm involved with a GPS mapping project for our regional trail conference and state parks. I've run into this straight line track issue as well as the odometer issue on the Montana. Bove have the potential to ruin the entire thing if I'm not real careful in the field, and even then, I'm still having problems. What's worse, I can't seem to edit out the straight track in Base Camp or Mapsource. It just puts it right back in. I'm probably going to have to use the Oregon next time out, and may never upgrade from v5.50. I'm running a real risk of going out and collecting miles and miles of tracks via hiking or biking, and then having them become completely useless. I spoke to Garmin about this a month or two ago. One tech seemed concerned enough and was diligent in collecting information and feedback from me (I think his name was Keith). The other was utterly useless, said that this is normal behavior, and that's just the way it is (I think her name was Tiffany). I was unable to convince her that the Oregon didn't do this prior to the release of v5.80, and her demeanor was more like that of the cranky receptionist at your local doctors office. That was early/mid July and nothing changed, so I guess they don't care enough about this, or enough people aren't complaining about it.

You're suffering from an illusion that Garmin actually tests their software, they don't. You're the tester. Since all these units (OR, DK, MT, etc.) have the same basic software, I just found the same defect on my OR 450 and I just reverted from the latest firmware v5.80 to an older v5.50. Time will tell. Indeed, the Oregon is now exhibiting this behavior as well, and I'm pretty confident it was not doing it before upgrading to version 5.80. They must be copying over bad code, and they've probably suceeded in toasting the odometers on all of the new handhelds. Here's more screen shots: Trip log of kayak trip, at the dock, upon conclusion, just prior to powering down: Trip log upon returning home, powering up, and walking a few footsteps. Note the large jump in the odometer reading in just one additional minute of accumulated time. Also affected is the average speed calculation: And finally, an example of the straight line track that another poster mentioned. That track is almost a 26 mile straight line leading from the lake straight back to my home, and instantlly appeared after powering up and acquiring a satelite lock here at home: My conclusion is that the odometer and track log are starting their calculations based on the last ending point, and not the current starting point. I'm not a GPS programming expert, but does it make sense to do it that way? I might try to figure out how to roll back software on the Oregon, and the Montana I'll just live with (the Montana has been doing this since I got it anyway). In the meantime I may also call Garmin this morning and would encourage others troubled by this to do the same.

You're suffering from an illusion that Garmin actually tests their software, they don't. You're the tester. Since all these units (OR, DK, MT, etc.) have the same basic software, I just found the same defect on my OR 450 and I just reverted from the latest firmware v5.80 to an older v5.50. Time will tell. It would seem that way. It's overall a good unit, and I like the features, graphics, and configurable options, but something like this is just pizz poor programming or a glaring oversight, or both, and you'd think something like this should be caught earlier.

Well, that's the other part of the issue I didn't originally mention. If I don't save and clear track logs after every single hike, they will be a mess of lines connecting my previous ending points to my current starting points. The Oregon behaves this way too, but does not apply these excess track point mileages to the odometer like the Montana does. What I've been doing is section hiking the Appalachian Trail. So I'll drive somewhere, hike 8 miles, end that hike, power down the unit. Then drive 50 miles to another section, power on, hike 10 miles, end, power down the unit, drive another 20 miles, power on, hike 4 miles, etc, etc. You get where this is going. The Montana is a disaster when trying to track mileages, averages, and record tracks over several hikes in different locations without some annoying improvising. It's just odd to me that it functions this way, and that Garmin rolled it off the assembly line like this.

It does. I'm glad it's at least been documented and noted somewhere. Thank you.

The issue I'm posting is regarding odometer mileage errors on the Montana 650. I'll try to explain as best I can. The Montana will always count mileage traveled to all of the odometers, as it should. However, it also applies the straight line mileage traveled between power cycles, which it should not. For example, I can power up here at home, reset mileage to zero, and power off. I can drive 50 miles, power on again, and will have a trip odometer reading of 50.0 miles within seconds of my power up. As a result, you can get screwed up information like this: Notice the outrageous 200.9 miles in 14 seconds in the first screen, and the second screen, at 1 minute 21 seconds, calculating an average of 8928 mph based on 200.9 miles in 1 minute and 21 seconds. In the unit's "brain", it believes it's traveled 200.9 miles in an instant. Note: I really had traveled 200.9 stright line miles from West Virginia to New Jersey, but the unit was turned off in my backpack. I powered on and reset in New Jersey, and as soon as it acquired the sattelites, that's what I got. It's probably not a big deal to many, but for me, and possibly other distance hikers, I like to accurately track miles and averages over days. It's very cumbersome when the unit behaves in this manner. When it's off, I don't want mileage logged. I wonder if anyone has ever contacted Garmin on this issue? I did a while back, but never recieved a reply, and I see no mention of it anywhere on line except in another topic I posted here a while back. The unit does have the most recent software, I just updated it before the trip. As always I welcome the opinions and feedback, and hope people will hound Garmin a little bit! Thank you.

Maybe someone can help: I've been wondering if it's possible to rig up the Montana or Oregon as a simple water depth and temperature tool for use on a kayak since the data fields are already in place? Garmin offers many different depth finders, sensors, transducers, etc, etc, but none list Montana or Oregon as compatable devices. It would seem a logical fit since both units are capable of displaying tide information and depth contours if you have the correct map sets. I'm wondering if it could be a simple matter of plugging in a certain brand of sensor to one of the available jacks in the back of the GPS. Something like this would be an awesome tool for my kayak fishing trips into the wilderness. Any feedback is appreciated.

Are people absolutely certain the 24K topo DVD isn't locked to one device? I was under the impression they too were device specific like the download. I am annoyed with having to switch the SD card between my Oregon and Montana, and one of these days I feel like I'll break one of the units, or drop and lose the mini card. I tried copying the map file from one micro SD to the other and it failed (must be copy protected). But if I know the DVD works for multiple devices I'll be able to sell the micro SD for about even money and I'll just buy the DVD. Thoughts?

It seems to be taking the unit a lot longer to lock on to the birds after this update. Anyone else notice?

My guess is that map downloads are in the same realm as music and video downloads, which most likely means you need a data plan, or be ready to pay hefty data download charges each time you use the app in the field.

Let me try to help out based on my experience, as I too use the units to track barometer trends here at home when they are not out hiking with me. I find the Barometer function on both the Oregon and Montana to be an improvement over earlier models. If your interest is in tracking Barometer, it is indeed important to use "Fixed Elevation" mode. Now, I use it with the GPS switched to off, and what I do is calibrate to my local altitude (about 750 feet here), and then switch to the Barometer plot. As you point out, even at "Fixed Elevation", the altitude wanders, and often quite significantly. However, it seems the unit does retain the initital calibration of 750 feet for the Barometer plot, even though it may no longer be indicating that in the Elevation field How I know is that there is about an 8-tenths of an inch difference between Ambient and Barometer at my altitude, and the unit will retain that 8-tenths difference indefinately. It also always matches the trends of our home barometer to the exact number. I believe the other user was correct when he stated it reports the GPS elevation if you are using it for sailing or any activity and have it set to "Fixed Elevation". Again, my plotting is always done at home here with the actual GPS feature disabled. But, I noticed once the Montana did this with the elevation when I took it hiking and forgot to switch back to "Variable Elevation". I thought there was something wrong with it until I realized my error. If you re-calibrate each time you set sail to your known elevation, and use "Fixed Elevation", your Barometer should be fine, but let us know, I'm curious. Also, of side note, make sure if you ever hike with it and want to track your altitude and altitude changes, re-calibrate it and switch to "Variable Elevation" or else those features will not work correctly.

I thought I had answered you but it must not have posted. Anyway, there is no way to input mileage. I often save screen shots of statistics I want to keep - easy enough to do in the settings. Since the Montana is pretty glitch prone, I would do it pretty often along your trip.

I've experienced both of these issues too, exactly as you described, all in one hike. In fact, it took me three tires to get the barometric plot switched to elevation/distance plot. I thought I might be stuck with it in barometric mode but it finally worked on try 3. On the same hike I was navigating toward my car, which was a mere 300 feet away at the time, and the montana showed 5.53 miles in the "Distance to Destination" field. I should also note I'm still running version 3.90 and haven't tried either Beta update yet.

I've generally loved all of my Garmins, and am a repeat customer. The units have been pretty user friendly and have been reliable in the field. That said, my big complaint is the sometimes glitchy, and just dopey newer unit software designs. As examples of what I mean: 1) You cannot reset the Odometer data field on the Oregons and Montanas. We used to be able to on older units. 2) The accumulated elevation on the Montana was thousands of feet off until the 3.70 software update. Why did it take 6 months to repair such a standard feature? 3) The Montana will not log tracks and mileages correctly from power off to next power on. It creates excess mileage and track points. 4) The nuvi 1490 would not display waypoints, which they acknowledged to me in a reply, but it took a year to fix. The maps finally look decent after all this time. Why? 5) The nuvi 770 powered off frequently for no reason, and was a common issue from what I remember. 6) Sometimes they respond to my inquiries, sometimes they don't. 7) Missing features, like Wherigo on the montana. 8) Other issues that don't necessarily affect me, but that others have pointed out and I"m sure are annoying. I could go on........point being it seems they just don't really test out all of the features, nor is there any urgency on their part to fix. Not saying other manufacturers are any better, as I have no experience and am pretty brand loyal. Point is they are good units, easy to use, but I am becoming concerned about the software on the newest units.