I tried unsuccessfully to get my TX16S with a crossfire diversity to do complete control over mavlink, so I’m going back to CRSF. This is done by disabling the rc_input driver and useing the crsf_rc driver.
I have noticed that there is CRSF telemetry code inside. Does this mean that using CRSF for radio control uses a different telemetry method than the rc_input driver? Is there some other place I should be looking for this? An RC input driver doesn’t really feel like the right place to be putting telemetry output code… What have I missed?
maybe a tangential question, but does that mean RC_PORT_CONFIG + RC_INPUT_PROTO == CRSF is useless?
I suspect it could be possible to use CRSF to send telemetry while something like sbus or ppm is used to receivethe RC signals. I was out of the RC gig for so many years that many things have changed. It used to be the case that you buy your radio and the receivers for that radio and that was the only option.
With PX4, I wonder why the two drivers are even separate? There is obviously value in having the switches available to exclude a protocol you don’t need, but adding an additional step for a common radio type probably doesn’t help attract users.
