FrSky ACCESS vs TWIN vs Tandem Receivers Explained

FrSky offers several receiver ecosystems which can be confusing at first glance. Terms such as ACCESS, TWIN, and Tandem describe how the receiver communicates with the transmitter, what kind of RF path is used, and how redundancy is implemented.

This guide explains what each system is, what problems each one is intended to solve, how FrSky redundancy switching works, and how these receivers are commonly used in RC helicopters and other aircraft.

FrSky Receiver Naming Guide

FrSky receiver model names usually indicate which RF system they belong to. Understanding the naming pattern makes it much easier to identify what a receiver actually is before buying or installing it.

Example Receiver Names

ACCESS vs TWIN vs Tandem

For most normal line-of-sight flying, ACCESS is already more than sufficient. TWIN and Tandem are typically chosen when additional RF redundancy is desired.

RF Architecture: ACCESS vs TWIN vs Tandem

FrSky receiver families differ primarily in how the radio link between the transmitter and receiver is structured. The diagrams below illustrate the RF paths used by each system.

ACCESS (Single 2.4GHz RF Link)

ACCESS uses a single high reliability 2.4GHz control link. This is the most common configuration used in helicopters and aircraft flying within normal line-of-sight distances.

TWIN (Dual 2.4GHz Redundant Links)

TWIN receivers use two independent RF links on the 2.4GHz band using different modulation systems. The receiver continuously evaluates signal quality and can switch between links if necessary.

Tandem (Dual Band RF Redundancy)

Tandem receivers use two completely separate RF bands operating simultaneously. The 2.4GHz link provides fast control response while the 900MHz LoRa link provides a longer range redundant path.

Where Do These Systems Fit?

In most hobby RC flying, a standard 2.4GHz control link is already very reliable. However, some installations create more challenging RF conditions:

• Carbon fiber fuselages and frames
• Large aircraft with more internal structure
• Scale models with enclosed fuselages
• High value aircraft where added redundancy is desired
• Longer distance or more difficult RF environments

FrSky redundancy systems attempt to provide multiple RF paths so the aircraft remains controllable even if one signal path becomes weak or degraded.

How FrSky Redundancy Works

Redundant FrSky systems continuously monitor multiple signal quality metrics to determine which RF link should be used for control.

• RSSI – Received signal strength
• VFR – Valid frame rate
• SNR – Signal-to-noise ratio

What Is VFR?

VFR stands for Valid Frame Rate. It indicates how many control frames are arriving correctly and are still usable by the receiver.

This is important because raw signal strength alone does not tell the whole story. A signal can appear strong but still be noisy, corrupted, or inconsistent. VFR is often a better indicator of actual control link health.

Typical Switching Logic

In simple terms, FrSky redundancy is not just looking at signal strength. It is looking at whether the receiver is still getting clean, valid control frames.

Where Redundancy Really Matters

For many pilots flying smaller aircraft or helicopters within normal visual line of sight, redundancy systems may not provide a major practical benefit.

Redundancy becomes more relevant in cases such as:

• Expensive scale helicopters
• Large turbine jets or large fixed wing aircraft
• Carbon fiber or enclosed fuselage models
• Aircraft where RF shadowing is a greater concern
• High value aircraft where an additional safety layer is desired

900MHz Tandem Interference With Servos

One issue occasionally reported with Tandem systems is servo jitter or erratic behavior when the 900MHz RF link is active. This is usually not a receiver protocol problem. It is more often caused by RF energy coupling into older or poorly shielded servo electronics.

Most modern servos are designed with better filtering and shielding. Some older analog servos and early digital servos were never really designed around having a relatively strong nearby 900MHz transmitter in the installation.

Why 900MHz Is More Likely To Cause This

Lower frequencies such as 900MHz have longer wavelengths than 2.4GHz signals. In practice, that means common wiring lengths and PCB traces can more easily pick up RF energy.

• Long servo leads can act like antennas
• Poorly filtered servo electronics are more susceptible
• Unshielded PCB traces can pick up RF noise
• Carbon structures can complicate RF behavior inside the model

If enough RF energy gets into the servo electronics, the result can be:

• Servo twitching
• Buzzing at idle
• Random movement

Common Situations Where This Happens

• Older analog servos
• Budget digital servos with minimal filtering
• Servos mounted very close to the receiver or antennas
• Tightly bundled servo and antenna routing
• Carbon or enclosed fuselage installations

Ways To Reduce or Eliminate Interference

• Increase physical distance between the receiver / antennas and servo electronics
• Lower 900MHz telemetry power when possible, such as using 25mW
• Avoid routing antennas along servo leads
• Add ferrite chokes to susceptible servo leads
• Use newer digital servos with better filtering and shielding
• Reposition antennas away from dense wire bundles and sensitive electronics

In most installations this problem does not occur, but it is a real consideration when using Tandem in tightly packed models with older electronics.

Receiver Output Styles

Serial Receivers

Many modern FrSky receivers used with flight controllers output digital serial protocols such as:

• SBUS
• F.PORT
• FBUS

These are commonly used in helicopters because the flight controller only needs a single serial control connection from the receiver.

PWM Receivers

Traditional receivers provide individual PWM servo outputs for each channel. These are more common in conventional airplanes and other installations where servos plug directly into the receiver.

