Well, here’s something interesting. QGC responds with audio call outs and Flight Mode display with v1.7.3Dev with Standard VTOL. Does this mean this issue is in the firmware?
If you are flying Multi-Rotor Manual and Stabliized are the same thing (I think). If you really want to find out what is going on you need to be talking with firmware folks. but you are in the QGC forum so you may not hit them.
I’ve reclassified this thread to Software Development as suggested by @DonLakeFlyer.
I’m not 100% sure I understand the issue. Flying master today, we can confirm call outs on mode change occurred on fixed wing. How the buttons are set up shouldn’t matter. Mode changes should be mode changes. Download the qgc daily version and give that a try.
Just to make sure everyone’s on the same page; I’m doing this on the bench during initial setup. It does audio call out “Reject Hold” when I choose the Loiter switch.
Humor me once. Change your flight mode setup where you have one channel on a 3-way switch then assign other flight modes to other 2-way or 3-way switches from other channels. As my example below, CH6 is on a 3-way that has Position, Altitude and Manual, CH9 on a 2-way as Stabilize; using, as you suggested, a QGC Daily Build.
When I switch CH6 to Altitude, QGC will audio call out “Altitude” and display it by the icon bar.
When I activate CH9 switch, I’m presuming it switched to Stabilize but have no confirmation since it didn’t make an audio call out on the flight mode and doesn’t show the change on the icon bar:
As @DonLakeFlyer indicated, this is a firmware issue, not a QGC one.
If you look at post #6, when I changed the airframe to a VTOL, the audio call out and icon bar display is correct, per the switch activation of CH9. And for good measure, I also upgraded to v1.8.2 Stable on the VTOL and it was working as well.
Ok - No problem. I’ll give it a try tomorrow and see what happens and write back on this.
Just following to find out if you had a chance to try this out. If you did, did you get the same results as I did?
The reason it doesn’t switch to the mode is because the vehicle presumably doesn’t have GPS signal on the bench. That’s why you only see the messages that it has been rejected.
Also, as you found some switches have higher “priority” than others. For instance, the return switch takes precedence over others.
Yes, that’s true after initial boot but once it has enough satellites, it doesn’t reject it but the change doesn’t show on the icon bar as the second image at my Post #11, it shows 14 satellites and 0.7 HDOP,
But besides that, if you look at my Post #6, with a VTOL airframe type, it does reflect and audio call out the correct flight mode as triggered by CH9 switch on the Tx. As @DonLakeFlyer mentioned, it has to be in the Airplane module/firmware as it seems to work in the Multi-Rotor code.
Hm, so this is a regression in master where the stabilized switch does not seem to work anymore?
I can only presume so. This is the first I’m using Generic Flying Wing instead of a VTOL airframe so the VTOL is my only one I can compare to.
Tested - You are right. It doesn’t call out mode changes done by switches. Tested with a fixed wing and just switches to change modes and with one switch to change the multi mode and another switch for a separate standalone mode.
So, can I presume that you’ll take care of the necessary process to file the issue and resolve it in the latest master? If so, could you post here that the issue has been resolved?
I’m not sure I follow what exactly the outcome of your tests was but I’d appreciate an issue about it.
@rollys I think you’ll be better suited to open an issue. I just briefly tested to see what you were saying.
@JulianOes by setting one channel to control (for example) activating manual flight mode, and another channel to activate stabilized flight mode in the flight modes pane. And this is with or in lieu of using the multi mode selector with one channel, qgc doesn’t fall out mode changes. In some instances (iirc) it wasn’t even changing the modes but I only tested it briefly but definitely doesn’t call out the modes this way.
Issue #11657 filed.
No problem. I didn’t do much but out of curiousity, do you plan on moving to 1.9 when in stable? I’ve seen better fw performance with it.
I would consider it but will it auto-start the FrSky Telemetry SYS_COMPANION param? My main interest is in VTOL but getting involved more with FW flying again due to professional piloting opportunities.
You can auto-start in 1.9. All that’s changing is the old format. It’s being deprecated to give yo more granular control over what constitutes what to each port but the functionality is the same. Take a look at the px4 parameter reference page for master (just select master in the top left side of the page). It’s there for frsky telemetry.