# DroneCore 1

<details>

<summary><strong>Page navigation</strong></summary>

*<mark style="background-color:$success;">**DroneCore 1 - YOU ARE HERE**</mark>*

* [**Box content**](/autopilots/dronecore-1/box-content.md)
* **Getting started**
  * [**First time setup**](/autopilots/dronecore-1/getting-started/home.md)
  * **Motor connection**
    * [Soldering motors](/autopilots/dronecore-1/getting-started/motor-connection/soldering-motors.md)
    * [ESC configuration](/autopilots/dronecore-1/getting-started/motor-connection/esc-config.md)
    * [ESC configuration APP (AMC Manager v1.0.0)](/autopilots/dronecore-1/getting-started/motor-connection/amc_manager.md)
    * [ESC configuration APP (AMC Manager v1.1.0)](/autopilots/dronecore-1/getting-started/motor-connection/amc_manager-1.md)
    * [Testing motors](/autopilots/dronecore-1/getting-started/motor-connection/motor_testing.md)
  * [**Ardupilot setup for power boards**](/autopilots/dronecore-1/getting-started/ardupilot-setup-for-.power-board.md)
* **Pilot boards**
  * [**DCS1.Pilot v1.0**](https://gitlab.airvolute.com/doc/dronecore.suite-documentation/-/blob/main/Documentation/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.0)
    * [Power supply](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.0/dronecore.pilot-power-supply.md)
    * [Peripherals](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.0/dronecore.pilot-peripherals.md)
    * [Connectors and pinouts](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.0/dronecore.pilot-connector-description-and-pins-assignment.md)
  * [**DCS1.Pilot v1.2**](https://gitlab.airvolute.com/doc/dronecore.suite-documentation/-/blob/main/Documentation/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.2)
    * [Power supply](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.2/dronecore.pilot-power-supply-1.md)
    * [Peripherals](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.2/dronecore.pilot-peripherals-1.md)
    * [Connectors and pinouts](/autopilots/dronecore-1/pilot-boards/dcs1.pilot-v1.2/dronecore.pilot-connector-description-and-pins-assignment-1.md)
* **Power/PDB boards**
  * [**DCS1.Power**](https://gitlab.airvolute.com/doc/dronecore.suite-documentation/-/blob/main/Documentation/autopilots/dronecore-1/power-pdb-boards/dcs1.power)
    * [Power supply](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/dronecore.power-power-supply.md)
    * [Peripherals](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/dronecore.power-peripherals.md)
    * [Connectors and pinouts](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/dronecore.power-connector-description-and-pins-assignment.md)
    * [Octocopter configuration](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/octocopter-configuration.md)
    * [.Power board diagnostics](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/.power-board-diagnostics.md)
    * [Board firmware update](/autopilots/dronecore-1/power-pdb-boards/dcs1.power/dronecore.power-firmware-update.md)

</details>

![DroneCore.Suite](/files/xYh9mpEL9XpYkY1LqWFg)

**DroneCore.Suite** consists of these main blocks

* **DroneCore.Pilot** - top board for control of the aircraft containing
  * Jetson Xavier NX
  * Cube flight controller
  * Internal 5V power supply
  * Power selector
  * Peripheral connectors
  * USB hub
* **DroneCore.Power** - bottom board with power electronic containing
  * 4 FOC UAVCAN ESCs - 20A permanent / 40A peak current
  * Power sensor (battery voltage and current measurement)
  * Analog inputs for battery cell monitoring
  * SMBUS
  * LED Driver for 4 x WS2812B strips

DroneCore.Suite provides easy to use ROS based software stack supporting development of autonomous applications.

Out of the box device is configured to fly a quadcopter (though flight controller calibration is needed anyway).

#### Specifications:

**Mechanical parameters**

* Weight 247g - including Cube orange, Xavier NX, Xavier heatsink with fan
* Dimensions 115 x 80 x 45mm
* Mount with 4 screws/spacers M3 109 x 74mm
* WiFi module
* WiFi antennas 2pcs

{% hint style="info" %}
**3D model of whole DroneCore.Suite will be added soon.**
{% endhint %}

{% hint style="info" %}
**3D models of DroneCore.Suite accessories will be added soon.**
{% endhint %}

**Electrical parameters**

* Power supply range: 12V – 35V (6S LiHV)
* Integrated DC/DC converter for control circuits
* Redundant power supply with power good monitoring for control unit
* Current protected peripheral connectors
* 4 x FOC UAVCAN ESC 40A, featuring motor identification and motor diagnostics
* Power sensor, SMBUS

**Ardupilot (Cube) Connections**

* PPM input
* PWM output (7 + 7 lines)
* 2x CAN
* 4x UART
* 2x I2C
* Buzzer
* Power sensor input
* ADC input
* Buzzer

**Jetson connections:**

* PCI Express (M2, Key E connector)
* 4 USB 3.0 (ZIF connectors, reductions available)
* Gigabit Ethernet (ZIF connector, reductions available)
* 6 CSI (22 pin)
* 4 GPIO
* UAV CAN, UART, I2C, SPI
* IMU BMI088 and barometer BMP388 on board
* USB 2.0 for debugging
* Micro SD card
* Video output connector (micro HDMI)
* Fan

**DroneCore.Power** (bottom power board)

* 4 x FOC UAVCAN ESCs – 40A peak / 20A permanent
* power sensor, SMBUS,
* LED Driver for 4x WS2812B strips

## Minimum viable configuration

![minimum viable configuration](/files/DmLhy20Edn4HJLO7CA5m)

{% hint style="info" %}
Minimum viable drone configuration consists of DroneCore.Suite assembled with Flight controller unit and Nvidia Jetson, 4 motors, power supply, and receiver for remote control.
{% endhint %}

{% hint style="info" %}
Of course, receiver is not mandatory if drone is controlled via wifi/bluetooth or completely autonomously. However, it is recommended to test flight controller regulators settings with manual control through radio first.
{% endhint %}


---

# Agent Instructions: 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://docs.airvolute.com/hidden-wip/dcs-1/dronecore-1.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.