Announcement

Collapse
No announcement yet.

D2 Charlie Altimeter / Vertical Speed <-> Aviation Units BUG

Collapse
X
  • Time
  • Show
Clear All
new posts

  • D2 Charlie Altimeter / Vertical Speed <-> Aviation Units BUG

    Running firmware 4.00 (latest at the time of writing), the D2 Charlie still suffers from the following nuisance/bug:

    Even though Aviation Units are enabled (e.g. elevation in *feets*):
    - altimeter (widget) *calibration* is still shown in the "system" units (e.g. *meters*)
    - FLY (app) *vertical* speed is based on "system" elevation units (e.g. *meters/minute*)

    This makes:
    - the altimeter (widget) a *nuisance* to calibrate (e.g. based on current airport known reference altitude)
    - the FLY (app) *dangerous* (since meters/minute are close enough to feets/minute to be easily mistaken and the discrepancy not obvious)
    Device: D2 Charlie
    CIQ apps: Garmin ConnectIQ Store
    Environment: Linux/Debian (emacs, vim, make, etc.)

  • #2
    This issue has already been added to the bug list by dbrobert, see https://forums.garmin.com/forum/on-t...e-version-4-00

    I got a new D2C last week. I am having an issue with the accuracy of the altimeter. I noticed that the Altimeter is approximately 250 feet off when calibrated using the barometric pressure obtained from the nearest METAR. I was at the airport the other day and I can confirm this issue. I understand that I can calibrate it manually but I just wanted to see if anyone else has experienced this issue.

    Comment


    • #3
      Originally posted by ghost_rider_av8or View Post
      This issue has already been added to the bug list by dbrobert, see https://forums.garmin.com/forum/on-t...e-version-4-00
      Yes. And it has been here right from the beginning (at least v2.90 as far as I can tell). It'd be nice if acknowledged by Garmin itself!

      I got a new D2C last week. I am having an issue with the accuracy of the altimeter. I noticed that the Altimeter is approximately 250 feet off when calibrated using the barometric pressure obtained from the nearest METAR. I was at the airport the other day and I can confirm this issue. I understand that I can calibrate it manually but I just wanted to see if anyone else has experienced this issue.
      Same here. Enable the Barometer widget and look at its calibration settings: you can set both the altimeter and the corresponding barometric pressure (QNH ?), thus "calibrating the instrumental error". Since then, the Altimeter - once calibrated with the actual altitude - has given me barometric pressure that match the current QNH quite closely (I expect calibrating it the other way around, thanks to METAR, ought to work better too).

      Garmin again:
      That being said, it'd be nice if the Altimeter could also be calibrated manually (not though METARs) using a known barometric pressure (QNH).

      (rant)
      It is appears the devs of the D2 know nothing of aviation and let pass the most glaring problems/inconsistencies.
      Sad given with the price of the gadget...
      (/rant)
      Device: D2 Charlie
      CIQ apps: Garmin ConnectIQ Store
      Environment: Linux/Debian (emacs, vim, make, etc.)

      Comment


      • #4
        I have a D2 Charlie now and have been working through the reported bug list and compiling my own list, including the issues with Garmin Pilot and with the auto-import feature of the FlyGarmin logbook. I've already reported a few additional issues, but I will make sure I put the full list together after the next release (overdue now) and send it to the D2 team.

        Cheers,
        Douglas
        Current tech: D2 Bravo (w/ tempe), fēnix 5 (w/ HRM-Run), GPSMAP 296
        Own/owned/used: D2 Bravo, fēnix 5, GPSMAP 396/296/196, GPS12, FR15, FR10
        CIQ Environment: MacOS 10.12.x, Eclipse Neon.3
        My apps: Garmin Connect IQ Store (dbrobert)

        Comment


        • #5
          The altimeter does not seem to catch-up with the changing elevation quickly enough...see my recent flight: https://connect.garmin.com/modern/activity/2766486656
          The airport elevation is roughly 1000 feet. I had the autofly mode enabled (500 fpm) which started recording after some distance after I took off. I was at least 1500 feet by that time it started recording..but it is showing as 1053 feet. Same thing when I landed...it is showing the altimeter as roughly 2000 feet when I touched down... I noticed some similar conversation going on in the fenix 5X forums as well..hopefully, garmin will fix it when they fix the similar issue with the 5x.

          Comment


          • #6
            Originally posted by ghost_rider_av8or View Post
            The altimeter does not seem to catch-up with the changing elevation quickly enough...see my recent flight: https://connect.garmin.com/modern/activity/2766486656
            The airport elevation is roughly 1000 feet. I had the autofly mode enabled (500 fpm) which started recording after some distance after I took off. I was at least 1500 feet by that time it started recording..but it is showing as 1053 feet. Same thing when I landed...it is showing the altimeter as roughly 2000 feet when I touched down... I noticed some similar conversation going on in the fenix 5X forums as well..hopefully, garmin will fix it when they fix the similar issue with the 5x.
            I think I might have the explanation for this behavior:
            Go to the *Barometer Widget* settings and verify the "Watch Mode" is set to "Altimeter". If it is set to "Auto" (the default, if I recall correctly), the watch attempts to work both as an altimeter and a barometer (...): if pressure variations are small enough, they are considered barometric pressure change; if pressure variations are fast enough, then they are considered altitude-pressure change. Of course, as an aviator watch, we want to make sure it behaves as an altimeter only, and not some weird mix of pressure-related instruments :-/
            Device: D2 Charlie
            CIQ apps: Garmin ConnectIQ Store
            Environment: Linux/Debian (emacs, vim, make, etc.)

            Comment


            • #7
              Originally posted by CedricD. View Post

              I think I might have the explanation for this behavior:
              Go to the *Barometer Widget* settings and verify the "Watch Mode" is set to "Altimeter". If it is set to "Auto" (the default, if I recall correctly), the watch attempts to work both as an altimeter and a barometer (...): if pressure variations are small enough, they are considered barometric pressure change; if pressure variations are fast enough, then they are considered altitude-pressure change. Of course, as an aviator watch, we want to make sure it behaves as an altimeter only, and not some weird mix of pressure-related instruments :-/
              Thank you. I will give that a try. Did this work for you? One would assume that Garmin already incorporated this when FLY app is started.

              Comment

              Working...
              X