The title says it all. If you are looking for a screen protector or know someone who would like one for Christmas stop by Zagg and pick up some invisibleSHIELD coverage for 50% off — today only. Zagg has screen protectors designed specifically for the Colorado, Oregon, Dakota, GPSMAP 62 and 60csx.

Related posts:

1. 50% Off All InvisibleShield Products
2. Zagg invisibleSHIELD for Garmin GPSMAP 62
3. 40% off invisibleSHIELD products

Groundspeak’s guidelines for chirp approval are as follows:

1. A new attribute for a “beacon” will be added soon. Any caches that use a Chirp (or any future similar device) should use this attribute.
2. If a cache owner puts a beacon in a traditional cache and geocachers have an alternative method to find it without using the beacon, then OK. I remind you to use the coming attribute.
3. If the cache owner insists on not providing an alternative means of finding the geocache, it must be listed as a mystery with the beacon attribute.
4. Cache descriptions may mention the “Chirp” as long as the text doesn’t go on and on with “overtones of advertising, marketing, or promotion” as per our long-standing commercial guidelines.
5. We do not plan to add a new cache type just for this.

This is a very fair (and quick) decision especially considering, as Groundspeak is claiming, they only found out about chirp two days before the public release.

The next question is whether non-Garmin ANT+ devices will be able communicate with a chirp.  According to this post by DC Rainmaker, the answer is yes.  Chirp reportedly is based on a new (pending?) ANT+ Geocache Node Device Profile.  ANT+ profiles specify the protocols which ANT devices use to communicate so it is possible that an iPhone with an ANT+ transmitter combined with the right application could talk with a chirp.  While time will tell if this standard is actually approved and whether an application will be developed I’m guessing this went a long way when Groundspeak was considering approval for the device.

As I anticipated in my original post I’ve also heard some interesting ideas about how these devices might be used:

• Orienteering or adventure racing check point
• Travel bug “tag” transmitter
• Personal “hello” beacon
• Lost key chain or another valuable finder
• Endurance sport timing and competitor validation
• Other geocaching uses
• @gpstracklog suggests putting them in geocaches as “I’m not a bomb beacons” (my favorite!)

Some of these suggestions may not work since there seems to be an issue when two or more chirps are within proximity of the same GPS.  The first chirp discovered is the one visible.  If you have a chirp on the key chain you are carrying you may not be able to see other chirps that you pass by, say, as you are looking for a chirp-enabled geocache.

REI had a bunch in store when I was there this weekend although I’ve heard that some stores are already out of stock. You can get them online at REI for $19.95.

There’s still one nagging issue that remains out of all of this.  When Garmin released its new chirp software many people noticed that the geocaching icon changed from the official Groundspeak icon to the more generic “geocache treasure box”.  While this is a minor change the press releases for chirp were also noticeably void of any references to geocaching.com and Groundspeak as well.  And why would Garmin have not told Groundspeak about chirp until two days before its release?  Honestly, I’m not one for conspiracy theories but I sense there is something else going on here that may play out over the coming weeks and months.

Related posts:

1. Garmin releases chirp – A wireless geocaching beacon
2. Garmin Chirp Announcement
3. Garmin chirp Review

Updated 11/4/10: I’ve added a chirp FAQ page on the Garmin Oregon wiki if you are looking for more detailed help with your chrip.

After getting my hands on a Garmin chirp this morning I’ve been able to play with the tiny transmitter to see exactly how it works. The chirp is a simple wireless beacon that transmits a small amount of pre-programmed information to a compatible Garmin GPS within proximity of the chirp.  Aimed primarily at geocachers, the $20 device should be an exciting addition to both new and existing geocaches and well as some creative non-geocaching uses (I’ve bought an extra one to put on my key chain).

Programming chirp

When you receive the Garmin chirp it is erased so the first GPS which connects to the chirp can program it.  Programming the chirp consists of enabling chirp on the GPS (Setup>Geocaches>chirp Searching) and sending the chirp a name, a “message” and set of coordinates.  The programming controls are found under Setup>Geocaches>Program chirp. This can be done by setting each field manually or by using a waypoint or geocache to transfer the information all at once.   The chirp will take on the name and coordinates of the waypoint or geocache selected.  The chirp message field is programmed with the waypoint note or geocache hint. The chirp name is limited to 9 characters and the message to 50 characters so the amount of information stored in the device is fairly limited.  It takes about 30 seconds to program the chirp once you start transmitting to the device.

