Wilhelm
Wilhelm
> some "real" input extension protocol Do you have special in mind?
> Wouldn’t trainer be a better fit than telemetry to get extra input in? It would be cool to have proportional external input as well as binary / ternary (or...
> Well, something that would be closer to the hardware, and thus allowing us to integrate at lower level, and thus be usable in many flexible ways. Do you mean...
Well, I don't think I2C would be a good idea here, because * if the handset is the master, it requires drives for all possible I2C slaves * if the...
> How about MAVLink as the "UART protocol"? Would be an option, but MAVLink is huge
> Yes, but the code is there: https://mavlink.io/en/getting_started/use_libraries.html (here especially https://github.com/olliw42/fastmavlink would likely be the one to go with). Especially the integrated MAVLink router in fastmavlink lib could be IMO...
What about MultiWii (MSP). Maybe a bit more widespread?
Thinking a bit more about this topic I got the impression, that MAVLink is not the right protocol for extending the built-in pots/switches/... of a handset. There are two reasons:...
I'm using the actual 07e0bfa git version. And flashed also the bootloader to this version. I'm using "Telemetry In" at AUX2: in this mode the power supply turns not on,...
Up to now you can only switch one widget to fullscreen, say one out of four in a 4x1 layout. What I mean is to switch the whole 4x1-screen to...