If the term AM32 has caught your attention recently, you’ve landed in the right place. In this article, we’ll dive deep into the world of AM32 ESC firmware – understanding its core features, unique advantages, and how you can leverage its power for your next FPV drone build.
But first, let’s quickly brush up on our basics. An Electronic Speed Controller (ESC) is a device used in the RC hobby to control the speed of your motors. To do this, every ESC must be loaded with a piece of software – the ESC firmware. Amongst the software available for 32-bit ESCs, BLHeli_32 has long reigned supreme. But there’s a new kid on the block – AM32. Let’s get to know it a bit better, shall we?
Table of Contents
Understanding the Constraints of BLHeli_32
For years, BLHeli_32 has been a staple in the FPV community, favoured for its reliability, efficiency, and rich feature set. But, like any technology, it has its challenges. Despite working fairly well, there’s a sense that it doesn’t tap into the full potential of what’s possible with ESCs.
The primary concern with BLHeli_32 is its closed-source nature. The firmware code is not accessible to the public for tinkering or improvements.
And it doesn’t stop there. For ESC manufacturers, there’s a price tag attached to using BLHeli_32 – a cost typically passed down to us, the consumers.
Enters the AM32 Firmware
This brings us to the AM32 firmware – an exciting development in the drone community. AM32 is an open-source ESC firmware, designed with modern ARM-based ESCs in mind.
What’s great about AM32 is that it doesn’t just trying to match BLHeli_32; in several aspects, it outshines it, such as efficiency and torque generation. This makes AM32 a viable and attractive alternative to the BLHeli_32 ESC. And there’s an added bonus: ESC manufacturers aren’t required to pay for licensing. Consequently, AM32-equipped ESCs can be more cost-effective.
Now, if you’re curious about what AM32 brings to the table, here are some of its compelling features, straight from its official description:
- Open Source firmware
- Firmware upgradable via betaflight passthrough (only support G4, F4 and F7 FCs, and make sure your betaflight
- firmware is up to date when you try to use passthrough)
- Servo PWM, DShot300, DShot600 ESC protocol support
- Bi-directional Dshot
- KISS standard ESC telemetry
- Variable PWM frequency
- Sinusoidal startup mode, which is designed to get larger motors up to speed
- Stuck motor protection
A Word of Caution
Before you dash off to download the AM32 ESC firmware, I feel it’s only fair to offer a word of caution. Remember, this is open-source software. On the one hand, that’s a brilliant thing because it’s continually being refined and improved. On the other hand, it’s a relatively new firmware that you might encounter bugs and issues that are still being worked through.
If the prospect of troubleshooting and problem-solving leaves you a little uneasy, you might be better off sticking with the tried-and-true BLHeli32 ESC for the time being.
How to Flash AM32
If your ESC is already running AM32, then updating and configuring is easy:
If your ESC is running BLHeli_32, and you want to flash it with AM32, you can follow my step-by-step tutorial: https://oscarliang.com/flash-am32-blheli32-esc/
If you’ve decided to give AM32 a try and don’t want to mess with flashing, there’s some good news. Some new ESCs are available on the market with AM32 firmware pre-installed! You can find them here: https://s.click.aliexpress.com/e/_Dm32AXj.
Hardware Compatibility
In terms of hardware compatibility, AM32 currently supports several MCUs including the STSPIN32F0, STM32F051, STM32G071, GD32E230, AT32F415, and AT32F421. It’s pretty versatile, which is yet another feather in its cap.
Not all BLHeli_32 is supported at the moment. For a complete list of supported ESCs, I recommend taking a look at this link: https://github.com/AlkaMotors/AM32-MultiRotor-ESC-firmware/wiki/List-of-Supported-Hardware
If your current ESC is on that list, you’re good to go! If not, don’t fret. Remember, this is an open-source project, which means new hardware is being added to the compatibility list all the time.
Wrapping Up
So, there you have it. AM32 is not just a great alternative to BLHeli32 ESC; it has the potential to become a game-changer in our hobby. By driving down ESC prices and fostering competition, it’s sure to spur innovation.
Personally, I’m always excited to see new open-source initiatives like AM32. They truly put the power in the hands of the user, providing us with the flexibility and freedom to explore and optimize our systems.
However, a final reminder if you’re considering this move: once you transition your existing BLHeli_32 ESC to AM32, there’s no turning back. So weigh your options carefully, and make sure you’re ready for this commitment.
Regardless of the path you choose, I hope this overview has helped you understand AM32 a little better. Here’s to enjoying the ride as we continue to explore new frontiers in this exciting hobby!
6 comments
I know they have just announced the non-continuation of BLHeli.
But QQ, if you can flash the bootloader for AM32 onto BLH ESC’s. Does that mean you could also flash BLH firmware onto an AM32?
No, BLHeli32 was closed sourced and ESC had to be licensed to use their firmware.
Buongiorno, desideravo chiedere una informazione tecnica, ho acquistato un esc flycolor francy 2 da 50A, vorrei cambiare il firmware da blheli32 a am32, per poterlo fare devo caricare un nuovo bootloader tramite st-link v2, la mia domanda è nel circuito dell’esc quali sono i pin swc e swd, desidero sapere anche se non è facile però spero voi potreste aiutarmi chiedendo qualche informazione? grazie
is there any boot-loader available for AT32F435 (I found one for AT32F421 from Alka motors – github). >?
Can you please write an article about AM32 settings and options?
That
This line suggests that the closed source software does not contain bugs. That’s not a fair comparison. If the reader is less experienced with software they may conflate this with open source is bad. The truth is the same types of people are making both, just that some are not sharing their work openly, not accepting community contributions, and charging for their work. Both can have amazing developers. Often open source developers have other jobs which is why they don’t feel the need to charge for their work.