Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions docs/en/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,7 @@
- [mRo Pixhawk (FMUv3)](flight_controller/mro_pixhawk.md)
- [mRo (3DR) Pixhawk Wiring Quickstart](assembly/quick_start_pixhawk.md)
- [Manufacturer-Supported Autopilots](flight_controller/autopilot_manufacturer_supported.md)
- [3DR Control N1](flight_controller/3dr_ctrl-n1.md)
- [Accton Godwit GA1](flight_controller/accton-godwit_ga1.md)
- [AirMind MindPX](flight_controller/mindpx.md)
- [AirMind MindRacer](flight_controller/mindracer.md)
Expand Down
90 changes: 90 additions & 0 deletions docs/en/flight_controller/3dr_ctrl-n1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
# 3DR Control N1 Flight Controller

<Badge type="tip" text="PX4 v1.18" />

::: warning
PX4 does not manufacture this (or any) autopilot.
Contact [3DR](https://3dr.com/) for hardware support or compliance issues.
:::

The _3DR Control N1_ is a compact, high-performance, low-profile and lightweight flight controller designed and assembled in USA.
It runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.

![3DR Control N1](../../assets/flight_controller/3dr_ctrl-n1/3dr_ctrl-n1.jpg)

::: info
This flight controller is [manufacturer supported](../flight_controller/autopilot_manufacturer_supported.md).
:::

::: tip
This flight controller requires a carrier board to work correctly, visit [3DR](https://3dr.com/) for more information.
:::

## Key Features

- **Processor:** STMicro STM32H743 Arm Cortex-M7 up to 480 MHz, 1 MB RAM, 2 MB flash, 8 MB external flash
- **Sensors:**
- 2x InvenSense IIM-42653 IMU (6-DoF)
- Asahi Kasei AK09940A magnetometer
- Infineon DPS368 barometer
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a variation of the DPS310? I thought the sensor on the board is dps310?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also what my FC docs generator says.

- **Interfaces:**
- 12x PWM motor outputs (DShot, bidirectional DShot, GPIO)
- 7x serial ports (3x with hardware flow control)
- 2x FD-CAN (up to 8 Mbps)
- 2x I2C (up to 400 kHz)
- 1x SPI (up to 40 MHz)
- 4x GPIO (push-pull, direct from MCU)
- 1x USB Full Speed (native STM32H7 port)
- 1x SDIO/SDMMC interface
- 1x addressable LED output (NeoPixel-compatible)
- Serial Wire Debug (SWD)
- **Dimensions:** 28 × 17.6 × 3.7 mm
- **Weight:** 2.32 g
- **Input Voltage:** 4.8 – 6.0 V
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a minimum required input current - and a maximum?

How much current can draw from the ports?

- **Operating Temperature:** -20 to 75 °C

## Building Firmware

::: tip
Most users will not need to build this firmware!
It is pre-built and automatically installed by _QGroundControl_ when appropriate hardware is connected.
:::
Comment on lines +48 to +51
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this true? I assume from PX4 v1.18 it will be


To [build PX4](../dev_setup/building_px4.md) for this target:

```sh
make 3dr_ctrl-n1_default
```

## Connectors

The Control N1 uses three Hirose DF40-series board-to-board connectors:

| Connector | Pins | Signals |
| --------- | ---- | ------------------------------------------------------ |
| J100 | 30 | USART1, USART2, USART3, UART4, SDMMC, USB |
| J200 | 30 | USART6, FDCAN1, SPI, SWD, miscellaneous |
| J300 | 80 | UART7, UART8, FDCAN2, I2C, ADC, Motor outputs CH1–CH12 |

For more information about the pinout, visit [3DR Control N1 Pinout Tool](https://docs.3dr.com/autopilots/control-n1/#pinout).

## Serial Port Mapping

| Port | Connector | Peripheral | Flow Control | Default Function |
| ---- | --------- | ---------- | ------------ | ---------------- |
| SG1 | J100 | USART2 | Yes | TELEM1 |
| SG2 | J100 | UART4 | Yes | TELEM2 |
| SG3 | J300 | UART7 | Yes | User |
| SG4 | J100 | USART3 | No | GPS2 |
| SG5 | J100 | USART1 | No | User |
| SG6 | J200 | USART6 | No | RC input |
| SG7 | J300 | UART8 | No | GPS |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps GPS1


## Debug Port

The [SWD debug port](../debug/swd_debug.md) is exposed on connector **J200**.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should include the tag connect adapter link. Some users won't know how to interface with the SWD plug of nails

A BOOT0 pin is also available on the same connector for firmware recovery.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We often say something about PWM outputs. This is what my (somewhat unreliable) tool says - please check.

NOTE, it is hard to know what to suggest for docs because this requires a carrier board.


## PWM Outputs {#pwm_outputs}

This flight controller supports up to 12 FMU PWM outputs (MAIN).

Outputs:

- Outputs 1-12 support [DShot](../peripherals/dshot.md).
- Outputs 1-11 support [Bidirectional DShot](../peripherals/dshot.md#bidirectional-dshot-telemetry).
- Output 12 supports Bidirectional DShot output only (no eRPM capture).

The 12 outputs are in 3 groups:

- Outputs 1-4 in group1 (Timer1)
- Outputs 5-8 in group2 (Timer2)
- Outputs 9-12 in group3 (Timer4)

All outputs within the same group must use the same output protocol and rate.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to add an RC section. Because this is on a carrier board you probably can't talk to much about the connections. But you should state

  • How the RC is wired - does it have an IO board, and if so, if the RC is to FMU or IO
  • If it is wired to FMU, what rc modules are support.
  • Whether PWM is on the same port or a separate port.

I think this uses COMMON_RC rather than RC input which means you probably support SBUS, DSM/DSMX, CRSF, and GHST receivers on the FMU. Not sure how you support PWM. In any case this means you would need to state that RC is not started by default but must be enabled on the port for the desired protocol

## Further Information

- [3DR Control N1 documentation](https://docs.3dr.com/autopilots/control-n1)
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ This category includes boards that are not fully compliant with the pixhawk stan

The boards in this category are:

- [3DR Control N1](../flight_controller/3dr_ctrl-n1.md)
- [Accton Godwit GA1](../flight_controller/accton-godwit_ga1.md)
- [AirMind MindPX](../flight_controller/mindpx.md)
- [AirMind MindRacer](../flight_controller/mindracer.md)
Expand Down