ryguyMN

That's what I get too...a steady falling line when it's off. It's like when I have it on for a while and scroll back looking at history it seems to correct itself and also playing around with the time scale (x-axis). I can't quite pinpoint when the correction occurs...still working on it.

The Colorado is taking readings, it's just not displaying the plotting properly upon power on. I'll bet dollars to donuts it's a software issue. If you change the x-axis scale using the left and right keys inside the rocker, you can determine over 3/6/12 hours if your unit has been plotting. After the unit takes it's first reading 15 minutes after power on, the plotting seems to correct itself on the 45 minute scale.

If the feature is there, then it should work properly, or what's the purpose of having it???

New OR owners should have full confidence and not hesitate to take the plunge! Colorado leaks, so why wouldn't the Oregon too with a similar form factor?

Yes, strangely enough the world does not revolve around freeday..... My theory is that the same programmers that worked on the Colorado worked on the Oregon, so instead of spending time fixing the Colorado, they have been busy trying to rush the Oregon to a release state.... My cynical side (OK my only side) would say that those same programmers have now been yanked over to the Nuvi 500 project...... This will be my only stupid question. How about downloading the Oregon update. Would that work on the Colorado. I know, I am not to tech savvy. Oh, I will not be the first to try it either. If you love playing Russian Roulette, then go for it!

Highlights from this link: 500 *No text-to-speech *Interface will be similar to the nuvi 2x5's *Support multi-destination routing however, unlike the 2x5's. *Maps include lower 48 states, plus Hawaii and Puerto Rico. 550 *Similar to 500, but offers highway coverage of the entire U.S. and Canada *No topo maps.

I think Garmin is trying to transition to using Webupdater excusively for updates of newer products.

That would be two bad launches....Colorado and Oregon. These units were clearly not ready for retail based on the firmware that shipped with the units. In the Colorado's case, there's no excuse for having to wait 8-9 months for a final release to get major bugs worked out. Why settle with mediocrity? This is comparable with nVidia's problems they had with the lack of Windows Vista drivers with that OS came out. I think it took almost a year to get stable Vista video card drivers.

It's a shame because Magellan's hardware is pretty dadgum good. Everything the Explorist is telling me is fairly accurate- positioning, compass, barometer, and even the air temperature. Too bad the support and software are not up to the standards of competitors.

