> For the complete documentation index, see [llms.txt](https://spaceandtech-engineerings.gitbook.io/space-and-tech-engineerings-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spaceandtech-engineerings.gitbook.io/space-and-tech-engineerings-docs/flight-controller/aazmuth/basic-configuration-and-calibration/escs-and-motor-connection.md).

# ESCs and Motor Connection

This article explains how to connect the ESCs, motors and propellers to Aazmuth.&#x20;

Connect the power (+), ground (-), and signal (s) wires for each ESC to theAazmuth's main output pins labeled M1 to M8 as by motor number Refer to the image below for better understanding. Find your frame type below to determine the assigned order of the motors.

<figure><img src="/files/T4tAsCbeEiyIvVBz187T" alt=""><figcaption></figcaption></figure>

## ESC Calibration Setup

Go to ESC Calibration Tab Under SETUP and then remove the propellers from the motor then follow the instruction given on the screen.

<figure><img src="/files/AvMNXKSVQ0KwJppYthDs" alt=""><figcaption></figcaption></figure>

### Motor order diagrams.

The diagrams below illustrate the motor sequence for each frame type. Propeller rotation is marked in green for clockwise (CW) and blue for counter-clockwise (CCW). The red labels identify the motors to activate during Mission Planner's Motor Test, located under SETUP > Optional Hardware.

#### QUAD FRAMES.

![QUAD PLUS](https://ardupilot.org/copter/_images/m_01_00_quad_plus.svg) ![QUAD X](https://ardupilot.org/copter/_images/m_01_01_quad_x.svg) ![QUAD V](https://ardupilot.org/copter/_images/m_01_02_quad_v.svg) ![QUAD H](https://ardupilot.org/copter/_images/m_01_03_quad_h.svg) ![QUAD V TAIL](https://ardupilot.org/copter/_images/m_01_04_quad_v_tail.svg) ![QUAD A TAIL](https://ardupilot.org/copter/_images/m_01_05_quad_a_tail.svg)

{% hint style="info" %}
**Note**&#x20;

Quad A Tail and V Tail frames do not rely on the front motors for yaw control (NYT). Motor rotation direction is not essential for basic operation. However, without opposite rotation on the front motors, roll and pitch inputs may produce adverse yaw, reducing the effective range of yaw control.
{% endhint %}

![QUAD PLUS (REVERSED)](https://ardupilot.org/copter/_images/m_01_06_quad_plus_rev.svg) ![QUAD X (BETAFLIGHT)](https://ardupilot.org/copter/_images/m_01_12_quad_x_bf.svg) ![QUAD X (DJI)](https://ardupilot.org/copter/_images/m_01_13_quad_x_dji.svg) ![QUAD X (CLOCKWISE)](https://ardupilot.org/copter/_images/m_01_14_quad_x_cw.svg) ![QUAD PLUS (NO YAW TORQUE)](https://ardupilot.org/copter/_images/m_01_16_quad_plus_nyt.svg) ![QUAD X (NO YAW TORQUE)](https://ardupilot.org/copter/_images/m_01_17_quad_x_nyt.svg)

{% hint style="info" %}
**Note**

Quad "No Yaw Torque" (NYT) frames are primarily designed for VTOL tailsitter configurations equipped with large control surfaces. The direction of motor rotation is not critical for these setups. However, unless the motors are configured to spin in the standard opposing directions of a typical quad frame, roll and pitch inputs may cause adverse yaw, which reduces the effective dynamic range of yaw control provided by the fixed-wing control surfaces.
{% endhint %}

![QUAD X (BF REVERSED)](https://ardupilot.org/copter/_images/m_01_18_quad_x_bf_rev.svg) ![QUAD Y4A](https://ardupilot.org/copter/_images/m_01_19_quad_y4a.svg)

#### HEXA FRAMES

![HEXA PLUS](https://ardupilot.org/copter/_images/m_02_00_hexa_plus.svg) ![HEXA X](https://ardupilot.org/copter/_images/m_02_01_hexa_x.svg) ![HEXA H](https://ardupilot.org/copter/_images/m_02_03_hexa_h.svg) ![HEXA X (DJI)](https://ardupilot.org/copter/_images/m_02_13_hexa_x_dji.svg) ![HEXA X (CLOCKWISE)](https://ardupilot.org/copter/_images/m_02_14_hexa_x_cw.svg)

#### TRICOPTER FRAMES

![TRICOPTER](https://ardupilot.org/copter/_images/m_07_00_tricopter.svg) ![TRICOPTER PITCH REVERSED](https://ardupilot.org/copter/_images/m_07_06_tricopter_pitch_rev.svg)

{% hint style="info" %}
**Note**

In tricopter configurations, the tail (or nose) servo handles yaw control, so motor rotation direction is not essential for basic operation. However, unless the front motors rotate in opposite directions, roll and pitch inputs may produce adverse yaw, reducing the effective range of yaw control.

If the tail (or nose) servo moves in the wrong direction in response to yaw inputs, set either the RCn\_REVERSED parameter for the corresponding RC input or the SERVOn\_REVERSED parameter for the tilt servo to 1 (reversing it from 0). For detailed instructions, refer to the TriCopter setup page.
{% endhint %}

#### Recognizing clockwise and counterclockwise propellers

The diagrams above show two types of propellers: clockwise (called pushers) and counterclockwise (called pullers). The most reliable to recognize the correct propeller type by its shape as shown below. The thicker edge is the leading edge which moves in the direction of rotation. The trailing edge is more radical scalloped and usually thinner. ![prop\_direction](https://ardupilot.org/copter/_images/prop-direction.png)

### Testing motor spin directions

If you have completed the Radio and ESC calibration, you can check that your motors are spinning in the correction direction:

1. Make sure there are no propellers on your copter!
2. Turn transmitter on and ensure the flight mode switch is set to Stabilize.
3. Connect battery.
4. Arm copter by holding the throttle down and rudder right for five seconds.
5. If it fails to Arm with the throttle down and to the right and the motors will not spin, it has probably failed the Pre-Arm Safety Check.
   * Pre-Arm safety check failure is also indicated by the red arming light double flashing and then repeating.
   * If the Pre-Arm check fails go to the Prearm Safety Check Page and correct the problem or disable the check before continuing.
6. When you can Arm successfully, apply a small amount of throttle, and observe and note spin direction of each motor. They should match directions shown in the images above for the frame you’ve chosen.
7. Reverse any motor spinning in the wrong direction.

   Tip

   Motor Direction is reversed simply by interchanging two of the

   three ESC to motor power leads.

### Checking the motor numbering with the Mission Planner Motor test

An alternative way to check that the motors have been hooked up correctly is to use the “Motors” test in the Mission Planner Initial Setup menu.

<figure><img src="/files/vUcFJGtkLq605wBjujF4" alt=""><figcaption></figcaption></figure>

When connected to the vehicle via MAVLink, you can click on the green buttons shown above and the corresponding motor should spin for five seconds. Letters correspond to motor numbers as shown in the example below.

* Take off your props first!
* If no motors turn, raise the “Throttle %” to 10% and try again. If that doesn’t work, try 15%

The first motor to spin will be the one located directly forward in the case of + configuration, or the first motor to the right of straight forward in the case of X configuration. The motor test will then proceed in a clockwise rotation.

<figure><img src="https://ardupilot.org/copter/_images/APM_2_5_MOTORS_QUAD_enc.jpg" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://spaceandtech-engineerings.gitbook.io/space-and-tech-engineerings-docs/flight-controller/aazmuth/basic-configuration-and-calibration/escs-and-motor-connection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
