28VDC BLDC Fan Control and Electrical Protection for Avionics Cooling

A 28VDC BLDC fan avionics cooling interface is not only an airflow choice. In a defense electronics enclosure, the fan is also an electrical load, a control device, a possible EMI source, and a maintainability item that must behave predictably during startup, speed changes, wiring errors, and rotor blockage.

A late fan substitution can force changes to the power supply, harness, thermal control software, or EMC plan. The practical lesson from avionics integration is simple: the electrical interface of a cooling fan should be frozen before harness fabrication, not discovered during thermal test. For related EMC context, see Military Fan EMC Design.

PWM speed control lets the host system command fan speed according to heat load, mission phase, or enclosure temperature. In many electronics duty cycles, peak heat load may occupy only 20-30% of mission time, so full-speed operation through the entire mission wastes power and raises acoustic output.

PWM frequency, voltage level, duty-cycle range, and loss-of-signal behavior must be confirmed from the product specification. A 25 kHz PWM input and 3.3 V or 5 V logic are common engineering references, but they are not universal requirements. The fail-safe state matters: running at maximum speed on PWM loss protects thermal margin, while stopping on PWM loss is suitable only when redundant cooling or a defined system-level safety case exists.

FG feedback, often implemented as an open-drain tachometer signal, allows the host to detect fan rotation loss before downstream components reach thermal shutdown. A useful integration rule is to define an RPM alarm threshold and a debounce period; for example, a system may flag a fault when measured speed remains 20-30% below commanded speed for 2-3 seconds. The exact threshold belongs in the platform fault-management specification.

A good fan interface specification also states what happens during partial-speed operation. Some systems command a minimum duty cycle to avoid stall-like behavior at very low speed; others prohibit low-speed operation during takeoff, radar transmit, or high-processor-load phases. The fan supplier and system integrator need the same definition of minimum commanded speed before software and hardware are released.

Engineering answer: PWM control and FG/RD feedback signals should be reviewed with the correct reference ground. The PWM control reference is normally tied to the fan negative return, and interface errors can cause unstable speed control, false fault feedback, or signal noise in electrically noisy defense platforms.

Engineering answer: FG feedback is used to monitor fan speed through pulse frequency, while RD feedback is used to monitor run or fault status. FG/RD outputs should normally be wired individually when independent fan monitoring is required; paralleling feedback outputs can hide faults or create ambiguous status signals.

Protection functions are integration requirements, not marketing labels. Reverse-polarity protection matters when fans are serviced under poor lighting or time pressure. Locked-rotor current limiting matters when debris, ice, cable interference, or mechanical deformation prevents the impeller from turning. Soft-start behavior matters when multiple fans start at once on a shared DC bus.

A concrete failure scenario is a blocked inlet after a ground vehicle maintenance event. If the fan attempts to start against an obstructed rotor without current limiting, winding temperature can rise quickly and the host power rail may trip before the thermal controller receives a useful airflow alarm.

The most useful protection documentation describes both the electrical limit and the recovery behavior. A fan that latches off after rotor blockage creates a different maintenance action than a fan that retries after a defined delay. In systems with remote payloads or sealed avionics bays, retry behavior, alarm reporting, and thermal shutdown logic must be coordinated before qualification testing.

• Confirm reverse-polarity protection is active at the hardware level.
• Confirm locked-rotor current limit value and response behavior.
• Confirm startup current and whether soft start is implemented over a defined ramp period, such as 0.5-2 seconds when specified.
• Confirm transient voltage protection against the bus environment invoked by the program.

Engineering answer: A single PWM control signal may be used to command multiple fans when the interface design supports it, but feedback monitoring should be evaluated separately for each fan. For mission electronics, isolated or protected I/O is preferred when the controller ground and fan power return are not naturally shared.

MIL-STD-704 is the main aircraft electric power reference for nominal 28 VDC bus planning, but the allowable voltage and transient envelope depend on the invoked revision and equipment category. RTCA DO-160G Section 16 is relevant for civil aviation power input testing, while RTCA DO-160G Section 21 and MIL-STD-461G CE102/RE102 become relevant when RF emissions are part of the acceptance plan.

A standard name alone does not prove interface compatibility. The supplier review package should identify the operating voltage, cable length, PWM state, load condition, fault state, and measurement setup used for any documented result. This is especially important when the same fan family is configured for different cable, connector, and protection options.

The fan should be treated as part of the platform electrical architecture. If the host harness adds long leads, shield transitions, or shared returns, the measured behavior can differ from a short-lead bench setup. The most reliable review compares the fan, cable, connector, and enclosure grounding plan as one electrical path.

A defensible fan selection package compares electrical behavior with the same discipline used for airflow and static pressure. For SWaP-sensitive platforms, the control strategy also affects power draw and acoustic signature; see SWaP Optimization in Aerospace Cooling for the broader trade space.

• Confirm nominal 28 VDC interface and the allowed program voltage envelope.
• Confirm startup current, steady-state current, and locked-rotor current behavior.
• Define PWM frequency, duty-cycle range, signal level, and fail-safe behavior.
• Define FG output type, pull-up voltage, pulses per revolution, and fault debounce logic.
• Review harness routing, connector pinout, shielding, and grounding before harness fabrication.
• Request product-specific P-Q curves, electrical interface data, and available test documentation before design freeze.