Oregon 2.85 BETA
#1
Posted 21 January 2009 - 02:26 PM
* Added support for Custom POI database and category selection
* Added ability to force the Oregon into mass storage mode by holding the power button for 30 seconds while plugged into a USB cable
* Added NMEA 9600 baud
* Improved map zooming
* Improved raster map appearance
* Improved map draw speed
* Improved battery gage for NiMH batteries
* Improved stability when changing profiles
* Fixed roads being shown on top of Garmin GB Discoverer maps
* Fixed airport points not displaying on the map
* Fixed some scan points not working properly with Garmin GB Discoverer maps
* Fixed track logging setting being changed when changing profiles while simulating GPS
Download it here.
Post on GPSFix. I'll update here with screen shots, new issues, as I test.
#2
Posted 21 January 2009 - 03:08 PM
#3
Posted 21 January 2009 - 03:29 PM
http://forums.Groundspeak.com/GC/index.php...p;#entry3795792
I cannot see the Battery differences!
This post has been edited by strumble: 22 January 2009 - 02:03 AM
#4
Posted 21 January 2009 - 03:32 PM
#5
Posted 21 January 2009 - 04:03 PM
#6
Posted 21 January 2009 - 04:28 PM
On the Colorado wiki I have a region file from Garmin that essentially does the same and it saved me a few times in the early days.
I just tried it. If you plug the OR into the USB cable, power off and then hold the power button for 30 seconds you do end up in USB storage mode and bypasses the the normal boot cycle (loading maps, waypoints, etc).
Good stuff.
#7
Posted 21 January 2009 - 04:40 PM
So should I update?? LOL
I rushed to 2.8 and was not happy.
#8
Posted 21 January 2009 - 04:49 PM
#9
Posted 21 January 2009 - 05:12 PM
The profile change problem is definitely fixed.
And the data base select for Custom POI's
This post has been edited by Tequila: 21 January 2009 - 05:13 PM
#10
Posted 21 January 2009 - 07:59 PM
Could someone please explain how to update to ver 2.85.
I read that it's not available from web updater, so I downloaded the 2.85 file but I'm not too sure how to install it
I'd like to be rid of the glitchs that 2.80 has.
Thanks for any advice
Roger
edit
I found how to do the update,
map redraws a lot quicker
and profile change problem is fixed for me
fingers crossed all works well
incase anyone else wants to know
Installation Instructions
Download the self-extracting archive file for your Oregon onto your hard drive.
Connect your Oregon to a USB port on your PC.
Allow your Oregon enter USB mass storage mode.
Unzip the files in the archive by running the downloaded executable file.
Follow the instructions provided by the launched update application on your computer.
This post has been edited by fnq2: 21 January 2009 - 10:07 PM
#12
Posted 22 January 2009 - 01:32 AM
Good news, but how did you find this? I looked for this in the Garmin site but I did not find anything
AA
#13
Posted 22 January 2009 - 01:48 AM
this is where I found the download and instructions.
https://buy.garmin.com/shop/store/downloads...1&pID=14905
there is a link for the download posted above by go casher
hope this helps
Roger
#14
Posted 22 January 2009 - 03:08 AM
gilius, on Jan 22 2009, 01:10 AM, said:
/gilius
You will not be able to load this version via a Macintosh.
This is a beta release, and Garmin does not provide Macintosh interconnectivity for their beta software.
You will have to wait for the software to exit the beta stage. At that time you will be able to load the software on to an Oregon by means of the Garmin Macintosh WebUpdater.
.
#15
Posted 22 January 2009 - 03:28 AM
#16
Posted 22 January 2009 - 03:40 AM
Oregon 300: http://www8.garmin.c...ils.jsp?id=4393
Oregon 400t: http://www8.garmin.c...ils.jsp?id=4397
Oregon 400c: http://www8.garmin.c...ils.jsp?id=4399
Oregon 400i: http://www8.garmin.c...ils.jsp?id=4401
#17
Posted 22 January 2009 - 05:28 AM
#18
Posted 22 January 2009 - 05:53 AM
That's not a feature that I like! Is it supposed to be doing something different? I had this same POI loaded before the update and it was working fine.
JetSkier
#19
Posted 22 January 2009 - 09:24 AM
#20
Posted 22 January 2009 - 09:34 AM
e.g.
Food
->italien
->american
Stores
-->clothes
-->electric
#21
Posted 22 January 2009 - 09:36 AM
1) As soon as the zoom level is changed the current layer is extrapolated to the new zoom level which happens very quickly but can look fuzzy (zoom in) or compressed (zoom out)
2) A few hundred milliseconds later the new layer is presented.
I would agree it is an improvement, but wasn't sure it was faster as Garmin claimed.
#23
Posted 22 January 2009 - 11:09 AM
#24
Posted 22 January 2009 - 11:22 AM
g-o-cashers, on Jan 22 2009, 10:36 AM, said:
1) As soon as the zoom level is changed the current layer is extrapolated to the new zoom level which happens very quickly but can look fuzzy (zoom in) or compressed (zoom out)
2) A few hundred milliseconds later the new layer is presented.
I would agree it is an improvement, but wasn't sure it was faster as Garmin claimed.
Well, my unit seems to draw faster at the 30-50mi zoom levels which pretty much took forever previously. I would agree with closer zoom levels in that it just draws them differently with speeds that seem on par with previous versions. It is nice to have some sort of visual reference now instead of a blank screen until the data loads.
#25
Posted 22 January 2009 - 11:30 AM
g-o-cashers, on Jan 22 2009, 03:28 AM, said:
g-o-cashers,
Thanks for the suggestion. I grabbed Oregon_WebUpdater__285.gcd from your wiki and followed the instructions , but it was a no-go.
I was not able to find \gupdate.gcd in the Garmin folder. So I'm not exactly sure where to place Oregon_WebUpdater__285.gcd.
Would you kindly elaborate?
Barrikady
This post has been edited by Barrikady: 22 January 2009 - 11:30 AM
#26
Posted 22 January 2009 - 11:44 AM
JetSkier, on Jan 22 2009, 08:53 AM, said:
That's not a feature that I like! Is it supposed to be doing something different? I had this same POI loaded before the update and it was working fine.
JetSkier
Anyone?
JetSkier
#29
Posted 22 January 2009 - 12:12 PM
Barrikady, on Jan 22 2009, 12:30 PM, said:
g-o-cashers, on Jan 22 2009, 03:28 AM, said:
g-o-cashers,
Thanks for the suggestion. I grabbed Oregon_WebUpdater__285.gcd from your wiki and followed the instructions , but it was a no-go.
I was not able to find \gupdate.gcd in the Garmin folder. So I'm not exactly sure where to place Oregon_WebUpdater__285.gcd.
Would you kindly elaborate?
Barrikady
Here's how to do it for your Mac:
On Garmin's website, you find the software download page for your unit. Make sure you have the proper version for your unit. This can be found by going to Mapping Handhelds, then selecting your unit, then selecting Software from that unit's page:
This link is for the 300:
https://buy.garmin.com/shop/store/downloads...5&pID=14903
This link is for the 400t:
https://buy.garmin.com/shop/store/downloads...5&pID=14904
Go to the above approrpiate link. Download the software but don't open it, save it to your desktop. It will be an .exe file for Windows, but if you have Stuffit, you can unstuff the .exe file. Once you've unstuffed, and have your Oregon connected to your computer as you normally would, take the "gupdate.GCD" file which is within the unstuffed file folder, and copy it over into the Garmin folder on the Oregon's hard drive.
Disconnect the Oregon from the computer as normal ("eject").
Then, restart the Oregon. You'll get some black screens with the blue dot progress bar as the Oregon processes the update. Once it's done (this takes a minute) the unit will start as normal and if you check your info screen, you'll see it says the software is Beta Software 2.85.
Easily done! Mac friendly! Life is good!
#30
Posted 22 January 2009 - 12:24 PM
@JetSkier: I just tried a simple custom POI test. I created a directory/file structure on my computer like this:
\Custom POIs\Near Home\Home Waypoints.gpx
\Custom POIs\Core Waypoints.gpx
Both gpx file contain a small number of waypoints.
In the POI loader (I'm using 2.5.3 on a PC) I selected the following:
Next
Garmin Device>Next
It finds my Oregon, select Next
Install new custom POIs>Next
Browse to the \Custom POIs directory above
Next>Next
On my Oregon under WhereTo?>Custom POIs I see:
Core Waypoints
Near Home
Selecting Core Waypoints displays a distance ordered list of POIs that were in Core Waypoints.gpx file
Selecting Near Home displays:
All Categories
Home Waypoints
Selecting either of these displays a distance ordered list of waypoints in Home Waypoints.gpx.
I can't see anything that is broken as you describe but it seems you can have 2 levels of hierarchy, the first is based on subdirectory beneath the root directory and the second is "category" based on the file under each subdirectory. I think this is consistent with other Garmin devices including the Colorado but others who are more familiar can chime in.
Are you running the latest POILoader on a PC?
#31
Posted 22 January 2009 - 12:30 PM
I tried BlueDamsel's suggestion and I was successful in installing 2.85 on my Oregon. There was a small glitch. I was not able to get Stuffit to open the .exe file, but ZipIt did the trick.
Thanks g-o-casher, now I see that I should have renamed Oregon_WebUpdater__285.gcd.
"Easily done! Mac friendly! Life is good!"
#32
Posted 22 January 2009 - 12:38 PM
Barrikady, on Jan 22 2009, 01:30 PM, said:
I tried BlueDamsel's suggestion and I was successful in installing 2.85 on my Oregon. There was a small glitch. I was not able to get Stuffit to open the .exe file, but ZipIt did the trick.
Thanks g-o-casher, now I see that I should have renamed Oregon_WebUpdater__285.gcd.
"Easily done! Mac friendly! Life is good!"
Groovy!
I have noticed the profile switch problem is cured... I hope the rest of the beta software works properly. Time will tell!
#33
Posted 22 January 2009 - 12:42 PM
c:\pq\address book\address book.gpx
This gpx only has 5 entries in it. In the POI Loader, I selected the following:
Next
Garmin Device>Next
It finds my Oregon, select Next
Install new custom POIs>Next
Browse to the c:\pq\address book
Next>Next
On my Oregon under WhereTo?>Custom POIs I see:
Address Book
When I select it, it acts as if it's a POI by itself and shows me on the map in the middle of the ocean 6000 miles east of Orlando, FL.
Then, as I originally said, if I go back and use the "abc" button, I can find each of my 5 entries by typing them in.
I'll have to do some more testing with different levels of folders to see if it acts differently.
Thanks for your reply!
JetSkier
#34
Posted 22 January 2009 - 01:17 PM
JetSkier, on Jan 22 2009, 12:42 PM, said:
c:\pq\address book\address book.gpx
This gpx only has 5 entries in it. In the POI Loader, I selected the following:
Next
Garmin Device>Next
It finds my Oregon, select Next
Install new custom POIs>Next
Browse to the c:\pq\address book
Next>Next
On my Oregon under WhereTo?>Custom POIs I see:
Address Book
When I select it, it acts as if it's a POI by itself and shows me on the map in the middle of the ocean 6000 miles east of Orlando, FL.
Then, as I originally said, if I go back and use the "abc" button, I can find each of my 5 entries by typing them in.
I'll have to do some more testing with different levels of folders to see if it acts differently.
Thanks for your reply!
JetSkier
This is a long shot but is there any chance the 'address book' is some sort of special name to Garmin. Have you tried using a more obscure name??
#35
Posted 22 January 2009 - 01:26 PM
JetSkier
#37
Posted 22 January 2009 - 01:52 PM
Affirmative on the transparent maps. They display as they always have.
#40
Posted 22 January 2009 - 07:12 PM
FYI, I have GSAK 7.5 and have been using the gps download that came with it.
No complaints so far.
This post has been edited by cds231: 22 January 2009 - 07:12 PM
#41
Posted 22 January 2009 - 10:15 PM
g-o-cashers, on Jan 22 2009, 12:24 PM, said:
\Custom POIs\Core Waypoints.gpx
Both gpx file contain a small number of waypoints.
In the POI loader (I'm using 2.5.3 on a PC) I selected the following:
Next
Garmin Device>Next
It finds my Oregon, select Next
Install new custom POIs>Next
Browse to the \Custom PO's exactly what i wantetIs directory above
Next>Next
On my Oregon under WhereTo?>Custom POIs I see:
Core Waypoints
Near Home
Selecting Core Waypoints displays a distance ordered list of POIs that were in Core Waypoints.gpx file
Selecting Near Home displays:
All Categories
Home Waypoints
Selecting either of these displays a distance ordered list of waypoints in Home Waypoints.gpx.
I can't see anything that is broken as you describe but it seems you can have 2 levels of hierarchy, the first is based on subdirectory beneath the root directory and the second is "category" based on the file under each subdirectory. I think this is consistent with other Garmin devices including the Colorado but others who are more familiar can chime in.
Thank's g-o-cashers for testing - that's exactly what i wanted to know.
Lets hope Garmin will also implement this feature also for the Garmin-POIs in 2010.
#42
Posted 23 January 2009 - 01:36 AM
Red90, on Jan 22 2009, 02:53 PM, said:
Affirmative. MapWell allows me to turn scanned 24K USGS quad maps into raster maps for my Oregon and I can still see the transparent road layer I've made for Montana ON TOP OF these raster maps. My guess is that Garmin may have given the GB maps a higher draw priority than the road layer folks have been complaining about. I may be comparing apples to oranges here since MapWell rasters and my transparent maps aren't Garmin products as GB Discoverer is, hence may not have their draw priority affected by specific language in the firmware. BUT if you're wondering about NW Trails ( i.e. North America), you're probably not concerned of it's interactions with GB Discoverer.
This post has been edited by yogazoo: 23 January 2009 - 01:41 AM
#43
Posted 23 January 2009 - 10:46 AM
yogazoo, on Jan 23 2009, 02:36 AM, said:
Red90, on Jan 22 2009, 02:53 PM, said:
Affirmative. MapWell allows me to turn scanned 24K USGS quad maps into raster maps for my Oregon and I can still see the transparent road layer I've made for Montana ON TOP OF these raster maps. My guess is that Garmin may have given the GB maps a higher draw priority than the road layer folks have been complaining about. I may be comparing apples to oranges here since MapWell rasters and my transparent maps aren't Garmin products as GB Discoverer is, hence may not have their draw priority affected by specific language in the firmware. BUT if you're wondering about NW Trails ( i.e. North America), you're probably not concerned of it's interactions with GB Discoverer.
Yep, it's apples and oranges. Mapwel vectorizes (is that even a word?) a raster image so that the format is equivalent to typical Garmin vector maps. Even older non-raster-capable units can display them (albeit slowly). It will probably require someone with one of these GB Discoverer maps (with what appears to be true rasters) to test a transparent vector map overlay to see if it works.
#44
Posted 23 January 2009 - 10:49 AM
#45
Posted 23 January 2009 - 02:35 PM
What am I saying? I'm saying I believe that there is no true raster image being displayed on-screen on Garmin handhelds, even the newer ones. IMO They're all converted in a similar way as is done by the third party software. Now I could be wrong, but MOAGU, MapWel, and images in GB Discoverer and the 400i/c series all behave and appear in a similar fashion. I could be and will probably be proven wrong but for now, and what I can tell with the naked eye without being a Garmin engineer, all supposed rasters are vectorized both to save space, maximize draw time and to save processor resources-i.e. power.
As those in the GIS world can attest to, going from a Vector to Raster format is often a disaster and undesireable. However, going from a raster to vector not only produces very good results, it can save alot of space and processor time.
This post has been edited by yogazoo: 23 January 2009 - 02:40 PM
#46
Posted 23 January 2009 - 02:39 PM
yogazoo, on Jan 23 2009, 05:35 PM, said:
What am I saying? I'm saying I believe that there is no true raster image being displayed on Garmin handhelds. IMO They're all converted in a similar way as is done by the third party software. Now I could be wrong, but MOAGU, MapWel, and images in GB Discoverer and the 400i/c series all behave and appear in a similar fashion. I could be and will probably be proven wrong but for now, and what I can tell with the naked eye without being a Garmin engineer, all supposed rasters are vectorized both to save space, maximize draw time and to save processor resources-i.e. power.
Rather that than have a need for ridiculous amounts of SDHC space and need for a dual processor, with all the required power consumption.
#47
Posted 23 January 2009 - 03:39 PM
Quote
I also have played with the 400i maps and Moagu, the performance of the 400i aerial images is much faster than the vectorized Moagu maps. Still not proof that Garmin isn't doing something similar I guess, but somehow it doesn't feel that way to me.
#48
Posted 23 January 2009 - 10:27 PM
g-o-cashers, on Jan 23 2009, 04:39 PM, said:
Quote
I also have played with the 400i maps and Moagu, the performance of the 400i aerial images is much faster than the vectorized Moagu maps. Still not proof that Garmin isn't doing something similar I guess, but somehow it doesn't feel that way to me.
Someone who has the GB Discoverer maps could test it by installing on an older unit and see if it displays. Not a conclusive test by any means (because a failure to load doesn't really confirm that it's a true raster), but it would be interesting to see.
#49
Posted 24 January 2009 - 06:59 AM
#50
Posted 24 January 2009 - 07:36 AM
I've been using my unit alot with the software updated to 2.85 and from what I'm seeing, you should feel pretty confident about upgrading. They (Garmin) is just covering their arse with the "use at your own risk" language.

Help








