Wez

Tested with: - ExpressLRS 2.4G hardware running the `mavlink-rc` branch, with MavFTP re-enabled - Speedybee F405 wing FC flashed with this PR - 250Hz packet rate, and also 333Hz-full rate...

I've pushed up https://github.com/ExpressLRS/ExpressLRS/pull/2626 on the ELRS side, for when this merges.

Closing this one down, as we went for a different solution. Thanks for your work @nekwebdev. Sorry it was somewhat wasted effort :(

@qqqlab just an FYI, we are aiming to cut a minor bugfix release towards the end of March, and hope to have all fixes merged to the 3.x.x-maintenance branch before...

> I know for a fact that [Spektrum did precisely this](https://github.com/SpektrumRC/SRXL2) with their SRXL2 protocol. If they can do it, so can you. Similar case with mavlink as well: https://github.com/mavlink/c_library_v2...

> I am in the middle of something quite major here, as I indicated above. I have privately messaged hydra already. My thing here could take quite some time to...

I actually think the "issue" you described is what we want (i.e. working as expected). The same bind phrase is supposed to be used across the ELRS ecosystem in order...

> Yeah, I know what you're saying, so it would be better to have the main firmware tell the TX backpack what the bind UID is rather than configure it...

An easier approach is to prevent the TX-backpack from sending any messages if it has a different UID to the TX

> > An easier approach is to prevent the TX-backpack from sending any messages if it has a different UID to the TX > > I don't like the idea...