Sub-2 GHz Command-Link Engineering for Matrice 400: Integration, Compliance, and Acceptance Testing

Publisher: UNITED UAV Official
Commercial disclosure: UNITED UAV sells the module discussed below. This engineering article includes one link to our related product listing and has been configured to decline author payout.

A radio module does not create a reliable command link by itself. Link reliability is the result of an entire system: permitted spectrum, transmitter configuration, antenna geometry, terrain, obstruction clearance, interference, aircraft orientation, firmware, operator procedure, and a mission-specific acceptance test. This is particularly important when a component is described with the attractive shorthand “sub2G.” Lower-frequency operation can offer useful propagation characteristics, but it does not repeal the radio horizon, remove Fresnel-zone obstruction, or authorize transmission in a band that local regulators have not made available.

The DJI Matrice 400 RC Plus 2 sub2G SDR Module is intended to add supported below-2-GHz communication capability to a compatible DJI RC Plus 2 Enterprise Enhanced controller used with Matrice 400. The current product listing identifies it as a module rather than a complete remote controller and lists the module, two screws, two screw washers, and a screwdriver in the package. DJI documentation adds several operational constraints that should shape procurement and test planning: usable frequencies vary by jurisdiction; sub2G is unavailable while the Matrice 400 is acting as an onboard relay; and a dual-operator configuration needs a module on both controllers before the corresponding frequency can be used.

Those details change the engineering question. The useful question is not “Does sub2G have more range?” It is: “For this aircraft, controller configuration, jurisdiction, route, interference environment, and operating concept, does the enabled link meet the required command-and-control margin with documented fallbacks?” This article provides a way to answer that question without turning a catalog description into an unsupported performance promise.

Start with an operational requirement, not a frequency preference

Before purchasing or enabling another radio path, define the failure that the project is trying to prevent. Examples include loss of margin behind vegetation, unstable video near an industrial site, poor coverage at a valley turn, or insufficient resilience when the aircraft changes attitude. Each symptom has different causes. A low-frequency option may help in some propagation environments, while doing little for a blocked radio horizon, an incorrectly placed controller, a damaged antenna, a saturated receiver, or an unauthorized channel.

Write a link requirement that can be tested. It should identify the approved operating area, maximum planned slant range, minimum aircraft height along the route, terrain and structure classes, controller location, required video quality, acceptable command latency, minimum warning margin, return-to-home behavior, and the response to degradation. Include the payload because its physical installation can shadow antennas or alter aircraft attitudes. Include the operating crew because a dual-operator mission has a different radio configuration from a single-controller flight.

Separate three traffic needs:

1. Command and control: low-rate but safety-critical pilot commands and aircraft state.
2. Situational video and telemetry: higher-rate information used to make operational decisions.
3. Payload data delivery: mission files or live streams that may have their own bandwidth and latency requirements.

A link can remain sufficient for basic command while video quality falls. Conversely, a seemingly clean video feed at one moment does not prove adequate control margin throughout a route. Acceptance criteria should therefore cover the actual functions the crew relies on, rather than one visual impression from the display.

What lower frequency changes—and what it does not

For an ideal free-space path, loss increases with frequency when distance and antenna gains are held constant. This is one reason lower-frequency links can be attractive. Real installations, however, do not hold everything else constant. Regulatory power limits may differ; compact antennas are electrically smaller at longer wavelengths; antenna efficiency and radiation pattern vary with installation; bandwidth and data rate may change; and the interference floor can be very different from one band to another. The system result cannot be inferred from frequency alone.

The Fresnel zone is an equally important part of the geometry. The radius of the first Fresnel zone at a point on a path can be approximated by:

r1 = sqrt(lambda × d1 × d2 / (d1 + d2))

where lambda is wavelength and d1 and d2 are the distances from that point to each end of the link. Because wavelength grows as frequency falls, the clearance volume becomes larger at lower frequencies. For an illustrative one-kilometre path with the obstruction at its midpoint, the first-zone radius is about 9.1 metres at 900 MHz and about 5.6 metres at 2.4 GHz. A common planning objective of roughly 60 percent clearance would require about 5.5 metres versus 3.4 metres at that midpoint. These are generic propagation calculations, not DJI range figures and not a statement that 900 MHz is available for this product in a particular country.

The practical lesson is counterintuitive: a lower-frequency path may tolerate some materials and diffraction conditions better, yet it also needs a larger Fresnel clearance envelope. Flying just above a ridge, vehicle roof, tree line, or building parapet can still erode margin. The correct response is to model the route and then measure it, not to assume that a sub2G selection makes obstruction irrelevant.