Geocaches > Setup	Programming Options
Manual Programming	Transmitting Data to chirp

Garmin has done an excellent job with security.  Once the chirp is programmed it becomes locked to the GPS which programmed it.  After that no other GPS can reprogram the chirp unless you have the last 5 digits of the unit ID of the GPS which “owns” the chirp.  I was able to swap control between my units without any issues but in general it seems secure enough to discourage people from stealing them or tampering with them in the field.

The GPS which “owns” the beacon can also erase the chirp. This puts the device back into its original unprogrammed state so it can be programmed by another GPS.

chirp After Programming

Programming an unowned chirp

Placing the chirp

Based on my testing you really want to have an unobstructed view around the chirp to get best results, placing it up high also seems to improve range.  When I placed the chirp on one side of a tree trunk I would consistently connect within about 20′-30′ if I was facing the chirp. However, with the tree between me and the chirp I had to be within 5′ to receive the alert.   If the chirp is in a metal container like an ammo can it won’t register until you open the container.

Finding the chirp

Once the chirp is programmed it is constantly transmitting its information to any GPS within range.  Users searching for the chirp must enable chirp searching on their GPS and when they get within range for about 10 seconds the chirp data is automatically downloaded to the GPS.  The Oregon/Dakota geocaching dashboard has a chirp status which tells you if chirp searching is enabled and whether you are in range or not. This feature is not available on the GPSMAP 62/78 geocaching dashboard.

Navigating to chirp

Oregon Geocaching Dashboard

When you view the chirp you see the name, message and coordinates as well as how many visits and when the last visit was made.  You can then “Go” to the chirp (similar to a waypoint) and this will be begin navigation to the programmed coordinates.  The chirp coordinates are saved as a special waypoint but the message is not preserved in this waypoint and you can easily overwrite the chirp waypoint when you encounter the next chirp.  Garmin should provide a way to save all of this data permanently once you move out of range and turn the unit off.

Battery Life and Other Details

Garmin claims the replaceable CR2032 lithium coin cell will last a year and work in cold weather.  One really nice feature is the warning you will get on the GPS if the battery is getting low. The unit is small (1.3″ x 0.9″ x 0.3″ / 3.3 x 2.3 x 0.7 cm), lightweight (< 1.o oz / 28 grams) and feels solid.  It comes with an IPX7 waterproof rating which means if you drop it in water or it gets rained on it will still work, Garmin does not recommend submerging the chirp.

Software and Compatibility

The only chirp-compatible units are the Garmin GPSMAP62/78, Oregon (300, 400 and x50) and the Dakota 20.  The Colorado does not seem to be supported even though it features the wireless ANT protocol which chirp is based on.

You’ll need to update your GPS software to use the chirp.  Updates were made available this morning and can be installed using Webupdater.

• GPSMAP 62/78 (2.70)
• Oregon x50 (4.00)
• Dakota (3.50)
• Oregon x00 (4.10)

If you are having problems connecting to your chirp with this software go to Setup>Fitness and disable the heart rate monitor and cadence sensor if you have them enabled. My Dakota would not connect to chirp because it was configured to search for an HRM. I’ve submitted this to Garmin as bug.

Pricing and Availability

The chirp is available online at REI for $19.95.

Summary

While I wish the chirp was capable of holding a little more data and cost about half as much but I like the way Garmin is thinking.  This is one of the most creative new products we’ve seen from Garmin in a while and its been done with typical Garmin focus on simplicity and ease of use.  Time will tell if the battery life, range and field durability is good but I like what I see so far and can’t wait to get my first cache out using chirp — hopefully tomorrow!

Related posts:

1. Garmin releases chirp – A wireless geocaching beacon
2. Garmin Chirp Announcement
3. Garmin chirp Approved by Groundspeak – Based on ANT+ Standard

That was quick.  After last night’s flurry around the Garmin chirp, Garmin has posted an announcement for the new wireless geocaching beacon on their blog this morning.  A few items to note:

