Rather than relying only on published specifications, we compared the physical PCB layouts, examined component placement, connected both ESCs to the AM32 Configurator, documented their hardware targets, and compared their factory configurations.

When the Just Cuz Robotics Pariah 70A was discontinued, builders immediately began looking for a replacement. Since ItGresa already carries the E-Power Aria 70A AM32, we wanted to answer a simple question: is it really the same ESC, or just another board with similar specifications?

Physical / PCB Comparison

Side-by-side comparison of the E-Power Aria and Pariah boards shows nearly identical component layouts: matching signal wire pad position, matching current shunt resistor (both marked R50m / 50 milliohm) in the same footprint and position, matching MCU footprint, matching gate driver IC placement, and matching FET array layout.

Both board silkscreens read DYS_32BIT_V1.0 — consistent with them being direct DYS/Zhengye reference designs. See notes below on the DYS/E-Power/FlashHobby relationship).

The one visible layout difference is the input protection component near the wire pads, it appears that the E-Power is populated and the Pariah is not — otherwise, the layouts are a direct match.

Firmware & Hardware Target: Confirmed Identical

Manufacturer Spec Comparison

Note on weight: the E-Power figure reflects wire leads attached; the other figures are bare-board weights. We believe that, once measured on a like-for-like basis and accounting for wire weight, all four boards are consistent with each other.

Factory Default Settings Comparison

The E-Power default configuration is clearly set up for drone applications. In general, these are still acceptable for combat robotics, and combat robots ran for years on standard BLHeli configurations. However, with the advent of AM32, it became simple to adjust programs, and the Pariah has been optimized for driving weapons in a combat robotics environment. Here is an analysis of the similarities and differences between the two ESCs’ settings:

AM32 can be programmed with our USB programmer/linker or Grey Skies Automation’s ESC programmer (multiport).

Which Settings Differences Actually Matter

Not every configuration difference carries the same weight. Here’s how we’d rank them, based on Just Cuz Robotics’ published AM32 setup guidance (link).

Tuning preferences, not safety-relevant

• Temperature limit — disabled by default on both boards.
• Low voltage cutoff — disabled by default on both. A tactical choice (preserving some drive if a weapon circuit browns out the battery near end of match), not a hardware risk either way.
• Timing advance, Motor KV, pole count — affect spin-up smoothness and motor sync. These must be matched to your specific motor regardless of which ESC you use.
• Brake on stop, running brake strength — feel and responsiveness only, adjust to preference. Note: braking only works at all if Complementary PWM is enabled (on by default on both boards) — turning that off silently disables all braking.
• Sinusoidal startup — off by default on both, which is correct for combat use. It trades extra low-RPM heat for extra torque, intended for slow-moving RC crawlers, not combat motors.
• Beeper volume — purely a preference. Some builders run it louder to hear it better trackside; no confirmed downside either way.

Does a Pre-Programmed Version Actually Help?

Fair question: AM32 requires Motor KV and pole count to match your specific motor, and no factory default — from any manufacturer — can pre-solve that. So does pre-programming add anything?

It splits into two categories:

• Motor-specific settings (KV, pole count) — no default can help here. You should set these to match your motor regardless of which ESC or configuration you buy.
• Application-specific settings (3D mode, Stall/Stuck Rotor Protection, sinusoidal startup, complementary PWM, low voltage cutoff, temperature limit) — these depend only on whether you’re running a weapon or drive application, which is known ahead of time.

Our pre-configured units handle the second category correctly out of the box — particularly the Stall/Stuck Rotor Protection pair, which is easy to get backwards. As highlighted above, you’ll still need to set Motor KV and pole count yourself to match your motor.

Bottom Line

Board layout, firmware hardware target, physical dimensions — they all line up. And with the settings corrected to match Just Cuz’s recommendation, we think the E-Power Aria 70A AM32 is a solid substitute for the discontinued Pariah. We have a ton of respect for Just Cuz’s expertise and we have adhered to Seth’s guidance on these ESCs. The E-Power Aria 70A is available with the default configuration or pre-configured for weapon-application use.

As always, confirm fitness for your specific application before competition use.

Our preconfigured weapon-application configuration (differences from E-Power’s factory defaults):

• Stall Protection: On (factory default: Off)
• Stuck Rotor Protection: Off (factory default: On)
• 3D mode: Off (already correct as shipped)
• Motor KV / pole count: set to match your specific motor — cannot be pre-configured

Specs and firmware behavior are current as of publication and may change with future firmware updates. If anything here doesn’t match what you find on your own unit, let us know.