I am pretty sure some of you have already viewed this. I would like to give JB a few thumbs up for coming up with this. I have in the past tried to think of ways to do what he did, but always come up short. JB, great work.



Why is this important? The biggest drawback with Frsky SBUS is the latency. On reason people are moving to Crossfire. But as Oscar just pointed out, the R9M lite is par with Crossfire.

https://oscarliang.com/r9m-lite-crossfir...y-testing/

But if you are using 2.4ghz Frsky, there is a big difference in latency from 8 channels vs 16 channels.



The JB solution lets you have your cake and eat it too. Putting everything on one channel allows you to reduce your latency by only using 8 channels vs 16 channels.

Real world applications. Although I am impressed, I don't think I will go down this route. I am not a professional racer. I don't see myself trying it. It might be fun to see if I can get it working.

Yes I watched it yesterday and thought it was quite a stroke of genius. I have to admit that I did need to rewind a few parts and play them back again to fully understand some of the stuff, but I think I got it in the end. It was a hard job trying to explain that complex setup in an understandable way so I think JB did quite well even tough some of the haters in the comments didn't seem to think so.

I can see this being useful on a whoop that can only has 8 channels available because of it having to be bound in D8 mode (as per non-EU FrSky whoops used with EU-LBT transmitters). Now you can implement as many features as you desire without running out of channels

One downside I do see to this however is that if yo get something wrong or something gets screwed up, it could turn into a complete brain explosion trying to figure out and debug where the problem is. Overlapping channels in Betaflight, mixer settings that are have to be in a certain order with specific channel weightings and values, and then logical switches also thrown into that lot as well !!!