QGC Doesn’t Call Out Flight Modes When Setup in Switch Settings Single Channel

[rollysing]

Complete thread discussion are here:
http://discuss.px4.io/t/qgc-doesnt-call-out-flight-modes-setup-in-switch-settings-section/9808

• All screenshots and testing are done on the bench during initial setup and no flight testing has been done.
• This issue is confirmed from v1.8.0 Dev up to current.
• Airframe: Airplane; FX-79 Flying Wing
• I don't know what version nor specific airframe @ryanjAA used to replicate this issue on his setup.
• I did try using a QGC Daily Build as @DonLakeFlyer suggested to no avail.

Issue:

Everything is normal in QGC's audio call out and display when Flight Modes are assigned under Flight Mode Settings via a single channel.

But when Flight Modes are setup under Switch Settings via individual channels, QGC doesn't call out the Flight Mode when activated by a single channel assignment nor change to display the active Flight Mode. In the example below, a set of Flight Modes were assigned to CH6 on a 3-way switch, and "Stabilize" mode was assigned to CH9 on a 2-way switch. When the 2-way switch is activated, the Flight mode on the icon bar still reflects what's on the 3-way and no audio call out for "Stabilize" is made. At this point, I have no confirmation whether it's in Altitude or Stabilize.

For comparison, I tried this on a VTOL build that had v1.7.3dev in it and when it's in FW mode, and a Flight Mode assigned to a single channel is activated, it does call out the Flight Mode and changes the display on the icon bar.

Semi-conclusion:
The issue seem to only affect the Plane Airframe Type firmware since it works fine in both MC and FW mode in VTOL airframe.

It would preferable if there's a patch that can be made to make it work with v1.8.0dev (it's the only version that auto-starts FrSky Telemetry in Telem2 when set in SYS_COMPANION, unless the next version will have it standard). If not, please advise when resolved and hopefully a downloadable link.

Thanks.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.