SBUS vs PPM vs iBus: RC Receiver Protocols and ELRS Explained

Last Updated: October 2026 | Difficulty: Beginner–Intermediate | Author: Dannyi Chen

Dannyi Chen, RC enthusiast and technical writer at SoarSky. This guide explains documented receiver interfaces and setup checks, without claiming comparative latency measurements or flight tests.

What is a receiver protocol, and how is it different from the radio link?

A receiver output protocol describes how channel data reaches the flight controller; the radio-link system determines whether the transmitter and receiver can communicate wirelessly. These are different compatibility checks.

For example, a receiver with SBUS output does not automatically bind to a Futaba transmitter. Likewise, two Flysky products may use different RF families, such as AFHDS 2A, AFHDS 3 or ELRS. Match the exact transmitter/module, receiver RF family, band and firmware requirements before considering the output connector.

Check both legs of the system: transmitter → wireless receiver, then receiver → flight controller. A bound receiver with the wrong wired configuration may show a healthy link LED but no channel movement in the configurator.

↑ Back to Contents

How do SBUS, PPM and iBus differ?

The practical differences are signal encoding, supported inputs, inversion and available features, not a universal ranking of speed or precision.

Sources: ArduPilot wiring guide, ArduPilot CRSF/ELRS guide and ExpressLRS receiver wiring. Consult the exact board and receiver manuals.

A frame's data-field size is not the same as usable control resolution. Packet interval is not the same as end-to-end latency. Receiver mode, RF packet rate, firmware scheduling and the rest of the control chain all affect the result. This guide therefore does not present fixed latency, range or bit-depth rankings as universal specifications.

↑ Back to Contents

Does SBUS always need a dedicated SBUS pad?

No. Standard SBUS needs the correct signal polarity, but inversion can be handled by a dedicated board input, a capable UART configuration or a suitable external inverter.

Choose the input from the board manual

A labeled SBUS pad is often the intended route on boards with a hardware inverter. It is not a universal rule that every SBUS receiver must connect to such a pad, nor that every ordinary UART can decode inverted SBUS. ArduPilot documents UART RC input with inversion settings where the processor and board support them.

Separate control data from telemetry

The SBUS channel stream itself does not provide flight-controller telemetry. Some radio systems provide telemetry through another port or protocol. Do not infer telemetry capability from an SBUS label alone, and do not treat S.BUS2 as interchangeable with every SBUS input.

Check receiver-specific channel support

The number of useful channels depends on the receiver and transmitter, not only the bus format. Futaba's R2008SB manual specifies up to eight channels through its S.BUS port depending on the transmitter; it should not be advertised as providing sixteen independent controls merely because it outputs SBUS.

Source: Futaba R2008SB manual.

↑ Back to Contents

Where can you connect a PPM receiver?

Connect PPM only to an input that the board and installed firmware explicitly support for PPM decoding. A spare UART RX label is not enough.

PPM stands for Pulse Position Modulation. Channel information is carried by the timing of pulses within a sequence; it is not the same as a separate PWM servo output for each channel. Frame timing, supported channel count and input polarity depend on the implementation.

Some boards multiplex a pin between a timer-based RC input and a UART function. Changing that configuration may enable one mode while disabling another. Other board/firmware combinations do not support PPM at all. Check the exact pin map and firmware target instead of copying a wiring diagram from a different flight controller.

PPM remains useful when a legacy receiver or controller requires it. For a new installation, use a supported serial interface when it better meets the system's feature needs. Do not replace compatible working equipment solely because a newer protocol name exists.

↑ Back to Contents

What should Flysky owners know about iBus and i-BUS2?

iBus support is a wired-interface feature, not proof that two Flysky devices use compatible wireless systems. Check the receiver's RF family and output mode separately.

The official FTr16S listing identifies AFHDS 3 and i.bus / s.bus / PPM outputs. That does not make it a universal replacement for AFHDS 2A receivers or an ELRS receiver. Compatibility must be checked for the actual transmitter or module and receiver firmware.

Do not equate a channel value stored in a multi-byte field with sixteen bits of effective control resolution. Likewise, avoid the blanket claim that all iBus devices have the same channel count or refresh rate. Flysky has documented different generations and firmware support requirements.

Flysky describes i-BUS2 as a single-wire bus for compatible sensors, servos, governors and other peripherals. It is not accurately summarized as simply “ordinary iBus with fourteen channels.” Distinguish the receiver's channel-output port, telemetry/sensor port and peripheral bus before connecting equipment.

↑ Back to Contents

How do CRSF and ExpressLRS fit together?

ExpressLRS is a radio-link system; CRSF is the serial interface commonly used by UART-based ELRS receivers to communicate with flight controllers. They are not mutually exclusive alternatives.

Normal UART receiver wiring

For the normal CRSF connection, wire receiver TX to FC RX and receiver RX to FC TX on the same supported UART, plus ground and the specified power supply. The return line carries telemetry. Check the board manual because some manufacturers use unusual labels or share receiver UARTs with other functions.

Packet rate is a configuration choice

Supported packet rates and channel modes vary with receiver hardware, band, firmware and transmitter configuration. A higher selected rate is not a universal promise of lower total latency or greater range. Choose a mode supported by the complete system and verify link health and failsafe before flight.

Band and firmware must match

The transmitter/module and receiver must support a compatible band and firmware combination. A shared binding phrase alone does not make incompatible hardware or firmware work together. Follow the official setup instructions for the installed version rather than assuming every new receiver is ready to bind without configuration.

