UNITED UAV

UNITED UAV

uniteduav@hubzilla.eskimo.com

This channel has not added a profile description yet

Gender:: Male

Welcome to Hubzilla.Eskimo.Com

Home of Censorship Free Hosting

Please tell your friends about hubzilla.eskimo.com and friendica.eskimo.com.

From sensor to safety case: integrating the DJI Matrice 4 Obstacle Sensing Module

2026-09-28 06:46:13

UNITED UAV

uniteduav@hubzilla.eskimo.com

official-dji-matrice-4d-matrice-4-series-obstacle-sensing-module.jpg

Engineering the DJI Matrice 4 Obstacle Sensing Module into an operational safety case

The DJI Matrice 4 Obstacle Sensing Module is easy to describe as an accessory and much harder to integrate responsibly. Model LR-01 combines a rotating LiDAR with millimeter-wave radar for compatible Matrice 4 and Matrice 4D aircraft. That combination can expand the sensing information available to the flight system, especially around thin conductors and low-light operations. It does not turn an aircraft into an autonomous collision-proof machine. The useful engineering question is therefore not simply, “Can we mount it?” It is, “What hazards does this module help control, under which conditions, and how will the operator prove that it is installed, configured and performing as expected?”

This guide treats the module as one layer in a larger operational safety case. It covers selection, mechanical integration, activation, acceptance testing, mission planning, maintenance and evidence. The objective is to help inspection teams, public-safety units, infrastructure operators and dock-program managers make a defensible deployment decision instead of treating a sensor specification as a substitute for risk analysis.

1. Establish the exact equipment baseline

Start with the product identity. The selected item is the DJI Matrice 4D / Matrice 4 Series Obstacle Sensing Module, model LR-01. DJI lists a mass of 235 g and dimensions of 103.3 × 64 × 85.8 mm. The published operating-temperature range is -20 °C to 50 °C. DJI describes the sensing architecture as a rotating LiDAR plus millimeter-wave radar. The rotating LiDAR field of view is listed as 58 degrees vertically and 360 degrees horizontally; the radar field of view is 90 degrees vertically and 90 degrees horizontally. DJI lists a maximum detection distance of 100 m, but that headline value must not be confused with a universal usable range for every target.

The official specification also states an effective sensing-speed condition of no more than 15 m/s for a 12 mm steel-core aluminum stranded wire. That is a tightly defined test condition, not a promise that every 12 mm object will be detected at every aspect, distance, weather condition or closure rate. Conductor material, background, orientation, atmospheric attenuation, platform attitude, relative motion and firmware behavior all influence the operational result. A team should preserve the wording and conditions of the source specification in its acceptance record rather than reducing it to “detects wires.”

Compatibility is similarly specific. The store listing identifies DJI Matrice 4D Series and DJI Matrice 4 Series aircraft, with current firmware required. The kit includes the module, H2.5 and H1.5 hex keys, a Matrice 4 adapter bracket and twelve reflective stickers intended for DJI Dock use. The bracket matters because the physical installation differs between aircraft families. Confirm the exact aircraft model, module part number, included bracket and current DJI documentation before issuing the equipment to a crew. A familiar name is not enough for configuration control.

2. Understand what sensor fusion changes—and what it does not

LiDAR and millimeter-wave radar observe the environment through different physical mechanisms. A rotating LiDAR measures optical time of flight and can build angularly dense range observations across its scan. Radar uses reflected radio energy and may continue to produce useful returns where visible-light imaging is weak. Combining them can broaden the set of conditions in which an obstacle is represented, but the sensors do not erase each other’s blind spots or uncertainty.

Thin conductors are a useful example. Their apparent cross-section changes sharply with view angle. A wire crossing the flight path may present a different return from one aligned nearly along the viewing direction. Background clutter, supporting hardware, vegetation movement and precipitation can complicate interpretation. A sensing system may first acquire a conductor at one distance, lose it briefly, then reacquire it as geometry changes. Operators should plan for this variability and avoid turning the first alert distance observed in a test into a fixed operational constant.

The module also works inside an aircraft system that already has native vision and ranging sensors, flight-control logic, configured obstacle-avoidance behavior and operator inputs. The LR-01 is therefore not a standalone safety device. Its output is interpreted by aircraft firmware and presented through DJI Pilot 2 or FlightHub 2 workflows. An alert, stop or bypass response depends on software state, mode, speed, geometry and configuration. The pilot or remote-operations supervisor remains responsible for understanding what response is expected and what escape action remains available.

3. Convert the specification into a purchase decision

A sound procurement decision begins with the hazard register, not the catalog. Write down the obstacles and environments that create unacceptable exposure in the intended missions. Examples may include distribution conductors, shield wires, communications lines, crane cables, suspended structures, narrow corridors, nighttime substations or low-contrast industrial surfaces. For each hazard, record the likely diameter, material, orientation, background, approach direction, minimum planned stand-off and environmental envelope.

Next, ask whether the module addresses a meaningful part of that exposure. If missions are conducted mainly in open terrain at conservative stand-off distances, improved thin-object sensing may provide limited incremental value. If the aircraft repeatedly traverses complex utility corridors or supports dock-based inspection near conductors, the added sensing layer may justify its mass, cost, commissioning effort and maintenance burden. The answer should be tied to actual routes and incident data, not to a generic desire for “more safety.”

Account for system effects. Adding 235 g changes the aircraft configuration and may affect endurance, acceleration, braking margin and wind response. Use the applicable aircraft manual and in-app estimates to assess flight time; do not subtract a guessed percentage from the nominal endurance. Check whether other payloads or accessories compete for mounting space, interfaces or permitted combinations. Review transport cases, spares, weather protection, inspection tools, firmware-management procedures and crew training. The purchase price is only one part of the deployment cost.

4. Use a controlled installation process

Installation should be performed against the current DJI user manual and recorded as a configuration change. Power the aircraft off before attaching or removing the module. This protects the interface and avoids asking the aircraft to enumerate hardware during connection. Inspect the connector, sealing surfaces, module body, bracket and fasteners under good light. Reject damaged contacts, contamination, cracked housings, distorted brackets or fasteners that cannot achieve the prescribed fit.

Use the correct bracket for the aircraft family and the supplied tools where directed. Seat the module without forcing the connector. Tighten the mounting hardware in the sequence and manner described by DJI; “hand tight” is not a transferable torque specification unless the manual defines it that way. Confirm that the module cannot rock, that cables or covers are not pinched, and that no part obstructs other sensors. When the system is used with a dock, apply and manage the supplied reflective stickers exactly as the dock documentation requires rather than treating them as decorative labels.