Hybrid / Multi-Function Receivers

Some larger FrSky receivers can support both traditional output styles and bus-oriented setups depending on the model and configuration. On certain receivers, individual output pins can be reassigned for telemetry or bus functions instead of only acting as conventional PWM outputs.

FBUS Device Topology

FBUS is FrSky’s digital bus system that allows control and telemetry devices to share a common data path instead of requiring separate PWM outputs and separate telemetry wiring.

In applications that support direct FBUS device connections, servos and sensors can be assigned and managed on the shared bus.

Traditional PWM + Separate Telemetry Wiring

Receiver
├── CH1 → Servo
├── CH2 → Servo
├── CH3 → Servo
├── CH4 → Servo
└── S.Port / Telemetry Port → Sensor

Traditional receiver wiring uses one output per servo channel plus a separate telemetry path for sensors.

Direct FBUS Shared Bus Concept

Receiver FBUS Port
│
├── FBUS Servo (Channel ID 1)
├── FBUS Servo (Channel ID 2)
├── FBUS Servo (Channel ID 3)
├── Telemetry Sensor (Application ID)
└── Additional FBUS Devices

On supported receivers, multiple compatible devices can share the same FBUS connection. Each device uses internal identifiers so it knows what data belongs to it.

How Devices Are Identified on FBUS

In simple terms, Channel ID tells a device what control signal to listen to, while Application ID tells the radio what kind of telemetry data is being reported.

FrSky Receivers for RC Helicopters

Most modern RC helicopters use a flybarless controller or flight controller. In these systems, the receiver usually only needs to provide a serial control link such as FBUS, F.PORT, or SBUS.

That means helicopter installations usually do not need a large PWM receiver unless there is a special application requiring direct receiver outputs.

This is why small serial receivers are so common in helicopters.

Example: Archer Plus RS Mini

The Archer Plus RS Mini is one of the most common receivers for small RC helicopters in the 100/200 class.

Its compact size and simple wiring make it ideal for helicopters where space and weight are limited.

For small helicopters with short installation distances, a single antenna is usually sufficient and simplifies mounting inside compact frames.

Example: Archer Plus RS

The Archer Plus RS is commonly used in larger RC helicopter installations such as 380 class and above where additional antenna diversity and installation flexibility are desired.

It uses dual external full-size antennas which can be mounted in different orientations to improve signal coverage inside carbon fiber frames.

For helicopters using modern flybarless systems or flight controllers, the Archer Plus RS provides a reliable serial receiver connection while allowing flexible antenna placement for improved RF performance.

Archer Plus RS Mini vs Archer Plus RS

Both the Archer Plus RS Mini and Archer Plus RS are ACCESS receivers commonly used in RC helicopters. They support the same serial receiver protocols such as SBUS, F.PORT, and FBUS, making them compatible with modern helicopter flight controllers.

For most micro helicopters where space is extremely limited, the RS Mini is usually the preferred option. For larger helicopters with carbon fiber frames, the Archer Plus RS allows dual antennas to be placed in different orientations which can improve RF reliability.

Redundant Receiver Options for Helicopters

For most RC helicopters using a flight controller, a simple serial receiver such as the Archer Plus RS Mini or Archer Plus RS is sufficient.

However, some helicopter installations benefit from additional RF redundancy. This is most common in:

• Large scale helicopters
• Enclosed scale fuselages
• Carbon fiber fuselage shells
• High value aircraft

In these cases, FrSky redundant receiver options may be used.

These receivers are alternative options where additional redundancy is required, such as expensive scale helicopters with enclosed fuselages.

FBUS in RC Helicopter Systems

FBUS is a digital communication protocol designed to carry receiver control signals and telemetry over a single connection, with the ability to support additional devices such as servos and sensors.

While FBUS is capable of supporting shared device buses, most helicopter flybarless systems currently use FBUS only as a receiver and telemetry communication link between the receiver and the flight controller.

Current Helicopter Implementation

In modern RC helicopters, the receiver sends control commands to the flight controller over a serial connection such as FBUS. The flight controller then handles all servo outputs and stabilization functions.

Transmitter
    ↓
FrSky Receiver
    ↓  FBUS (Receiver + Telemetry Link)
Flight Controller / FBL Unit
    ├── Cyclic Servo 1
    ├── Cyclic Servo 2
    ├── Cyclic Servo 3
    ├── Tail Servo
    ├── ESC
    └── Sensors / Telemetry

In this configuration, the receiver sends control commands to the flight controller over the FBUS link, while telemetry from the flight controller and sensors is returned to the transmitter through the same connection.

Future FBUS Capabilities

FBUS was designed with the ability to support shared digital device buses where servos and sensors communicate directly using device identifiers. While this capability exists in the protocol design, it is not widely used in helicopter flybarless systems today.

Future flight controller designs may expose FBUS connections across servo and sensor ports. For example, the Rotorflight project has discussed potential future flybarless systems that could support FBUS communication across all device connections.

Future Concept (Not Common Today)

Receiver FBUS Port
│
├── FBUS Servo
├── FBUS Servo
├── FBUS Servo
├── FBUS Sensor
└── Additional Devices

© New England RC — Independent technical resources and support guides for RC helicopters, radios, and electronics.