10.3 known issues/bugs - list?

I think it's time we had a comprehensive list of issues/bugs from Avidyne with a status of each.  Avidyne has been incredible with their transparency over the years, and hopefully that will continue through this 10.3 debacle. 

Edited by pburger - 27 Oct 2022 at 2:09pm

Steve,

Bugs 10.3.0.2 (known)


1) *CRITICAL*  system reboot when highlighting or selecting non-RNP required AR/RF approach -  work-around enable RF legs in maintenance mode?

2) IFD loses the last selected frequencies upon power up
3) Altitude Setpoints over ARINC429 - If an altitude constraint is present, an altitude setpoint is sent out over the ARINC429 interface (the value sent is the altitude constraint +1), even if Enroute VNAV is turned off.  This is a new behavior with 10.3 and causes unexpected operation from at least some autopilots.
4) EFB loses connectivity to the IFD to push flight plans (Unable - IFD became unresponsive)
5) unable to connect an android device to the IFD (work around available)
6) (dual IFDs) If I try to enter a direct-to airport, my other IFD440 will pop up the keyboard as expected... I can then try to type the icao id of the airport which works fine... however, the "Activate KXYZ" simply comes and immediately goes away... My current workaround is to use the BT keyboard which allows the "Activate KXYZ" to persist until I select it
7) when using ADS-B in from a wireless device (eg Stratux), IFD will randomly reject connections and issue various datalink errors, may also extend to hardwired units
8) (dual IFDs) I cannot seem to edit the "cross"/"at"/"wxyz ft" section in the FMS via the latest IFD100 on my iPad... I have no problems editing it on either IFD-440 though.
9) (dual IFDs)  I have seen cases where on one of my IFD-440's, I can "direct-to KXYZ" but that my other IFD-440's FMS will still show the previous "direct-to" that was entered.
10) TOD descent rate reset to a descent ANGLE of 4 degrees instead of fpm as was originally (AUX -> Setup -> FMS, expand FMS, expand VNAV and set the descent rate appropriately.
11) airdata calculator brings up full keyboard instead of numeric only
12) IFD offering UHF frequencies (Jeppesen? Avidyne? issue?)
13) IFD not always ID'ing nav frequencies (showing EE)
14) No Comm Icarus Alt (false alarm message, clear and continue)
15) some users have reported that they are unable to acquire a GPS signal after power up - seems to be very few and might be a red herring




Edited by PA23 - 03 Nov 2022 at 11:01am

Edited by PA23 - 02 Nov 2022 at 11:48am

PA23 wrote: The list I've compiled so far includes 15 items that have been publicly discussed, I'm sure there are more that either I've missed or have not been discussed publicly.  For the bug description either I've summarized the issue or I have simply taken the description verbatim from the posters message.  It is possible that some of these "bugs" are working as intended. Bugs 10.3.0.2 (known) 1) *CRITICAL*  system reboot when highlighting or selecting AR/RF approach -  work-around enable RF legs in maintenance mode?

Thanks for doing this, @PA23.  I reported the 1st item.  Please edit your post to show it is for non-Auth Required Radius to Fix approaches. These approaches are usable by all GA aircraft and pilots,  which is why I stumbled across it.  I do not know how an Auth Required/Radius to Fix approach would behave with the maintenance default of RF Legs = Disabled. 

Dallas90 wrote: I would like to add something to your list that is a mistake being touted as a feature.  (Reminders no longer trigger the MSG alert on some PFDs). This should be a user option, since it will someday keep someone from running a tank dry or getting an out of limits fuel imbalance.  Building a reminder in some heavier aircraft will get you a "Message Alert" and an aural warning that will repeat every couple of minutes until cleared. That is an appropriate level of alerting for reminders. Avidyne is stating that this was suggested by pilots, but I believe they confused a desire for less "Class (B,C,D) airspace ahead" alerts with removing all alerts that are not major system failures form the PFD.

