ESC Related Configuration

ESC Protocol

Ardupilot supports several communication protocols with brushless motor ESCs:

• Normal (standard PWM 1000uS - 2000uS pulse widths)
• Oneshot
• Oneshot125 (PWM pulse widths divided by 8)
• DShot150 at 150kbaud (recommended)
• DShot300 at 300kbaud
• DShot600 at 600kbaud
• DShot1200 at 1200kbaud

These are selected by the MOT_PWM_TYPE parameter on Copter or Q_M_PWM_TYPE on QuadPlanes for copter function motors. On Plane, other motors use Normal (PWM) protocol.

Note

The autopilot should be re-booted after changing the protocol type.

However,in Plane, other motors,like the traditional fixed wing’s main motor or Dual Motor Tailsitters (SERVOn_FUNCTION = 70 throttle, 73 throttle left and / or 74 throttle right), can be changed to another protocol using the SERVO_BLH_MASK parameter to specify the output number of the motor together with the SERVO_BLH_OTYPE parameter to select the protocol of these motors independently of that selected for the copter function motors.

Warning

Be sure your ESC can support the configuraton you select for it. Damage can occur otherwise. This includes frame rates discussed below.

PWM ESCs Frame Rates

ArduPilot defaults will work with all PWM ESCs. If the ESC is capable of a higher frame rate than 50Hz then RC_SPEED parameter can be set accordingly. This includes use with OneShot125 ESCs if they support the higher frame rates.

OneShot is a special case. It is Normal PWM, but at a frame rate that is the same as the main loop rate, SCHED_LOOP_RATE .

DShot

The DShot protocol can run at different speeds. ArduPilot supports four speeds:

• DShot150 at 150kbaud (recommended)
• DShot300 at 300kbaud
• DShot600 at 600kbaud
• DShot1200 at 1200kbaud

We recommend using the lowest baud rate, DShot150, as it is the most reliable protocol (lower baudrates are less susceptible to noise on cables). Higher values will be beneficial once ArduPilot’s main loop rate is capable of speeds above 1kHz.

Note

When an output is configured for DShot, the SERVOx_MIN/MAX parameters for that output will always be reset to 1000/2000, respectively, upon every boot, since DShot does not use these parameters and they can affect scaling in other sections of the code. The SERVOx_TRIM value will be reset to 1000 if its a reversible output, or 1500 if normal output setup in DShot.

Autopilot Output Capabilities

While all the servo/motor outputs of an ArduPilot autopilot are capable of Normal PWM operation at 50Hz frame rates, not all are capable of advanced configurations. And, usually, these configurations must apply to pre-designated groups of outputs, even if they are not all driving an ESC. So the following cautions apply:

1. The 8 “MAIN” outputs of autopilots using an IOMCU (like PixHawk and Cube), cannot be used for protocols other than Normal PWM and OneShot. On these autopilots, only the additional “AUX” outputs can properly support OneShot125 and DShot protocols. If you attempt to set a “MAIN” output to DShot, then normal PWM output will occur, even though it has been set to a DShot protocol.
2. For Pixracer and other boards without a separate IOMCU coprocessor, all servo/motor outputs can be used.
3. Groups of outputs sharing a common timer, MUST have the same advanced configuration. Usually, these are specified in the autopilot’s hardware description linked from the Autopilot Hardware Options page. For example, if an output is configured for DShot in a group, then you cannot use another output in that group for Normal PWM ESC or normal PWM servo operation.

BLHeli32 Compatibility

Ardupilot is compatible with BLHeli32 Passthrough and ESC Telemetry Functions:

• BLHeli32 Passthrough
• BLHeli_32 ESC Telemetry
• Connecting your ESCs for use with Dshot protocol and BLHeli_32 features
• Use as Battery Monitor