Jump to content

Oregon 2.95 beta released


Recommended Posts

Change History

Changes made from version 2.94 to 2.95:

 

* Report any problems with beta software to OregonBeta@garmin.com

* Added big numbers option to the trip computer

* Added new trip computer dashboards

* Added POI subcategories

* Added 'search near' option to Geocaches search

* Added change location to Sun and Moon

* Added change location to Hunt and Fish

* Fixed shutdown on the map

* Date: April 1, 2009. Weather: Cool. Health: good. Food: 905 pounds. Next landmark: 190 miles. Miles traveled: 364 miles.

 

http://www8.garmin.com/support/download_details.jsp?id=4393

Link to comment

I love the flexibility they have added to the Trip Computer.

 

And there is now Search Near available in Geocaching, as well as Where To.

 

Garmin is certainly concentrating on the Oregon.

 

Very cool release..I did not believe it is true story on 1st April :unsure:

 

I've found first problem. After few minutes of playing with device -- white screen on map (grey-gree when switched to different profile) .. Profile change did not help, only restart solve it.. Hopefuly there won't be other .. This is known story since Colorado and could be map combination (autonavigation products) related

Edited by kafkar
Link to comment

@strumble

 

Please update header of the first post (in advance modus), so that we know whats inside.

 

Thanks.

 

I believe this is the page jotne is looking for:

 

http://www8.garmin.com/support/download_de...d=4397#Instruct

 

........by the way - what's with the "weird" entry next to the "date" that reads "Date: April 1, 2009. Weather: Cool. Health: good. Food: 905 pounds. Next landmark: 190 miles. Miles traveled: 364 miles." ??? Why is all that information there???

 

Bill

Link to comment

Maybe something to do with the release date ?

 

My Oregon just appeared on my visa, now it just has to appear on my doorstep - and no big numbers in the trip computer and POI subcategories were two of the things I thought I were going to miss from my 60Cx - great timing :unsure:

 

Gary

Link to comment

I have quite a few extra waypoints, "Here lies ..." 10 to be exact. Could these some type of clue? Just a prank by an engineer? I have Here lies ... Chad, Paul, Tom, Brad, Timm, Dan, Adam, Wilson, Chura, and Jerad. Each have their own little sayings...

 

Don

 

I figure they are Colorado developers who took the easy way out.

Link to comment

I notice the URL posted shows the update is for a 300, is it safe for a 400t ?

 

Here are the direct links for the entire Oregon series:

 

Oregon 300 software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4393

 

Oregon 200 software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4395

 

Oregon 400t software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4397

 

Oregon 400c software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4399

 

Oregon 400i software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4401

 

Bill

Link to comment

I notice the URL posted shows the update is for a 300, is it safe for a 400t ?

 

Here are the direct links for the entire Oregon series:

 

Oregon 300 software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4393

 

Oregon 200 software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4395

 

Oregon 400t software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4397

 

Oregon 400c software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4399

 

Oregon 400i software version 2.95 Beta as of April 1, 2009

http://www8.garmin.com/support/download_details.jsp?id=4401

 

Bill

I can just add the 2.95 and it will include everything from the other vesions right?

Link to comment

I can't find the POI catagories...the POI's in my OR looks the same, and I also don't see the easter eggs in the waypoints...what am I doing wrong..

 

That's because they are all 1500+ (give or take)miles away :unsure: Goto your waypoints, use the ABC touchpad to type in one of the names (see Post 16 above) and tap the green check mark.

 

Bill

Edited by 2Wheel'in
Link to comment

I can't find the POI catagories...the POI's in my OR looks the same, and I also don't see the easter eggs in the waypoints...what am I doing wrong..

 

If you have City Navigator loaded, when you press Where To, you should be able to press the Food category and then get a menu of food types (Italian, Mexican,, etc.)

 

Works fine on mine. Just like the old 60CSx

Link to comment

A user on the wiki figured out the strange release notes (and the mysterious waypoints also make sense). Way to go ClimbGuy!

 

http://garminoregon.wikispaces.com/message...w/home/10762542

 

http://en.wikipedia.org/wiki/The_Oregon_Tr...(computer_game)

 

My kids used to play that game. Glad to see the OR beta team have a sense of humour. And thrilled at the real easter eggs they gave us in this update. Keep em coming.

Link to comment

Great updates in the new release!

 

grumble grumble, no WAYPOINT AVERAGING, grumble grumble.

 

You would think that with a bunch of people e-mailing them about the lack of waypoint averaging in the Oregons they would just go ahead and add it. Is there some legal reason they've kept it out?

 

PS: I feel bad for the Colorado owners. I hope some of these great new features make it over their way.

Link to comment

A little off subject, but can you use a car charger from a Razr phone for the Oregon? I know it will not charge it.

Thanks

 

You can use the razr charger. Just plug it in while in the car. The OR will operate as if it is on AC. Saves battery life while traveling, plus it leaves the back light on all of the time.

Link to comment

I'll bet i know why we don't have waypoint averaging on the Oregon yet. Its obvious they have accuracy issues at low/no speeds. This is most pronounced in the drunken tracklogs. Well, if you have accuracy problems while standing still, averaging probably won't work just right.

 

