This will be long winded:
I’m in the process of configuring my herelink Controller v1.1 and MP 1.3.82 in a Cube Orange+. I’m somehow missing something. I’m trying to configure the short and long button configs. And though I’m able to configure the buttons in the controller using the herelink settings app, and confirm that they are functioning as configure, I able to confirm that they are functioning in the MP Setup in Radio Calibration, I’m unable to get the button function to show and function in the Flight Modes. If I set the para FLTMODE_CH to the matching channel for a single button function, the mode for the short and long press display and function, but this is only working for one channel and not for any of the buttons with changed channel settings (if that makes sense). So, what am I doing wrong. I cannot find any newer material out on the web that matches my newer versions. Thank you.
EDIT: I’m leaving this post intact in case it helps anyone (and don’t blame me if you crash). But see my next response below for a far better answer from CubePilot’s docs.
I don’t think you’re the first to struggle with this, and I think I recall that there isn’t exactly a clean solution. I’m replying because it’s been over two weeks with no answer, and though I’m no expert on HereLink, I’ll reply with a couple of assumptions and some certain facts.
First the facts:
FLTMODE_CH works best on a 6 position RC switch.
CubePilot’s documentation discourages use of HereLink buttons on FLTMODE_CH, seemingly for good reason.
A little assumption:
I think you can use multi-button config to emulate a multi-position switch to change flight modes, despite the recommendation, so long as you accept the risk incurred by doing so (“Autopilot mode selection must not be programmed to sbus channels. Mode selection should be configured to Mavlink commands within Solex or QGC to ensure predictable behavior in the event of signal loss or system reboot.”).
An admission:
I have no idea what Solex is. EDIT: Solex looks like it’s the app that’s intended to be displayed on the screen, and it appears to feature flight mode selection. If that’s possible, just use it!
If you want to proceed, you need all of your buttons to function on one channel (FLTMODE_CH), assigning values that fall within the following PWM ranges for each flight mode:
The default at power on should probably be Loiter mode or RTL in case of a disconnect or power cycle during operation.
Disclaimer:
You do this at your own risk. It does not seem advisable.
An alternate but still inadvisable solution if you have a few spare channels at your disposal:
Assign each button to its own channel. Use the RCx_OPTION parameter to set a single flight mode for each channel. When the channel goes high, the flight mode for that RCx_OPTION will be selected. There are still pitfalls with this solution, so again, use it at your own risk.
This page discusses setting flight mode buttons correctly. I highly encourage you to use this method (or whatever variation exists on your version):
If you continue to have problems, suggest posting at https://discuss.cubepilot.org/ for more direct help with their products.
Thank you Yuri, you were the first to at least offer a suggestion. Like I mention, the screen shot you provided is not like in my version of MP. I have looked into the CubePilot forum and posted the same question.
No one mentioned that the modes could be flakey, so I will take caution when programming and testing.
Again, thank you.
Update Mission Planner - you are on an old release. The screen I showed is under Setup/Flight Modes…but…
Use MAVLink buttons on the HereLink for your flight modes. I see no downside to that approach. Set FLTMODE_CH to 0, and ignore the Flight Mode page in Mission Planner.
My MP is v.1.3.82. (1.3.8979.17128). I thought it stated it was the current stable version.
This is what was stated.
There are a few extra options because I was connected to a multirotor. Plane doesn’t have simple mode.
Again, all of this is somewhat irrelevant if you follow CubePilot’s docs to set up MAVLink buttons.
My apologies, I corrected it, but my version does not show “Simple Mode, Super Simple mode” on my version. .
That explains it, I’m using Plane - for VTOL