RadioMaster Boxer ELRS — bench-only setup reference

BLUF

This note captures a user-provided proposed setup workflow for a RadioMaster Boxer ELRS transmitter: EdgeTX and SD-card alignment, internal ELRS firmware alignment, a model RF configuration, receiver pairing, and preflight checks. It is a reference and planning note, not an instruction to transmit, bind, arm, or fly.

The internal ELRS link, receiver pairing, packet-rate selection, and transmit-power settings are all controlled RF activities under the Drone Lab safety boundary. No radio, receiver, battery, vehicle, firmware, binding, RF transmission, or flight activity was performed while creating this note.

Safety and stop gate

Before any real-radio work, create a written test plan that records:

1. exact transmitter and receiver hardware/revisions;
2. firmware versions and official download checksums or provenance;
3. intended frequency band, packet mode, and transmit-power setting;
4. local legal and site constraints;
5. bench location, RF containment or separation controls where applicable;
6. receiver power source; props removed; motors disabled; and emergency power-off method;
7. evidence folder and rollback path.

Stop immediately if the model is attached to a powered vehicle with props installed, the regulatory/frequency status is unknown, firmware target identity is uncertain, or a receiver/vehicle is not owned and authorized.

Proposed workflow — captured, not executed

Key technical concepts

• EdgeTX is the transmitter operating environment and model configuration surface.
• Internal ELRS module is the Boxer transmitter radio module; it must be identified by exact hardware target before any update.
• CRSF is the control/telemetry protocol configuration expected by the transmitter-model and flight-controller integration path; a documented configuration is not proof of correct vehicle behavior.
• Binding identity is shared configuration between transmitter and receiver. Treat it as a private configuration value, not a value to publish in this vault.
• Packet mode and transmit power trade latency, range, link robustness, heat, battery use, and regulatory exposure. They are not universal presets and must not be copied blindly from a social post or video.
• Failsafe is a safety requirement. It must be tested on a restrained, props-removed bench setup before any flight discussion.

What this note does not establish

• Correct firmware target or current vendor-supported release.
• Compatibility with a particular receiver, flight controller, Betaflight, INAV, PX4, or ArduPilot build.
• Lawfulness of a frequency or power setting at a particular location.
• Correct motor mapping, control direction, arm logic, failsafe behavior, or physical-flight readiness.
• Permission to transmit or bind to any receiver other than owned, authorized equipment.

Source intake and provenance

The user supplied the following secondary/community sources. All were processed through Insane Search on 2026-07-20 before inclusion. Retrieval status is not a correctness endorsement.

Primary-source validation still required

Before controlled bench work, validate against the current official RadioMaster Boxer documentation, EdgeTX release documentation, and ExpressLRS target/release documentation. The user-provided community sources may be stale, variant-specific, or incomplete.

Suggested evidence record

Date/time:
Operator:
Radio hardware and revision:
Receiver hardware and revision:
Vehicle state: props removed / motors disabled / bench powered
Firmware sources and versions:
Model export location:
RF plan and legal check:
Binding identity stored privately: yes/no
Failsafe test result:
Channel-map test result:
Telemetry/link observation:
Rollback/power-off plan:
Open issues and next safe action:

Related notes

• Drone learning map
• Safe learning path
• LiteWing first-flight checklist
• Sources and validation
• Drone Lab safety boundaries