I'm sure its within their technical abilities to add it, and they will, as soon as it will actually do us any good.

Link to comment

One complaint from me and the problem started back with v2.93. When plugging into the PC the unit now often locks up. Have to pop the batteries (plenty of juice in them still) and plug it into the PC again. Has not locked up on any of the second attempts.

 

Matt

Link to comment

Just sent an email to the beta reporting address listed in 1st post.

==========================================

 

Thanks for the recent improvements! Trip Computer data field options are awesome. POI subcategories have made finding places easier. Here's a list of my findings.

 

- When plugging into the PC the unit now often locks up. Have to pop the batteries out and back in (plenty of juice in them still) and plug it into the PC again. Has not locked up on any of the second attempts. Started happening with v2.93.

 

- Would like to see 'Voltage' as an available data field. The battery indicator is OK but voltage gives much better information. Don't replace the battery icon, just make the 'Voltage' data field available.

 

- Waypoint Averaging....please!

 

- Data fields should have optional white text on dark field background. I'm all about having options and know that it's possible because the early versions used this format.

 

Thanks again,

Matt

Edited by mattalbr
Link to comment

Changes made from version 2.94 to 2.95:

Report any problems with beta software to OregonBeta@garmin.com

Added big numbers option to the trip computer

Added new trip computer dashboards

Added POI subcategories

Added 'search near' option to Geocaches search

Added change location to Sun and Moon

Added change location to Hunt and Fish

Fixed shutdown on the map

Date: April 1, 2009. Weather: Cool. Health: good. Food: 905 pounds. Next landmark: 190 miles. Miles traveled: 364 miles.

 

I'm intrigued by the last change :?

 

Thanks to Allory for posting about the release here and including links to the various release.

Link to comment

Changes made from version 2.94 to 2.95:

Report any problems with beta software to OregonBeta@garmin.com

Added big numbers option to the trip computer

Added new trip computer dashboards

Added POI subcategories

Added 'search near' option to Geocaches search

Added change location to Sun and Moon

Added change location to Hunt and Fish

Fixed shutdown on the map

Date: April 1, 2009. Weather: Cool. Health: good. Food: 905 pounds. Next landmark: 190 miles. Miles traveled: 364 miles.

 

I'm intrigued by the last change :?

 

Thanks to Allory for posting about the release here and including links to the various release.

 

Last change is a humorous reference to an old video game called The Oregon Trail. There is a more detailed link further back in this thread.

Link to comment

I'll bet i know why we don't have waypoint averaging on the Oregon yet. Its obvious they have accuracy issues at low/no speeds. This is most pronounced in the drunken tracklogs. Well, if you have accuracy problems while standing still, averaging probably won't work just right.

 

I'm sure its within their technical abilities to add it, and they will, as soon as it will actually do us any good.

 

Hey tylosaurus, I'm going to have to respectfully disagree with your premise that the Oregon has accuracy problems. The only problem I can see is with the drawing of the track itself. Stationary accuracy and Tracklog accuracy are two different species. Stationary accuracy, i.e. finding a geocache (stationary object) seems to be on par. What really dissapoints is 1) The smoothness/presentation of the tracklog and 2) WAAS pickup and retention. A little more averaging of the tracklog may not be such a bad thing. This may be why, as g-o-cachers noticed in the early days of the Oregon, the tracklog was so heavily averaged. Reduce the averaging and you get what we have now, messy but relatively accurate Tracklogs. After reading other posts and the Delorme posts (PN-40 uses the same chipset) I really think the problem is in the manufacturers firmware specs. Cartesio needs to step it up and issue the companies using their products a fix.

 

I'm so tired of not picking up WAAS on these newer models. WAAS has only been out for what a DECADE?? Come on Garmin, let's dial in the WAAS pickup on these things. :laughing:

Edited by yogazoo
Link to comment

... I'm so tired of not picking up WAAS on these newer models. WAAS has only been out for what a DECADE?? Come on Garmin, let's dial in the WAAS pickup on these things. :laughing:

 

I haven't done any real testing of this, but it appears that there might be an issue with accuracy when WAAS is enabled and locked. I saw this happening to me this morning. I turned my GPSr on with the new update and it was accurate enough. As I drive towards work, it was already off by 50-75 feet when I was just a few miles from home. I power cycled the unit and it jumped right back to the [seemingly] correct location. I drove another 5-6 miles and the GPSr appeared to have drifted off by 50-75 feet again, so I power cycled again. I turned off WAAS and the unit seemed to remain accurate for the last 10 miles of my trip to work. I hope to perform some more "serious" testing of this over the next few days...

Link to comment

This a bit obscure. My unit hangs (hour glass shows forever - unit is not locked up) when I do the following

 

Where To / Tracks / BT Hike - Niagara 1

 

where BT Hike is a track I loaded to the GPS via Mapsource.

 

I can hit Current Track or Go Back arrow to break out of it.

 

All relevant material sent to OregonBeta.

Link to comment

I have installed several maps generated from raster images with Bmap2mp. Tried to create new route with route planner by tapping next point and use map. After tapping on map Oregon shutoff. If I have these maps disabled all working OK. Sent error log to Garmin.

 

Good luck there. Garmin does not approve of custom maps.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...