Before first power-up, photograph the installation and record aircraft serial number, module serial number if exposed, bracket identity, installer, date and firmware baseline. This creates traceability if an intermittent issue appears later. It also prevents a module that passed acceptance on one aircraft from silently moving to another without a configuration review.

5. Activate and verify the digital configuration

DJI documents two activation paths. For dock use, the aircraft should be powered and linked with the dock; the DJI Enterprise app is installed on a compatible Android phone, the phone is connected to the USB-C port of the dock electrical cabinet, and the on-screen activation workflow is completed. For operation with a remote controller, power the controller and aircraft, open DJI Pilot 2 and complete the activation prompt. Follow the current manual and local account-management policy because interface details can change with software revisions.

After activation, update the relevant devices to a mutually supported firmware baseline. “Latest” should be captured as explicit version numbers in the maintenance log. For a docked system, confirm the module icon is present in the FlightHub 2 device panel. For a controller-based system, confirm LR-01 appears on the DJI Pilot 2 home page. Absence of warnings is necessary but insufficient: also verify that the accessory identity persists through a controlled restart and that status remains healthy after the aircraft reaches operating temperature.

Do not perform firmware changes immediately before a critical mission. Treat updates as maintenance events: read release notes, stage the update, re-run acceptance checks and retain a rollback or grounding decision if behavior changes. In a multi-aircraft fleet, configuration consistency matters. A route validated on one firmware-and-module combination should not automatically be assigned to an aircraft with a different baseline.

6. Build an acceptance test that measures behavior

An acceptance test should establish whether the installed system behaves consistently enough for the intended concept of operations. It is not an attempt to recreate DJI’s laboratory qualification. Use a controlled site, an approved test plan, competent personnel, a visual observer where required, conservative heights and speeds, and a readily accessible manual escape path. Never improvise tests around live energized conductors, traffic or uninvolved people.

Begin with static checks. Confirm the module identity, attachment, clean sensor windows, app status, time synchronization and log storage. Capture screenshots of status pages. With the aircraft restrained only as the manufacturer permits, check for unexpected warnings during startup. Then perform a low-risk hover in a clear test area to observe vibration, attitude stability, telemetry and any abnormal acoustic or thermal signs.

Progress to representative targets in stages. Use a visible, non-energized target whose location and dimensions are known. Test several approach angles, backgrounds and lighting conditions at speeds well below the published upper condition. Record first indication distance, aircraft response, operator response and closest approach. Repeat each condition enough times to expose variability; a single successful pass demonstrates little. Add a negative control in open space to check for nuisance behavior. If thin-object performance is essential, commission a test fixture designed and supervised by a qualified safety team rather than suspending ad hoc wire in an active flight area.

Define acceptance thresholds before testing. Examples include: module recognized on every cold start; no connection warnings during a specified observation period; alerts presented in the expected interface; repeatable response within a conservatively defined corridor; no unexplained false response in the negative control; and complete logs for every run. If a threshold fails, ground that configuration, preserve logs and diagnose the cause. Do not repeatedly fly until one pass happens to succeed.

7. Design the mission around residual risk

Even after acceptance, route design should assume that an obstacle can be missed or acquired too late for the desired maneuver. Maintain stand-off based on aircraft dynamics, navigation uncertainty, wind, latency, target geometry and the consequences of a failed detection. The module supports risk control; it does not replace separation.

Speed deserves explicit treatment. DJI’s published 15 m/s condition refers to a specified 12 mm conductor. An operational speed limit should usually be lower and should reflect the tested geometry, stopping or bypass distance, remote-link latency and local procedure. Slow down before entering a conductor-rich segment rather than waiting for an alert. Avoid aggressive lateral motion that reduces time available for both the control system and the pilot to respond. Establish an abort point before the narrowest part of the route.

Weather remains part of the hazard assessment. DJI notes that clouds, fog, rain and snow can affect obstacle avoidance and bypassing. Contamination, condensation, glare, strong electromagnetic environments and moving objects also deserve consideration. The official notes state that the aircraft cannot actively avoid fast-moving objects because of safety-system limitations. A vehicle, swinging cable, moving crane component or another aircraft therefore requires procedural separation and active monitoring, not reliance on the module.

The remote crew should know what it will do when sensing information conflicts with the planned route. Define who can pause or abort the mission, how an alert is communicated, what telemetry is monitored, and how the aircraft is recovered if automatic behavior places it in a poor position. For dock operations, set exception-handling rules: a repeated obstacle event should trigger review, not an endless series of automatic retries.

8. Treat IP55 and temperature figures correctly

DJI lists IP55 for the module and specifies -20 °C to 50 °C operation. Those values are environmental design inputs, not permission to ignore installation state or weather procedures. The store listing notes that IP55 applies when the module is used with the Matrice 4D Series. A complete ingress-protection claim depends on the specified combination, proper fit, intact seals and correct installation. A Matrice 4 Series setup should be evaluated against its own documentation rather than inheriting the 4D statement.

Temperature affects more than whether electronics power on. It can influence batteries, condensation, icing, material stiffness and the time required for a stable system state. Moving equipment between cold and warm humid spaces can produce moisture on optical surfaces. Build acclimation and inspection time into dispatch procedures. If sensor surfaces become wet, dirty, iced or damaged, ground the aircraft until they can be restored under the approved maintenance process.

9. Maintain the sensing chain, not just the enclosure

Preflight inspection should include cleanliness, damage, attachment, status recognition and firmware compatibility. Use only cleaning methods approved for the sensor surfaces; abrasive wiping can convert a minor contaminant into permanent optical damage. Check the bracket and fasteners after transport, a hard landing, unexpected vibration or contact with vegetation. Compare the module’s orientation with baseline photographs if displacement is suspected.

Periodic functional checks should be based on usage and consequence, not only calendar time. A dock aircraft exposed continuously to dust, precipitation and temperature cycling may need a different inspection interval from a controller-operated aircraft stored indoors. Trend connection warnings, nuisance detections, missed detections observed during controlled checks and any changes after firmware updates. Serial-level records make it possible to distinguish an aircraft issue from a module issue.

Define removal-from-service criteria in advance. Cracked housing, compromised seals, damaged connector contacts, persistent recognition failure, abnormal rotation noise, repeatable test failure or an unexplained change in detection behavior should trigger grounding and technical review. Field repair beyond the manufacturer’s authorized scope can introduce hidden alignment or sealing problems. Preserve logs and contact the appropriate service channel.

10. Create evidence that survives handover

Professional operations need evidence that another person can audit. The configuration record should identify the aircraft, module, bracket, firmware, apps and dock or controller involved. The acceptance package should contain the approved test plan, site conditions, target description, flight logs, screenshots, results, deviations and sign-off. The operating procedure should state speed limits, route stand-off, weather exclusions, alert response and the conditions that force a return to manual review.

