Compass is off by 10 degrees!!!!!

As the title says...

On my week old 5x  I have noticed even AFTER calibrating it is off by between 5 and 10 degrees.. I have tried calibrating when standing on a hill where there was nothing for several Km's  and still off.. I check it using a Silva Mil Compass and when comparing to My Suunto Ambit 3 Peak which matches my Silva compass it is always off...  Any ideas what to do next?

regards

Crags

  • First thing that comes to mind is  magnetic vs true north settings.  Unless your Silva has the declination adjustment function (and is set properly for your area) it is pointing Magnetic North.  The Fenix defaults (I think) to True North. but can be set for True, Magnetic, Grid or User.  Check the Magnetic Declination for your area and see if this fits the differences you are seeing.  Another note - although I have not checked lately, I "complained" to Garmin years ago that when you set to Magnetic North, the display will actually depend on whether you are using the widget compass or within an application (and, in some caused, would mix both Mag and N within the same widget wher the arrow and the text direction did not match).

  • Already checked all those things before posting and no difference.. and a Mag Dec would only be a degree or two at worst... not 10 degrees.

  • Already checked all those things before posting and no difference.. and a Mag Dec would only be a degree or two at worst... not 10 degrees. I the UK it is 1 degree west at the moment

  • It was just a thought!  My declination is about 12 degrees!

  • I appreciate  your input... But I certainly are not a novice, 30 years military, with SAR thrown in to now be an outdoor activities instructor and still SAR. Been using Outdoor activity watches for around 25 years and used all the ambit range too.... Also not my first Garmin watch either...

    SO I went through all the trouble shooting things before posting...

    Now what is curious is I was on the beta firmware(23.71) when I had the issue, reflashed to standard firmware (22.40) and the issue is gone... SO it would suggest its a firmware issue!! I have emailed the beta team about it...... Lets see whats happens.... Least I now know its not a hardware fault!!!!