disable summary screen?

[chimera15]

Current Behavior

after disarming a summary screen wipes out the osd

Desired Behavior

no summary screen

Suggested Solution

a toggle or cli command to disable that function

Who does this impact? Who is this for?

I'm running a multi flight controller vtol with betaflight controlling the vertical takeoff and landing, and the inav controlling the horizontal flight, I need to be able to disarm and still have the osd functioning, disarming causes the summary screen to blank out my osd and put a bunch of stuff up while I'm still in flight. I need to be able to disarm because I need to use the throttle to control the other fc and remain in flight.

Also a way to arm with the throttle high is another problem I'm having if anyone knows if there's a workaround for that. I've been asking chatgpt and looking through all the documents and I can't find anything that actually works. I've been trying to program a work around in the programming tab but nothing seems to work.

Additional context

[MrD-RC]

This sounds like a very specific use case. Not something that many, if any, other INAV pilots would find useful. It may be better for you to fork the project and make your own changes.

[sensei-hacker]

I don't know what you're actual goal is, but one definitely might want to consider just using the native VTOL functionality in INAV.

I could see using Betaflight for a racing quad, but a VTOL is FAR from a racing quad.

[chimera15]

I don't know what you're actual goal is, but one definitely might want to consider just using the native VTOL functionality in INAV.

I could see using Betaflight for a racing quad, but a VTOL is FAR from a racing quad.

I've tried that, there's an issue with pids, and transitioning profiles and mixer profiles. This allows me to keep the betaflight fc active without having to switch to forward flight immediately. Think basically as using a quad to tow a plane into the sky, as two separate things, there's lots of advantages to that rather than having to switch and suddenly have it have to be reactive to the flight pids.

Also my understanding is that betaflight has way way better filters and flight dynamics and controls for quads, i term relax and ag gain for instance, Feed Forward working different, although I've never built a quad in inav even, but built lots of planes, and obviously inav is better for the plane parts and servos and such, so its the best of both worlds this way imo if I can get these little issues ironed out.

I'm using this as a test bed to test wing profiles as well, so pids are going to be tuned a lot. Currently the quad is flying perfectly on betaflight, but when I add the wing things are going to have to be tweaked for sure.

This is essentially a flying wind tunnel if you want to think of it that way.

[chimera15]

This sounds like a very specific use case. Not something that many, if any, other INAV pilots would find useful. It may be better for you to fork the project and make your own changes.

ok, so part of this is just checking and making sure before I try to do that, you're saying there's no current way to just turn this stuff off?

I may just end up using a camera switch in that case rather than having to fork and struggling with compiling an open source project that I've had endless nightmare problems with before.

Still have the arm problem though. I can just go to zero throttle and arm but again, one of the main things I'm trying to do is create an extremely smooth transition between vtol and forward flight, so that sort of ruins that.

[chimera15]

Got this working with the help of Grok, it did a ton of heavy lifting to help me compile, would have been completely lost without it, there were like dozens of problems I had to solve with the target and everything specifically.

I realized I didn't actually need to disarm, I just needed to remap the throttle for the inav fc to a slider to have separate throttles, so I can achieve a perfect transition, I can give it throttle and keep the betaflight fc armed until I'm confident that the airfoil is flying stable, then I can disarm betaflight, but I never have to disable inav cause I can just go to zero throttle separately now.

What's up with inav not allowing to remap channels either, had to hard code in the throttle to my slider...it works but still pretty not good for something I would want to commit right? Talking to grok it actually seems like it might be pretty easy to just add a drop down or something to allow the throttle channel to be configured in the configurator.... hmm

[MrD-RC]

On any normal setup, the first 4 channels are always pitch, roll, yaw, and throttle. You can change the order of these in INAV. But what you can't do is say the throttle is on channel 10 for example. 99.999999% of people would never want to do this. Hell, some protocols demant that the first 4 channels are the control channels. You're blaming INAV for faults because you're wanting to use it in an extremely unique way.

[chimera15]

On any normal setup, the first 4 channels are always pitch, roll, yaw, and throttle. You can change the order of these in INAV. But what you can't do is say the throttle is on channel 10 for example. 99.999999% of people would never want to do this. Hell, some protocols demant that the first 4 channels are the control channels. You're blaming INAV for faults because you're wanting to use it in an extremely unique way.

I'm not "blaming" it, and yes admittedly this is pretty unique, although part of the issue is I didn't realize how unique it was when I opened the thread.

But, things should be configurable, things like resource remapping in betaflight allow for a lot of things that aren't allowable in inav, lots of cli commands that aren't broken out that Inav also doesn't have parallels. This was a "feature request" to begin with, and got no help. if I want to blame anything on inav it would be that. I solved it and now can compile my target for future mods so whatever.

Also I think my initial request of just being able to disable the disarm summary screen is something that should be available by cli command at least, even if it's not broken out into a configurator slider or something. There are other situations other than mine that I could forsee that being useful for, there are other cases where you might want to disarm or might disarm by accident or something and still be flying and not want to be presented a wall of text.