When the fleet or route changes, use change control. New firmware, a replacement module, a different aircraft, a modified route, a new obstacle type or a revised avoidance mode can invalidate part of the prior evidence. The response does not always need to be a complete requalification, but the responsible person should document why a limited regression test is adequate.

Metrics should measure the control, not create false precision. Useful measures include recognition success on startup, warning rate per mission hour, aborted missions caused by sensing anomalies, maintenance findings and repeated controlled-test performance. Avoid publishing a single “detection reliability” percentage unless the test population, target geometry and confidence bounds support it.

11. Procurement and commissioning checklist

Confirm the aircraft is a supported Matrice 4D or Matrice 4 Series model and identify whether dock or controller operation is intended.
Confirm module model LR-01, included adapter bracket, hex keys and dock reflective stickers at receipt.
Record the 235 g mass, 103.3 × 64 × 85.8 mm envelope and environmental limits in the aircraft configuration file.
Review payload combination, endurance estimates, mounting interference and transport arrangements.
Power off before installation; inspect connectors, sealing surfaces, bracket and fasteners.
Activate through the documented dock or controller workflow and record explicit firmware versions.
Verify the LR-01 identity in FlightHub 2 or DJI Pilot 2 and confirm status after restart.
Run a controlled acceptance plan with known targets, multiple approach geometries and negative controls.
Set conservative route speed, stand-off, weather exclusions, alert response and abort criteria.
Create inspection intervals and grounding criteria tied to operating exposure and consequence.
Retain logs, screenshots, photographs, deviations and approvals as part of the operational safety case.

Engineering conclusion

The LR-01 is most valuable when it is attached to a specific hazard-control argument. Its rotating LiDAR and millimeter-wave radar can add sensing diversity, and DJI publishes a meaningful thin-conductor test condition. Those facts justify evaluation for power inspection, industrial corridors and selected dock missions. They do not justify reducing separation, removing human oversight or skipping route analysis.

A mature deployment has five visible properties: the exact configuration is controlled; installation and activation are traceable; performance is checked against representative targets; operational limits remain more conservative than the edge of the published envelope; and anomalies cause review rather than normalization. If a team cannot maintain those properties, the module should remain an unclaimed accessory rather than a credited safety control.

Primary references

Commercial disclosure: This technical article is published by UNITED UAV Official. UNITED UAV sells the product discussed here. Verify current specifications, regional availability, compatibility, firmware requirements and operating rules before purchase or deployment.

View the current DJI Matrice 4D / Matrice 4 Series Obstacle Sensing Module listing at UNITED UAV

UAV Technology Enterprise Operations Safety Engineering

Integrating a 6-14S 180A ESC: Power-Path, SBEC, Thermal, and Commissioning Method

2026-09-20 08:18:16

UNITED UAV

uniteduav@hubzilla.eskimo.com

official-hobbywing-platinum-hv-180a-sbec-v5-esc-6-14s.jpg

Integrating a 6-14S 180A ESC: Power-Path, SBEC, Thermal, and Commissioning Method

An electronic speed controller is often selected by matching three headline numbers: battery cell count, continuous current, and peak current. That is necessary, but it is not an engineering integration. A high-voltage ESC sits at the intersection of the battery, wiring, connectors, motor, propeller or rotor, receiver, flight controller, servos, telemetry bus, cooling path, and fail-safe logic. A mismatch in any one of those interfaces can produce voltage collapse, overheated joints, receiver resets, unexpected motor response, or a protection event at the exact moment the propulsion system is most heavily loaded.

This article uses the HOBBYWING Platinum HV 180A SBEC V5 listing at UNITED UAV as a concrete example. The manufacturer identifies it as product 30209103, specifies a 6–14S LiPo input, lists 180A continuous and 260A peak current, and provides a programmable 5–12V switch-mode BEC rated at 10A continuous and 30A peak. The stated application scope is 550–700-class electric helicopters or fixed-wing aircraft. Those statements define a component envelope; they do not prove that a particular motor, propeller, airframe, connector, installation, or mission is safe. The objective here is to turn the published envelope into a reviewable integration and acceptance process.

1. Convert labels into electrical boundary conditions

Begin with voltage at every relevant state, not the nominal pack label. A standard LiPo cell charged to 4.2V makes a 14S pack approximately 58.8V immediately after charging, while a 6S pack is approximately 25.2V. Confirm the actual battery chemistry, charger termination voltage, series count, and any high-voltage cell setting before connecting the ESC. A controller marked 14S must not be exposed to a pack whose fully charged voltage exceeds the manufacturer's limit. Also account for regenerative or commutation-related voltage excursions; the absence of an over-voltage event on a short bench run is not proof that the installed system will remain inside its limit during rapid unloading.

Current labels need an equally careful interpretation. At 58.8V, 180A represents about 10.6kW of electrical input at that instant; 260A represents about 15.3kW. These arithmetic products are not output-power ratings and are not promises of continuous operation at those levels. Motor efficiency, ESC switching loss, conductor loss, connector loss, cooling air, duty cycle, ambient temperature, timing, PWM strategy, and mechanical load all change the result. The peak rating is especially incomplete without its permitted duration and starting temperature. If the project needs a defined transient, obtain the manufacturer's current-versus-time condition rather than treating 260A as a general operating point.

Create a boundary table with maximum charged-pack voltage, expected steady current, worst credible transient current, transient duration, minimum in-flight voltage, ambient-temperature range, cooling condition, and maximum component temperature. Populate expected current from motor and propeller test data at the actual voltage. A static thrust stand can reveal a high-current point, but it may not reproduce the cooling or dynamic load of flight. A helicopter governor transient, a fixed-wing propeller unloading in the air, and a stalled motor are fundamentally different events. Keep the uncertainty visible instead of hiding it inside a single "maximum amps" cell.

2. Match the motor and mechanical load before tuning the ESC

The motor, gear ratio, rotor or propeller, and pack voltage determine what the ESC must switch. Verify motor Kv, winding configuration, pole count, insulation voltage, phase-current capability, allowable timing range, and manufacturer-recommended controller settings. On a fixed-wing aircraft, propeller diameter, pitch, blade count, air density, and inlet condition can shift current materially. On a helicopter, main-gear ratio, rotor speed, blade loading, governor target, and collective transients shape the load. A current prediction based on a different propeller or a partially discharged pack is not an acceptance test.