Some ExpressLRS receivers can provide alternative serial outputs for legacy equipment. The official serial-protocol guide recommends CRSF when the connected hardware supports it and notes that SBUS does not provide flight-controller telemetry.

↑ Back to Contents

Which receiver fits your setup?

Choose by exact RF compatibility first, then electrical input support, telemetry requirements and installation space.

The Futaba R2008SB manual explicitly distinguishes S-FHSS/FHSS from FASST. Do not select a receiver solely by transmitter brand or a store title containing a list of radio models.

Four checks before power-up

1. Input and protocol: confirm the actual pad, UART allocation, inversion and configured receiver mode.
2. Ground: connect receiver and flight-controller ground as documented.
3. Power: use the receiver's specified supply range and a rail with sufficient capacity. Supply voltage and serial signal logic voltage are different specifications.
4. Safety: check polarity, solder bridges and wire routing. With propellers removed, verify channel order, endpoints, arming behavior and failsafe.

↑ Back to Contents

SoarSky Editorial Experience: what is our practical recommendation?

Our editorial recommendation is to solve compatibility and wiring before comparing headline speed claims. This is a documentation-based assessment, not a customer testimonial or a claim of measured shop testing.

We have not retained the previous draft's unverified “150Hz vs 500Hz shop test” as evidence. Meaningful latency comparisons require a stated test method and matching hardware and firmware conditions.

↑ Back to Contents

What are the most common receiver setup questions?

Does SBUS always require an external inverter?

No. A board may provide hardware inversion or a supported UART inversion setting. Follow its manual.

Can PPM connect to any UART RX pad?

No. PPM needs a supported decoding input; a spare UART label alone does not establish compatibility.

Are CRSF and ELRS competing receiver protocols?

Not in this context. ELRS is the radio-link system; UART-based ELRS receivers commonly use CRSF to talk to the FC.

Will an SBUS receiver bind to any Futaba radio?

No. SBUS is an output interface. The receiver and transmitter must also use compatible RF systems and modes.

Does an iBus data field guarantee sixteen-bit control resolution?

No. Storage width is not usable control resolution; check the transmitter, receiver and firmware specifications.

Do normal CRSF connections need both RX and TX?

Yes. Use the documented full UART connection, crossing receiver TX to FC RX and receiver RX to FC TX.

Does a protocol name guarantee radio range or latency?

No. RF hardware, configuration, antennas and the complete control chain determine the result.

↑ Back to Contents

Which receiver listings can you compare at SoarSky?

These listings were available for sale when checked on October 28, 2026. Prices are USD and can change. Confirm exact RF and firmware compatibility before ordering; availability for sale does not establish physical stock quantity.

DolphinRC DP-ELRS Nano Receiver

ELRS receiver option for a compatible transmitter/module and configured FC.

$14.59

Buy Now

DolphinRC DP-ELRS Nano board and antenna, shown in the product graphic.

Flysky PR02 True Diversity ELRS Receiver – Dual-Chip 2.4GHz for FPV Drone & RC Aircraft

ELRS receiver listing; check hardware, antenna placement and firmware setup.

$24.99

Buy Now

Flysky PR02 in its retail packaging with connection leads.

FLYSKY FTr16S 2.4G 16CH AFHDS3 Micro Receiver

AFHDS 3 micro receiver with selectable serial output options.

$26.99

Buy Now

Flysky FTr16S showing its dual antennas and labeled output connections.

Flysky FS IA6B RC Receiver 6CH

Receiver option for compatible AFHDS 2A equipment; verify output mode.

$12.99

Buy Now

Flysky FS-iA6B with conventional channel headers and bus connectors.

FUTABA R2008SB 2.4G 8-way Receiver For 6J/6K/8J/14SG/18MZ/18SZ

S-FHSS/FHSS receiver with S.BUS output; verify the transmitter's RF mode.

$62.99

Buy Now

Futaba R2008SB with S.BUS labeling and conventional channel connectors.

↑ Back to Contents

Which related guides can help with your build?

These guides expand the component-selection context once the transmitter, receiver and flight-controller interface are matched.

FPV Flight Controller Complete Guide
Understand processor, firmware and peripheral choices before assigning receiver UARTs, then use the exact board manual for pin mapping and configuration.

Understanding and How to Choose the Right FPV Motor
Review motor specification terminology when planning the powertrain after the radio link, keeping receiver-interface decisions separate from propulsion requirements and component sizing.

Ultimate Beginner's Guide to Building Your First Drone
Place receiver installation within the wider build sequence, from component planning and wiring checks to configuration and a controlled pre-flight verification routine.

SoarSky RC Parts Buying Guide
Explore the broader accessory categories when completing your parts list, while confirming each selected receiver against the specific radio and controller manuals.

↑ Back to Contents

Additional reference retained from the original draft: original receiver-protocol discussion. Current recommendations are grounded in the linked manufacturer and firmware documentation rather than the original draft's unsupported performance comparisons.

About SoarSky: RC transmitter accessories, FPV components and hobby gear, with technical guides for practical component selection. About SoarSky.

Tags: receiver protocol, SBUS, PPM, iBus, CRSF, ELRS, FPV receiver, drone receiver, receiver buying guide, flight controller wiring

Copyright © October 2026 SoarSky. Adapted with attribution from the original discussion, with revised technical guidance. Disclosure: SoarSky sells the listed products. No buyer testimonials or measured latency tests are claimed. Product names are quoted from current store listings and do not independently establish compatibility. Seven superseded embedded infographics were replaced with corrected text and tables. Last Updated: October 2026.