Wilhelm
Wilhelm
Well, I modified the very first example a bit: ``` #include #include namespace sml = boost::sml; volatile uint8_t r = 0; namespace { struct start {}; struct run {}; struct...
Updating the internal and the external ELRS module to 3.3.4-RCx fixed the freeze problem.
Well, I don't know, what the problems with the actual implementation is, so I can't imagine to nearby solution. I do not even know for sure if this is also...
Would be cool to have a CRSF-command to switch the active receiver. This is not to "waste" one of the 16 rc-channels for that switching purpose. The drawback would be,...
Another cool option would be to have the "disabled" receivers still output the channel data. Well, you call it dangerous, but in the ship/boat-modelists scene, it it not uncommon to...
The firmware on my external µC was working I think at least until 2.8.x and remains unchanged, but the radio stops recognizing the telemetry data the µC sends now. Maybe...
Ok, the first question is, what the motivation was to introduce this check: https://github.com/EdgeTX/edgetx/commit/ff2b3ac22ab3756204066153cd5fc2ac08212026#diff-c4a06aa2127e48201e600ecfb1fd4805378bc8b6d532adc93244f54a26589f48 This enables telemetry-in only when external module is ppm. That doesn't make sense to me.
Thank you for your explanation! The first question is: what is the purpose of `PROTOCOL_TELEMETRY_FRSKY_D_SECONDARY` ? And what is `PROTOCOL_TELEMETRY_FRSKY_D` instead? If I grep the sources, I get: ``` $...
> AFAIK, it was to be able to support some DIY Multiplex module which was outputting its telemetry into the S.PORT pin in this format. Ok, sounds really that I...