Feature Request: EdgeTX LUA Forward Programming & Expanded ESC Telemetry/Configuration (YGE, Scorpion, Hobbywing)

[BenStone1234]

Current Behavior

As a Fixed Wing LOS (Line of Sight) and FPV pilot, I often need to tune airplane parameters and ESC settings at the flight line. Currently, INAV relies heavily on a PC, OTG cable, or wireless module (like the SpeedyBee app) for deeper configuration. Furthermore, INAV's ESC telemetry support is mostly limited to drone-centric protocols (AM32/BLHeli32). For pilots flying larger fixed-wing aircraft or using high-end ESCs (Scorpion, YGE, Hobbywing), we lack the ability to read telemetry from these ESCs or program them directly from our transmitters.

Desired Behavior

I would love to see INAV adopt two major quality-of-life features:

Comprehensive EdgeTX LUA Forward Programming (MSP): Implement full FC configuration directly from an EdgeTX radio via LUA scripts (similar to Spektrum Forward Programming). This would completely remove the need for a PC or mobile device at the field.

Expanded ESC Telemetry & ESC Forward Programming: Support for YGE (OpenYGE), Scorpion (UNC), and Hobbywing ESC telemetry. Additionally, implement the MSP passthrough required to allow configuring these ESCs directly from the EdgeTX LUA script.

Suggested Solution

Since Rotorflight (which is forked from Betaflight) already successfully implements these specific ESC telemetry protocols and highly robust LUA-based forward programming via MSP, the suggested solution would be to port or adapt these existing open-source implementations into the INAV codebase. The protocols and architecture already exist within our sister projects, which should hopefully streamline the integration.

Who does this impact? Who is this for?

This greatly impacts Airplane users, specifically traditional LOS pilots, advanced Fixed Wing pilots, and builders flying larger-scale aircraft. It completely bridges the gap for pilots accustomed to expensive proprietary systems (like Spektrum AS3X or Aura8) who want to migrate to an open-source ecosystem without losing the convenience of flight-line tuning and high-end ESC integration.

Additional context

With flight controllers like the RadioMaster Nexus (and Nexus XR) getting an INAV target, we finally have the perfect 8-channel PWM gyro system for the open-source fixed-wing community. Adding forward programming and premium ESC telemetry would make INAV on a Nexus FC the ultimate open-source alternative to traditional fixed-wing gyros.

I want to clarify that this is in no way meant as a demanding "please just add this" request. I began flying FPV in 2021, now fly LOS planes and helicopters, and have used INAV extensively across multiple airframes. I genuinely believe this is the logical next step for the project and would fill a huge gap in the RC hobby.

While I am a developer myself, I am not currently familiar with the INAV codebase. However, I am highly motivated to see this come to life and am more than willing to dedicate my time to help. I can assist with rigorous field testing, providing logs, troubleshooting, or helping in whatever capacity I can to support the maintainers who take this on.

[sensei-hacker]

For adjustments and tuning via the radio, you might be interested in the discussion happening right now on the Discord.

like the RadioMaster Nexus (and Nexus XR) getting an INAV target, we finally have the perfect

The Nexus XR is the single most limited flight controller that can support a subset of INAV features. So in a real way, it is the worst flight controller you could possibly run INAV on (or part of INAV, anyway). It's also one of the heaviest. After INAV 10, we may no longer release the stripped-down version of INAV for the Nexus and other F722 targets, so I wouldn't invest too much into those.

[BenStone1234]

For a traditional LOS fixed-wing pilot, you honestly don't need waypoint navigation, complex GPS return-to-home logic, or heavy blackbox logging running at max rates. What makes something like the Nexus XR appealing for a plane or heli is that it acts as a very user-friendly, drop-in replacement for a standard traditional PWM receiver (like a RadioMaster ER6), roughly the same physical size, but with the massive benefit of a built-in gyro for stabilization.

For a lot of us, using it as a simple, reliable stabilizer with solid telemetry functionality right out of the radio is the real goal.

That said, even if the FC hardware debate is split, the wider ESC telemetry support (for YGE, Scorpion, Hobbywing, etc.) and better radio configuration tools are features that would benefit so many fixed-wing and heli pilots across the board, regardless of whether they are running a full-fat board or a smaller target.

By the way, which specific Discord channel is this particular thread active in so I can follow the rest of the debate? But anyway, thanks for the quick response and everything you and the team have done for the INAV project!

[sensei-hacker]

By the way, which specific Discord channel is this particular thread active in so I can follow the rest of the debate?

It's in General. There's not really a "debate", as much as a discussion of ideas on how to enhance and improve upon an idea. It's about finding the very best ways to do it, to perfect it. Not really a "I want yes!", "I want no!".
More of a "I'm concerned about X and I think Y would be a way alleviate that concern".

From the best I've been able to determine, what draws some pilots to the Nexus is that it feels kinda familiar. Because of the rectangular case. That seems to be what it comes down, it looks kinda like another receiver because it's in a metal box. Same board inside as any other Ali budget FC, same DuPont connectors. Just in a rectangular box, and that feels comforting.

So I'm working with some manufacturers to put much more capable FCs into a rectangular box.