docs(boards/3dr/ctrl-n1): add 3DR Control N1 flight controller documentation#27406
docs(boards/3dr/ctrl-n1): add 3DR Control N1 flight controller documentation#27406TOTON95 wants to merge 3 commits into
Conversation
github-actions
Bot
added
kind:chore
|
@hamishwillee Here's the documentation for the 3DR Control N1. Please let me know if I need to modify or correct anything. Thanks in advance! |
|
No broken links found in changed files. |
| - **Sensors:** | ||
| - 2x InvenSense IIM-42653 IMU (6-DoF) | ||
| - Asahi Kasei AK09940A magnetometer | ||
| - Infineon DPS368 barometer |
There was a problem hiding this comment.
Is this a variation of the DPS310? I thought the sensor on the board is dps310?
There was a problem hiding this comment.
This is also what my FC docs generator says.
|
|
||
| ## Debug Port | ||
|
|
||
| The [SWD debug port](../debug/swd_debug.md) is exposed on connector **J200**. |
There was a problem hiding this comment.
We should include the tag connect adapter link. Some users won't know how to interface with the SWD plug of nails
|
|
||
| The [SWD debug port](../debug/swd_debug.md) is exposed on connector **J200**. | ||
| A BOOT0 pin is also available on the same connector for firmware recovery. | ||
|
|
There was a problem hiding this comment.
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.
|
|
||
| The [SWD debug port](../debug/swd_debug.md) is exposed on connector **J200**. | ||
| A BOOT0 pin is also available on the same connector for firmware recovery. | ||
|
|
There was a problem hiding this comment.
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
| | SG4 | J100 | USART3 | No | GPS2 | | ||
| | SG5 | J100 | USART1 | No | User | | ||
| | SG6 | J200 | USART6 | No | RC input | | ||
| | SG7 | J300 | UART8 | No | GPS | |
| - Serial Wire Debug (SWD) | ||
| - **Dimensions:** 28 × 17.6 × 3.7 mm | ||
| - **Weight:** 2.32 g | ||
| - **Input Voltage:** 4.8 – 6.0 V |
There was a problem hiding this comment.
Is there a minimum required input current - and a maximum?
How much current can draw from the ports?
| ::: tip | ||
| Most users will not need to build this firmware! | ||
| It is pre-built and automatically installed by _QGroundControl_ when appropriate hardware is connected. | ||
| ::: |
There was a problem hiding this comment.
Is this true? I assume from PX4 v1.18 it will be
hamishwillee
left a comment
hamishwillee
left a comment
There was a problem hiding this comment.
I've added some comments for the docs, but I agree with @dirksavage88.
This is hard to decide how it should be documented. It would be useful to have information on the carrier boards in a separate doc with purchase links.
3 participants
Adds the 3DR Control N1 flight controller page.