LockDownRadioControl has three parts you can build. To fly, you need a transmitter and a receiver. The dongle is for pilots who keep the radio they have.
The transmitter
Two sticks, eight switches, a 5-inch touchscreen and the radio. This is Version 2.
Cost: over £120 in parts (approximate; the full total is being worked out)
Time: a day, but an intense one: Malcolm advises at least two
Skills: soldering, crimping and 3D printing. No programming: the software goes in from a web page and a free loader
A soldering iron with a fine tip, solder and flux.
A multimeter. You will use it to check every power lead before you plug it in.
Wire strippers, side cutters and heat-shrink sleeve.
A crimp tool for DuPont connectors, or ready-made DuPont leads.
A magnifier, to check small joints.
A 3D printer, or a printing service, for the transmitter's case.
A computer (Mac, Windows or Linux) with Chrome or Edge.
Software: nothing to compile. The screen and the receiver are flashed from a web page; the Teensy with PJRC's free Teensy Loader. Some computers also need the CH340 USB driver for the screen.
Data cables: USB-C for the screen and the receiver, micro-USB for the Teensy. Many cables only charge. Use ones that carry data.
Is it for you?
Buy a shop radio if you want one that works out of the box, with a warranty and dealer support.
Build LockDownRadioControl if you enjoy making things, and want to set up and tune Rotorflight helicopters from the transmitter or your phone. It also loads the right model memory by itself when you switch the model on. That is rare: elsewhere we found it only on Multiplex's SMART SX and Mikado's VBar Control.
And it is yours to change. Its author often adds a feature within a day of a pilot asking, and everything is open, so you can change it yourself. A shop radio is almost always take it or leave it.
Enough radio for almost all model flying. Some radios offer more range and more channels. LockDownRadioControl's 16 channels and about 2 km of range are more than enough for almost all model flying.
No programming needed. The screen and the receiver are flashed from a web page, the Teensy with a free loader. After that, everything updates itself over WiFi.
Version 2 arrived in October 2026 and still gains features most weeks. The radio link itself has flown since 2020.
Before you start: the law and safety
Radio rules
The radio modules that do the transmitting and receiving carry the CE mark and FCC ID 2ALPH-E01: Ebyte's E01-ML01DP5 in the transmitter and E01-ML01SP4 in the receiver.
They run at about 100 mW (20 dBm), the UK and EU limit for 2.4 GHz. An aerial cannot add power: it only shapes where the signal goes.
As with any model you build yourself, check the radio rules where you live before you fly.
Safety: blades off
Take the rotor blades or the propeller off for every test on this page. Unplug the motor too, unless the test needs it. A spinning rotor can cause serious injury.
Safety: the battery
Charge the 2S pack with a balance charger made for its type. A LiFePO4 pack needs a LiFePO4 charger (3.6 V a cell). A LiPo or Li-ion charger (4.2 V a cell) overcharges it.
With the charger in the transmitter (LiPo or Li-ion packs only): plug it into any 5 V USB outlet, a wall plug or a computer. The red light goes out when it is charged. You may use the transmitter while it charges, and watch the voltage on its front page.
For a longer battery life, do not always charge it full: stop once it is over 4 V a cell. And do not run it below about 3.75 V a cell.
Never leave it charging unattended.
If it swells or gets hot, stop charging it and stop using it.
Fitting the charger board in the case? It must be set for two cells. The LX-LISC-V3 board comes that way: change nothing on it. The Chinese words printed on it say how to make it charge three cells: do not.
Three of Malcolm's transmitters charging. Each red light goes out when its pack is charged.
No warranty
LockDownRadioControl is free software and open hardware. It comes with no warranty. You build it and fly it at your own risk.
The transmitter
The Version 2 transmitter has a Teensy 4.1 main board, an Ebyte radio module, two FrSky Hall-sensor sticks, eight switches, and a 5-inch touchscreen (Elecrow's 5-inch IPS panel).
The Teensy flies the model: sticks, mixing and the radio link.
The screen talks to you: the pages, WiFi, Bluetooth, sound and updates.
Already have a Version 1 transmitter?
It becomes a Version 2 when you swap its Nextion screen for the new 5-inch screen and flash the Version 2 firmware.
Your models, main board, sticks and switches stay.
Print the Version 2 case front: it holds the new screen. Your Version 1 case back stays: fill its old charger hole with epoxy resin.
To flash the Teensy, use a USB lead with its red (5 V) wire cut, and power the transmitter from its battery. Or lift the Teensy out of its socket.
Keep your Teensy's own card. It holds your models. Copy it to a computer first. Then add the example's help and Images folders to it. Do not replace MODELS.DAT or mod.
It can be built in a day, but it is an intense day: take at least two.
Start the 3D printer on all the case parts first.
While it prints, solder everything to the main board. Use sockets (female DuPont headers) for any module you might want to swap, such as the Teensy.
Take a break.
Flash the Teensy and the screen.
Begin the assembly. The screen goes in first.
Parts list
Prices are approximate, for parts only, in pounds, in October 2026. A dash means we have no reliable price yet.
Buy the right screen
Buy the 16 MB screen: Elecrow's 5-inch IPS panel, SKU DLE06050B (ESP32-S3 N16R8: 16 MB flash, 8 MB PSRAM). New features need it. The older CrowPanel 5.0" ESP32 HMI, SKU DIS07050H, N4R8 (4 MB flash) is full: since November 2026 it gets fixes only, no new features. Do not buy it for a new transmitter. The firmware tells them apart at start-up; print the case front for the one you have. Already on the 4 MB screen? Moving a transmitter to the 16 MB one takes Malcolm about 3 hours (it needs the 16 MB case front). Not Elecrow's newer "Advance" series: its card slot and speaker are on other pins, so the display would light up but the screen would find no card.
Easy to miss: the INA219
Older parts lists left out the INA219 voltage sensor. Without it, the transmitter cannot read its own battery.
Part
Exact type
How many
What it is for
Where to buy
About
The main board
Circuit board
2 layers, about 83 × 91 mm, from the Gerber files
1
Carries everything else
A PCB maker (Malcolm uses JLCPCB)
–
Teensy 4.1
PJRC Teensy 4.1 (600 MHz)
1
The transmitter's computer: reads the sticks, runs the radio link
PJRC, The Pi Hut, Cool Components
£30
Radio module
Ebyte E01-ML01DP5 (nRF24L01+ with amplifier). Its aerial socket is SMA
1
The 2.4 GHz radio. It needs a capacitor across its power and ground pins (below)
Ebyte's own shops
–
Voltage sensor
INA219 breakout module, I2C address 0x40. Malcolm has used the purple GY-219 and the blue "INA219 DC Current Sensor" board: either works, its A0 and A1 pads left open
1
Measures the transmitter's battery
Adafruit, SparkFun, or a compatible module
£5
Clock
"Tiny RTC" DS1307 module with its coin cell (Malcolm's is marked HW-111)
1
Date and time for the logs. The screen sets it from the internet
Electronics shops
–
Power switch
Pololu 2808 pushbutton power switch
1
Switches the transmitter on and off. Lets the Teensy switch itself off
Pololu, or a reseller
£5
5 V regulator, Teensy
Pololu S13V10F5 (5 V, 1 A, step-up/step-down); the 2 A S13V20F5 fits too. 1 A is plenty: what matters is the step-up/step-down
1
The Teensy's 5 V. It holds 5 V even when the pack runs low, so the radio link keeps flying the model if the screen drops out first
Pololu
–
5 V regulator, screen
7805
1
The screen's 5 V. No heatsink needed
Any electronics shop
–
3.3 V regulator
AMS1117-3.3
1
3.3 V for the radio, the sticks and the sensors
Any electronics shop
–
Diodes
1N5406 × 2, 1N4001 × 2
4
Protect the regulators and the power button's circuit
Any electronics shop
–
Capacitors
Electrolytic: 330 µF, 100 µF, and one for the radio module (Malcolm uses 220 µF; the value is not critical). Tantalum: 330 µF (0E907) × 2, 47 µF (1206) × 2. Ceramic, 1206: 330 nF × 2, 100 nF × 4, 10 µF × 1
14
Keep the supplies smooth
Any electronics shop
–
The screen
Touchscreen
New transmitter: Elecrow 5-inch IPS panel, DLE06050B (ESP32-S3 N16R8, 16 MB flash, 8 MB PSRAM, 800 × 480). Not the 4 MB CrowPanel 5.0 (DIS07050H): fixes only, no new features
1
The pages, WiFi, Bluetooth, sound and updates
Elecrow, RobotShop
£40–£43
microSD card for the screen
Any size, formatted FAT32
1
Pages, fonts, sounds and pictures. The screen fills it itself
Anywhere
–
Speaker
Nextion's Box Speaker (2 W), the one that comes with a Nextion display. Its 2-pin plug (1.25 mm) fits the 16 MB screen's SPK socket. Any 8 Ω, 1–2 W speaker works too; a 4 Ω one is louder
1
Voice and sounds. Plugs into the screen's SPK port (the older 4 MB CrowPanel's is a 2 mm PH2.0 socket)
Nextion dealers, electronics shops
–
Screen data lead
HY2.0 4-pin lead ("Grove" style)
1
Joins the screen's UART0 port to the main board
Electronics shops
–
Screen power lead
A short USB-C lead, its far end cut off
1
Takes 5 V from the main board into the screen's USB-C socket
Anywhere
–
Sticks, switches and lights
Sticks
FrSky M9 Hall-sensor gimbals
2
The two sticks
FrSky dealers, model shops
£40–£60 a pair
Trims
FrSky trim switches (X9D Plus spare part)
4
Digital trims beside the sticks
Model shops
–
Top-edge switches
Three-position switches made for RC transmitters, with a long lever. Single pole, three tags; the middle position connects nothing (ON-OFF-ON). Several brands make them
4
Safety, banks, rates and more: you choose each one's job
Model shops (spare transmitter switches)
–
Front switches or knobs
The same three-position switches (each with two equal resistors, below), or 10 kΩ linear knobs (potentiometers, often marked B10K)
4
Channels 5 to 8, or any job
Model shops, electronics shops
–
Power button
16 mm vandal-resistant, momentary push button
1
On and off; held at switch-on, it starts binding
Electronics shops
–
Status light
KY-016 RGB LED module: a 5 mm common-cathode RGB LED on a small board, its resistors already fitted. Its pins are marked R, G, B and −
1
Red: trying to connect. Green: connected. Blue: busy
Online: search for KY-016
–
Power and aerial
Battery
2S pack (two cells): LiPo or Li-ion. LiFePO4 can be used, but Malcolm does not recommend it, and the built-in charger is not for it. Malcolm uses RadioMaster's 2S Li-ion 21700 pack, 5000 mAh; their 6200 mAh pack fits too. Give its main lead a 3-pin DuPont female plug: + in the middle, − on both sides, so it cannot go on the wrong way round
1
Powers the transmitter
Model shops
–
Charger Optional
A small USB-C charger board on the IP2326 chip, such as the LX-LISC-V3 (its name is on the back), and a red LED for its charge light. It sits in the charger bay on the back. The LX-LISC-V3 comes set for two cells: change nothing. For LiPo or Li-ion packs: a LiFePO4 pack needs a LiFePO4 charger
1
Charges the pack inside the case. Must match the battery type: LiPo/Li-ion or LiFePO4
Electronics shops
–
Aerial
2.4 GHz aerial with an SMA plug (a pin in the middle), and a 20 cm SMA male-to-female extension. Not RP-SMA
1
Brings the aerial outside the case. Most WiFi aerials are RP-SMA: they screw on, but do not connect
Electronics shops
–
Cards, wiring and case
microSD card for the Teensy
Any size, FAT32 or exFAT
1
Models, logs and the help texts
Anywhere
–
Connectors
Male and female headers, three-row headers, a 2×4 socket (for the radio), servo cable, DuPont 3- and 4-pin connectors
Various
Join the controls to the board
Electronics shops
–
Case
3D-printed, in PETG or similar
1 set
Holds everything
Print it yourself
–
Fixings
Tiny flange-head self-tapping screws (photo below): they hold the screen, the charger board and the case back, so buy plenty. M3 bolts with locknuts, 2 mm cable ties, five-minute epoxy
Various
Hold the case and the parts together
Hardware shops
–
Total
Parts only, approximate. Prices change. The priced parts alone come to about £120–£143. The full total is being worked out.
Over £120
The main board
Version 2 uses the same main board as Version 1. Its Gerber files (the files a PCB maker needs) are in the repository. They are the board Malcolm builds today, and none of its parts is obsolete.
Download the repository
On GitHub, press Code, then Download ZIP. Unzip it.
Zip the Gerber files
Open the folder TXV2/Circuits/Transmitter - CADCAM. Put every file in it into one zip file.
Order the boards
Upload the zip to a PCB maker. Choose 2 layers and 1.6 mm thickness. The board is about 83 × 91 mm.
Makers usually sell at least five boards. Share the spares with friends.
Or ask Malcolm: he has spare boards for the transmitter and the receiver. If you live close enough, he can give you one or two, or perhaps post them. Email Malcolm.
Check: the maker's preview looks like the picture below.
The top of the main board, drawn from its Gerber files. Every connector has its name printed beside it.The underside.
The board's design is a Proteus project (TXV2/Circuits/TransmitterMay24.pdsprj), under the CERN-OHL-S-2.0 licence. See the Gerber files on GitHub.
Optional: ready for an ELRS module
The transmitter can also carry an ExpressLRS (ELRS) transmitter module inside its case, to fly models that have an ELRS receiver as well as your LDRC models: for example a helicopter on a RadioMaster Nexus-XR, which has Rotorflight and an ELRS receiver built in. This is being tested now. It is not in the released firmware yet, and LDRC flying is unchanged.
If you may want ELRS one day, make this small change to the main board before you build it in. It is much easier now than later. The released firmware does not use the TX_MODULE header, so a board changed like this flies LDRC exactly as before.
Cut one track
On the underside, cut the track from the TX_MODULE header's SIGNAL pin to Teensy pin 6, on its long straight run (the red mark in the picture). A small burr in a rotary tool gives the neatest cut: slowly, only through the copper. Leave the wide battery track beside it alone.
Add one wire, with a 1 kΩ resistor
Solder a wire with a 1 kΩ resistor in it from Teensy pin 24 to the TX_MODULE header's SIGNAL pin. Pin 24 is on the same row as pin 6, eight pads further on. Its neighbour is the 3.3 V pad: do not mix them up.
Check with a meter: SIGNAL to pin 24 about 1 kΩ. SIGNAL to pin 6 open. SIGNAL to ground open.
The underside of the main board by the TX_MODULE header, drawn from its Gerber files: the cut, and the new wire to pin 24.
Power for the module, for now. The module must be off when you fly LDRC. Take its power from the TX_MODULE header's middle pin: the transmitter's battery, whenever the transmitter is on, so the transmitter's battery warnings cover the module too. The simplest and safest way to have it off is no switch at all: put the module in only when you fly ELRS, and take it out for LDRC. Then nothing can switch it off in flight by accident. Put it in or take it out only with the transmitter off, and make sure it cannot work loose (the printed bay below holds it with two click arms). If you fit a switch instead, switch the + side, never the ground, and place it where it cannot be knocked in flight. If the module plugs into the TX_MODULE header, use a plug that fits only one way round: turned round, ground and signal swap. Check your module's input voltage, and fit its aerial before you power it.
On the way: a MOSFET switch, so that the transmitter turns the module on and off by itself (from Teensy pin 10, on the BUDDY header). The printed bay below already has a place for its small board. Later, a new version of the main board with all of this built in.
The printed parts for the module. Malcolm's module, a RadioMaster Ranger Nano, sits in a new case back. One set of parts, in TXV2/STL files/V2/ELRS (STEP files to edit or print, STL files to print):
A new case back, BACK_ELRS_HIGH. Print it instead of the Version 2 back: only its opening differs, longer and higher. The module's aerial goes up through the standard handle, and its tip stands above the top of the transmitter.
The module and charger bay, ELRS_CHARGER_BAY_CLICK_SWITCHBOARD. One part, glued into the back from the inside with five-minute epoxy, like the Version 2 charger bay. The charger board sits at the bottom, as before. The module slides in from the top, under two straps, onto a strip of pins, and clicks in: two springy arms with a tooth each snap over its shoulders. To take it out, spread the tops of the two arms and slide it up. Inside the case the bay has a place for the small power switch board, held by two M3 x 8 screws. Print ELRS_CHARGER_BAY_CLICK_SWITCHBOARD_PRINT.stl as it lies, in PETG, supports off. Afterwards snap out the loose prop under the charger's two risers, and snip off the four tiny posts under the arms.
A jig, PIN_STRIP_JIG, that holds the pin strip while its glue sets (below).
A dummy module, ELRS_MODULE_DUMMY. It clicks in like the module and covers the pins whenever the module is out.
A storage box and its lid, ELRS_MODULE_CASE and ELRS_MODULE_CASE_LID, for the module with its aerial on.
The new back with the module and charger bay, drawn from the design files. Two things in the picture have changed. It shows the first bay, which held the module with two screws: the bay now holds it with two click arms. And it shows a taller handle: that proved unnecessary, and the standard handle is used.
The pins. The module plugs onto an 8-way 2.54 mm turned-pin strip: round pins, because the module's sockets do not take square DuPont pins. Only three are wired. The module's sockets 1, 2 and 3 are SIGNAL, GROUND and BATTERY, from the left, looking at the module's back with its aerial up. Check yours before you glue. The module's own XT30 power socket then stays empty.
The jig. Holding the strip still while its glue sets is very hard by hand. The jig holds it for you. Malcolm's way, from experience:
Put the strip in the comb, its fat brass collars against the comb and its long thin pins pointing up. The wires go through the window.
Put sticky tape over the window at the back, so that glue cannot run through it.
Rub a little candle wax or grease on the jig's nose, so that the glue cannot hold it.
Slide the jig in from the top end, like the module, until it stops. The pins lie in its slots and touch nothing. A spring tab under the upper strap holds the strip down on its pad and back against the comb.
Very carefully, put one drop of thin superglue where the strip meets the comb. It runs: keep it well away from the pins.
When the superglue has set, press the tab and slide the jig out.
Then reinforce the joint with a generous amount of five-minute epoxy, over the comb and the wires. Be extremely careful not to get any on the pins or their connections.
Never glue the strip with the module in place: glue must not reach the module. Print the jig on its side, supports off. It weighs about 8 g.
The jig: how it holds the strip, in place in the bay, and how it prints.
Printing the case
The printed parts, drawn from their design files.
The Version 2 parts are in TXV2/STL files/V2: two case fronts, one for each screen (TXV12_FRONT_16m_V2.step for the 16 MB IPS panel, TXV12a_Front_4meg_V2.step for the 4 MB CrowPanel: their dimensions differ slightly), the case back TXV12a_BACK_V2.step (STEP files: most slicers open them directly), and the charger bay CHARGERBAY.stl, which takes the place of Version 1's JR module bay on the back and holds the USB-C charger module.
The other parts are in TXV2/STL files: handle, inner support plate, gimbal protectors, LED mount and a spacer. (The module bay and its blank cover are Version 1's: a Version 2 prints the charger bay there instead.) STEP files for editing are in STL files/STEP files.
Print in PETG or a similar tough plastic. The settings are not critical: Malcolm uses 0.16 mm layers and the slicer's default infill.
The screen has no mounting holes. Four tiny self-tapping screws hold it in the Version 2 case front. The same screws hold the charger board and the case back: buy plenty.
RX.stl and RX_LID.stl in that folder are the Version 1 receiver's case. The Version 2 receiver has no case yet: Malcolm covers it in clear heat-shrink, because it is tiny.
One of the tiny self-tapping screws, on a centimetre grid.The case back, the charger in its bay.
Flashing the screen and the Teensy
Do this on the bench, before anything is wired in. The screen's USB-C socket will later carry its power, and the Teensy is easiest to flash on its own.
There is nothing to compile. The screen is flashed from a web page, the Teensy with a free loader. After this, updates come over WiFi, and you should not need the cables again.
Get the two tools
About 5 minutes
For the screen: Chrome or Edge on a desktop or laptop. Nothing to install.
For the Teensy: PJRC's free Teensy Loader (Mac, Windows or Linux), and the firmware file ldrc-v2-teensy41.hex. That link always gives the latest release.
Rather build it from the source?
Install PlatformIO and get the code. Then these commands do the work of steps 5 and 7:
git clone https://github.com/Mmessiter/LDRC_V2.git
cd LDRC_V2/TXV2-Screen
pio run -e ips16 -t upload --upload-port /dev/cu.usbserial-XXXX
cd ../TXV2/TransmitterCode
pio run -e teensy41 -t upload
ips16 is the 16 MB screen. The older 4 MB CrowPanel takes crowpanel50. pio device list names the screen's port; on Windows it looks like COM3. All of these build from a fresh copy of the repository (checked 10 November 2026).
Flash the screen, in your browser
About 5 minutes
Put a blank microSD card, formatted FAT32, in the screen's slot before you power it. The screen only looks for its card when it starts. Cards over 32 GB come as exFAT: reformat them.
Plug the screen into your computer with a USB-C data cable. Open this page in Chrome or Edge and press its one button:
The page finds out which screen it is (16 MB or 4 MB) and writes the right firmware in about a minute. No buttons to press on the screen: it resets itself.
No screen in the browser's list? Try another cable: many carry power only. The screen's USB chip is a CH340, and your computer may need its driver.
Check: the page says it has finished, and the screen restarts.
The first line on the glass:LDRC V2 screen sd=1 pages=0 touch=1 is a healthy fresh screen (no pages yet: the first fetch brings them). With sd=0, the line under it (Card: ...) says what the screen found on the card and what to do. touch=0: the touch chip did not answer.
Give the screen WiFi and let it fill its card
About 15 minutes; about half an hour on the older 4 MB screen
The new screen says No WiFi yet. Tap WiFi setup. Choose your network and type its password on the screen's keyboard.
The screen then fetches the latest release from messiter.com by itself: about 430 files (about 230 MB), most of them the help animations. If it asks first, tap Install now. Then it restarts as a complete screen.
The screen's WiFi is 2.4 GHz only.
An iPhone hotspot works if you switch on Maximise Compatibility.
The password stays in the screen's chip. It is never written to the card.
No panel on the glass? Hold the top-right corner of the screen for three seconds: the WiFi page opens.
The WiFi page. Up to eight networks are remembered.
Check: the screen fills its card and restarts by itself. The first line then counts its pages (pages=90 or so, no longer 0). Until the Teensy is wired in, that line is all it shows.
Flash the Teensy, on its own
About 5 minutes
Plug the Teensy 4.1 into your computer with a micro-USB data cable. Keep it out of the main board for now.
Teensy already in the board?
Never power the transmitter from the Teensy's USB. Use a USB lead with its red wire (the 5 V wire) cut, and power the transmitter from its own battery. Or lift the Teensy out of its socket and flash it on its own.
Open Teensy Loader.
Choose File, then Open HEX File, and pick ldrc-v2-teensy41.hex from step 4.
Press the small white button on the Teensy.
In the loader, press Program, then Reboot. With its Auto button on, it does both by itself.
On Linux, install PJRC's udev rules first (the Teensy Loader page has them).
Check: Teensy Loader says Reboot OK.
Prepare the Teensy's card
Version 1 owner? Skip this step. Keep your own card.
Format a microSD card as FAT32 or exFAT. From the repository you unzipped in step 1, copy everything inside TXV2/TransmitterCode/SD Examples/Teensy SD Example onto it: the folders help, Images and mod, and the file MODELS.DAT. Then make an empty folder called log.
The example models are Malcolm's. Step 21 (Reset transmitter) clears them from the model memories. Their backup files stay in the mod folder, if you want to look at them.
A blank card works too: the transmitter makes its own MODELS.DAT. You then start with nothing, so calibrate the sticks and set up each model yourself. The example card saves that work and brings the help texts.
Check: the card's top level shows help, Images, log, mod and MODELS.DAT.
Assembly
Note
The board's printed labels name every connector. Take your time, and check each joint with a magnifier.
Inside one of Malcolm's transmitters, the screen lifted out. Tap to enlarge.
Solder the small parts
Do the surface-mount (SMD) parts first. After that the order is up to you.
Fit the diodes, the capacitors, the 3.3 V regulator (AMS1117) and the two 5 V regulators. The regulator marked 7805 feeds the Teensy. The one marked NEXTION feeds the screen.
Watch which way round the diodes and the electrolytic and tantalum capacitors go.
Check: no solder bridges between pads.
Fit the headers and sockets
Fit a socket for the Teensy, the 2×4 socket for the radio (DP1), and headers for the power switch, the INA219 and the clock. Then the three-row headers for TRIMS, EDGE SWITCHES and CHANNELS 1-8, and the headers for the LED, the button, the battery and the screen. Sockets let you swap a module later, the Teensy above all. Leave the BUDDY and TX_MODULE headers empty: Version 2 does not use them. (Made the ELRS change? Then the module may plug into TX_MODULE.)
Test the power before the modules go in
Safety: battery the right way round
Before the first switch-on, put the meter on volts across the battery's own plug. Red probe on the pin that will meet + on the board (the middle one): it must read plus 6 to 8.4 V, not minus. A battery the wrong way round can destroy the board at once.
Fit only the Pololu 2808 power switch, the power button and the battery lead (BATTERY header). Leave the Teensy, the radio and the other modules out.
Power the main board only ever from its battery, switched on by the button and the 2808: now and always.
Before the battery goes on, measure the resistance between + and − on the battery plug. It must not be close to zero.
Connect the battery and press the button. Measure:
5 V on the Teensy socket's VIN pin;
5 V on the middle pin (pin 3) of the screen header;
3.3 V on the radio socket's VCC pin (next to its GND pin).
Find pin 1 of the screen header now: battery off, meter on beep. Pin 1 is the end pin that beeps to the battery's − (in the case, the end nearer the bottom of the transmitter). Mark it.
Check: all three voltages are right. If not, switch off and find the fault before you go on.
Fit the modules
Aerial on before you switch on
Screw the aerial extension and the aerial onto the radio now. The radio transmits at full power from switch-on; with no aerial its amplifier can be damaged.
Use SMA, not RP-SMA. An RP-SMA aerial screws on, but does not connect.
First, the radio's capacitor. Solder a capacitor across the radio module's power and ground pins (VCC and GND). Malcolm uses 220 µF; the value is not critical. Its striped leg (minus) goes to GND.
The radio, its capacitor soldered across its power and ground pins.SMA: the aerial's plug has a pin in the middle (left), the radio's socket a hole (right).
Fit the Teensy (with its card), the ML01DP5 radio, the INA219 and the Tiny RTC clock. Match each one to the outline printed on the board.
The clock: connect it by its five-pin row (DS, SCL, SDA, VCC, GND), and leave its seven-pin row unconnected. On the main board only that row's holes are wired (GND, 5 V, SDA, SCL; DS is not used). On some newer modules the seven-pin row's "GND" hole is joined to the coin cell instead of ground.
The clock needs 5 V. On 3.3 V it keeps time but does not answer.
Check: nothing gets warm when you switch on.
Wire the sticks
Each stick axis has three wires: 3.3 V, GND and the signal. They go to CHANNELS 1 to 4.
Wire the sticks exactly like this, whatever mode you fly. The Stick mode setting (step 22) swaps the two up-and-down axes for Mode 2.
Mode 2? Only the springs change. The left stick's up-and-down must stay where you leave it (it is the throttle), and the right stick's must spring back to the centre. Set the gimbals up that way before you fit them.
Wire to
Stick and direction
Channel in Mode 1
CHANNELS 1 Teensy pin A0
Right stick, left and right
1 Aileron
CHANNELS 2 Teensy pin A1
Left stick, up and down
2 Elevator
CHANNELS 3 Teensy pin A2
Right stick, up and down
3 Throttle
CHANNELS 4 Teensy pin A3
Left stick, left and right
4 Rudder
Wire the trims and the switches
Trims go to the TRIMS header, trims 1 to 4 as printed. Each trim has a common and two contacts: the common to GND, the two contacts to that trim's two pins.
Top-edge switches go to the EDGE SWITCHES header, switches 1 to 4. Each switch is read as two inputs to ground: the centre tag to GND, the two outer tags to the switch's two pins.
Front switches or knobs go to CHANNELS 5 to 8. A knob (10 kΩ works well) has three wires: 3.3 V and GND on its outer tags, the signal on its middle tag.
A three-position switch on CHANNELS 5 to 8 needs two equal resistors to make its middle position: one from its middle tag to each outer tag. Then wire it as a knob: the middle tag to the signal, the outer tags to 3.3 V and GND. (The resistor in Malcolm's photo is 7.5 kΩ: violet, green, red.)
If a trim or a top-edge switch works the wrong way round, do not re-solder it. Calibration fixes it.
Wire the light, the button, the battery and the aerial
RGB LED module to the RGB LED header. GND is the header's end pin that beeps to the battery's − (meter on beep): the module's − goes there. Then R, G and B, in that order from it. Step 18 checks the colours.
Power button: already fitted in step 11.
Battery lead: already fitted in step 11.
Aerial: already on the radio from step 12. Route the extension to the case.
Charger, if you fit one: put it in the charger bay, its USB-C socket in the bay's opening. Before you tighten its two tiny screws, push a USB-C plug into the socket (a lead plugged into nothing), as in the first photo below. That lines the board up with the opening, so a plug goes in and out easily later. Then tighten the screws and pull the plug out. Its B+, BM and B− go to the pack's 3-pin balance plug through a matching JST-XH plug: B+ to the red wire, BM to the middle one, B− to the black. A red LED in the bay's wall is its charge light: its + (the long leg) through a 100 Ω resistor to the board's LED pad, its − to the board's GND pad. If it does not light while the pack charges, turn it round. Leave the LED loose until the charger bay is in the case back. In its hole it sticks out, and gets in the way as the bay goes in. Then push it into its hole. When everything is in position, fix the bay with plenty of five-minute epoxy from the inside, so none shows on the outside (second photo).
1. Tighten the two screws with a USB-C plug in the socket. The LED stays loose.2. The bay in the case back, the LED in its hole, epoxy all round from the inside.
The charger in its bay, joined to the pack's balance plug (white).The USB-C socket in the charger bay.
Before closing the case: the charger's lead plugs into the battery's balance lead (the white plug).
Wiring the screen
The screen goes where Version 1's Nextion screen went. Data goes to its UART0 port. Power goes into its USB-C socket.
The screen's data lead and power lead. Tap to enlarge.
Main board, screen header
Goes to the screen
Pin 4 (Teensy pin 1, TX1)
UART0 pin 1: RX (IO44), yellow
Pin 5 (Teensy pin 0, RX1)
UART0 pin 2: TX (IO43), white
Pin 1 (GND)
UART0 pin 4: GND, black. Also the USB-C lead's GND
Pin 3 (+5 V, the screen's regulator)
The USB-C lead's +5 V
Pin 2
Not used
–
UART0 pin 3 (3V3): leave unconnected
Pin 1 is GND: the end pin nearer the bottom of the transmitter. Then pin 2 (not used), pin 3 in the middle (5 V), and pins 4 and 5 (the Teensy's transmit and receive). Check pin 1 before you plug the screen in: battery off, meter on beep, it beeps to the battery's −. (You marked it in step 11. Version 1 owners: find it now.)
Never two power supplies
Do not plug a computer into the screen's USB-C socket while it is wired to the main board. That socket is its power input, and its UART0 port shares the USB chip. Unplug the screen leads first.
Both boards use 3.3 V logic. The link runs at 921,600 baud.
The 3V3 pins on the screen's ports are outputs. They cannot power the screen.
Wire the screen
Find the +5 V and GND wires of the cut USB-C lead with a meter: colours vary.
Wire the screen as shown above. Plug the speaker into the screen's SPK port.
Check: battery off, meter on beep: the USB-C lead's GND beeps to pin 1, its +5 V to pin 3; the screen's RX goes to pin 4, its TX to pin 5.
First power-up
On the front screen, Transmitter opens Transmitter setup and Model opens Model setup. So Transmitter → System means: press Transmitter, then System.
Check again for a short circuit
Now that everything is wired, measure the resistance between + and − on the battery plug, before the battery goes on.
Check: it is not close to zero.
Switch on
Connect the battery (the right way round, as in step 11) and press the power button. The status light turns red: it is trying to connect (no model is on). The screen starts, and the front page appears.
If the clock does not answer, the screen says so and lists the I2C addresses that did: 0x40 is the INA219, 0x68 the clock, 0x50 the clock's memory chip.
Check: the front page shows the transmitter's battery voltage. If the light is green with no model on, the red and green wires are swapped: swap them.
Bring everything up to date
Tap Transmitter → Transmitter updates. It asks messiter.com for the latest version, and installs what is newer straight away. The first time, that brings the Teensy's card its newest help texts.
Updates need the safety on and no model connected. Your switches are not set up yet: if Transmitter updates is grey, skip this step and do it after step 26.
Your models, settings and logs are copied to the screen's card first.
If new firmware would read your models differently, the old firmware comes back by itself.
It fetches the update and says how long is left.Done. It says what changed.
Check: the screen says Update complete, or that you already have the latest version.
Close the case
Only now close the case. Fit the screen in the case front, then the sticks, switches, trims, LED (in its printed mount), button and aerial. Run the wires through the case's cable guides and hold them with a few cable ties. They need not be tidy: Malcolm's often are not, and with the back on it always looks tidy anyway. What matters is that every wire goes to the right place, and that none can catch a gimbal or stop the back closing.
The leads through a cable guide (left), held by a cable tie, and along the wall behind the battery tray.Malcolm's, ready for its back. Not tidy, but every wire is in its place, none near the gimbals, nothing in the way of the back.
Check: switch on again. The front page comes up as before.
Calibration and set-up
Reset the transmitter
A few minutes
For a new transmitter, or a new owner: Transmitter → Calibrate → Reset transmitter.
It deletes every model memory (but not the backup files) and sets stick Mode 2. Do not switch off while it works.
Set the stick mode
Transmitter → System, page General (1 of 3): set Stick mode to 1 or 2. Do this before you calibrate.
On the same page, switch Automatic model selection on. Reset transmitter switches it off. Press OK to save.
Then open System again and press Next twice, to Advanced (3 of 3). Switch Keep log files on and press OK. Reset transmitter switches it off too.
General (1 of 3): stick mode, automatic model selection, and the Bind button.
Calibrate the sticks, knobs and switches
Transmitter → Calibrate, then:
Press Calibrate sticks etc.
Move every stick and knob to its ends, several times.
Press Next.
Centre the sticks and knobs. Push all four top-edge switches fully away from you.
Press Finish.
Calibrating: the bars show each channel as you move it.
Check: the screen says Calibration saved. Each stick moves its bar the full width.
Calibrate again whenever you change a stick or the stick mode.
Calibrate the trims
On the same page, press Calibrate trims and follow the words on the screen. Without it, trims may work backwards.
Set the battery type
Transmitter → Batteries: choose your transmitter battery (2S LiPo or Li-ion, or 2S LiFePO4). Then the percentage means something.
Check: the voltage on the front page matches a meter. If not, correct it on System → Advanced (3 of 3), in hundredths of a volt per cell.
Give each switch its job
Transmitter → Switches. Touch a switch and choose its job: Safety, Banks 1 2 3, Bank 4 & Motor, Rates, Buddy, or a channel from 5 to 16.
Positions are near (towards you), mid and away.
Safety: near is safety off. Away is safe.
Bank 4 & Motor: near is bank 4 with the motor off.
Eight switches. Each shows its job and where it is now.
Check: when you move a switch, its position changes on the page.
Every page on the transmitter has a Help button. It explains that page in plain words.
Before any model flies on it
A new transmitter: check every function very carefully before a model goes into the air, and do a range check as well. See Testing before the first flight.
Finished: Malcolm's, back on, screen lit.
The receiver
The Version 2 receiver is a Seeed XIAO ESP32-S3 with one to three nRF24L01+ radio modules. With two or three, it switches to another radio if the one in use loses the link.
It feeds a flight controller over CRSF, SBUS, IBUS or PPM.
It sends Rotorflight telemetry (battery, head speed, ESC temperature) back to the transmitter.
It talks to the phone app over Bluetooth, and updates itself over the air.
It binds to Version 1 and Version 2 transmitters.
It has no PWM servo outputs, so it needs a flight controller. For a model without one, use the Version 1 receiver from the Version 1 repository.
The dual-radio receiver board, drawn from its design files. A second radio sits on the other side.
What it is made of
Part
Exact type
How many
What it is for
Where to buy
About
Every receiver
XIAO ESP32-S3
Seeed Studio XIAO ESP32-S3, with the little aerial in its box
1
The receiver's computer, WiFi and Bluetooth
Seeed Studio, The Pi Hut
£7
Radio modules
Ebyte E01-ML01SP4 (nRF24L01+ with amplifier), or any 2.4 GHz nRF24L01+ module
1–3
The radio link. Two or three give a steadier link
Ebyte's own shops
–
Radio aerials
2.4 GHz dipole aerials with IPEX (u.FL) plugs
1 per radio
Mount them about 90° apart
Electronics shops
–
Lead
Four wires to the flight controller's receiver port
1
Signals out and in, and power
Often in the flight controller's box
–
Capacitor Wired by hand
100 µF, one per radio
1–3
Keeps each radio's supply steady. The circuit board has its own
Electronics shops
–
On the circuit board (when its files are published)
5 V regulator
Pololu S7V7F5 (takes 2.7–11.8 V in)
1
Makes a steady 5 V, even from 5 V
Pololu, or a reseller
–
3.3 V regulator
AMS1117-3.3, SOT-223
1
The radios' own 3.3 V supply
Electronics shops
–
Capacitors
1206: 100 µF × 2, 22 µF, 10 µF
4
Keep the radios' supply smooth
Electronics shops
–
Status light
LED and 100 Ω resistor, both 1206
1 + 1
Off: no link. On: receiving. Flashing twice a second: binding
Electronics shops
–
Lead socket
JST-GH 4-pin, 1.25 mm, horizontal (SM04B-GHS-TB)
1
The lead to the flight controller
Electronics shops
–
Optional
Cover
Clear heat-shrink, wide enough for the board. There is no case yet: the receiver is tiny
1
Protects the board
Electronics shops
–
Total
Parts only, approximate. Prices change.
about £35
The circuit board
The receiver's circuit board files are in the repository: RXV2/kicad/receiver. Send RXV2_NEWB_gerbers.zip to a PCB maker (two layers, 1.6 mm), or ask Malcolm for a spare board (email him). Or wire the receiver by hand, as shown below. The firmware is the same either way.
The AMS1117 first: it sits under the XIAO.
The Pololu regulator: flat on the board, its component side towards the board and its printed side (VIN, GND, VOUT) facing out, as in the photo.
The status LED: its − (cathode) to the pad joined to the ground plane. The wrong way round, it simply does not light.
The XIAO last.
Power: the board takes up to at least 8.5 V from the flight controller's lead, so a 2S BEC is fine. Its Pololu regulator sets the limit.
The regulator side. The Pololu regulator's printed side faces out.The XIAO side. The AMS1117 is underneath the XIAO.
Soldering the XIAO
Dry joints on the XIAO's edge pads are the most common fault. Solder can sit on the pad and look fine without flowing into the half-hole.
Finish every pad with the iron: flux, a little more solder, a little more time, one pad at a time.
Check each one with a magnifier.
Restarts on battery but fine on USB? Suspect a ground joint.
Fewer radios found than you fitted? Suspect a radio's wires or joints.
Sticks work but no Rotorflight or telemetry? Suspect D5.
Wiring it by hand
Every pad of the XIAO and its job. Tap to enlarge.
Every radio: GND, VCC (3.3 V), SCK (D8), MOSI (D10) and MISO (D7) are shared. Leave IRQ unconnected.
Radio 1: CE to D2, CSN to D3.
Radio 2: CE to D0, CSN to D1.
Radio 3: CE to D4, CSN to D9.
Each radio: solder a 100 µF capacitor across its VCC and GND, right at the radio, + to VCC.
The radios' 3.3 V comes from the XIAO's 3V3 pad. That is enough, even for three radios: only one is used at a time.
Flight controller: its RX to D6, its TX to D5, +5 V to 5V, − to GND.
Go by the D-labels printed beside the pads. The full table is in Connections.txt.
Power
Wired by hand, the XIAO takes its 5 V straight from the flight controller's port. Use only a port that gives a steady 5 V, such as a Nexus receiver port. Never a servo or BEC pin: those can carry 6–8.4 V and would destroy the XIAO.
Aerials: fit a dipole to each radio and mount them about 90° apart.
Fit the XIAO's own aerial (pressed onto the tiny gold socket). Without it, Bluetooth and WiFi reach only about an arm's length. A dipole works far better than a stubby one for WiFi.
Put the firmware on
Never two power supplies
Flash the receiver before it is wired to the flight controller, or with the flight controller unplugged. Never plug a computer into the receiver's USB socket while the model's battery is connected.
Put the board into flashing mode
Plug the XIAO into a computer with a USB-C data cable. Hold B, tap R, let go of B. The two tiny buttons are beside the USB socket.
Check: the yellow light goes out. (A red light may stay on: that is the charger. Ignore it.)
Click once in your browser
About a minute
Open the one-click flasher in Chrome, Edge or Opera, on a desktop or laptop. Press Flash this chip. Leave it alone until it says it has finished.
It erases the chip first, so the same button also resets a used board.
Unplug it and plug it in again
The chip does not restart by itself after flashing.
Check: the board appears in the phone app as Untitled.
Prefer the command line? The five files and the esptool command are on the dongle page. To build from source, see the receiver's README.
First set-up on the phone
Install the app and connect
Get the free app from the Phone Apps page (iPhone, iPad and Android). Open it, tap Connect, and choose Untitled.
Rename it at once
Its front page asks you to. Two boards with the same name cannot be told apart.
Check the radios
The Home page shows each radio it found.
Check: it lists every radio you fitted. One missing? Check that radio's wires and joints.
Give it your WiFi
Setup → WiFi settings. With WiFi it can update itself. At the field it needs only Bluetooth.
Choose the output
Setup → Output protocol. CRSF (the default) for Rotorflight. SBUS, IBUS or PPM for other flight controllers.
Home: both radios (slots 1 and 2) found.Setup: output, WiFi, name and updates.
No phone? Join the board's own WiFi network, called Untitled, from a computer, and open 192.168.4.1 in a browser.
Connect it to the flight controller
Safety: servos
Unplug the servos (or leave the BEC off) until the wizard's Servos step has set their frequency and the BEC voltage is right. A wrong setting can burn out a servo in seconds.
Check the lead with a meter before the first plug-in. The port's + must reach the receiver's + (the XIAO's 5V pad, if hand-wired) and − its GND. Hand-wired, + must read about 5 V with the flight controller powered (USB is enough). Over 5.5 V: stop.
Wire TX to RX and RX to TX, plus + and −. Use the flight controller's receiver port: Port A on a Nexus, often marked ELRS or RX on others. It already listens for CRSF.
In Rotorflight, that port must be set to Serial RX, with the receiver type CRSF and the TELEMETRY feature switched on. With a USB-C data cable from the flight controller to the receiver, the app's Ports page does all of this in one Save. Without the cable, use the Rotorflight Configurator once.
The Rotorflight button never appears? Swap TX and RX first. Crossed wires are the usual cause.
Head speed and ESC temperature on the transmitter: switch on the RPM and temperature sensors in Rotorflight's CRSF telemetry, and set the main gear ratio.
Then bind it (next section) and follow the app's New helicopter wizard. Stop before its Blades on step. First do every check in Testing before the first flight, blades off.
No phone to hand? A transmitter with the 16 MB screen has the same steps: Model → Rotorflight → Guide & checks → New helicopter guide. It ticks each step off, and remembers the ticks for each model.
The New helicopter wizard: blades off first.
Battery voltage without telemetry: if your flight controller does not send the flight battery's voltage over CRSF, a small divider board can feed it to pad D9, for packs up to 12S: RXV2/kicad/vdiv (Gerbers ready to order, and how to wire it). Use it only with one or two radios: D9 is radio 3's CSN.
Binding the transmitter and the receiver
Binding pairs a receiver with your transmitter. You do it once per receiver. One transmitter can bind any number of receivers.
Every receiver bound to it listens to it, so switch on one model at a time.
Safety: before you bind
Blades or propeller off, and the safety on (switch away), before you switch the model on.
Choose a model memory
On the transmitter, Model → Models: choose an empty model memory for this model and give it a name.
Put the transmitter into bind mode
Switch on and keep holding the power button for about three seconds (more than two, less than five). You hear a chirp and "binding enabled", and the light blinks.
Or: Transmitter → System → Bind. The button then reads Stop binding.
Switch the receiver on
A new receiver is already waiting to bind. On the circuit board its light flashes twice a second.
Was it bound before? Open it in the app, tap Bind, then Enter bind mode. Changed your mind? The same button now reads Cancel bind: it puts the old pairing back.
The transmitter then asks whether to save this receiver's ID with the model memory you chose. Press OK. Cancel saves nothing, and the model does not connect.
Check: the transmitter's light turns green and it says it is connected.
Check the model's ID
Model → Model IDs shows the stored ID. If it says No ID stored, press Store this model's ID.
From then on, Automatic model selection (switched on in step 22) loads this model memory by itself whenever you switch this model on.
Check: switch everything off and on again. The right model name appears on the front page.
The dongle
The dongle is a bare XIAO ESP32-S3 with four wires, on a spare port of the flight controller. It brings the phone app's Rotorflight set-up to any helicopter, whatever radio flies it.
It can also turn a receiver of almost any make into a USB joystick for a simulator.
Solder four wires: the flight controller's RX to D6, its TX to D5, +5 V to 5V, − to GND. The lead in the Nexus box is the easiest. Check its colours with a meter.
Plug it into a spare port: Port B or C on a Nexus, never Port A (the receiver's).
Then fit a USB-C data cable from the flight controller to the dongle. Or, to use the lead alone, choose dongle on a wire for that port on the app's Ports page (it sets MSP, 115200).
A finished dongle: the board and the Nexus's own lead.
Build it with four wires, not the carrier board
The repository holds a dongle carrier board (RXV2/kicad/dongle). Do not order it. Its connector is the wrong way round: it put the flight controller's 5 V onto a signal pin and destroyed two chips.
Never two power supplies at once
Once the dongle is wired to a flight controller, power it only from the flight controller. Never plug a computer, charger or power bank into its USB socket while the flight controller is connected: the dongle drives the USB cable, so two supplies would meet.
Flash it, or use it as a simulator interface, with the flight controller unplugged.
A new transmitter: check every function very carefully before a model goes into the air, and do a range check as well.
Do every check below before the first flight. Do them again after a crash, a repair, or a change of receiver or settings.
Safety: blades off
Take the rotor blades or the propeller off for every test. Unplug the motor too, unless the test needs it. Hold or strap the model down.
On the bench
Transmitter first, then the model
Always switch the transmitter on first. A receiver that hears its transmitter within a second of power-up keeps its WiFi off.
Once, switch the model on with the transmitter off. A receiver with no transmitter always starts safe: motor off, sticks centred.
Check: nothing moves and the motor cannot start.
The right model loads
Switch the transmitter on, then the model.
Check: the model's own name appears on the front page.
Each stick moves the right channel
In the app (connect within 30 seconds of switching the model on), Setup → View channels. Move each stick and switch in turn.
View channels: a live bar for every channel.
Check: each stick moves only its own bar, the right way, to both ends.
The model moves the right way
Helicopter: right cyclic tilts the swashplate right; forward cyclic tilts it forward; up collective raises the blade pitch; right rudder changes the tail pitch to turn the nose right.
Aeroplane: right aileron raises the right aileron; up elevator raises the elevator; right rudder moves the rudder right.
A channel the wrong way: Model → Reverse on the transmitter. A servo or the swashplate the wrong way: set it in Rotorflight (the app's New helicopter wizard and the transmitter's New helicopter guide do this step by step).
Rotorflight, with the 16 MB screen: under Model → Rotorflight → Guide & checks, Direction check asks you to tilt and turn the model and shows each move in green or red. Check my setup then lists anything that would stop it arming, each with a button to the page that puts it right.
Then move every stick slowly to its ends.
Check: everything moves the right way, and nothing binds or touches.
Safety switch and motor switch
Blades off, motor connected, model held down.
Safety on (switch away): the motor must not run, whatever you do with the sticks and switches. A Rotorflight model stays disarmed. The transmitter's Rotorflight menu says why it will not arm.
Safety off: check the motor starts and stops the way you expect, on the throttle and on the Bank 4 & Motor switch (near is motor off).
The screen's WiFi and Bluetooth switch themselves off when the safety is off.
Switch a Rotorflight model on with the safety already off, and the transmitter will not connect to it. A bright red box reads SAFETY OFF!! and ARMING ON!!, with a warning sound, until you put the safety on.
Check: with the safety on, nothing you do starts the motor.
Failsafe: what happens if the link is lost
Set it up first:
CRSF with Rotorflight: Rotorflight's own failsafe is in charge. Check it once in the Rotorflight Configurator's Failsafe tab, on a computer (neither the app nor the transmitter can change Rotorflight's failsafe). Stage 2 should stop the motor.
SBUS, IBUS or PPM: on the transmitter, Model → Failsafe (or in the phone app: Setup → Receiver settings → Failsafe positions). Tick the channels, hold the sticks where the model should go (motor off), and press Save while connected. The positions are saved in the receiver.
With a Version 2 receiver every channel goes to its saved position, ticked or not. Hold every stick and switch where it should be, motor off, before you press Save. (A Version 1 receiver moves only the ticked channels.)
Then test it, blades off and model held down: safety off, run the motor slowly, then switch the transmitter off (hold the button through the countdown).
Check: within a few seconds the motor stops and stays stopped. When you switch the transmitter on again, the motor does not start by itself. Then put the safety on.
Battery warnings
Model → Options: set the Stop flying voltage per cell: about 3.6 V for LiPo. The voltage recovers a little when the motor stops.
Transmitter → System: set the transmitter's low-battery warning high enough that you can land with time to spare.
The power button is guarded
Check: while connected, a quick press does not switch the transmitter off. Holding it starts a countdown.
Check the link
About 500 packets a second
With the model connected: Model → Telemetry.
Frame rate (packets a second) should be close to 500. A little lower is normal while the receiver's WiFi is on.
Longest comms gap should be below about 250 ms, and is normally well below 100 ms.
Measured on the first Version 2 flight (5 October 2026): an average of 491 packets a second, 0.21 % lost, and a longest gap of 15 ms.
The Telemetry page (sample figures).
Check: frame rate close to 500; longest gap well below 250 ms. If not, move the receiver's aerials (dipoles, 90° apart) and check them for damage.
Reconnection times
On the Telemetry page, press Gaps. The chart shows how long each reconnection took. Look at it after landing, not in flight.
Reconnection times (sample figures).
Check: most reconnections take under 8 ms. Many over 100 ms mean the aerials need a look.
Look at the 2.4 GHz band (optional)
Transmitter → Scan RF shows how busy each channel is, and names the quietest and the noisiest. Useful at a new field.
The interference scan.
Range test
Walk away with the transmitter
The transmitter has no low-power range-check mode. It always runs at full power, so walk further than you will ever fly.
Put the model on the ground in an open space. Blades off, and the motor unplugged. Safety on.
A helper stays with the model.
Put a Frame rate box on your front screen (Transmitter → Appearance), so you can read it as you walk.
Walk away. Every so often, stop and move the sticks. The helper checks that the servos follow smoothly.
Keep going well past your usual flying distance.
Back at the model, look at the Telemetry and Gaps pages.
Check: the servos follow all the way out and back, the frame rate stays up, and the longest gap stays short.
First flight
A short first hover
Choose a calm day and an open space, away from people.
Charge the transmitter and the flight battery.
Flight battery unplugged: fit the blades (or propeller). Check they are tight and the pitch is right (the wizard's Blades on step).
Safety on (switch away). Transmitter on first, then plug in the flight battery. Check the model name.
Step well back. Only then switch the safety off.
Hover briefly, low. Land.
Safety on, then unplug the flight battery, before you touch the model.
Check the trims, the temperatures and the Telemetry page.
Rescue mode: set it up on the bench. Test it later, high in the air, before you rely on it.
Check: after landing, the frame rate, the longest gap and the reconnection times look like they did on the ground.
The short version, for the field
Transmitter and flight battery charged
Blades or propeller on and tight
Safety on until you are ready to fly
Transmitter on first, then the model
Only one of your models switched on
The right model name on the front page
Controls move the right way; nothing binds
Frame rate close to 500 a second
Failsafe tested since the last change
Range tested since the last change
Open space; people well away
Safety on and battery out before you touch the model
Getting help
Email Malcolm:mmessiter@gmail.com. Say which transmitter, receiver and flight controller you have, what you did, what you saw, and what you expected.
From the phone app: open the Event log (Rotorflight setup and Wizard → À la carte → Black box → Receiver log → Event log; with no Rotorflight: Receiver log → Event log; on a dongle it is on the Home page) and tap Send debug data to Malcolm. It gathers the receiver's version, its event log and what the app did into one text file. No passwords are included.
On the transmitter: every page has a Help button. With Keep log files on (step 22), the logs are under Model → Log.