The operating constraint
A customer needed a cooling fan to stop more quickly after power-off. The existing fan continued to coast for approximately 15 to 18 seconds, which was unsuitable near service access and moving equipment. The requirement was a product-level coast-down improvement, not a substitute for the machine's guard, interlock, isolation or emergency-stop design.
The installation allowed only a two-wire fan. Adding PWM or another external control wire was not an option, so the response had to work through the existing supply interface without changing the customer's harness.
- Existing two-wire connection had to remain unchanged.
- The fan footprint could not change.
- The requirement concerned power-off behaviour, not normal speed control.
Engineering approach
The team reviewed the fan behaviour after supply removal and developed a braking approach within the fan electronics. A BLDC fan does not become electrically inert the instant its supply is removed: while the rotor is still moving, the motor can generate back-EMF, and the braking path has to manage that energy without exceeding the fan electronics or customer's power-input limits. The published case keeps the circuit implementation at a high level because the correct design depends on the application and fan platform. The engineering decision also had to protect normal startup, rated-voltage operation, low-voltage behaviour, thermal loading and the life of the motor electronics.
- No added signal wire.
- No PWM-based solution required.
- No footprint change in the customer system.
- Normal run performance and restart behaviour checked alongside coast-down time.
Validation points for a two-wire braking function
A shorter coast-down time is meaningful only when the measurement method and operating condition are defined. The test should start from the same stabilized speed, remove power at the same point, and record the time to the agreed residual-speed or full-stop threshold. Because generated voltage and braking current are related to the motor's speed and electrical characteristics, the initial high-speed portion deserves particular attention. Confirm that braking does not create unacceptable current, voltage transients, back-feed, noise, vibration or heat in the fan or the customer's power system.
- Define whether the target is time to a residual RPM threshold or time to complete stop.
- Repeat power-off tests at rated voltage, operating voltage limits and representative temperatures.
- Check repeated stop-start cycles, low-voltage startup and restart after an interrupted stop.
- Measure supply current, electronics temperature, noise and vibration before and after the change.
- Confirm that the fan does not back-feed or disturb the customer's power input during coast-down.
- Keep guards, interlocks and machine-level emergency-stop controls as the primary safety measures.
Result and relevance
The reported coast-down time was reduced to approximately 7 seconds. That is more than half the original stopping time while preserving the existing two-wire interface. The result is specific to this fan and test condition, so a new application still needs its own acceptance threshold and verification plan.
This approach is relevant where guards, panels or nearby assemblies require a fan to stop sooner after shutdown. It should not be described as an emergency-stop function unless the complete machine, control circuit and risk assessment have been evaluated to the applicable requirements.
- Before: approximately 15–18 seconds.
- After: approximately 7 seconds.
- Published result: faster stopping without an added wire.
- Safety boundary: fan braking supports the product design but does not replace machine guarding or energy isolation.
From a wiring constraint to a tested custom fan
When a standard fan meets the airflow requirement but fails a wiring, stopping-time or integration constraint, MEGA Tech can review the existing two-wire interface and develop a sample around the customer's actual operating sequence. The sample can be checked for normal cooling, power-off behaviour, restart, electrical compatibility and the mechanical conditions around the fan.
After approval, the braking configuration, stop-time method and production acceptance limits should be documented with the fan specification. This gives the customer a repeatable basis for small builds and volume production without changing the interface unexpectedly.
- Review the supply interface, normal operating point and required coast-down threshold.
- Develop and test a two-wire sample without changing the customer's footprint.
- Validate stop-start cycling, voltage limits and electrical compatibility.
- Freeze the approved control behaviour and production inspection method.
Engineer Questions About This Case
The useful lesson is not one stop-time number, but how to define and validate power-off behavior without changing the customer harness.
Q: Why was a standard two-wire fan not enough? A: The fan met the normal cooling need but coasted for approximately 15 to 18 seconds after power-off. The product needed a shorter, defined stop sequence while keeping the two-wire harness.
Q: What was customized? A: The braking behavior was developed inside the fan electronics. No PWM, tachometer or brake wire was added, and the result remained tied to the specific fan, controller, voltage and load.
Q: How was the result measured? A: Start from a defined stabilized speed, remove power at a defined trigger, and measure time to the agreed residual-speed or full-stop threshold. Startup, restart, transients and temperature must be checked as well.
Q: What did the project report? A: Coast-down was reduced to approximately 7 seconds from the original approximately 15 to 18 seconds under the project test condition. This is not a universal stop-time guarantee.
Q: Does fan braking replace a machine safety circuit? A: No. Guarding, interlocks, emergency stop and energy isolation remain functions of the complete machine design.
- Separate project-reported values from general engineering guidance.
- Record the test condition, mounting, voltage, speed and measurement method with every result.
- Use the case questions to define the next sample or validation step.
Talk through a constrained fan design
When a standard fan meets airflow requirements but fails a safety, wiring or integration constraint, share the application conditions with our engineering team. We can review whether a standard configuration or a custom control approach is appropriate.
Define what “power off” means in the equipment
A two-wire fan has no separate control input, so “power off” may mean supply removal, a high-side switch opening, a low-side switch opening, a controlled voltage reduction or an upstream controller entering a safe state. These cases can produce different coast-down behavior and different interactions with a protection diode or shared DC bus. The test plan should name the switching point and measure the voltage at the fan connector, not only at the supply output.
Start with a baseline coast-down trace at the nominal voltage and the installed air path. Record the time from command removal to the first speed change, the time to stop, the bus voltage transient and any reverse or regenerated voltage. Repeat at minimum and maximum expected voltage, at cold and warm conditions, and with the fan mounted as it will be used. Do not infer braking performance from a free-air hand test.
The equipment designer owns the decision about whether a natural coast, an electrical brake or a mechanical stop is appropriate. The fan supplier can provide interface limits and sample observations, but the switch, protection, controller and emergency behavior must be reviewed as a system.
| Condition | Measure | Why |
|---|---|---|
| Nominal supply | Connector voltage, RPM and stop time | Establish baseline behavior |
| Low/high supply | Transient and restart behavior | Check tolerance sensitivity |
| Installed path | Pressure, noise and stop behavior | Avoid free-air assumptions |
| Repeated cycles | Switch stress, heat and timing | Find repeatability issues |
Validate restart and service behavior after braking
A brake that stops the rotor quickly can also make the next start more demanding. Test the restart immediately after power removal, after the defined off time and after a repeated cycle. Record start current, voltage sag, time to stable speed, FG or RD behavior if present, and the protected temperature. If the fan is switched frequently, include the actual duty pattern rather than a single long run.
Check the mechanical consequence of repeated stopping. Braking torque, bearing load, mounting resonance and cable movement can create a fault that does not appear in one cycle. Inspect fasteners, grommets and the fan frame after the test. If the fan is part of a redundant array, confirm that its stopped state does not create reverse flow that steals air from the active fan.
The final requirement should state which behavior is required and why. A short stop time may support a safety or process requirement, while a gentle coast may reduce stress and noise. The right answer comes from the equipment risk and operating sequence, not from assuming every two-wire fan behaves the same way.
Engineer FAQ: two-wire fan power-off behavior
Q: Can a two-wire fan be commanded to brake precisely? A: Only through a defined power and switching architecture that has been validated with the exact fan and application.
Q: Why measure voltage at the connector? A: Cable resistance, inductance and shared loads can make the connector waveform different from the supply waveform.
Q: Does a fast stop prove the design is better? A: No. Compare restart, transient, repeated-cycle, noise, bearing and thermal effects against the actual requirement.
Q: What if the fan coasts too long? A: Review the required stop definition, switching topology and whether a controlled electrical or mechanical solution is appropriate; do not add an unverified clamp.
Q: What should be frozen for production? A: Switch topology, protection, connector, cable length, stop threshold, cycle pattern and restart acceptance.