• Price of the chirp is noted as $22.99
• Size: 1.3″ x 0.9″ x 0.3″ (3.3 x 2.3 x 0.7 cm)
• Weight: <1.0 oz
• Range: 32 feet (10 meters)
• Waterproof: IPX7 – 1 meter for 30 minutes
• No mention of Colorado support
• Security features which only let the owner program the device – this is very important so that these $20 items aren’t useful if stolen and can’t be tampered with in the field
• Battery life of 1 year with continuous use and it the battery is a replaceable CR2032 lithium coin cell
• Warning will appear on GPS if battery is getting low (nice!)
• Transmits coordinates, hints, count of visitors and date of last visit

Garmin has posted these placement tips:

• Do not mount the chirp inside a metal container.
• Do not bury the chirp.
• Do not put the chirp in water.
• A compatible Garmin device should detect the chirp within 10 m. For maximum transmission range, allow the chirp to have an unobstructed view in all directions.

Neat stuff, I’m hoping to get one today and get a cache out based on chirp soon.  Watch here for my first reports later in the day assuming Garmin releases the software to support the chirp.

Garmin’s full release:

Starting today, geocachers have a new trick up their sleeves – and in their caches – as we’re introducing chirp, a unique wireless beacon designed specifically for the outdoor adventures of geocaching. Affordable, durable and waterproof, chirp can communicate with, and be programmed by, any compatible wireless-enabled Garmin handheld for a more interactive and enjoyable geocaching experience. Cache creators and seekers alike will enjoy the benefits as chirp stores hints, transmits multicache coordinates, counts visitors and confirms the cache is nearby.“With chirp, geocachers have a new tool to enhance the joys of creating and finding caches around the globe,” said Dan Bartel, Garmin’s vice president of worldwide sales. “In listening to and participating in the vibrant geocaching community, Garmin created a one-of-a-kind device that builds on popular innovations such as paperless geocaching and downloading cache details directly to the device.”

Geocaching is a high-tech version of hide-and-seek where participants of all ages explore the outdoors in search of hidden treasure and adventure, and chirp’s wireless interactivity introduces a world of possibilities for creative caches. Experienced cachers will embrace the countless options now available in creating cutting-edge caches, and beginners will appreciate chirp’s features that make those caches easier to find. Simple to use and password-protected, chirp can be programmed by any compatible wireless-enabled Garmin handheld to store geocaching hints and other information. When other geocachers arrive near your cache, they’ll be alerted that the cache is nearby, and then they’ll be able to access the hints you’ve loaded into chirp. And when you return, chirp will tell you how many visitors have been to your cache.With chirp, setting up and maintaining a multicache has never been easier. Using your compatible Garmin handheld device (such as Oregon, Dakota and the recently announced GPSMAP handhelds), chirp automatically transmits program coordinates so other cachers can find each stage of your multicache. Or if you’re on a multicache, chirp lets you download coordinates. So there’s no need to manually enter numerous sets of complex coordinates – there’s just one simple touch and you’re on your way to the next stage.

Designed and tested by geocachers, chirp is built to take the rigors of the outdoors. And because chirp is password protected, the owner is the only one with programming powers. With a battery life of up to a year and a battery that’s easy to replace, chirp is long-lasting and user-friendly. Measuring 1.3” by 0.9” (slightly bigger than a quarter) and weighing less than an ounce, chirp is small enough to incorporate easily into your favorite caches – whether they’re already placed or still being planned.

The helpful hints provided by chirp are brought to life through paperless geocaching, which allows geocachers to help the environment and be more efficient by having cache information downloaded and displayed directly on the device. Compatible Garmin models store and display details such as location, terrain, difficulty, hints and description, so that you don’t have to carry around printouts. Learn about geocaching, getting started and going paperless at www.garmin.com/geocaching.

Available now for a suggested retail price of $22.99, chirp represents the latest breakthrough from Garmin, which has spent more than 20 years developing technologies and innovations to enhance users’ lives, making Garmin a household name in the automotive, aviation, marine, wireless, outdoor and fitness industries. For more about features and product compatibility, as well as information about Garmin’s other products and services, go to www.garmin.com, www.garmin.blogs.com and http://twitter.com/garmin.

