Related
Options

D2 Delta - version 7.10

dbrobert

Garmin has released version 7.10 for the D2 Delta series. From Garmin's "Updates & Downloads" pages for the various D2 Delta devices (see below for individual links), the consolidated list of changes are below; where a feature only applies to a specific device it is so identified.

Changes made from version 7.00 to 7.10:

  • Improve METAR widget crosswind calculation
  • Fix potential device crashes and freezes.
  • Fix bugs related to Explore syncing.
  • Fix issue with adding power data fields

Changelog links:
Delta: "Updates & Downloads"
Delta S: "Updates & Downloads"
Delta PX: "Updates & Downloads"

  • 0

    I continue to maintain a list of bugs, requests, fixes and workarounds. I personally have a D2 Delta device but I am unable to contribute to the list for anything that specifically/only affects the Delta S or the Delta PX.


    I've bolded anything that would generally consider to be a serious issue that impedes use of the watch or included functionality (ie. reboots versus display or other issues). Reply below with comments and I'll keep the list updated.

    Outstanding issues / bugs:

    • [WATCH] Altimeter hardware does not seem to properly handle rapid elevation changes, either from lag or hanging (also affects Fenix 5X+)
    • [WATCH] Running Dynamics drops out around two minute mark when phone is connected; workaround: disable connection to phone while running (also affects Fenix 5X+)
    • [WATCH] There is no way to clear the tail number (aircraft registration) once entered into the watch config
    • [WATCH] sunrise/sunset calculations appear to be incorrect
    • [APPS] HSI data screen is missing from the FLY app
    • [GPS] cannot receive a GPS fix within the flight deck of an Airbus A-320 (and several other aircraft)
    • [WIDGETS] METAR widget uses watch setting for METAR visibility -- add configuration option for "visibility" to "Aviation Units" section
    • [WIDGETS] METAR widget displays blanks screen if station (nearest or manually entered) does not have a published METAR (eg. CYCZ)
    • [WIDGETS] METAR widget does not display the numeric value for the TAF visibility, and instead shows "P SM" or "SM" without the number
    • [WIDGETS] METAR widget does not calculate the runway headwind/crosswind components properly (runway magnetic heading is used with METAR wind, which is true heading)
    • [WIDGETS] Temperature widget does not display the proper density altitude when using metric units on the watch
    • [CONNEXT] Garmin Pilot does not receive the altitude from the watch


    Feature requests:

    • [WATCH] don't display the Nav Data status at the end of the "About" section, but instead display it after firmware version numbers
    • [WATCH] add configuration option for "visibility" to "Aviation Units" section, to allow selection of SM, meters or kilometers
    • [WATCH] add configuration option for "pressure" to "Aviation Units" section, to allow selection of inHG or mb
    • [WIDGETS] METAR widget only displays cloud coverage (sky) information when there is a measured ceiling but should display FEW and SCT when no ceiling is present
    • [WIDGETS] METAR widget "Use Nearest" function should retrieve an active GPS fix rather than using the last known position
    • [WIDGETS] METAR widget only displays the first six (6) periods of the TAF, which I believe is a holdover from the memory issues on the older D2 Bravo devices


    Fixed issues:

    • [WIDGETS] METAR widget does not handle one-way runways properly when displaying runway wind information [fixed in 6.10]
    • [WATCH] add support for Galileo GNSS
    • [WATCH] add support for Spotify (feature request, added in FW 4.50)
    • [WATCH] pop-up first-time help/hint bubbles are displayed after every reboot and/or sync [fixed in 5.40]
    • [WIDGETS] Altimeter widget ignores the widget configuration for display units of "feet" when general watch config is set to metric [fixed in 5.40]


    Old issues [could not be confirmed or appear to work as expected]:

    • none at this time
  • 0 in reply to dbrobert

    .... tentative observation - this seems to resolve the altitude issue introduced in 7.00.