Navigating the Future of ESC Firmware in FPV

In a recent discussion, Ian from MadsRC tackled a pressing issue in the FPV community concerning Electronic Speed Controllers (ESCs) and the firmware they operate on. The abrupt end of BLHeli_32 has left many in the hobbyist community uncertain about the future of their equipment and the integrity of the software being used.

The End of BLHeli_32

This year has marked a significant turning point with the cessation of BLHeli_32, a popular ESC firmware. Ian explained that the reasons behind this closure are complex, rooted in geopolitical issues that have affected the business landscape globally. What was once a thriving enterprise, generating close to a million dollars annually, has unfortunately come to a halt due to factors beyond anyone's control.

BLHeli_32 was a closed-source firmware, meaning manufacturers paid licensing fees for its use, which raised concerns about the accessibility and transparency of the software. With the shutdown of BLHeli AS, the company behind the firmware, there is now a complete lack of new licensing options. This situation raises the question of what alternatives are available for ESC manufacturers.

Emerging Alternatives

As the dust settles, manufacturers have a choice to pivot towards open-source alternatives like AM32 and Escape32. Ian emphasized that while some manufacturers are embracing these options, others have taken a troubling shortcut by shipping ESCs with test versions of BLHeli_32 that were never intended for public use. This practice is alarming, as it poses risks to users who may be unaware of the potential issues these firmware versions might carry.

Ian highlighted that these test versions, often labeled with numbers like 31.10 or 31.92, were designed for internal testing purposes only. They may contain unresolved bugs and limitations, such as arming issues, leaving users vulnerable to malfunctioning equipment. Furthermore, many manufacturers are still utilizing these test versions while simultaneously collaborating with AM32 for legitimate firmware development.

The Community's Responsibility

Ian's frustration is palpable as he calls for the FPV community to take a stand against these practices. He argues that consumers must vote with their wallets, supporting manufacturers who prioritize legitimate software development over those who cut corners. He firmly believes that accepting illegitimate software will only lead to a stagnation in firmware development, ultimately harming the community.

Manufacturers like Skystars and TBS are already producing quality AM32 ESCs, showing that there are viable alternatives that do not compromise user safety and software integrity. Ian encourages users to explore these options and to remain vigilant against products featuring test firmware.

Conclusion: A Call to Action

As Ian wraps up his discussion, he reiterates the importance of transparency and integrity in the FPV community. He pledges not to endorse any products equipped with unlicensed BLHeli_32 firmware going forward, setting a clear boundary for what he will support. The community's collective action will be crucial in shaping the future of ESC firmware and ensuring that manufacturers are held accountable.

To keep the conversation going, Ian invites viewers to share their thoughts in the comments, encouraging a dialogue on how the FPV community can navigate these challenges together.

FAQ

What is BLHeli_32? BLHeli_32 is a closed-source firmware designed for 32-bit ESCs, requiring manufacturers to pay licensing fees.
Why did BLHeli_32 cease operation? The business behind BLHeli_32, BLHeli AS, stopped trading due to complex geopolitical issues.
What are the alternatives to BLHeli_32? Open-source alternatives like AM32 and Escape32 are available and gaining traction among manufacturers.
What should I do if my ESC has test firmware installed? It is advisable to avoid using ESCs with test firmware and to support those manufacturers who provide legitimate software solutions. Stick to AM32 for 32 Bit ESC.

For more insights and updates on this topic, consider supporting Ian's channel on Patreon.