Related posts:

1. Garmin releases chirp – A wireless geocaching beacon
2. Garmin chirp Approved by Groundspeak – Based on ANT+ Standard
3. Garmin chirp Review

To get an idea of how chirp might be used, imagine you are creating a new a multi-stage geocache.  Normally you would place a card or piece paper in the first stage that would provide coordinates to the next stage.  A finder would enter these coordinates manually on their GPS and navigate to that stage. Garmin’s chirp allows you to replace that piece of paper with a wireless beacon that automatically transmits this information to your GPS once you are within proximity of the device. It also seems like there is an ability to transmit some amount of data (i.e. a hint, distance, bearing, geocache ID, etc) along with the coordinates.

The article mentions that chirp is compatible with Garmin’s GPSMAP 62/78, Oregon and Dakota handheld GPS units. The Colorado, even though it supports the wireless ANT protocol which chirp is based on, is not mentioned.  I’m guessing new software updates from Garmin will be required to use the device.

Chirp is waterproof  and the site indicates it has a range of 10 meters.  Battery life is mentioned to be 1 year.

Price for the chirp is $20 US according to users who have already seen it at REI stores today.

I really should be getting one of these for my key chain!  It’ll be interesting to see what other creative uses people can come up with for this device.

Hopefully we’ll see an announcement from Garmin in the next few days.

Related posts:

1. Garmin Chirp Announcement
2. Garmin chirp Review
3. Garmin chirp Approved by Groundspeak – Based on ANT+ Standard

For those not familiar with the issue, most owners consistently report that the Trip Odometer records less than the actual distance traveled. This has plagued the Cartesio-based units in varying degrees since the Oregon x00 was released. Based on many tests I’ve found that the tracklogs, especially on the GPSMAP 62 and Oregon x50, provide reasonably accurate distance when compared to other GPSs like the 60csx and to test tracks which I’ve measured hundreds of times. However the trip odometer distance field always records short, sometimes by as much as 50% on slow (< 2mph) twisty hikes under dense tree cover.

I’ve upgraded all of my units to this release and haven’t seen any major new issues.  This weekend I’m hoping to get out and see if there is an improvement.  Let us know on the wiki forums (GPSMAP 62/78 | Oregon x50 | Oregon x00 | Dakota) if the fix is working for you!

GPSMAP 62/78

Changes made from version 2.50 to 2.60:

* Fixed issue while using spell search in route planner.
* Fixed issue where tracks could not be disabled from the map.
* Fixed issues with odometer distance.
* Fixed shutdown while panning the map for extended periods of time.

Oregon x50

Changes made from version 3.80 to 3.90:

* Fixed issue while using spell search in route planner.
* Fixed issue on 3D View where vehicle could move after using the map.
* Fixed issue where tracks could not be disabled from the map.
* Fixed issues with odometer distance.
* Fixed shutdown while panning the map for extended periods of time.

Oregon x00

Changes made from version 3.90 to 4.00:

* Fixed issue on 3D View where vehicle could move after using the map.
* Fixed issue on map page where back button would jump to the main menu.
* Fixed issues with odometer distance.
* Fixed shutdown while panning the map for extended periods of time.

Dakota

Changes made from version 3.30 to 3.40:

* Fixed issue while using spell search in route planner.
* Fixed issue where tracks could not be disabled from the map.
* Fixed issues with odometer distance.
* Fixed shutdown while panning the map for extended periods of time.
* Fixed occasional shutdown when turning off a marine alarm.

Related posts:

1. Garmin Oregon 450/550 and Dakota Beta Fixes Bugs
2. Garmin releases chirp – A wireless geocaching beacon
3. Garmin Oregon x00 Beta 3.15 Available

Updated: GPSMAP62/78 2.44 Beta also includes multi-caching support and possible altimeter improvements.

If you use an Oregon or Dakota you are probably tired of your friends who own 60CSx’s snickering at you every time you have to enter coordinates for a multi-cache or mystery cache in the field.  On the newer units once you enter coordinates for a subsequent stage you are forced leave behind all of the paperless caching features, switch back-and-forth between waypoints and geocaches to see the cache details, and the geocaching dashboard is no longer helpful since it only navigates to geocaches.

