Wilhelm

This is a long-standing issue: https://github.com/EdgeTX/edgetx/issues/134 But after some years of experience now, I would say, that a transparent channel value transport (bit-precise) would be against the concepts of EdgeTx...

Oh, cool, that you did spend a lot of work on it!!! This PR is against master, would it be applicable to 3.x.x-maintenance also (for #2975) ? Yes, I will...

Just wanted to test that in a HappyModel ES24 TX module, but that errors with "not enough space". Is there a change to reduce the fw size?

I have a setup with a ESP8285-RX-as-TX, an ER6 receiver, and four other devices (addresses: 0xc6, 0xc8, 0xca, 0xcc). These devices do respond to a device-ping, their device-info response is...

Changing the timing so that all devices respond within ca. 25ms does not help  Attached is a LA trace to see the timing: on the TX line the first...

Tracing also the packets that come out of the TX-module shows, that not all device-info packages that the receiver gets come thru to the TX module. On the attached LA...

If only one external device responds to a device-ping package, its responding package only occasionally comes thru to the TX-module. The next image show the receiver receiving a device-info package...

Changing to 50Hz and 1:2 telemetry ratio does not help.

With ELRS V3.5.4. this situation is much better:  Here all packges come thru.

I made the above tests also with a TBS Trace tx-module and receiver. With this setup, there are no problems with 4 external devices: all 6 devices (including tx-module and...