Radio horizon also remains. Raising either end of the link can improve geometric visibility, but the permissible aircraft altitude, terrain, airspace, and visual-line-of-sight rules still govern the operation. Increasing controller height by moving to a safe elevated position is often more effective than standing beside a vehicle, metal fence, or building that blocks or reflects the signal.

Treat spectrum authorization as a configuration item

“Sub2G” is a range of possible frequencies, not one globally harmonized UAV channel. Allocations, permitted equipment, radiated-power limits, duty cycles, bandwidths, licensing conditions, and coordination requirements differ by country and sometimes by user class or location. The product listing correctly warns that frequency availability varies and that relevant radio licensing and regulatory authorization are required.

Create a spectrum authorization record before activation. At minimum, it should contain:

• operating country and, where relevant, region;
• approved frequency or channel set shown by the current controller and firmware;
• equipment approval or conformity evidence applicable to that destination;
• licence holder, licence reference, site authorization, or other basis for use;
• permitted power, bandwidth, duty cycle, and operational restrictions;
• responsible person and review date;
• the exact firmware and controller configuration to which the review applies.

Do not copy a channel plan from another country or from an online screenshot. Do not infer permission from the fact that a menu option is visible. Software exposure, hardware capability, and legal authority are separate states. If the operating organization cannot establish all three, keep the function disabled and resolve the gap with its spectrum or compliance specialist.

This record also controls change. A firmware update, controller replacement, cross-border deployment, or revised mission area should trigger a review. For a fleet, encode the approved region and radio configuration in the aircraft/controller assignment record so that a controller cannot casually move between jobs with incompatible authorizations.

Verify the exact controller and aircraft combination

The module is designed for DJI RC Plus 2 Enterprise Enhanced. “RC Plus 2” alone is not a sufficient compatibility description. Record the full controller designation, hardware identity, firmware version, aircraft model, aircraft firmware, DJI Pilot 2 version, and module identity before installation. The module is not a substitute for the controller, and the presence of a physical mounting location does not establish functional compatibility with another aircraft series.

DJI’s current Matrice 400 information distinguishes pairing support from sub2G support. The enhanced controller can support some other aircraft families after specified updates, but DJI states that those aircraft do not thereby gain the sub2G function. This is a useful general rule: compatibility must be evaluated per function, not merely per connector or pairing result.

For a single-controller Matrice 400 mission, the inventory needs one correct controller/module set. For Dual Operator Mode, DJI specifies that both controller A and controller B need the module for the corresponding frequency to be available. That means the procurement quantity, installation record, firmware baseline, and preflight inspection must cover both controllers. One equipped controller and one unequipped controller is not an acceptable way to test the dual-operator sub2G configuration.

There is another architecture constraint: DJI states that sub2G is unavailable when the Matrice 400 is used as an onboard relay. Relay operation and sub2G should therefore be treated as mutually exclusive mission configurations unless later official documentation explicitly changes that behavior. A team planning both should have two configuration cards and should verify the intended mode during briefing rather than discovering the exclusion in the field.

Install as controlled avionics work

The supplied screws, washers, and screwdriver make the physical job look simple. The quality requirement is still avionics-level configuration control. Work on a clean, dry, electrostatic-safe surface with the controller powered down. Confirm the package contents and inspect the module, connector, fasteners, and controller interface for contamination or damage. Photograph the pre-installation condition and record serial or asset identifiers where available.

Follow the current DJI procedure for the exact controller hardware. Do not invent a torque value if DJI does not publish one in the accessible procedure. Use the supplied fastener stack in the documented positions, bring fasteners down evenly, and stop if the module does not seat without force. A screw that appears tight can still be cross-threaded, bottomed out, missing a washer, or clamping an incorrectly aligned module. The acceptance criterion is correct seating and retention according to the manufacturer’s procedure, not maximum hand force.

After installation, inspect for gaps, trapped debris, damaged seals, pinched material, loose hardware, and interference with the controller’s battery, cooling path, rear cover, strap hardware, or other accessories. Account for the module during transport: a controller pressed against a case insert that was designed for a different rear profile can load the module or its fasteners.

DJI’s user manual describes a solid red module LED when the controller is powered and the module is properly connected. Treat that indication as a connection check, not as proof of spectrum authorization, aircraft link performance, or correct mission configuration. If the indication is absent or abnormal, stop and inspect the installation, controller recognition, and firmware state before flight.