Do not use the ESC rating as a target. The desired operating region is one in which measured current, semiconductor temperature, capacitor temperature, wiring temperature, and voltage remain inside documented limits with margin. Select that margin for the consequences of failure and the quality of the test evidence. A commercial fixed-wing platform that depends on one propulsion channel may require a different margin and monitoring plan from a sport helicopter. If the intended aircraft is outside the manufacturer's published application scope—including a multirotor or another UAV architecture—request written compatibility guidance and validate the control mode, motor characteristics, cooling, and fail-safe behavior. The word "high-power" does not make one controller universally interchangeable across aircraft types.

3. Design the battery-to-ESC path as a complete circuit

The official specifications list one red and one black 10AWG input lead, each 255mm, and three black 10AWG motor leads, each 150mm. They also state that input and output connectors are not supplied. That makes connector selection, soldering, insulation, strain relief, and polarity control part of the integrator's responsibility. Select a connector using its documented continuous current, transient current, voltage, contact-temperature rise, mating-cycle life, retention, and environmental suitability. A connector advertised with a large ampere number but tested under unknown conditions is weak evidence for a flight-critical joint.

Keep the high-current loop compact without shortening or extending wires casually. Added battery-lead length increases inductance and can aggravate voltage overshoot at the ESC input. If installation geometry requires longer leads, obtain the controller manufacturer's guidance on added capacitance, capacitor placement, and maximum length. Do not move input capacitors away from the controller or substitute a capacitor solely by matching capacitance; voltage rating, ripple-current rating, equivalent series resistance, temperature, and mechanical support matter. Route positive and negative conductors together to reduce loop area, while maintaining clearance from receiver antennas, GNSS, magnetometers, and low-level sensor wiring.

Use a controlled soldering process. Strip only the required insulation length, prevent loose strands, fully wet the conductor and terminal, limit heat exposure to the controller, and support the joint while it cools. After assembly, inspect for incomplete wetting, solder spikes, heat-damaged insulation, exposed conductor, and a joint that can flex at the solder boundary. Apply strain relief to the cable, not to a fragile circuit-board termination. Verify polarity with a meter and a second-person check before connecting a battery. The manufacturer's Platinum 180A HV SBEC V5 manual specifically warns that poor soldering can cause shorts or damage and instructs users to disconnect the battery after use.

4. Treat inrush and arcing as system behavior

Large input capacitors initially appear close to a short circuit, so plugging in a high-voltage pack can produce substantial inrush current. The manufacturer describes a built-in anti-spark circuit, but this does not remove the need for connector inspection, correct connection order, or a defined arming procedure. Verify the behavior with the actual pack and connector. Repeated pitting, discoloration, softened housings, or increasing connection resistance indicates a problem even when the aircraft still arms normally.

Define an unambiguous safe state for maintenance: propulsion battery disconnected, stored energy allowed to discharge, and the motor treated as capable of starting until verified otherwise. Never use a propeller or rotor as a visual indicator that power is absent. If the airframe has a separate avionics or backup battery, document which systems remain energized after the propulsion pack is removed. Labels, accessible disconnects, and a checklist reduce the chance that a technician works on an apparently quiet but powered system.

5. Engineer the SBEC as an avionics power supply

The built-in switch-mode BEC is specified as adjustable from 5V to 12V in 0.1V increments, with 10A continuous and 30A peak output. This is an interface specification, not permission to set 12V for every receiver, flight controller, servo, or accessory. Build a load inventory showing each device's allowed voltage, steady current, startup current, stall current, and transient behavior. The lowest maximum-voltage limit on the shared rail governs the setting. A single 8.4V-rated device on a nominal 12V bus can be destroyed even if the BEC itself is operating correctly.

Measure the rail at the actual loads. Exercise servos simultaneously, operate landing gear or payload actuators, transmit telemetry, and create the highest credible receiver/flight-controller demand while logging minimum bus voltage. Servo stall current can be far above its moving current, and multiple digital servos can align their peaks. A 30A peak statement is incomplete without duration, input voltage, airflow, and permitted voltage droop. Acceptance should therefore be based on recorded rail voltage, connector temperature, BEC temperature, and device behavior under a scripted load case.

If a backup receiver battery or redundant supply is planned, do not simply parallel sources. Check whether the architecture permits current sharing, reverse current, independent fault isolation, and safe charging states. The manufacturer describes an anti-reverse BEC circuit, but the complete redundancy design still depends on the second supply, wiring, switches, and power-distribution unit. Test loss and restoration of each source without a receiver reset or unexpected motor command. Record which source powers telemetry and the ESC control electronics when the propulsion pack is absent.

6. Make cooling measurable

The manufacturer's product page describes a double-sided heat sink, a side vent, and airflow intended to pass through the controller. Published size and weight—100.6 × 45.5 × 26.1mm and 250.6g—are stated without the fan. The programming interface can also be used to power a cooling fan. Confirm whether a fan is included in the purchased package and whether the intended installation requires it. A component photographed in open air can behave very differently inside a fuselage pocket surrounded by foam, batteries, or stagnant hot air.

Plan an inlet, a path across the heat-rejection surfaces, and an outlet. Avoid a cosmetic vent that pressurizes one corner but leaves a recirculation zone around the controller. Keep debris, loose wiring, and water away from the fan and vents. If ram air is used, evaluate low-speed climb, hover-like operation, ground running, and high ambient temperature—the conditions with the least cooling may coincide with high electrical load. Mount the controller so that structure supports its mass and wires do not carry it, while preserving the airflow path and access for inspection.

Instrument the initial runs. Attach temperature sensors using a repeatable method or use the controller's supported telemetry where validated. Record ESC temperature, capacitor temperature if available, ambient temperature, pack voltage, current, throttle command, RPM, and time. The temperature after landing can be lower than the in-flight peak, so a handheld reading minutes later is not adequate evidence. Establish an abort limit based on manufacturer data, then test the worst expected duty cycle with margin. Protection should remain a last line of defense, not the normal way to discover inadequate cooling.

7. Configure control mode deliberately

The V5 controller supports different aircraft functions, including fixed-wing operation and helicopter governor-related modes described in the manual. The correct choice depends on the aircraft's control architecture. A flight controller that already closes the RPM loop should not unknowingly fight an ESC governor. Conversely, a helicopter governor requires correct motor, gearing, rotor-speed, startup, and autorotation settings. Document who owns the speed loop, what throttle signal represents, and how arming, spool-up, shutdown, and rapid restart are intended to behave.

Start with the manufacturer's documented defaults and change one parameter at a time. Timing, startup force, acceleration, governor gain, brake behavior, freewheeling-related functions, low-voltage response, and motor direction can affect current and mechanical stress. A parameter that makes the motor sound smoother on the bench may increase switching loss or produce an unsafe transient under load. Save the final configuration, firmware version, programming-tool version, and date. A screenshot or exported configuration is much more useful than "configured as usual" in a maintenance log.

