Jay Blackman

This would be perfect on a 7x7 AT32 and put onto the VTX with canvas support via serial. The preference is to move all video processing OFF the flight controller...

@hydra For this to be merged you'll need to move all aspects of your implementation into the lib directory, provide a non specific interface in 'main' so other implementations could...

> Firstly, hi, thanks for the update! > > Can you clarify why there should be no specific spracing defines in 'main', as this is the approach we take for...

I'm not sure on this one. Why reuse? Configurator is not the only tool using msp.

> Happy to add a new parameter to the message. But as this was removed six years ago don't think it would be used anymore. The issue is we don't...

> Same issue with SpeedyBee F7 V3, motors not spining at all (tested in BF Configurator, BlheliSuite32 and after arming a quad from radio). ESC are up to date (32.10)....

the command `feature list` might be worth adding some params - or simply return all, including unavailable as you indicated.

> When this PR is open - is it worth supporting `feature softserial telem -led_st -osd 3d` ( = multiple enable.disable in single command)? this would make the diff and...

> Another possible implementation: > > * augment https://build.betaflight.com/api/options/4.5.0-zulu with group and option id's (small integer that is not reused on protocol changes) > * add python (or perl) code...

I would not worry too much about payload size. It's a once per connection request response. I'm more concerned with flash space and maintainability.