I understand you and I know what can be done, but my problem is that I only have 12 channels and all are busy, if I have to use a channel just to change panels, it is a bit absurd. If the function I request, could be implemented, we would save a channel for those who do not use more than a single panel. Greetings
first, thanks for the continuous development of this fantastic software.
My question: I’ve installed plane 4.0.1 release but I don’t find the TAKEOFF Mode in the Flight Mode list.
Am I missing something ? Is it a parameter to set in Parameter List/Tree only ?
Hi Corrado- I have enabled Takeoff mode on a Nano Talon but only tested int indoors with no props and in the SITL. The props spin up from throwing acceleration so it should work. Weather is bad here to try it for real. I think if you have it working in a mission it will work as a mode.
While it is possible that updating MissionPlanner will help, what you probably need to do is tell MissionPlanner to rebuild it’s parameters. Open the Control-F menu, then select “Param gen” (it is 7th down on the left side). Then leave MissionPlanner running for a couple of minutes. After that restart it and you should find that TAKEOFF has been added.
I’m not able (in v4.0.1) to find parameter SCR_ENABLE to start playing with the scripts (more specifically, to have more freedom for my in-flight glow plug igniter (winter is cold here!)). Is there something else that needs to be enabled to access scripting?
Can scripts be updated remotely via MavLink?
Are there any “spare” parameters (call it user params if you want) to be used in scripts? These could be easily changed from the ground station to give more flexibility to the scripts.
Thinking of a glow plug igniter, I’d could use one of these user parameters to store the PWM of the throttle below which I’d like the igniter to be on… It could then be easily adjusted from the ground station.
Hi Nicolau, which flight controller do you have?
For scripting the flight controller requires over 1 MB. SCR_ENABLE is therefore not displayed on a Pixhawk 1 or a Matek F405, on modern Pixhawks with 2 MB or, for example, the F765 wing, the parameter is visible.
I tried Randy’s procedure to check if this board was affected to no avail (I guess the NSH is no longer valid in ChibiOS).
I updated to v4.0.1 the other Pixhawk I have and the SCR_ENABLE is there, meaning I do things right and that the former Pixhwak I tried surely has the 1MB flash bug (interestingly, I bought that one recently… sellers probably have a stock of these).
Thanks for the hints, guys!