The official specification says transmitter programming, LED program cards, and LED program boxes are not supported, while the LCD program box, OTA programmer, a separate program port, and firmware upgrades are supported. Procure and test the required programming path before installation closes access to the controller. Do not assume that a tool used with an older Platinum controller supports this model or firmware. After an update, reload or verify all settings and repeat the relevant acceptance tests; firmware changes should not be treated as clerical maintenance.

8. Validate telemetry as data, not decoration

The manufacturer lists telemetry support including Mikado VBar and Futaba S.Bus2, among other integrations. Protocol support does not guarantee that every receiver, adapter, firmware version, or displayed field is compatible. Build a signal map showing throttle command, telemetry return, ground reference, BEC power, programming connection, and any required adapter. Verify pinout and voltage before mating connectors. A reversed or misidentified lead can damage both the ESC and receiver.

Compare telemetry against independent instruments during commissioning. Check pack voltage with a calibrated meter, current against a suitable current sensor, and RPM against an optical or other independent reference when practical. Look for scale, sign, unit, update-rate, and dropout errors. Then define useful alarms: sustained current above the tested operating region, bus-voltage sag, rising controller temperature, abnormal capacitor temperature, or lost telemetry combined with another symptom. An alarm threshold should trigger a known pilot or autopilot response; filling a screen with unreviewed values does not improve safety.

9. Understand protection functions without relying on them

The product material lists startup, current, temperature, overload, throttle-signal-loss, capacitor-temperature, and input-voltage-abnormality protections. Each protection has a detection rule and an output response. Obtain those details from the applicable manual and firmware, then test what can be tested safely. Does signal loss stop immediately, reduce output, or follow another policy? Does low voltage reduce power or cut it? What indication remains after a protection event? Can the event be distinguished from a loose connector or a flight-controller command?

Protection can prevent some damage, but it cannot make an undersized connector cool, restore a brownout-reset receiver, or keep an aircraft aloft after propulsion is removed. A thermal trip during flight is already a loss of commanded capability. A low-voltage cutoff set for cell protection may conflict with an aircraft's need for controlled landing energy. Coordinate ESC thresholds with battery monitoring and flight-controller actions. Make the earliest safe layer—the flight controller or pilot warning—respond before the controller reaches its protective limit.

10. Use a staged commissioning sequence

Stage one is a document and workmanship review. Confirm product number, firmware, battery range, motor compatibility, wiring gauge, connector selection, solder inspection, insulation, mounting, airflow, BEC setting, receiver voltage limits, signal pinout, and saved parameters. Measure resistance only with methods appropriate for semiconductor equipment; a simple continuity beep can be misleading. Verify that the propulsion area is clear and the airframe is restrained for every powered test.

Stage two is control-power testing with the motor mechanically unable to produce thrust where possible. Power the receiver and avionics through the intended supply path, exercise all servos and accessories, log bus voltage, and test source-transfer behavior. Verify arming logic, throttle range, motor-stop command, signal-loss behavior, and recovery after a controlled power cycle. Where the ESC requires the propulsion battery to run the BEC, use a safe setup that respects its minimum input and arming requirements.

Stage three is low-power motor operation without a propeller or rotor, if the motor manufacturer permits it. Check direction, smooth startup, abnormal vibration, phase connections, telemetry, and shutdown. Never infer loaded performance from this stage: no-load current says little about propeller or rotor demand. Stage four uses the intended mechanical load in a protected test environment with suitable restraint, exclusion zone, fire precautions, instrumentation, and an immediate shutdown method. Increase load in planned steps, pausing to inspect temperature, connectors, wiring, voltage sag, current, RPM, and error indications.

Stage five is an incremental flight program. Begin with conservative duration and maneuvering, then inspect and download logs after each step. Expand toward the worst approved combination of pack state, ambient temperature, sustained power, acceleration, and control-surface or servo activity. Define pass/fail limits before looking at the data. If a connector, capacitor, BEC rail, or ESC temperature approaches its limit, redesign rather than averaging the run with cooler periods.

11. Build an acceptance record that another engineer can audit

The record should identify the exact ESC product number and serial number if available, firmware, airframe, motor, propeller or rotor, gearing, battery chemistry and series count, connector types, wire changes, cooling arrangement, BEC voltage, connected loads, control mode, telemetry protocol, and programmed parameters. Attach photos of the installation and solder joints before they are concealed. Include calibration information for current and voltage instruments, ambient conditions, test sequence, raw logs, plots, anomalies, and corrective actions.

Use a test matrix rather than one successful flight. Rows can cover fully charged and partially discharged packs, low and high ambient temperature, maximum continuous power, acceleration transient, simultaneous servo loading, link loss, telemetry loss, low-voltage warning, and cooling-fan failure if a fan is required. Columns can show expected response, recorded voltage, current, RPM, BEC minimum, controller temperature, connector temperature, error code, and result. Not every fault should be intentionally created at full power; use analysis, simulation, safe bench methods, or manufacturer evidence where destructive testing would create unacceptable risk.

Close every anomaly. A single receiver reset, unexplained RPM discontinuity, damaged connector surface, intermittent telemetry value, or protection flag is not "probably noise" until evidence supports that conclusion. Reproduce it safely, isolate the cause, apply a controlled correction, and repeat the affected tests. Preserve both failed and passed results. This discipline makes later maintenance meaningful because the team has a baseline against which to compare new logs.

12. Maintain the installation as a power system

Inspect connectors for looseness, oxidation, pitting, discoloration, recessed contacts, and softened housings. Check wire insulation where it crosses structure, and verify strain relief and mounting fasteners. Keep the heat sink and air path free of debris. Review capacitor condition and any available capacitor-temperature history. A rise in temperature at the same current and ambient condition may indicate worsening airflow, contact resistance, or component aging. Trend data is more useful than an isolated post-flight touch test.

After motor, propeller, rotor, gearing, battery, connector, wiring length, cooling, firmware, or major avionics changes, identify which acceptance tests must be repeated. A "same cell count" replacement pack can have lower internal resistance and produce a sharper current transient. A more aggressive propeller can overload an unchanged controller. A firmware update can alter defaults or telemetry behavior. Configuration management is therefore part of airworthiness, even on a non-certified experimental platform.

Disconnect the propulsion battery after use as directed by the manufacturer. Store batteries according to their own instructions and protect the controller from conductive debris and moisture. If the ESC has experienced severe overheating, reverse polarity, a short, crash impact, water ingress, or an unexplained protection event, remove it from service pending inspection rather than clearing the fault and flying again. Semiconductor and capacitor damage may not be visible externally.

Procurement and design-review checklist

