Alt Setting issue D2C

I wasn't able to replicate this issue on my D2 Charlie. Can you post your configured settings for both the Altimeter sensor and for the Altimeter widget?

Also, if you go to the Atimeter widget settings, do you have the Auto Calibrate (labelled as "Auto Cal.") set to "On"?

Cheers,
Douglas

Hi,
I’m having an issue with alt set in my D2C. With baro set to auto adjust by METAR, the system always change the hPa to -2 hPa from METAR. Even after perform an alt calibration, it turns again in a -2 offset. When METAR is 1013hPa, the watch shows 1011hPa and the altitude match this gap.
Anyone else having same problems?
Any suggestion to correct?

I have noticed that on the D2C I used to own. The altimeter was off by several hundreds of feet as well. I exchanged that for another one which did not do that. Do you see the difference when using data from METAR only or when manually calibrating as well (i.e., manually entering baro)?

I wasn't able to replicate this issue on my D2 Charlie. Can you post your configured settings for both the Altimeter sensor and for the Altimeter widget?

Also, if you go to the Atimeter widget settings, do you have the Auto Calibrate (labelled as "Auto Cal.") set to "On"?

Cheers,
Douglas

@ settings > Sensors & Accessories > Altimeter > Barometer = METAR
@ Barometer widget = alt set is currently, as usual, - 2hpa from METAR.
Already tried to calibrate barometer manually, but it comes again to -2. This issue is consistent despite de location.

@ settings > Sensors & Accessories > Altimeter > Barometer = METAR
@ Barometer widget = alt set is currently, as usual, - 2hpa from METAR.
Already tried to calibrate barometer manually, but it comes again to -2. This issue is consistent despite de location.

Try contacting garmin support. I think that is a valid reason to send it back for another unit. I had to send mine back twice to get the unit that worked as advertised.

Try contacting garmin support. I think that is a valid reason to send it back for another unit. I had to send mine back twice to get the unit that worked as advertised.

Send it back will be a huge headache. I live in Brazil, so send it will be painful, expensive and nothing close to easy deal.
It seams to be a firmware bug, and maybe next version correct the issue. I'm not sure when started this behavior, but wasn't always like now.
If there bug continues to go on...I'll have to accept it as a fate.
I'll try a full restore too. Who knows.