Oh Happy Day! Release the doves!!! FINALLY!!!!! Scratch one major annoyance off the list. Many more to go. Progress is slow, but progress exists. A few months from now us GPS nerds will laugh this whole Colorado "beta" experiment off over a few beers. ( Yes!!! 2.6 fixed a lot of the problems, waypoint deletion crashing was the biggest nuisance and finally we get a blessed firmware release from Garmin. Accruacy is about 11-13 feet on average which is comparable with the nuvi 350. Pretty pleased with this version. My confidence is gradually being restored with Garmin and my fears of this being one big beta experiment are going away!

Good point - Unit ID is different from Serial Number. Probably all serials start with 18Z. I believe all Unit IDs start with 34. Oh great, they are taking Magellan's lead. Why can't they just use one number for consistency?

Give them the serial number under your battery on the microsd card holder. The one that shows on your reciever is missing a digit. Thanks storm, but someone suggested to use the number on the SD card holder, as opposed to the about screen. It starts with 0 and begins with 119. I've tried it with the zero, without the zero, played with the numbers at the end of the serial number, and still couldn't get anything to work. Magellan is still silent on a response. I was hoping to get some current software to replace the DirectRoute 1.0 maps I got in there now to give the Explorist a little more life.

GO$Rs, how did you get your hands on 2.6 firmware for Colorado?

I just want to be able to register my Explorist 600 on Magellan's site, but I can't even do that because of my serial number doesn't follow the 0118 format. I'm trying to give Magellan money for their AccuTerra maps, but I can't even do that!

If you need a GPS today, go with the 60CSx, and avoid the Colorados and Oregons for now.

Good choice! If I had to do it again, I would have bought a 60 series like the CSx. It's widely recognized as a great performing GPSr like the nuvi 350 on the automotive side.

While Garmin is clearly above Magellan in support, Garmin needs to be careful what they are treading into with the Colorado and Oregon. So far these two products have received less than stellar reviews so far and are plagued with bugs.

Dude, did you not read the Topic of this thread? Garmin confirmed a HARDWARE ISSUE requiring unit replacement. Not so fast. It's a similar issue involving the barometer. For my issue, the unit is charting the pressure, albeit not the correct one. The issue in question from the original poster, is no plotting at all if I understand correct. After doing some more testing, the issue appears to correct itself after the unit has been powered on 5-10 minutes and is taking more readings. You just can't power on the unit and look at past readings while it was off. It's strange to say the least, but I'm convinced it's a software plotting issue.

Well I got gitty and took the plunge upgrading to 2.54b. Ran into two issues so far: 1. As reported, manual deleting waypoints cause the unit to crash and shut down. When the unit is powered up the waypoint still exists. The only known way to delete a waypoint is through the Waypoint Manager. 2. Barometer trending is buggy that I brought up in the barometer thread. Here are some snapshots of the barometer during the overnight. The unit was shut off around midnight and here's what it looked like until about 8 AM. It has been properly caliberated as far as I can tell. Screen 1 Screen 2 Screen 3 Screen 4 Screen 5 Screen 6

I'm waiting to hear from a vendor. I hope to have a post up later today or tomorrow showing the 400t available. If it's anything like the Colorados, have fun putting up with major bugs and potential hardware failures! How can anyone be possibly anticipating these Oregon with all the problems? I would be a bit skeptical.

Now that you mention this, Yes, my 300 w/v.2.54 beta is doing the same thing. It's like it is smoothing out the trend dropping any variations. Either that or just drawing a straight line between the current and last known data, hmmm. Wonder if this is a software or hardware issue? It sounds like it might be software. Since it's still beta, it's hard to tell. Yeah, when it's off it will report pressures decreasing all night and I think it even recorded a negative value at one point. Once the unit is powered on it will report the current barometer, although it seems like it's about .2 inHg too high. It would be nice to be able to calibrate it. On my Explorist 600, the barometer is always within .01 inHg, which is pretty impressive for a piece of equipment not designed specifically for weather.

I turned on that feature on my Colorado 300 about 30 hours ago. When I enabled it, my unit was right at the border between 2 & 3 full green bars. I just checked my unit and it is still a solid 2 full green bars, and I used my GPSr a few short times off the external power, so I would say that the drain is rather minor. I have a 400t and my pressure trending works great. Looks like a hot clear day tomorrow. Now if we can just get those fires out... My Colorado's barometer is doing a quiky thing. I have trending set to save always, but when the unit is off the barometer will start trending towards 0 inHg overnight before reseting to the current pressure. Has anyone experienced this? I can do a hard reset, but I was just checking to see if it's worth the trouble or should I be contacting Garmin. Barometers are a nice feature to have to see what kind of weather might be rolling in within the next 24-48 hours.

You'll need to look at the serial no. underneath the battery. It has an extra digit in front and back of your serial no. that you see on your About screen. Thanks for the tip, but this process is still being a pain in the a**. My serial number starts with 0119, however Magellan will only allow input starting with 0118. Does anyone have any other suggestions? Between this and Garmin's lack of support for Colorado, I'm starting to get real pissed with handheld GPS units. It shouldn't be this difficult. Why can't stuff just work the way it should???

I'm trying to register my serial number with Magellan in order to download and use these maps correctly since the map is linked to the serial number. Using the serial number on the about screen on my Explorist 600, the web site is saying my number is too short. What was the work around for this? Thanks!

I would advise against installing 2.54b for now. There seem to be too many reports of units being bricked trying to load the new firmware. I'm holding out for the next update...whenever that might be.