Confirm product number 30209103, current firmware, included accessories, and whether a cooling fan or programming device is supplied.
Confirm the battery's maximum charged voltage and the motor/propeller or motor/rotor current from relevant test data.
Obtain the permitted duration and conditions behind any peak-current requirement; do not design around an undefined peak label.
Select and validate input and motor connectors because the published specification lists no factory-installed connectors.
Review battery-lead length and any required additional capacitance with the manufacturer before modifying the input path.
Verify every receiver, flight-controller, servo, and accessory voltage limit before setting the 5–12V SBEC.
Measure SBEC voltage during simultaneous actuator loads and test any backup-power architecture for isolation and transfer behavior.
Define an inlet, heat-sink airflow path, and outlet; verify temperature during the worst expected duty cycle.
Document control mode, governor ownership, motor direction, startup, brake, low-voltage response, timing, and fail-safe behavior.
Validate telemetry values against independent instruments and assign a response to each alarm.
Run staged ground and flight acceptance tests with predeclared limits and retain the raw data.
Reassess compatibility if the intended aircraft falls outside the manufacturer's stated helicopter or fixed-wing scope.

Primary product references

Commercial disclosure: This technical article is published by UNITED UAV Official. The linked HOBBYWING Platinum HV 180A SBEC V5 is sold through the UNITED UAV store. The calculations and integration method above do not expand the manufacturer's ratings, certify a specific airframe, or replace the applicable motor, battery, aircraft, and regulatory requirements.

UAV Propulsion ESC Integration Electrical Systems

Roof Inspection with the UIS220: A Field-to-Report Method for Visual and Thermal Evidence

2026-09-12 04:15:57

UNITED UAV

uniteduav@hubzilla.eskimo.com

official-uis220-industrial-drone-for-roof-inspections.jpg

Roof Inspection with the UIS220: A Field-to-Report Method for Visual and Thermal Evidence

A professional roof survey is not a collection of attractive aerial photographs. It is a controlled attempt to answer specific maintenance questions with traceable evidence. Where is the membrane discontinuity? Which flashing detail deserves a closer physical inspection? Has a previously mapped anomaly changed? Can another inspector locate the same feature without guessing from a cropped image? The aircraft is useful only if the flight plan, payload, environmental record, image quality, interpretation rules and final report all serve those questions.

The UNITED UAV UIS220 product listing identifies the aircraft as an industrial inspection platform and offers several selectable configurations. Its default option is described as "Just one drone without any payload." Accordingly, this method never assumes that a thermal camera, telephoto camera, RTK module, cellular module or docking station is included in a particular purchase. Confirm the exact payload and deliverable files before committing to an inspection specification. The practices below are a field method, not a claim that any aircraft can diagnose a roof by itself.

1. Define the decision before defining the flight

Start with the asset, not the drone. Obtain a roof plan or create a simple zone map showing the roof boundary, elevations, access points, drains, parapets, plant, skylights, solar arrays and known repairs. Record the roof-system type and the owner's question. A post-storm screen for visibly displaced components needs different imagery from a condition baseline, a leak investigation or a survey intended to identify candidate wet-insulation areas. For each question, write an observable acceptance condition. "Document every drain and adjacent membrane from at least two useful views" is auditable; "inspect the entire roof thoroughly" is not.

Separate what the imagery can establish from what it can only suggest. Visible photographs can document tears, punctures, open laps, displaced flashing, ponding residue and physical debris when resolution and viewing angle are adequate. They cannot prove the hidden extent of water intrusion. Thermal imagery maps apparent surface-temperature patterns under particular environmental conditions; a warm or cool area is not, by itself, proof of moisture, a leak path or failed insulation. A roof professional should decide which exceptions require a close-up, a moisture meter, a core sample or another accepted verification method. That distinction prevents a colored thermal map from being mislabeled as a repair specification.

2. Treat aircraft configuration as an inspection control

The UIS220 page lists wide-angle, telephoto and thermal imaging capabilities in its product material, alongside optional RTK, 5G and docking-related configurations. The selectable variant, however, must be read literally: the base option says there is no payload. Request an itemized configuration with aircraft, gimbal, exact camera module, controller, batteries, charger, storage media, firmware versions and any licenses or software needed to export original images. Do not infer inclusion from a photograph of a fully equipped aircraft. Verify that the selected thermal module produces the required still images, radiometric data if temperature analysis is in scope, and metadata accessible to the intended review software.

Before the first client mission, capture a short test set over known roof details or a safe equivalent target. Examine unprocessed originals at full resolution. Check whether the wide image resolves seams and small fasteners at the planned standoff, whether the telephoto view remains sharp at the distance needed for safe clearance, and whether a thermal file preserves measurement settings rather than only a color palette. Record the serial numbers and installed payload identifiers in the job file. A specification-sheet pixel count does not replace this acceptance test, because focus, motion blur, compression, viewing geometry and target contrast determine the usable detail.

3. Build a roof-specific hazard map

The takeoff area, roof edge and facade are parts of one operational volume. Mark potential aircraft hazards: rising exhaust, HVAC discharge, cranes, guy wires, antennas, overhead utilities, high parapets, glazing that can confuse visual sensing, narrow light wells and areas where GNSS reception may be poor. Also mark people and property at risk below the flight path. Establish a practical stand-off from the roof and obstacles for the actual aircraft, wind and camera combination; do not borrow an arbitrary distance from another site. If the needed image detail would require an unsafe approach, change lens, viewpoint or inspection method instead of eroding the clearance.

Conduct a preflight that includes propellers, arm locks, battery condition, payload attachment, gimbal movement, storage space, navigation status, return behavior and controller-link quality. Define where the aircraft should go after a link loss or low-battery event, and check whether that route crosses a roof obstacle or occupied area. The product's published maximum flight time is a ceiling stated without conditions specific to this roof, not a usable roof-coverage promise. Reserve enough energy for repositioning, unexpected headwind and an unhurried landing. Confirm the local aviation, site-access, privacy and night-operation requirements applicable to the job; they vary by jurisdiction and cannot be inferred from a product page.

4. Design visual coverage in two layers

Use a context pass to make the roof navigable to someone who was not present. A high-level nadir or near-nadir set can establish roof-zone boundaries, drainage direction, equipment locations and relationships between findings. Maintain deliberate overlap between adjacent frames so that a reviewer can follow one feature across images. If an orthomosaic or dimensional comparison is part of the deliverable, plan the overlap, camera geometry and control for that output rather than assuming every set of overlapping photographs will reconstruct reliably. USGS guidance on UAS image calibration explains why acquisition geometry and ground control affect accuracy; ground sample distance alone is not a positional-accuracy certificate.

