Which radio controllers does the TRS TX module fit?

The TX module uses the NANO external-module bay found on compact OpenTX/EdgeTX radios such as the Radiomaster Pocket and Jumper T-Pro. Radios with the larger traditional JR module bay can use it through a JR-to-NANO adapter.

How do I bind the TRS TX module and receiver?

Hold the receiver's bind button while powering it on — the LED blinks rapidly to show binding mode. Then power on (or power-cycle) the radio with the TX module installed; the two bind automatically within a few seconds.

Do I still need a separate telemetry radio with the TRS?

No — that's the point of the system. The same encrypted 2.4 GHz LoRa/FHSS link carries both the RC control channels and a bidirectional MAVLink data stream up to 8 KB/s, so one TX module and one receiver replace the usual RC-receiver-plus-telemetry-radio pair.

Which TRS mode should I use — long-range, standard, or high-speed?

Long-range mode (2.4 KB/s data, 50 Hz RC) reaches the farthest and suits cruising aircraft and mapping. High-speed mode (8 KB/s, 150 Hz RC) gives the snappiest control feel and fastest parameter/mission transfer at reduced range. Standard sits between. The TX module's serial baud rate is tied to the mode automatically, and the receiver adopts it after re-binding.

Can I see telemetry on my phone with the TRS?

Yes — the TX module has built-in Bluetooth. Pair it with QGroundControl on an Android phone (Comm Links → Add → Bluetooth → scan for MicoAir-TRS-xxxxx) and QGC connects to the flight controller through the TRS link.

MicoAir TRS — 2.4 GHz RC + Telemetry Combo User Manual

The TRS is an integrated radio-control + telemetry communication system on a single 2.4 GHz link. It has two parts: a TX module that slots into your radio controller, and a tiny receiver on the aircraft that outputs SBUS for control and a serial telemetry port for MAVLink. One encrypted LoRa/FHSS link carries your stick inputs and your Mission Planner/QGC data — at the same time, in both directions.

MicoAir TRS TX module and receiver — 2.4 GHz RC and telemetry combo

Where to buy

Available from Robofusion: robofusion.net

New to this? Why "RC + telemetry in one" matters

A conventional long-range build carries two independent radio links: an RC system (say, ELRS) for control, and a separate telemetry radio (like the LR900 or LR24) for ground-station data. That's two receivers to mount, two antennas to place, two frequency plans to keep from fighting each other.

The TRS folds both jobs into one link:

TRS system overview — one 2.4 GHz link carrying RC control and telemetry

The TX module rides in your radio's external module bay and talks to the aircraft.
The receiver outputs SBUS (the RC protocol virtually every flight controller accepts) to the FC's RC-in, and a telemetry serial stream to a TELEM port.
Your ground station connects through the TX module — including wirelessly from a phone over built-in Bluetooth.

One link also means no 2.4 GHz self-interference problem — the usual warning against putting a 2.4 GHz RC receiver next to a 2.4 GHz telemetry radio doesn't apply, because control and telemetry share the same coordinated FHSS transmission.

Key specifications

Link

Item	Specification
Band	2.4 GHz
Technology	LoRa spread spectrum + encrypted FHSS hopping
TX module power	up to 30 dBm (1000 mW)
Receiver power	up to 27 dBm (500 mW), self-adaptive
Range	10–15 km effective in open, interference-free conditions (farther with a high-gain directional antenna on the TX module); 3–5 km with light interference, unobstructed
Telemetry throughput	up to 8 KB/s bidirectional
RC update rate	up to 150 Hz
RC output protocol	SBUS

Compatibility

TX module bay: NANO — fits compact OpenTX/EdgeTX radios (Radiomaster Pocket, Jumper T-Pro, etc.); traditional JR-bay radios via a JR→NANO adapter.
Flight controllers: anything that speaks SBUS + MAVLink serial telemetry — ArduPilot and PX4 included.
Ground stations: Mission Planner / QGC on the bench via the TX module; QGroundControl on Android over Bluetooth wirelessly.

Physical

	TX module	Receiver
Dimensions	76.8 × 40 × 18.7 mm	24 × 18.2 × 5.8 mm
Weight	32 g	2.5 g

TRS TX module and receiver dimensions

Work modes — range vs. responsiveness

The TRS trades range against control rate and data rate in three fixed modes:

