Greetings,
I've been depressed ever since I found out that the new R7008SB receiver would not work with all the FC boards that currently support s.bus. It was obvious that Futaba changed something, but we didn't know what, until now
I spent some quality time with a logic analyzer, and compared the output of an older R6203SB receiver which works, to the new R7008SB that doesn't work. I also had to do some research, which was made easy by the mbed folks who documented the original s.bus protocol.
I'm somewhat bleary from staring at this all day, but the good news is that not much changed. The protocol is 25 bytes, including a start and end byte, with data stuffed in the middle. Everything is the same except for the endbyte. That used to be all zeros, but now it seems to change randomly between 4 different patterns.
Seeing as I'm not a programmer, I documented all the results as clearly as I could in the attached pdf file. My hope is that some clever programmer will look at this and realize that they can fix this in less time than it took me to type this post. I'm not sure if that will be the case or not. Can the endbyte be ignored somehow, or can we look for any one of several possible endbytes?
Thanks,
Rusty (desperately wants to use telemetry on his fancy new radio)
Note that the pdf is being updated as changes are made.