Add a detail pass for failure-prone interfaces: penetrations, curbs, expansion joints, edge metal, parapet caps, scuppers, drains and previous patches. Capture each finding with three linked views: a wide locator image, a medium view that shows the surrounding assembly, and a close detail that can support a maintenance decision. A close crop without a locator can be impossible to place on a large commercial roof. Use oblique views to see raised laps or vertical flashing faces that a straight-down image hides. Where a telephoto payload is actually installed, prefer an optically sharp image at a safe standoff; digital enlargement cannot recreate detail that the sensor never captured.

Decide the smallest feature that matters before selecting altitude. A simple planning estimate is ground footprint divided by image pixels along the same axis, but the roof is not a flat calibration chart. Oblique views stretch pixel footprints away from image center, and high-contrast seams may be visible at a different scale from low-contrast punctures. Make a short pilot pass, inspect originals at 100 percent, and adjust height, angle or capture interval. Do not promise that a quoted megapixel number will detect every crack. For repeat surveys, keep the same zone boundaries and document any change in height, lens or viewing angle so apparent differences are not mistaken for roof deterioration.

5. Use thermal imaging as a hypothesis test

The relevant physical signal is heat flow, not a color. After solar heating, different roof areas may cool at different rates; construction layers, retained moisture, shading, surface contamination and reflected radiation all influence the pattern. ASTM C1153-23 addresses night-time infrared location of wet insulation for a defined class of roofs with insulation above the deck in contact with the waterproofing. It covers ground and aerial imaging, environmental conditions and verification, but it does not identify the moisture entry point or establish that a roof is watertight. Do not present a general daytime temperature survey as compliance with that specific practice.

For a thermal assignment, log recent rain, cloud cover, solar exposure, wind, ambient temperature and the inspection time. Note shadows from plant and parapets, wet surface water, reflective metal and differing roof materials. Compare like areas under similar conditions. A hot mechanical unit can reflect in a low-emissivity surface; a dark patch in a palette can simply be a scale choice. FLIR's thermography measurement guidance identifies emissivity, reflected apparent temperature, distance and atmospheric factors as inputs to temperature measurement. Record the settings actually used, and preserve the original radiometric file if quantitative claims are made.

Pair every thermal exception with a visible locator image. Outline the candidate area, note its relation to drains or seams, and assign a confidence level based on repeatability and competing explanations. If the pattern disappears after changing viewing angle, investigate reflection. If it follows a structural bay or a material boundary, investigate construction before calling it moisture. Ask a qualified roof specialist to select a small number of verification points; invasive confirmation may be necessary for a wet-insulation conclusion. A thermal camera cannot see through an opaque roof membrane, and temperature contrast cannot by itself determine a leak's source.

6. Keep geometry and positioning honest

RTK can improve the recorded camera position when an appropriate module, correction source and fixed solution are present. It does not turn every pixel into a survey-grade coordinate, and it does not correct blurred imagery, an inaccurate camera model or a poorly surveyed roof plan. If the deliverable requires measured areas or repeatable coordinates, define the required accuracy with the client and use suitable control and independent check points. Record coordinate reference system, vertical datum where relevant, control method, checkpoints, processing software and residuals. If those elements are absent, describe locations as approximate roof-zone references, not certified measurements.

The USGS calibration guidance distinguishes pixel resolution from geometric accuracy and discusses the roles of tie points and ground control. Apply that lesson to commercial roofs: use repeatable image geometry and well-distributed control where measurement is requested. For simple defect documentation, an annotated roof plan and photo IDs may be more defensible than a superficially precise coordinate. The purpose of location data is to help a crew find the defect, not to create false precision. Provide enough context that a technician can reach the correct penetration or flashing segment without relying on the inspector's memory.

7. Run quality assurance while the aircraft is still on site

Do not leave the site with only a green flight-complete indicator. Review at least one original image from each roof zone and each imaging mode before packing up. Check focus at the corners, exposure on white and dark surfaces, motion blur near edges, shadow loss under equipment, thermal saturation, missing geotags, timestamp drift and whether the final row of images actually covers the roof boundary. Re-fly a failed zone while weather and access are still available. If a camera pauses recording during a battery change, log the gap explicitly.

Use a compact coverage matrix with rows for zones and columns for context, seams, penetrations, drains, edges and thermal frames where applicable. Mark each cell complete, blocked or not applicable. "Blocked" should carry a reason, such as a safety standoff, tenant privacy restriction or equipment shadow. A client can then distinguish an uninspected area from an area with no observed defect. This is more valuable than a large image count: 900 near-duplicate frames can still omit one critical scupper.

8. Classify observations without overstating them

Write an observation in three parts: what the image shows, why it matters, and what should verify it. For example: "The visible frame shows a lifted edge at the north side of drain D-04; water-flow direction and the nearby ponding stain make the detail a priority for close inspection; the aerial image alone does not establish a leak." This wording is actionable without turning an image into a warranty finding. Distinguish observed surface condition from inferred mechanism and from recommended next step.

Use consistent severity labels tied to response, not adjectives. An urgent field check might mean a visibly open penetration above sensitive equipment. A scheduled check might mean a small seam irregularity without an observed opening. A monitor item might mean a repeatable thermal contrast with no visible defect and no confirmatory test. Define the labels in the report so two reviewers do not apply different thresholds. Also record negative evidence: a drain was visible and clear in the captured frames, or a previously photographed patch appears unchanged under comparable lighting. Negative evidence is only meaningful where coverage and image quality are documented.

9. Preserve the evidence chain

Keep original files read-only after transfer. Generate working copies for crops, annotations, orthomosaics and color adjustments, and retain a manifest that maps each derivative to its source. Store capture time, camera/payload identifier, flight or battery number, roof zone, weather notes and operator. If a thermal palette is adjusted, preserve the original temperature data and record the display range used in the report; palette changes can make the same data look more or less dramatic. If software aligns visible and thermal images, verify the alignment around roof edges and vertical objects rather than assuming the overlay is exact.

A simple file convention helps: site ID, visit date, zone, pass, sensor and frame number. The report should refer to stable IDs, not transient filenames assigned by a messaging app. Keep client-sensitive images under an agreed access policy; roofs may reveal security equipment, access routes or occupants. If the inspection is repeated after repair, preserve the baseline, repair record and follow-up separately. Do not silently replace an earlier image with a corrected or sharpened version. An auditable chain lets a second reviewer reconstruct how a conclusion was reached.

10. Deliver a decision-ready report

The first page should state scope, date, weather, roof type if known, equipment configuration, zones covered, zones not covered and the limits of the method. Then provide a roof map with numbered findings. Each finding needs a locator, visible detail, thermal companion if used, concise observation, confidence, reason for uncertainty and recommended field verification. Include an exception table sorted by response priority, not by the order in which frames were captured. If a measured area is supplied, disclose the method and accuracy basis. A color thermal picture without its scale, capture time and paired visible image should not be presented as a diagnostic result.