With the introduction of today’s betas on the Dakota, Oregon x50 and x00 Garmin has introduced multi-cache support (which works for all cache types not just multis).  Once this beta is installed and you are navigating to a geocache you will notice a new button under Geocaches called “Enter Next Stage”.   Pressing this button will land you on a coordinate entry screen where you can type in the coordinates for a subsequent stage.   This creates a temporary geocache called “Next Stage” which is linked to the original “parent” cache.  Selecting it will display all of the parent cache level attributes like description and hint but it will show up on the map with the same icon as the parent cache at the new location. The geocaching dashboards will also identify “Next Stage” as a geocache .  You can continue to mark Next Stages as you move through the stages of the cache and when you finally log your attempt the Next Stage will go away. Next Stage gets saved across power cycles so if you decide to bail out half way through a long multi you can pick up where you left of the next day.

Enter Next Stage from Geocaches Menu	Next Stage visible on the Map Page
Next stage visible on the Geocache List	Next Stage on the Geocaching Dashboard

There are some limitations.  You can only use this feature on one cache at a time since there is only one special Next Stage geocache.  Setting a Next Stage on one cache will wipe out a Next Stage you had set for a previous cache.  Similarly, within the same multi-cache you will lose coordinates for the second stage when you navigate to the third stage.  Garmin does not automatically save each stage a waypoint which would have been a very nice way to prevent this type of data loss.  You can deal with this issue manually.  Once you have entered a Next Stage and are navigating to it, go back to the Main Menu, select Geocaches>Show Description and press the “Flag” button to save a waypoint.  This will save a copy of Next Stage so if you need to get these coordinates later you can (and you’ll have a nice record of the entire multi-cache).  Hopefully Garmin will consider automatically adding waypoints in the future or at least prompt when the Next Stage is set to save a waypoint or not.

There are several other changes worth mentioning.  All three units received fixes to improve Trip Odometer accuracy.  We’ll have to spend some time testing to see if any real improvement was made.  The Dakota picked up Track Archiving, the ability to move waypoints on the map page, gpx import progress monitor, track/route detail improvements, and the auto shaded relief changes which were introduced in earlier Oregon x50 betas.   Oregon x00 users only pick up the auto shaded relief and trip odometer improvements — it seems like Garmin is starting to limit the changes it is port back into the older Oregons.

Full details on the three releases are below.  Please note the special instructions required to upgrade the Oregon x50 from 3.71 and 3.74 on the Garmin site.  I had no problems performing the upgrade but it is more complex and error prone than the usual beta upgrade, some people are reporting bricked units.  Follow the instructions to the letter if you decide to take the plunge.

Changes made from version 3.71 to 3.74 (Oregon x50):

• Added multicaching support.
• Added display color to track gpx files.
• Added ability to set user declination direction.
• Improved accuracy of trip odometer.
• Fixed occasional shutdowns.
• Fixed issue with stuck route button.
• Fixed issue with Oblique Mercator User grid.
• Wiki thread

Changes made from version 3.12 to 3.14 (Dakota):

• Added multicaching support.
• Added ability to move waypoints using the map.
• Added display color to track gpx files.
• Added periodic track archiving.
• Added Automatic Shaded Relief option.
• Added ability to set user declination direction.
• Added import indicator for gpx files.
• Added track review page improvements.
• Improved accuracy of trip odometer.
• Fixed occasional shutdowns.
• Fixed issue with Oblique Mercator User grid.
• Wiki thread

Changes made from version 3.81 to 3.85 (Oregon x00):

• Added multicaching support.
• Added Automatic Shaded Relief option.
• Added ability to set user declination direction.
• Improved accuracy of trip odometer.
• Fixed occasional shutdowns.
• Fixed issue with Oblique Mercator User grid.
• Wiki thread

Changes made from version 2.40 to 2.44 (GPSMAP 62/78)

• Added multicaching support.
• Added display color to track gpx files.
• Added periodic track archiving
• Added Automatic Shaded Relief option.
• Added import indicator for gpx files.
• Added track review page improvements.
• Improved accuracy of trip odometer.
• Fixed occasional shutdowns.
• Fixed calendar to display all geocache finds and attempts on the correct day.
• Fixed paging after logging a geocache.
• Fixed issues with inconsistent altimeter readings.

