Aloft Forums
Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
R10 Pro Sbus
- Thread starter Redraider
- Start date
Sbus is simply a serial version of all the channels either being 16 channels when in ACCST or 24 channels when in ACCESS mode. You will however need a Sbus to PWM module to pick off the required channels.
thenated0g
Moderator
Sbus is a single cable digital communication. Usually you would only use sbus if you were using a flight controller. If your servos are going to be connected directly to your receiver than you are not going to be using sbus.
in a flight controller setup, like on quadcopters and some fpv planes, all the servos connect directly to the flight controller board. To tell the flight controller what to do from the RX you connect them together with an sbus connection.
in a flight controller setup, like on quadcopters and some fpv planes, all the servos connect directly to the flight controller board. To tell the flight controller what to do from the RX you connect them together with an sbus connection.
SBUS was originally intended to allow one wire to daisy chain all the servos together, rather than a rat's nest of multiple wires. But it needed special SBUS servos that could be set to "know" which channel to respond to. The hardware referenced in the video linked below was made to get around that issue with conventional servos. In recent years, SBUS has been pretty much only used for sending info from the receiver to flight controllers, since they are completely digital.
Here's a video about the older converter and channel changer that I have used in the past to get 4 additional channels.
BUT - the instructions for the R10 warn about using analog servos on an SBUS output, due to the much higher data speed. Talk with Aloft FIRST to verify whether this solution is still viable with the R10 and the specific servos you intend to use.
One used to be able to tie together two old RX8's to get 16 outputs at the pins (1-8 on one, 9-16 on the other). It is unclear as to whether one can do this with ACCESS. It does have a channel remapping function so perhaps one can bind two receivers, and remap one to put higher channels out of the pins. Again, call ALOFT to find out....
Here's a video about the older converter and channel changer that I have used in the past to get 4 additional channels.
BUT - the instructions for the R10 warn about using analog servos on an SBUS output, due to the much higher data speed. Talk with Aloft FIRST to verify whether this solution is still viable with the R10 and the specific servos you intend to use.
One used to be able to tie together two old RX8's to get 16 outputs at the pins (1-8 on one, 9-16 on the other). It is unclear as to whether one can do this with ACCESS. It does have a channel remapping function so perhaps one can bind two receivers, and remap one to put higher channels out of the pins. Again, call ALOFT to find out....
This intrigued me, so I asked over on another forum. Apparently one can remap any channel to any output pins on the ACCESS receivers. So with two receivers, one can have one control chs 1-8, and the second 9-16. Even better, you can duplicate individual channels on each receiver - so if Ch 7 was aileron, it could be mapped to both receivers at the same time. Yet the others could be whatever same or different you needed....
That opens up the possibility of using a cheaper 6ch ACCESS receiver for non-flight critical functions, if noise filtering on those is not a concern.
That opens up the possibility of using a cheaper 6ch ACCESS receiver for non-flight critical functions, if noise filtering on those is not a concern.