The final section should answer the commissioning question directly. If the objective was a post-storm visual screen, say which components were checked and which could not be seen. If the objective was candidate wet-insulation mapping, present candidates and verification status without claiming a confirmed moisture footprint before testing. If the objective was a repair closeout, compare equivalent pre- and post-work views and list any differences in acquisition conditions. Attach the image index and raw-data handover instructions. The report should enable an owner to authorize the next physical inspection or repair step with a clear understanding of what the UAV did and did not establish.

11. An example acceptance gate for a commercial roof

Consider a flat-roof site divided into five zones, with two equipment clusters and several drains. Before flight, the owner provides a roof plan and asks for a visual condition baseline plus a thermal screen of candidate insulation anomalies. The operator first checks whether the selected UIS220 configuration actually includes both visible and thermal payloads and whether the thermal export is suitable for the intended analysis. A daytime visual mission maps drains, curbs and perimeter details; a separate thermal mission is scheduled only if roof construction, weather and operating permissions make the method appropriate. These are different capture conditions, not one automatic "multi-sensor" flight.

The acceptance gate is explicit: every zone has a context image; every drain and penetration has a useful medium and detail image; every thermal exception has a visible locator and environmental record; original files and a coverage matrix are delivered; and each inaccessible area is labeled. A reviewer checks image sharpness and source-file links before accepting the report. One verified anomaly may lead to targeted physical testing, while a visually intact area is recorded only as "no visible exception in the acquired views." This scenario avoids inventing a universal flight altitude, a promised defect-detection size or a moisture diagnosis from the image alone.

12. Where the UIS220 fits, and what to verify before purchase

The UIS220 is relevant to this workflow because the official listing positions it for inspection and provides options for wide, telephoto and thermal sensing, with additional modules listed separately. That makes configuration control central to procurement. Ask for the exact camera model and raw-file examples; the installed lens and sensor determine whether the required roof detail is achievable from a safe standoff. Ask how batteries, controller and carrying case are packaged for the chosen variant. Verify whether any RTK or cellular function is included or optional, and test data export and repeatability before promising a client-specific deliverable. Published maximum flight time and link range should remain planning references, not commitments for a cluttered urban roof.

UNITED UAV supplies a broader range of UAV systems and components; this note concerns one roof-inspection application, not the full scope of the brand. A good aircraft selection follows the inspection question, risk envelope and required evidence. If the job requires a thermal moisture survey, obtain the appropriate payload and qualified interpretation. If it requires only visible close-up documentation, a simpler configuration may be enough. The defensible outcome is a traceable roof decision, not a persuasive collection of drone footage.

Method references and product configuration

UNITED UAV UIS220 current product listing and selectable variants. Confirm the selected package and current specifications with the seller.
ASTM C1153-23, Standard Practice for Location of Wet Insulation in Roofing Systems Using Infrared Imaging. Its stated scope is narrower than general roof thermography; full standard text is not reproduced here.
FLIR, Thermographic Measurement Techniques. Measurement settings and reflected radiation matter when interpreting apparent temperature.
USGS, Guidelines for Calibration of Uncrewed Aircraft Systems Imagery. Image resolution and positional accuracy are different properties.

Commercial disclosure: This technical article is published by UNITED UAV Official. The linked UIS220 product is sold through the UNITED UAV store. The operational method and cited standards are not a claim that a particular purchase includes every optional payload, satisfies a jurisdiction's flight rules, or replaces a qualified roof assessment.

UAV Technology Roof Inspection Field Methods

DJI Agras T10 spray tank parts: a code-first replacement checklist

2026-08-30 07:18:14

UNITED UAV

uniteduav@hubzilla.eskimo.com

official-dji-agras-t10-spray-tank-parts-accessories.jpg

Why the material number matters

A spray-tank repair can involve parts that look similar but serve different sealing, filtering, mounting or flow-control roles. The current UNITED UAV listing for DJI Agras T10 Spray Tank Parts & Accessories preserves the item number, material number and English material name for each selectable component. Use all three identifiers when matching a replacement; appearance alone is not enough.

What the illustrated assembly covers

The spray tank and its upper-cover, cover-ring and sealing-pad components.
Inlet and outlet parts, including the inlet filter, filter rubber ring, outlet cover and outlet sealing pad.
One-way-valve shells, plugs, bases and their individual sealing rings.
The liquid-level meter, installation nut and associated sealing ring.
Connection hose, foot pads, tank legs and specified mounting hardware.

Before ordering

Read the material number from the removed part or the aircraft service documentation.
Match the item number, material number, material name and required quantity to the listing variant.
Inspect adjacent hoses, connectors, seals, brackets, tank surfaces and fasteners so a neighboring fault is not missed.
Do not infer compatibility from the product photo; confirm the exact DJI Agras T10 assembly and regional variant where applicable.

After replacement

Power off the aircraft and remove the battery before inspection or installation.
Confirm alignment, connector seating, hose clearance and secure fasteners before operation.
Check the serviced fluid path for leaks and correct operation before returning the aircraft to field use.
Use a qualified technician familiar with DJI Agras T10 maintenance procedures.

UNITED UAV supports a broad range of UAV platforms, components and application workflows; this article focuses specifically on one agricultural-drone spray-tank assembly.

Commercial disclosure: This post is published by UNITED UAV Official and links to a product sold through the UNITED UAV store.

Review the illustrated parts list and current selectable variants

API connection test from UNITED UAV Official.

UAV Technology Maintenance

UAV battery integration checklist: Tattu 14S 20000mAh HV smart battery

2026-08-24 08:13:22

UNITED UAV

uniteduav@hubzilla.eskimo.com

official-tattu-4-0-14s-20000mah-hv-smart-drone-battery-front-view.jpg

UAV integration focus

UNITED UAV's current catalog includes Tattu 4.0/3.5 14S 20000mAh 53.2V HV 25C Smart Drone Battery - Integrated MOSFET / Anti-Spark Modular.

For this 14S HV battery platform, the listing headline specifies 20,000 mAh, 53.2 V and 25C. Treat those values as system-design inputs, not an automatic compatibility guarantee.

Before ordering or integration

Confirm the airframe's 14S voltage window and peak and continuous current demand.
Match the exact connector option and polarity; similar housings are not proof of compatibility.
Verify BMS or DroneCAN integration and the charger's supported battery profile before operation.
Check dimensions, retention, cooling and environmental protection against the aircraft design.

Commercial disclosure: This post is published by UNITED UAV Official and links to a product sold through the UNITED UAV store.

View the current product listing and available configuration

API connection test from UNITED UAV Official.

UAV Technology Product Integration Drone Batteries