Configure deliberately in DJI Pilot 2

For Matrice 400, DJI’s documented path is from camera view to the HD settings, then Work Frequency, then Multi-Frequency, where sub2G can be enabled. Menu names can move with software revisions, so the current manual and release notes remain the controlling reference. Capture the displayed frequency options after the regulatory review; that screenshot is useful evidence that the fielded software configuration matches the authorized plan.

Enabling a band should not be confused with forcing every packet onto it at all times. Multi-frequency systems can select or combine resources according to their implementation and environment. The acceptance test should focus on observed end-to-end behavior and documented system indications rather than assuming a hidden selection algorithm.

Before flight, confirm:

• controller, aircraft, module, and application firmware are on the approved baseline;
• the controller is correctly linked to the intended Matrice 400;
• sub2G is enabled only where authorized;
• controller A and B are both equipped when Dual Operator Mode requires it;
• onboard-relay mode is not selected for a sub2G test;
• normal lost-link and return behavior is configured and briefed;
• logs, screen recordings, and observer forms are ready;
• the crew can return to the baseline frequency configuration without improvisation.

The rollback step matters. If the new configuration behaves unexpectedly, the team should be able to return to a previously accepted state, verify that state, and distinguish a module issue from an unrelated aircraft, controller, antenna, or environmental fault.

Build a route-specific link budget

A useful preflight engineering model includes transmitter power, cable and connector loss where applicable, antenna gain and pattern, free-space path loss, estimated obstruction or foliage loss, polarization mismatch, receiver sensitivity for the relevant mode, interference allowance, and a design margin. If vendor documentation does not expose a term, mark it unknown rather than filling the spreadsheet with an optimistic guess.

Geometry deserves its own map. Plot controller position, aircraft route, terrain elevation, buildings, tree lines, towers, and critical mission points. Evaluate line of sight and Fresnel clearance in both directions; the return path is not automatically identical in an asymmetric radio system. Mark places where the aircraft banks, yaws, climbs behind an obstruction, or carries a payload between its antennas and the controller. Antenna radiation patterns contain weaker directions, and vehicle attitude can move a weak direction toward the ground station.

For portable operations, specify the controller position as carefully as the takeoff point. Keep it away from large metal surfaces, running generators, high-power transmitters, and crowds that can block or reflect the path. Define how the operator holds or mounts the controller so that antenna orientation is repeatable. “Operator stood somewhere near the vehicle” is not repeatable test evidence.

Do not use one long-distance flight as the entire validation. A link that survives a straight outbound leg in quiet spectrum may fail during a low turn behind vegetation or when the site becomes busy. Divide the route into radio-critical segments and identify why each is critical.

Use a staged acceptance test

The safest useful test program expands one variable at a time.

1. Bench and static recognition

With propellers removed or the aircraft otherwise made safe according to the approved procedure, power the controller and verify the module indication, application recognition, aircraft pairing, approved frequency controls, and log capture. In a dual-operator configuration, repeat the check for both controllers and transfer control through the documented workflow. Verify that selecting onboard-relay operation makes the expected sub2G limitation visible before anyone depends on the link.

2. Short-range ground check

At an authorized test site, establish the baseline with the aircraft and controller close together. Verify command response, telemetry, video, alerts, and recovery behavior. Rotate or reposition the equipment only within a safe procedure to look for installation-dependent nulls or unexpected shielding. This is not a substitute for flight testing, but it can catch recognition, configuration, and gross antenna problems.

3. Baseline flight on the accepted configuration

Fly a simple route using the previously accepted radio configuration, with the same aircraft, payload, controller position, and environmental record planned for the comparison. Record available link indications, warning events, video behavior, command response, aircraft position and altitude, orientation, and timestamps. Note other emitters or site activity. The purpose is to create a same-day reference, not to demonstrate maximum range.

4. Controlled sub2G comparison

Enable the authorized multi-frequency configuration and repeat the route without changing unnecessary variables. Test the radio-critical segments progressively. Establish stop conditions before launch: persistent warnings, loss of required video, unexpected latency, disagreement between operators, abnormal module indication, or any aircraft behavior that consumes the planned safety margin. An observer should call conditions and record events so the pilot is not trying to conduct an RF experiment while controlling the aircraft.

5. Edge cases and degraded conditions

