The History of BLHeli_32 and the Reasons Behind Its Recent Discontinuation: Its Legacy in the FPV Drone Community
Introduction
BLHeli_32 has long been a beloved 32-bit ESC (Electronic Speed Controller) firmware in the FPV (First Person View) drone community. Known for its high performance and reliability, it became an essential tool for drone pilots worldwide. However, in June 2024, BLHeli AS, the Norway-based company behind BLHeli_32, abruptly announced the cessation of its operations, halting all firmware updates and support. BLHeli AS, a small tech firm specializing in drone-related software, left the FPV community in shock with this decision. For longtime users like myself, it was a deeply frustrating blow. In this post, I’ll explore the origins and evolution of BLHeli_32, dive into the reasons for its sudden discontinuation, and discuss its impact and what lies ahead for the FPV world.
BLHeli_32 has long been a beloved 32-bit ESC (Electronic Speed Controller) firmware in the FPV (First Person View) drone community. Known for its high performance and reliability, it became an essential tool for drone pilots worldwide. However, in June 2024, BLHeli AS, the Norway-based company behind BLHeli_32, abruptly announced the cessation of its operations, halting all firmware updates and support. BLHeli AS, a small tech firm specializing in drone-related software, left the FPV community in shock with this decision. For longtime users like myself, it was a deeply frustrating blow. In this post, I’ll explore the origins and evolution of BLHeli_32, dive into the reasons for its sudden discontinuation, and discuss its impact and what lies ahead for the FPV world.
The History of BLHeli_32
The story of BLHeli_32 begins with BLHeli, an open-source project launched in the early 2010s by German developer Steffen Skaug (aka "sskaug"). Designed for ESCs running 8-bit microcontrollers (MCUs)—the processors embedded in the ESC itself, distinct from the flight controller’s MCU—BLHeli offered simple yet efficient motor control that quickly gained traction in the drone community. This was followed by BLHeli_S, a variant supporting 16-bit MCUs, which introduced smoother motor responses and digital protocols like DShot, marking a significant step forward.
The story of BLHeli_32 begins with BLHeli, an open-source project launched in the early 2010s by German developer Steffen Skaug (aka "sskaug"). Designed for ESCs running 8-bit microcontrollers (MCUs)—the processors embedded in the ESC itself, distinct from the flight controller’s MCU—BLHeli offered simple yet efficient motor control that quickly gained traction in the drone community. This was followed by BLHeli_S, a variant supporting 16-bit MCUs, which introduced smoother motor responses and digital protocols like DShot, marking a significant step forward.
BLHeli_32 officially debuted around 2017, built on 32-bit ARM MCUs for vastly improved processing power. Again, this MCU refers to the chip controlling the ESC’s motors, not the flight controller’s processor. Key features included support for high-speed digital protocols like DShot1200, programmable PWM frequencies (up to 48kHz), automatic motor timing adjustments, and current/voltage limiting capabilities. These advancements maximized motor smoothness and efficiency, elevating FPV drone performance to new heights. Paired with BLHeliSuite32—a user-friendly configuration tool integrated with flight controller software like Betaflight—BLHeli_32 was distributed as a closed-source firmware, with licenses sold to commercial ESC manufacturers.
It didn’t take long for BLHeli_32 to dominate the market. Brands like Wraith32, Tmotor, and iFlight adopted it, cementing its status as the standard for 32-bit ESCs. Innovations like bidirectional DShot and RPM filtering further boosted stability and responsiveness, earning it widespread praise among racing and freestyle pilots. Yet, despite its success, external pressures would eventually threaten its reign.
Reasons for Discontinuation: A Collision of Complex Factors
On June 4, 2024, BLHeli AS officially announced the end of BLHeli_32. Their servers went offline permanently with a “maintenance” message, and firmware updates and new licenses ceased. This decision stemmed from a tangled mix of factors.
On June 4, 2024, BLHeli AS officially announced the end of BLHeli_32. Their servers went offline permanently with a “maintenance” message, and firmware updates and new licenses ceased. This decision stemmed from a tangled mix of factors.
Geopolitical Risks and Regulatory Pressure
As a Norway-based company, BLHeli AS operated under the European Union’s legal framework and Norway’s strict export control laws. Following the Russia-Ukraine war in 2022 and ongoing conflicts in Palestine, the EU tightened regulations on technologies that could be used in warfare. Concerns arose that BLHeli_32 might be repurposed for military drones, placing the company in a difficult position—unable to definitively prove or disprove such usage. For a small firm, the regulatory scrutiny and potential legal risks were overwhelming. Their official statement citing “risks tied to a complex geopolitical environment” hints at this struggle.
As a Norway-based company, BLHeli AS operated under the European Union’s legal framework and Norway’s strict export control laws. Following the Russia-Ukraine war in 2022 and ongoing conflicts in Palestine, the EU tightened regulations on technologies that could be used in warfare. Concerns arose that BLHeli_32 might be repurposed for military drones, placing the company in a difficult position—unable to definitively prove or disprove such usage. For a small firm, the regulatory scrutiny and potential legal risks were overwhelming. Their official statement citing “risks tied to a complex geopolitical environment” hints at this struggle.
Economic Sustainability Challenges
BLHeli_32’s closed-source model relied on licensing fees from manufacturers, providing financial support for developers but also driving up maintenance and server costs. As the FPV drone market grew more competitive, open-source alternatives like AM32 emerged, potentially eroding BLHeli_32’s market share and profitability. Some in the community speculate that the company simply couldn’t sustain itself financially, prompting the shutdown.
BLHeli_32’s closed-source model relied on licensing fees from manufacturers, providing financial support for developers but also driving up maintenance and server costs. As the FPV drone market grew more competitive, open-source alternatives like AM32 emerged, potentially eroding BLHeli_32’s market share and profitability. Some in the community speculate that the company simply couldn’t sustain itself financially, prompting the shutdown.
Ethical Dilemmas
There’s also talk of ethical concerns playing a role. Supporting a technology that could be used militarily might have clashed with the developers’ personal values. While this remains unconfirmed, it’s possible that citing “war-related sanctions” was a convenient excuse masking other internal reasons for the closure.
There’s also talk of ethical concerns playing a role. Supporting a technology that could be used militarily might have clashed with the developers’ personal values. While this remains unconfirmed, it’s possible that citing “war-related sanctions” was a convenient excuse masking other internal reasons for the closure.
Impact on the FPV Community
The discontinuation of BLHeli_32 sparked immediate chaos. As someone who’s relied on it for years, I felt a profound sense of loss—like losing a trusted companion. The news hit hard. Existing ESCs with BLHeli_32 will still function, but upgrades or downgrades are no longer possible. On the bright side, BLHeliSuite32 can still connect to tweak settings on installed firmware, offering some comfort. However, a known “spool-up bug” in versions 32.9 and below—where motors randomly spin to max speed—poses safety risks. With the fix in version 32.10 now inaccessible, pilots are left uneasy.
The discontinuation of BLHeli_32 sparked immediate chaos. As someone who’s relied on it for years, I felt a profound sense of loss—like losing a trusted companion. The news hit hard. Existing ESCs with BLHeli_32 will still function, but upgrades or downgrades are no longer possible. On the bright side, BLHeliSuite32 can still connect to tweak settings on installed firmware, offering some comfort. However, a known “spool-up bug” in versions 32.9 and below—where motors randomly spin to max speed—poses safety risks. With the fix in version 32.10 now inaccessible, pilots are left uneasy.
Remaining BLHeli_32 ESC stock won’t receive new features, pushing manufacturers to pivot to alternatives like AM32 or Bluejay. In the short term, this might not be a crisis—existing ESCs remain configurable, and stock should last a few months. Open-source options like BLHeli_S were unaffected, giving the community time to adapt.
Future Outlook: Alternatives and Adaptation
To fill the void left by BLHeli_32, open-source firmware like AM32 and ESCape32 are gaining attention. AM32 mirrors many of BLHeli_32’s features and is actively developed by the community. Bluejay, built for BLHeli_S-based ESCs, is also rising in popularity with performance enhancements. I’ve considered switching to AM32 myself, but flashing it onto existing ESCs feels daunting—compatibility checks, optimization, and the risk of failure make it a time-intensive process. Buying ESCs pre-loaded with AM32 seems like a smarter move. These open-source projects highlight the limitations of closed-source models and could become the new standard for the FPV ecosystem.
To fill the void left by BLHeli_32, open-source firmware like AM32 and ESCape32 are gaining attention. AM32 mirrors many of BLHeli_32’s features and is actively developed by the community. Bluejay, built for BLHeli_S-based ESCs, is also rising in popularity with performance enhancements. I’ve considered switching to AM32 myself, but flashing it onto existing ESCs feels daunting—compatibility checks, optimization, and the risk of failure make it a time-intensive process. Buying ESCs pre-loaded with AM32 seems like a smarter move. These open-source projects highlight the limitations of closed-source models and could become the new standard for the FPV ecosystem.
Manufacturers are already rolling out ESCs with alternative firmware, and while this shift may cause short-term supply hiccups, it promises a more flexible, sustainable future. The FPV community’s resilience has shone through before, and this crisis could spark fresh innovation.
Conclusion
BLHeli_32 played a monumental role in advancing FPV drones, but geopolitical pressures, economic challenges, and ethical considerations brought its journey to an end in 2024. For longtime users like me, it’s a bitter pill to swallow, yet it underscores the value of open-source alternatives. Its history is a testament to the intricate dance between technological innovation and external forces. Moving forward, FPV pilots should maximize their current gear while carefully transitioning to options like AM32. Personally, I’d recommend skipping the hassle of flashing and opting for pre-loaded AM32 ESCs. Change is tough, but as always, our community will adapt and build a brighter future together.
BLHeli_32 played a monumental role in advancing FPV drones, but geopolitical pressures, economic challenges, and ethical considerations brought its journey to an end in 2024. For longtime users like me, it’s a bitter pill to swallow, yet it underscores the value of open-source alternatives. Its history is a testament to the intricate dance between technological innovation and external forces. Moving forward, FPV pilots should maximize their current gear while carefully transitioning to options like AM32. Personally, I’d recommend skipping the hassle of flashing and opting for pre-loaded AM32 ESCs. Change is tough, but as always, our community will adapt and build a brighter future together.
댓글
댓글 쓰기