Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Oregon Doesn't Lock to WAAS/EGNOS

Former Member
Former Member over 15 years ago
Having been in the Oregon Wiki for sometime now I can see that this is a serious issue.

The Oregon basically cannot lock reliable to any SBAS (WAAS/EGNOS) signal therefore making the 1-3 meter accuracy (or even an 'improved' accuracy) this device claims to have, impossible. My 60CSx has no problem with SBAS and can lock within seconds and stay locked, even if it’s been off for some weeks.

The Oregon has a new chipset and I’ve become aware that this doesn’t store an Almanac as such? Some have indicated that this could be a potential cause along with the ceramic antenna design. If this is the case, then Garmin could have a legal case on their hands?

However, I’m hoping the Oregon’s design is not the issue and there is a firmware fix. But despite the many recent upgrades this problem still exists.
Please Garmin, fix this before my unit goes on eBay (or I look into ways of retrieving my money back) and I return to my 60CSx!

:mad:
  • Former Member
    0 Former Member over 15 years ago
    Which model are you talking about and what is the firmware version now installed?
  • Former Member
    0 Former Member over 15 years ago
    Which model are you talking about and what is the firmware version now installed?



    All models and firmware versions!
  • Former Member
    0 Former Member over 15 years ago
    My Dakota 20 is a total stinker in this regard as well. My original unit was a Summit HC, and on the basis of that experience, I had come to expect good WAAS lock in a more or less prompt manner.

    I live in Colorado, and often have a clear sky view of 49 and 51 to the south. I can leave my Dakota 20 to sit for 30 minutes looking for WAAS, often with the signal level bar pegged for either 49 or 51. However, the bars remain white -- NOT green -- as evidently the Dakota is unable to pull down the requisite almanac information in a timely manner no matter how good the signal, and then the unit moves on to search for another satellite.

    I purchased this unit with the understanding that it was to be WAAS/EGNOS capable. While it can see the WAAS satellites, it appears to be completely incapable of working with them. I understand that many Oregon users suffer from the same problem.

    My Summit HC runs circles around my Dakota 20 in this and certain other respects -- one of the "other respects" that it produces far more stable coordinate data far more quickly, likely because it is able to fix on and use WAAS quickly.

    I'll be contacting Garmin next week to discuss this with them. The device is advertised as WAAS-enabled (and yes, I DID remember to turn it on in the Setup menu), but the WAAS capability appears to be very limited with these units. For my purposes, the Dakota is less capable than my old Summit HC. I may return it as "defective" if there isn't some resolution to this problem.
  • Former Member
    0 Former Member over 15 years ago
    So is it of the opinion that the Oregon (for me the 550) is WAAS worthless?
  • Former Member
    0 Former Member over 15 years ago
    no.. its not anyones opinion, its a fact!
  • Former Member
    0 Former Member over 15 years ago
    I know nothing about the Oregon but I do remember the wass enable feature on the older units works backwards from what you think.try setting it to disable and see what happens.
    Jack
  • Former Member
    0 Former Member over 15 years ago
    GPSMAPMAN , I am speaking for a large number of people that all have the same problem, and yes, i did try it. Turning off the SBAS (WAAS/EGNOS) function is indeed a good idea, but only to save power from the constant and futile attempts at searching for SBAS birds.

    Switching SBAS (WAAS/EGNOS) off disables the search for any Sats past Sat (Garmin ID) 32. Basically meaning, SBAS is Switched OFF!