Only after the nominal test passes should the program assess approved edge cases: both headings along the route, representative payloads, operational altitude bands, seasonal foliage, likely controller locations, and the dual-operator setup. Do not deliberately create an unsafe lost-link event. Validate failsafe behavior through the manufacturer’s documented method and within the organization’s flight-test authorization.

6. Repetition and review

One pass is anecdotal. Repeat enough flights to separate consistent behavior from a quiet-spectrum accident. Review aircraft and controller logs, screen recordings, observer notes, and RF survey data on a synchronized timeline. The decision should be traceable to defined criteria, not to a pilot’s memory that the bars “looked better.”

Define pass/fail criteria before collecting data

Good criteria are functional and route-specific. Examples include no command-link warning on the approved route, no unexplained control latency, video remaining adequate for the stated decision task, no module or controller fault indication, successful dual-controller control transfer where applicable, and correct automatic response to the tested degradation procedure. Set quantitative thresholds only for parameters the system actually exposes and the team can measure reliably.

Use an event table for analysis:

Time	Position and height	Aircraft heading	Controller position	Mode/configuration	Link or video event	Crew action	Outcome
T+00:00	Launch point	North	Surveyed mark A	Baseline	None	Continue	Normal
T+04:20	Ridge segment	West	Surveyed mark A	Multi-frequency	Warning or degradation if observed	Execute predefined response	Record result

The sample row is a template, not a claim about product behavior. Add environmental fields that matter to the operation: precipitation, foliage condition, known site transmitters, temperature, and whether a vehicle or structure changed near the controller.

Acceptance is not “sub2G performed better somewhere.” It is “the approved configuration met every mandatory criterion across the defined mission envelope, with no unresolved anomaly.” If results are mixed, restrict the approved route or configuration and investigate. A lower-frequency option can be one layer of resilience without becoming the only layer.

Common failure modes and diagnostic order

If the function is unavailable, begin with architecture and configuration before blaming RF propagation:

1. Confirm that the controller is the Enterprise Enhanced model and the aircraft is the intended Matrice 400.
2. Confirm physical seating, fasteners, and the documented LED indication.
3. Confirm compatible, approved firmware and DJI Pilot 2 versions.
4. Confirm the feature is permitted and exposed for the operating region.
5. Confirm that onboard-relay mode is not active.
6. In Dual Operator Mode, confirm modules are installed and recognized on both controllers.

If the function is available but field performance is poor, check the route geometry, controller placement, antenna orientation, payload shadowing, aircraft attitude, interference environment, firmware changes, and hardware condition. Compare against the baseline configuration on the same day. Moving immediately to greater range makes diagnosis harder and can reduce the recovery margin.

Intermittent faults deserve particular caution. A module that reconnects after handling, transport, or temperature change may have a mechanical or interface problem. Quarantine the controller/module set, preserve logs, inspect the mounting and contacts through the approved service process, and do not normalize the issue as “radio variability.”

What should be in the technical file

For each installed unit, preserve:

• purchase and part identification;
• controller and aircraft assignment;
• installation date, technician, procedure revision, and inspection images;
• module, controller, aircraft, and application version evidence;
• jurisdictional spectrum approval and review date;
• approved single- or dual-operator configuration;
• relay-mode restriction acknowledgement;
• baseline and sub2G test plans, logs, anomalies, and disposition;
• accepted routes, payloads, controller locations, and environmental limits;
• maintenance inspections and any removal or replacement history.

This turns a small accessory into a controlled system capability. It also prevents a later crew from assuming that because the module is physically present, every frequency, aircraft, mode, and country is approved.

Procurement checklist

Before ordering, ask five concrete questions. Is the controller exactly DJI RC Plus 2 Enterprise Enhanced? Is the mission aircraft Matrice 400, and is sub2G required for the mission rather than merely desirable? Has the operating organization confirmed permitted spectrum and licensing? Will the mission use Dual Operator Mode, requiring two equipped controllers? Will the aircraft act as an onboard relay, in which case the current DJI documentation says sub2G is unavailable?

If those answers support the configuration, confirm package contents, current documentation, firmware baseline, spares strategy, installation responsibility, and acceptance-test resources. The DJI Matrice 400 RC Plus 2 sub2G SDR Module should then be evaluated as part of a documented command-link design—not as a range upgrade whose outcome can be assumed from its name.

The engineering value of sub2G is real only when the complete operating system is legal, compatible, installed correctly, route-tested, and supported by evidence. That is the standard that makes a radio option useful in enterprise UAV work.