Garmin Oregon x50 Software 2.3 Available
After a relatively bug free introduction Garmin has released its first maintenance release, 2.3, for the Garmin Oregon 550 and 550t. Garmin lists the following release notes:
- Added LKS92 map datum
- Added GPS firmware 3.70
- Added support for GPI Routes
- Added thumbnail to camera page for quick review/deletion of most recently created photo
- Added estimation of the number of remaining photos that the unit can take
- Improved compass responsiveness
- Fixed possible shutdown from low alkaline batteries when on camera page
- Fixed possible shutdown due to deleting a waypoint while panning on the map page
- Fixed issue where multiple GB Discoverer maps would not draw
- Fixed issue with the address wizard not searching in the correct city
- Fixed issue with backlight timer not functioning properly
- Fixed user heading setting for mils so that all applicable headings are displayed with the correct heading format
GPS firmware 3.7 is probably the same firmware which Oregon x00 users have had access to since the 3.12 beta release. Based on my experience and the feedback I’ve received from other users, this GPS software is performing very well on the x00’s – tracks are much cleaner, seem to be accurate and are not over averaged. Issues with recording too much stopped time, stuck heading pointers, and poor WAAS performance still linger on the older platform so I’m not expecting any change on the x50’s with this new software.
Adding a quick review/delete button on the camera is a nice convenience and the improvement to the compass is related to making the compass rotate a little faster, something I complained about in my first review of the 550t.
Check out Setup>Camera>Photo Resolution for an estimate of the number of photos you can store at the three available resolutions.
The GPI routes feature sounds like Garmin is adding “point of interest” route support along with the traditional POI waypoint support but this will require some verification.
The release is only available via WebUpdater but I’ve captured the rgn file and will post them on the x50 Versions page over on the wiki. Discuss this release here.
Related posts:
September 2nd, 2009 at 2:48 pm
[...] Dakota Software 2.2 Available Sep.02, 2009 in Garmin Dakota Straight on the heels of a new update for its larger cousin, the Oregon 550, Garmin has given the Dakota a new set of bits with some very [...]
September 2nd, 2009 at 3:29 pm
[...] this page was mentioned by KingstonGeocaching (@kageocachers), GPSTracklog.com (@gpstracklog), gpsfix.net (@gpsfix) and others. [...]
September 15th, 2009 at 5:35 pm
I’m not sure how you define “point of interest route support” — making a route from a series of POIs is possible now on the Oregon 550. Perhaps that’s new?
I would like to see refinements in the Find Nearest POI functionality (e.g., find a restaurant) that is along the active route.
Example: I drive along the freeway and search for gas stations ahead. I’m ideally looking for one about 50 miles from where I am now, along my active route.
Where To> Find Another > Fuel Services > Auto Fuel…
Today Oregon displays stations up to 49.9 miles behind me, or even to my left or right on roads I do not want to travel. Then it shows those that are 50 miles out, on my way. I must scroll down and examine the little red arrows.
I want Oregon to consider my route when sorting search results, and not offer to take me off course or backtrack. At least sort the results by those that lie ahead of the traveler, then those that are far off course or behind the traveler.
The only way I’ve found to do this is to move my point of reference before searching, which seems like a lot of extra tapping.
Where To> Find Another > tap target > A Map Point > scroll & tap map > Use > Fuel Services > Auto Fuel…
But, then, Oregon’s UI is all about lots of extra tapping.
September 16th, 2009 at 8:12 am
Here are some details on GPI routes and how/what they are used for:
http://garminoregon.wikispaces.com/message/view/home/13935251
I agree that “find nearest to route” would be a nice feature addition — similar to the StreetPilots and Nuvis have. I’m guessing this is one of those features Garmin could add but won’t — who would buy another GPS like a Nuvi if the Oregon was too good!