Mode	long-range	standard	high-speed
Telemetry rate	2.4 KB/s	4 KB/s	8 KB/s
RC update rate	50 Hz	100 Hz	150 Hz
Serial baud rate	57600	57600	115200
Relative range	★★★	★★	★

How to choose:

Long-range — maximum reach; 50 Hz control is plenty for cruising wings, mappers and anything that isn't acro.
High-speed — snappiest stick feel and the fastest parameter/mission transfers, at reduced range.
Standard — the middle path.

Two things the system handles for you:

The TX module's baud rate is tied to the mode — you never set it manually.
The receiver adopts the matching telemetry baud automatically after re-binding. Example: switch the TX module to high-speed, re-bind, and the receiver's serial port is now 115200 — remember to set the flight-controller port to match (57600 in long-range/standard, 115200 in high-speed).

Binding

The receiver LED tells you everything: solid = linked, slow blink = not connected, fast blink = binding mode.

Hold the receiver's bind button and power it on — the LED blinks rapidly (binding mode).
Power on (or power-cycle) the radio with the TX module installed — the pair binds automatically within a few seconds; the receiver LED goes solid.

TX module OLED

The TX module's OLED shows the link's working state at a glance — mode, power, and connection status:

TRS TX module OLED display layout — RSSI, work mode, Tx power, SBUS status, Bluetooth LED and USB-C

Receiver wiring

TRS receiver interface and pinout

SBUS out → the flight controller's RC input.
Telemetry serial → a flight-controller TELEM/serial port — same three rules as any telemetry radio: TX↔RX crossed, common ground, matching baud rate.
Configure the FC's serial port for MAVLink as in the ArduPilot / PX4 telemetry guides, with the baud from the mode table above.

Configuration and driver

TX-module parameters are configured with MicoAssistant over USB — select the baud rate matching the module's current mode.

Windows needs the CP2102 driver first: CP2102 Driver Installation (Windows).
Android needs no driver.

Connect QGroundControl on Android over Bluetooth

The TX module's built-in Bluetooth lets an Android phone running QGC become your wireless ground station — no cable to the radio.

Open the QGC app → Application Settings → Comm Links → Add.
Set the connection Type to Bluetooth.
Scroll down, tap Scan with the phone near the radio — the TX module appears as MicoAir-TRS-xxxxx. Select it and tap OK.
Back in Comm Links, select the new Bluetooth link and tap Connect. After a few seconds the TX module's Bluetooth indicator turns solid.
Return to the QGC main view — the app connects to the flight controller and loads its parameters (provided the TX module and receiver are bound, and the receiver's telemetry port is wired and configured on the FC).

FAQ

Which radios does the TX module fit?

Compact OpenTX/EdgeTX radios with a NANO module bay (Radiomaster Pocket, Jumper T-Pro and similar) directly; JR-bay radios via a JR→NANO adapter.

Do I still need an LR900 or LR24 with this?

No — telemetry is built into the link. Choose the TRS when you want one radio system for both jobs; choose a dedicated telemetry radio when your RC link is already decided or the ground side isn't a hand-held radio (e.g. RTK, fixed ground stations).

The receiver LED blinks slowly and won't connect

Slow blink = not linked. Re-bind (button + power on the receiver, then power-cycle the radio), check both ends are powered, and check the TX module is seated in the bay.

No telemetry in the ground station, but RC works

RC and telemetry share the link, so if sticks work the RF side is fine — the issue is on the wire: check the receiver's telemetry serial is wired crossed to the FC port, the FC port is set to MAVLink at the mode's baud rate (57600 or 115200), and you re-bound after any mode change so the receiver's baud followed.

Can iOS QGC connect over Bluetooth?

Bluetooth GCS connection is currently supported with QGroundControl on Android.

Written and maintained by the Robofusion engineering team.

Where to buy​

New to this? Why "RC + telemetry in one" matters​

Key specifications​

Work modes — range vs. responsiveness​

Binding​

TX module OLED​

Receiver wiring​

Configuration and driver​

Connect QGroundControl on Android over Bluetooth​

FAQ​

Which radios does the TX module fit?​

Do I still need an LR900 or LR24 with this?​

The receiver LED blinks slowly and won't connect​

No telemetry in the ground station, but RC works​

Can iOS QGC connect over Bluetooth?​

Related guides​