Related posts:

1. Garmin Oregon/Dakota Beta Adds Geocache Filtering
2. Garmin Dakota Beta Picks up Latest Oregon Changes
3. Garmin releases chirp – A wireless geocaching beacon

Geocache Filter Setup

In response GPS devices like the Lowrance Endura and Magellan eXplorist GC which support geocache filtering, Garmin released beta software yesterday which adds this feature to the Dakota and Oregon.  Geocache filters allow you to view the geocaches loaded on your GPS which match the criteria of a filter that you create, especially useful with the newer units like the Oregon x50 and GPSMAP 78 which support up to 5,000 geocaches.  For example, if you want to view only traditional caches which are micros that have a difficulty between 3 and 5 you can now create a filter on your GPS to do this.

Filters can be based on any combination of the following geocache parameters:

• Type:  Any combination of Traditional, Multi, Puzzle, Letterbox, Event, Mega-Event, CITO Event, EarthCache, Wherigo, Virtual, WebCam.
• Size: Any combination of Micro, Small, Regular, Large, Other, Not Chosen.
• Difficulty: Range between 1 and 5
• Terrain: Range between 1 and 5
• Status: Any combination of Found, Unattempted, Did Not Find.

There are two types of filters.  The “Quick Filter” is available under Main Menu>Geocaches>Quick Filter.  Simply specify the parameters above, select “Search” and you will see a list of caches matching the filter.  Quick Filters are erased if the GPS is rebooted.

Geocaches Menu Showing Quick Filter and Saved Filters

Filter by Geocache Type

Saved Filters can be created under Main Menu>Setup>Geocaches>Filter Setup in exactly the same way. However, these filters can be named, saved and will show up under Main Menu>Geocaches>[Saved Filter].  Use a Saved Filter if you need to run a filter frequently and you want to have it available after your reboot your GPS.

Setup>Geocaches	Saved Filter List
Editing Saved Filters	Filter by Cache Size

The new betas also fix a few bugs, most notably the hang caused by selecting “All POIs” on the Oregon x50. I have encountered a few issues with the geocache filters.  The first time I created a saved filter and was switching between a quick filter and a saved filter I started to see partial results or no results.  When I inspected the quick filter the Difficulty, Terrain and Status fields were set incorrectly. Manually setting them seemed to clear the issue and I have not been able to reproduce the problem since.

Regardless of these minor glitches its nice to see that Garmin is listening to requests from the user community and not falling behind the competition.  A few enhancements like the ability to “Select All” or “Select None” would be helpful and now that GPX 1.0.1 is available wouldn’t it be nice to filter by attribute! I’d love to be able to create “Dog Friendly” or “Significant Hike” filters for example.

Full release notes and links are below.  As usual, to get quick notifications of these new releases follow GPSFix on twitter.

Oregon x00 3.82

• Added Geocache filtering. Select Setup > Geocaches to add custom filters.
• Fixed issue syncing with BaseCamp.

Oregon x50 3.52

• Added geocache filtering. Select Setup > Geocaches to add custom filters.
• Improved keyboard responsiveness.
• Fix hang searching for POI.

Dakota 3.12

• Added Geocache filtering. Select Setup > Geocaches to add custom filters.
• Improved keyboard responsiveness.

Related posts:

1. Garmin Adds Multicache Support in Latest Beta
2. Garmin Oregon Beta Adds Dashboards, Improves Track Nav
3. Garmin chirp Review

Related posts:

1. 50% Off invisibleShields Today Only
2. 50% Off All InvisibleShield Products
3. Garmin Oregon $50 Rebate Starts Today

• long WAAS acquisitions times (> 5 minutes) even with direct view to an optimal WAAS/EGNOS satellite
• inability to hold WAAS signal under any type of canopy
• in the event of signal loss the unit makes lengthy hunts through a sequence of WAAS/EGNOS satellites which aren’t optimal at the user’s location

Late last week Garmin announced a beta which included new GPS firmware for the Oregon x50, Oregon x00 and Dakota.   All three drops included an “Improved WAAS performance” release note, so we spent some time over the long weekend to test WAAS on an Oregon 550 and Dakota 20.  Here’s what we observed:

