S-Bus Protocol

Start
Prev
1
Next
End

ZeXx86
Topic Author
Offline

18 Sep 2017 12:13 #64478 by ZeXx86

S-Bus Protocol was created by ZeXx86

Dear members,

I have a question for anyone that is technically more skilled in the communication of the receivers.
We want to implement support for the S-Bus protocol that can work with RX-SBUS receiver or any similar. Unfortunately it looks like it is a different from Futaba S-BUS implementation.
For this reason we would like to know what are differences in the protocol?

Thank you,

Spirit System developer

victzh
Offline

22 Sep 2017 04:23 #64578 by victzh

Replied by victzh on topic S-Bus Protocol

Which specific receiver do you mean when you say "RX-SBUS"? Walkera RX-SBUS? How did you find out that it's different?

ZeXx86
Topic Author
Offline

22 Sep 2017 06:24 #64582 by ZeXx86

Replied by ZeXx86 on topic S-Bus Protocol

Simply - because it does not work.
While all Futaba receivers and also all FrSky receivers are working properly.

Yes, it is Walkera RX-SBUS receiver.

vlad_vy
Offline

22 Sep 2017 07:54 #64588 by vlad_vy

Replied by vlad_vy on topic S-Bus Protocol

Probably transmitter and receiver is not connected. What is state of Rx LED? What about PPM protocol?

aMax
Offline

22 Sep 2017 09:53 - 22 Sep 2017 09:57 #64591 by aMax

Replied by aMax on topic S-Bus Protocol

Assuming the target is a quad with F3 mcu, test your receiver with none inverted signal setting on the FC uart.
Maybe they have setup this way because the F4 chips don´t have this option and need a hardware solution.

If your FC has a F4 mcu, make sure you are using the intended uart port.
Frsky and Futaba receivers have an inverted signal output..

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02

Last edit: 22 Sep 2017 09:57 by aMax.

Start
Prev
1
Next
End

Time to create page: 0.035 seconds