PA23 wrote: The list I've compiled so far includes 15 items that have been publicly discussed, I'm sure there are more that either I've missed or have not been discussed publicly.  For the bug description either I've summarized the issue or I have simply taken the description verbatim from the posters message.  It is possible that some of these "bugs" are working as intended. Bugs 10.3.0.2 (known) 1) *CRITICAL*  system reboot when highlighting or selecting non-RNP required AR/RF approach -  work-around enable RF legs in maintenance mode? 2) *potentially critical* some users have reported that they are unable to acquire a GPS signal after power up or WAAS integrity warnings during approaches - downgrade to 10.2 and the issues went away - not all users are experiencing this issue. 3) IFD loses the last selected frequencies upon power up 4) Altitude Setpoints over ARINC429 - If an altitude constraint is present, an altitude setpoint is sent out over the ARINC429 interface (the value sent is the altitude constraint +1), even if Enroute VNAV is turned off.  This is a new behavior with 10.3 and causes unexpected operation from at least some autopilots. 5) unable to connect an android device to the IFD (work around available) 6) (dual IFDs) If I try to enter a direct-to airport, my other IFD440 will pop up the keyboard as expected... I can then try to type the icao id of the airport which works fine... however, the "Activate KXYZ" simply comes and immediately goes away... My current workaround is to use the BT keyboard which allows the "Activate KXYZ" to persist until I select it 7) when using ADS-B in from a wireless device (eg Stratux), IFD will randomly reject connections and issue various datalink errors, may also extend to hardwired units 8) (dual IFDs) I cannot seem to edit the "cross"/"at"/"wxyz ft" section in the FMS via the latest IFD100 on my iPad... I have no problems editing it on either IFD-440 though. 9) (dual IFDs)  I have seen cases where on one of my IFD-440's, I can "direct-to KXYZ" but that my other IFD-440's FMS will still show the previous "direct-to" that was entered. 10) TOD descent rate reset to a descent ANGLE of 4 degrees instead of fpm as was originally (AUX -> Setup -> FMS, expand FMS, expand VNAV and set the descent rate appropriately. 11) airdata calculator brings up full keyboard instead of numeric only 12) IFD offering UHF frequencies (Jeppesen? Avidyne? issue?) 13) IFD not always ID'ing nav frequencies (showing EE) 14) No Comm Icarus Alt (false alarm message, clear and continue) 15) EFB loses connectivity to the IFD to push flight plans (Unable - IFD became unresponsive)

@PA23, based on the thread that I initiated in http://forums.avidyne.com/potential-rnav-approach-issue-with-ifd540_topic2433.html, you should probably add the issue of an RNAV approach getting downgraded from LPV to LNAV minimums AFTER the IF (in certain situations) to this list. I think this would qualify as a major issue.

PA23 wrote: The list I've compiled so far includes 15 items that have been publicly discussed, I'm sure there are more that either I've missed or have not been discussed publicly.  For the bug description either I've summarized the issue or I have simply taken the description verbatim from the posters message.  It is possible that some of these "bugs" are working as intended. Bugs 10.3.0.2 (known) 1) *CRITICAL*  system reboot when highlighting or selecting non-RNP required AR/RF approach -  work-around enable RF legs in maintenance mode? 2) *potentially critical* some users have reported that they are unable to acquire a GPS signal after power up or WAAS integrity warnings during approaches - downgrade to 10.2 and the issues went away - not all users are experiencing this issue, possibly related to early hardware revisions 3) IFD loses the last selected frequencies upon power up 4) Altitude Setpoints over ARINC429 - If an altitude constraint is present, an altitude setpoint is sent out over the ARINC429 interface (the value sent is the altitude constraint +1), even if Enroute VNAV is turned off.  This is a new behavior with 10.3 and causes unexpected operation from at least some autopilots. 5) unable to connect an android device to the IFD (work around available) 6) (dual IFDs) If I try to enter a direct-to airport, my other IFD440 will pop up the keyboard as expected... I can then try to type the icao id of the airport which works fine... however, the "Activate KXYZ" simply comes and immediately goes away... My current workaround is to use the BT keyboard which allows the "Activate KXYZ" to persist until I select it 7) when using ADS-B in from a wireless device (eg Stratux), IFD will randomly reject connections and issue various datalink errors, may also extend to hardwired units 8) (dual IFDs) I cannot seem to edit the "cross"/"at"/"wxyz ft" section in the FMS via the latest IFD100 on my iPad... I have no problems editing it on either IFD-440 though. 9) (dual IFDs)  I have seen cases where on one of my IFD-440's, I can "direct-to KXYZ" but that my other IFD-440's FMS will still show the previous "direct-to" that was entered. 10) TOD descent rate reset to a descent ANGLE of 4 degrees instead of fpm as was originally (AUX -> Setup -> FMS, expand FMS, expand VNAV and set the descent rate appropriately. 11) airdata calculator brings up full keyboard instead of numeric only 12) IFD offering UHF frequencies (Jeppesen? Avidyne? issue?) 13) IFD not always ID'ing nav frequencies (showing EE) 14) No Comm Icarus Alt (false alarm message, clear and continue) 15) EFB loses connectivity to the IFD to push flight plans (Unable - IFD became unresponsive) 16) When IFD100 is connected a second (EFB) device is not recognized.

LarryPetro wrote: My IFD440s (10.2 versions) have been experiencing GPS Integrity Lost during RNAV approaches for a couple years. LPV approaches are downgraded to LNAV, or lower. This seems to occur while in the course reversal, most commonly.

@LarryPetro,

don't discount the antenna, the waas antennas are powered and have an amplifier in them, I have had them go bad in the past.

I am assuming, from what I have seen so far after updating to 10.3.1.2, that #2 on your list has been fixed: 

Edited by comancheguy - 23 Feb 2023 at 10:41am

Ok, so this is new information.  Nothing changed in my configuration since before 10.3.0.2.

Steve - 

Thanks, Steve 

Thanks, Randy. 

New to forum and came across the list of known 10.3 issues. Has the following issue been resolved?