PeterLester
Member
Naza and WKM Assistant software will show their D.bus port connecting to the Futaba Receiver S.bus port!
One would expect these bus communication protocols to be be quite diferent and not be compatible or be named the same, e.g., s.bus signifying compatibility.
But in any case it works....
What is D.Bus? It is an open source communication protocol developed for the PC industry by RedHat http://en.wikipedia.org/wiki/D-Bus
What is S.bus? It is a communication protocol developed by Futaba and has since been reverse engineered http://diydrones.com/profiles/blogs/futaba-sbus-rc-protocol-reverse-engineered
That makes it possible for Arduino developers to use it as well.
While D.Bus and S.Bus are synonymous in case case of Futaba and Naza.... I don't believe it is possible to achieve communication between DJI's Can-Bus and S.Bus or D.Bus.
In any case the cable end plugs are designed to prevent incorrect connections.
What is Can-Bus? CAN bus is a message-based protocol, designed specifically for automotive applications but now also used in other areas such as industrial automation and medical equipment.
If you have ever connected an OBD or OBD2 diagnostics tool to your vechicle diagnostics port, you have used Can-Bus.
What do all three have in common?
It is my understanding that they are all variants of Modbus, a defacto worldwide time based communication protocol.
S.Bus and D.Bus only require 3 wires.... Can-Bus likely only needs three wires but uses four pin plugs.
Futaba Hobby RC products are an offshoot from the mainline Industrial products especially their wireless Overhead crane systems.
As such they have extensive experience using Modbus and CanBus, understand the future potentials of moving this way which obviously led to them implementing the concept into their Hobby Radios.
DJI likewise understands these benefits for enabling a long term future migration path.
Better coordination between product manfacturers such as Zenmuse and DJI should make it possible to remove some of the current inflexibility when sharing or re-assigning s.bus ports and device channels.
One would expect these bus communication protocols to be be quite diferent and not be compatible or be named the same, e.g., s.bus signifying compatibility.
But in any case it works....
What is D.Bus? It is an open source communication protocol developed for the PC industry by RedHat http://en.wikipedia.org/wiki/D-Bus
What is S.bus? It is a communication protocol developed by Futaba and has since been reverse engineered http://diydrones.com/profiles/blogs/futaba-sbus-rc-protocol-reverse-engineered
That makes it possible for Arduino developers to use it as well.
While D.Bus and S.Bus are synonymous in case case of Futaba and Naza.... I don't believe it is possible to achieve communication between DJI's Can-Bus and S.Bus or D.Bus.
In any case the cable end plugs are designed to prevent incorrect connections.
What is Can-Bus? CAN bus is a message-based protocol, designed specifically for automotive applications but now also used in other areas such as industrial automation and medical equipment.
If you have ever connected an OBD or OBD2 diagnostics tool to your vechicle diagnostics port, you have used Can-Bus.
What do all three have in common?
It is my understanding that they are all variants of Modbus, a defacto worldwide time based communication protocol.
S.Bus and D.Bus only require 3 wires.... Can-Bus likely only needs three wires but uses four pin plugs.
Futaba Hobby RC products are an offshoot from the mainline Industrial products especially their wireless Overhead crane systems.
As such they have extensive experience using Modbus and CanBus, understand the future potentials of moving this way which obviously led to them implementing the concept into their Hobby Radios.
DJI likewise understands these benefits for enabling a long term future migration path.
Better coordination between product manfacturers such as Zenmuse and DJI should make it possible to remove some of the current inflexibility when sharing or re-assigning s.bus ports and device channels.