Files
PX4-Autopilot/docs/en/flight_controller
Hamish Willee 79431c0a3c docs(boards): restructure ARKV6X page to the board template (#29587)
* docs(boards): restructure ARKV6X page to the board page template

Move the existing content into the flight-controller page template's
sections, headings and anchors, with no change to what the page says,
so that the content additions that follow can be reviewed on their own.

The flat Sensors, Microprocessor, Other Features, Power Requirements and
Additional Information lists become Specifications sub-sections, Where to
Buy moves after them, and See Also becomes Further Information. Port
labels are in code style, and headings, units and spelling follow the
docs style guide. No page links to the anchors that changed.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): add ARKV6X specifications, PWM outputs and setup sections

Fill in the sections the board page template expects, from the board
source (boards/ark/fmu-v6x) and ARK's own documentation.

- Specifications: core, IO processor, sensor buses, the IIM-42653
  Extended Range variant, interface counts, power monitoring and
  operating temperature
- PWM Outputs: FMU outputs, DShot and bidirectional DShot support,
  timer groups, PX4IO outputs on carriers that have one, and the
  FMU_CAP capture channel
- Power, Voltage Ratings, Ethernet, SD Card, Assembly (Radio Control,
  GPS & Compass, Telemetry, CAN) and Debug Port, describing the ARK PAB
  Carrier where the connectors depend on the carrier
- Serial Port Mapping: flow control column, and GPS1 label
- Version badge, firmware build tip, and links to ARK's current docs,
  datasheet and 3D model

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): fix ARKV6X version badge and voltage ratings

The ARKV6X target was backported to the 1.13 branch and first shipped
in v1.13.1, so the badge said the board wasn't supported on v1.13.x
when it is.

The voltage ratings had been taken from the Pixhawk 6X, and claimed
the power inputs survive up to 10 V. ARK's datasheet gives 4.8 V
minimum and 5.5 V absolute maximum for the module, so use ARK's
figures, with the ARK PAB Carrier's input priority and protection
thresholds from its own page.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): apply ARKV6X review style fixes

Apply the style findings from review: carrier port labels as printed
(UART4/I2C3, RC/SBUS), MCU peripheral names as plain text and device
paths in code, links for the first use of terms the page relies on,
the Radio Controller option label, the carrier's unsupported PPM and
DSM ports, Ethernet speed, mounting hole spacing, and the board's
other build targets.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): apply ARKV6X review minor fixes

Link ARK's and InvenSense's canonical URLs rather than ones that
redirect, give the input voltage range from ARK's datasheet, count
power monitoring by power inputs, and drop casual italics.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): apply ARKV6X review fixes

Apply the fixes from dakejahl's review of #29587, checked against the
carrier schematic and the board source. Correct the stale ARK PAB Carrier
voltage thresholds and warn that inputs above the module's 5.5 V absolute
maximum still pass through. Note that the Extended Range needs v1.14.
Cover DSM binding and power on the RC/SBUS port, FMU_CAP as a PWM output,
encrypted_logs output labelling, and INA238 setup for the 12S PAB power
module. Format the USB pin table on the PAB page.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

* docs(boards): apply ARKV6X board review fixes

A board docs review against the board source and sibling pages found
that the ARKV6X Ethernet uses a static 192.168.0.4 address with no DHCP,
so the defaults on the linked Ethernet setup page don't apply. It also
found that the DSM port can't be read in any build, because it carries
only a timer capture pin, and that the encrypted_logs build loses the
carrier's PX4IO outputs and RC input as well as the output labels. Align
the reference-design and standards links, Ethernet speed and capture-pin
details with the FMUv6X sibling pages, and give the RC/SBUS connector type
from ARK.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>

---------

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
2026-11-04 15:22:39 +11:00
..
2026-03-04 09:45:50 +11:00