The Vortex F80 product page offers AM32 and HF32 firmware selections on a single-ESC platform. That makes the control system an early buying decision: identify how the aircraft or vehicle will command the motor, then select the supplied firmware and quantity. The listed 3–8S power envelope and 80A continuous rating are only part of that selection.
In this guide: specifications · Protocol comes before a firmware preference · Build a serviceable single-ESC installation · Treat firmware changes as a hardware-specific operation · FAQ
OddityRC Vortex F80 3-8S ESC (AM32) at a glance
| Item | Listed detail |
|---|---|
| Input | 10.8–33.6V, listed as 3–8S LiPo |
| Current | 80A continuous / 90A instantaneous burst |
| BEC | 5V 3A |
| MCU | AT32F421 |
| Board dimensions | 36.2 × 24.3mm |
| Options | AM32 / HF32; single, multiple or kit selections |
Protocol comes before a firmware preference
The current listing describes PWM support for the AM32 selection and says the HF32 option does not support PWM. A project that relies on PWM therefore needs that distinction resolved before purchase. Do not choose firmware solely because its name is familiar from a different build.
The page also documents DShot options. Map the selected ESC protocol to the actual flight controller and firmware configuration. Features listed for one supplied firmware are not automatically available in the other, and two ESCs with similar physical boards may still require different setup files.
Build a serviceable single-ESC installation
For a multirotor with separate ESCs, decide how power, signal and ground wiring will reach each unit. Keep the ESC and heatsink accessible enough to inspect the installation. A clean wire route should also leave practical clearance around moving parts and the frame’s service points.
For load planning, use 80A as the listed continuous figure and keep the instantaneous 90A burst separate. The motor, propeller, battery, wiring and airflow define the real operating condition. The 5V 3A BEC also needs a peripheral power plan rather than an assumption that every connection on a build is interchangeable.
Treat firmware changes as a hardware-specific operation
The page warns that moving between AM32 and HF32 is not a freely reversible choice through every method. Confirm the supplied revision, target and supported procedure with OddityRC before changing firmware families. Save the working settings and keep a record of the original selection.
The official AM32 repository is a primary reference for its firmware ecosystem. Use the configuration path appropriate to the exact ESC hardware. The aim is a reproducible setup and recovery route, not an update performed just because a newer file exists.
Before you choose
- Match the required command protocol to AM32 or HF32.
- Check sustained load, cooling and the 5V peripheral plan.
- Choose quantity and kit contents separately from firmware.
Frequently asked questions
Can the HF32 option be assumed to accept PWM?
No. The current F80 listing explicitly says its HF32 option does not support PWM. Confirm the actual control requirements before selecting it.
Is the PDB option a complete ESC kit?
The page lists separate PDB and kit choices. Check the selected variant’s contents rather than relying on the main title.
Does an 8S-compatible ESC make every other component 8S-compatible?
No. The FC, peripherals, BEC arrangement, capacitors and wiring must all be checked for the intended supply.
Explore the configuration
View OddityRC Vortex F80 3-8S ESC (AM32) options and current specifications. Select the exact variant, then check the remaining parts of your build against its requirements.
Sources and related reading
Product details checked on 30 October 2026: OddityRC product listing. Read the related product guide, or browse Last update for the full article archive.