• Acquisition time with a clear view of the most optimal (ie. highest elevation) WAAS satellite is faster.  After the initial lock which still took 5-7 minutes both the Dakota and Oregon acquired WAAS within 30-60 seconds after power on.  The Dakota takes about 5-15 seconds longer than the Oregon in most tests.
• Under tree cover the performance is marginally better but not enough that I could observe any improvement in my location accuracy.
• The most frustrating thing is when WAAS signal to the most optimal satellite is lost the GPS proceeds to hunt through a long list of satellites which are at very low elevation (2-15 degrees).   The unit spends about one minute waiting to lock on each of these satellites (and never does) which means that it takes about 8-10 minutes to cycle back to the most optimal satellite effectively rendering WAAS/EGNOS useless for that 10 minute period of time unless you are willing to power cycle the unit.

In short, there are improvements in WAAS/EGNOS but practically speaking I don’t see that the improvements add any value unless you are operating in an environment without tree cover such as desert or alpine hiking, on the water or in the air.  I was not able to get WAAS long enough on my test track to see if the accuracy of the unit improves with WAAS, although I did notice my EPE drop to 9 feet and based on BirdsEye maps my position looked about the same as it did without WAAS (both were good).

The complete set of release notes for this beta software reveals some other significant bug fixes and improvements:

• Added brightness adjustments for BirdsEye imagery.
• Improved WAAS performance.
• Improved speed, trip odometer, and stopped/moving time data fields while in low velocity.
• Fixed issue with map POI’s showing twice for a single point.
• Fixed elevation profiles to always use the most detailed DEM data loaded.
• Fixed future plot with tracks that have no elevations in them.
• Fixed issue with calculator % function.

If you are looking for the BirdEye brightness adjustments you’ll find them under Setup>Map>Map Information Select Map>BirdsEye Satellite Imagery.  Previously you would see just “Enable” and “Disable”, whereas with this new release you will find, “Enable – Brighter”, “Enable – Bright”, “Enable – Normal” and “Disable”.    I’ve provided some screenshots to illustrate the differences.  My preference is for the “normal” mode but it might be worth setting this parameter to “brighter” in a “high visibility” profile if you are using the unit under bright overcast skies and are having problems seeing BirdsEye maps.

Brightness control	Brighter
Bright	Normal

We were also curious about the low speed data field improvements because I’ve found speed, stopped time and trip odometer to be unreliable since day one.  Based on my tests Garmin has made some improvements, especially with “stopped time”.  Previously I would see much more stopped time recorded by both the Dakota and Oregon – during my test loops over the weekend I only observed a few 10′s of seconds of stopped time as compared to several minutes in past tests.  Speeds reported below 3mph also appear more stable.  The trip odometer is a little better, particularly on the Oregon, measuring closer to the tracklog but still underestimating the distance of my track by ~2-4%.  The Dakota error was higher, on some tests it was closer to 10% underestimation.  I’ll attribute this to the Dakota’s somewhat inferior antenna design, I’ve always seen poorer sensitivity on the Dakota as compared to either of my Oregon’s and I’m guessing that that this leads to more variation in the speed and trip odometer data.

At least one user has reported a problem upgrading an Oregon x00 to this release which resulted in a bricked unit (System Software Missing) so please consider this before upgrading. I have not experienced any problems upgrading my three units, but there is always a risk associated with beta upgrades.  There is one new bug introduced which causes a hang when you attempt to navigate to all POIs (WhereTo?>All POIs).  You’ll need to pull the batteries to recover if you encounter this.   I’ve also experienced one shutoff on my Oregon 550t while editing a waypoint but it is not reproducible.

These beta releases can be downloaded here:

Oregon x50 (3.51/4.46)

Oregon x00 (3.81/4.46)

Dakota (3.11/4.46)

Join us on the wiki discussion threads (Oregon x00, Oregon x50, Dakota) to let us know your experiences if you decide to take the beta upgrade plunge!

Related posts:

1. Garmin Oregon/Dakota Beta Adds Geocache Filtering
2. WAAS problems on Oregon and Colorado
3. Garmin Oregon 450/550 and Dakota Beta Fixes Bugs