Commit Graph
129 Commits
Author SHA1 Message Date
Silvan Fuhrer b4134d75f2 feat(tecs): don't trade altitude for speed above trim airspeed (#29009)
* fix(tecs): don't trade altitude for speed above trim airspeed

With an airspeed setpoint above trim and the throttle at `FW_THR_MAX`, TECS pitches down to
keep chasing the setpoint and settles below the altitude setpoint.
Accelerating above trim should be the throttle's job; losing altitude at high speed is not wanted.

The pitch loop now sees the airspeed setpoint capped at max(trim, current airspeed);
the throttle loop still tracks the full setpoint. Below trim, pitch still trades height for speed, up to trim.
Overspeed above the setpoint is still corrected with pitch.
The cap fades out as the effective `FW_T_SPDWEIGHT` goes from 1 to 2, so gliders (weight 2),
fast descend and underspeed recovery keep using pitch to reach their airspeed.
The behaviour is documented in the TECS docs and the `FW_T_SPDWEIGHT` description.

Signed-off-by: Silvan <silvan@auterion.com>

* fix(tecs): use tas and not tas_sp for the pitch loop

Signed-off-by: Silvan <silvan@auterion.com>

* fix(tecs): don't counter throttle acceleration with pitch above trim

Capping the pitch loop's airspeed setpoint at max(trim, airspeed) keeps
pitch from diving to gain speed, but between trim and the setpoint the
throttle's acceleration still shows up in the kinetic energy rate
estimate. Against a kinetic energy rate setpoint of zero, the pitch loop
then pitches up and turns the throttle's energy into height. At a speed
weight of 1 this halves the acceleration and lifts the vehicle above the
altitude setpoint while accelerating.

Remove the kinetic term, setpoint and estimate, from the pitch loop
between trim and the setpoint, so pitch controls height only there. As
for the cap, this fades out with speed priority.

Point-mass simulation with the TECS defaults, speed step from 15 m/s:
- to 20 m/s: 95% of the step in 21 s instead of 37 s, 1.2 m instead of
  2.4 m above the altitude setpoint
- to 28 m/s, above the 24.7 m/s the vehicle can reach: 2.2 m instead of
  5.2 m above the altitude setpoint, still no altitude loss
- deceleration, climbs, a speed weight of 2 and cruise at trim are
  unchanged; in turbulent cruise above trim the pitch rate RMS is 6%
  higher, as the kinetic term switches when the airspeed crosses the
  setpoint

The remaining rise comes from the lift gained with speed at constant
pitch, which only altitude feedback corrects.

Assisted-by: Claude:claude-opus-5-5

* fix(tecs): fade the pitch loop's kinetic setpoint only once

Between trim airspeed and the airspeed setpoint, the capped pitch loop
setpoint already fades the kinetic energy rate setpoint in with the
speed weight between 1 and 2. Scaling it by the same fade factor again
faded the setpoint quadratically but the estimate only linearly, so at a
speed weight of 1.5 the pitch loop countered acceleration it should only
half ignore. Scale only the estimate.

Speed weights up to 1 and of 2 are unaffected. In a point-mass
simulation at a speed weight of 1.5, a step from 15 to 20 m/s now takes
30 s instead of 37 s and rises 1.6 m instead of 2.4 m, between the
results at weights 1 and 2 instead of worse than both.

Assisted-by: Claude:claude-opus-5-5

* docs(tecs): show the pitch and throttle speed roles in a diagram

The paragraph on how pitch and throttle share speed control above trim
was hard to follow. Show the three regions of measured airspeed (below
trim, between trim and the setpoint, above the setpoint) with what the
pitch and throttle loops do in each, and describe each region in its own
bullet. Also state that there is no middle region with a setpoint at or
below trim.

Assisted-by: Claude:claude-opus-5-5

---------

Signed-off-by: Silvan <silvan@auterion.com>
2026-10-15 08:33:02 +02:00
Hamish Willee 22a4608d1d docs(sensor): restructure LIDAR-Lite rangefinder page (#29191)
The page said the driver is usually present in firmware and gave its key
as drivers/ll40ls. That is only true for the I2C driver: the PWM
connection uses a separate driver, ll40ls_pwm, which is not in the
common distance sensor set.

Add a Firmware Support section covering both drivers, a supported models
table, specifications, pinout and I2C wiring from the Garmin v3 manual,
new I2C and PWM wiring diagrams, per-connection configuration with the
range PX4 uses, and testing instructions. Use Garmin's "LIDAR-Lite"
casing throughout.

Update the rangefinder index entry to match.

Assisted-by: Claude:claude-opus-5-5

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
2026-10-14 02:55:15 +11:00
Anil Kircaliali b2d495019f docs(log): add PX4 ULog Viewer VS Code extension to analysis tools (#28996) 2026-10-14 01:09:53 +11:00
Silvan 026f8d1fa8 docs(fw): define the fixed-wing pitch angle and FW_PSP_OFF
PX4 never said in which frame fixed-wing pitch angles are given, and
FW_PSP_OFF was described as an offset added to the pitch setpoint and as
the angle of attack, which holds only for TECS and Stabilized mode, and
only in level flight measured from the body x-axis.

- Trimming guide: a side-view diagram of the body frame, the pitch angle
  and FW_PSP_OFF, and where FW_PSP_OFF is used.
- Messages: state that pitch setpoints and limits are absolute, drop the
  FRD frame tag on an Euler angle, correct the pitch range to +-pi/2,
  and describe the TECS pitch integrator as a correction term.
  Comment-only, so no message version change.
- Parameters: describe FW_PSP_OFF as the level-flight pitch, mark the
  absolute pitch parameters as such, and describe the asymmetric
  FW_MAN_P_MAX range with a non-zero FW_PSP_OFF.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Silvan <silvan@auterion.com>
2026-10-13 11:36:46 +02:00
Hamish Willee c9b9e4e25e docs(docs): fix link checker errors in uORB summary and external links (#29100)
* docs(msg_docs): sync uORB summary and remove stale pages

The link checker reported SensorsStatusGnss and VehicleGnssHeading as
missing from the table of contents, and SensorGps as an orphan.

SensorGps and EstimatorGpsStatus document messages that no longer exist
(renamed to SensorGnss in #24399 and removed in #28520), so the pages
are deleted. The uORB block in SUMMARY.md now matches the output of
Tools/msg/generate_msg_docs.py.

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

* docs: fix external links reported by the link checker

Updates permanently redirected links to their targets, and points the
discontinued Bitcraze Crazyradio PA and Z-ranger deck v2 links at pages
that still exist.

The 3DR Control N1 link is ignored for 6 months: the site serves a
certificate that does not cover its hostname, which only the vendor can
fix.

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

* docs: remove orphaned images

The two ICE control diagrams were superseded by SVG versions, and the
jMAVSim screenshot was left behind when the jMAVSim docs were replaced
with SIH and Hawkeye. No page in any language references them.

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

---------

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
2026-10-13 02:35:09 +11:00
airpixel-cz 327b87f324 docs(docs): Add AirPixel TAG-E (Sony ILX-LR1 MAVLink camera controller) (#28878) 2026-10-01 16:13:26 +10:00
Silvan 1bcefdd86c feat(docs): improve IC engine docs
- add dedicated page for ICE config and explanation
- update diagrams and screenshots

Signed-off-by: Silvan <silvan@auterion.com>
2026-09-24 12:10:34 +02:00
23890f9988 feat(boards/zenfc): Add ZenFC H743 board support (#28360)
* Add ZenFC H743 board support plus the documentation. 

---------

Co-authored-by: abhishek-kumar-prodev <abhishek.kumar.ubuntu@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Farhang <46557204+farhangnaderi@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-09-22 22:14:50 -07:00
Julian Oes 4565d0db06 docs(boards): flesh out the NWBlue Pro H757 page
Address the review feedback from @hamishwillee: add a board photo,
mechanical and electrical data, a Radio Control section stating that RC
is wired directly to the FMU, and per-connector pinout tables taken from
the manufacturer documentation.

Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Julian Oes <julian@oes.ch>
2026-09-11 15:10:50 +12:00
zhucaiguiandzhucaigui 2c510b8195 feat(boards): add siyi_unifc-6-pico flight controller (#27835)
This adds siyi_unifc-6-pico flight controller board in addition to the docs provided for the same board in this PR. 

Co-authored-by: zhucaigui <zhucaigui@siyi.biz>
2026-09-10 00:31:07 -04:00
7df3dbcc73 feat(boards/agam-robotics): add Agam Robotics FMU-v6XRT board support (#28285)
* feat(boards/agam-robotics): add Agam Robotics FMU-v6XRT board support

---------

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Farhang <46557204+farhangnaderi@users.noreply.github.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-09-08 10:47:44 -04:00
Hamish Willee ba5a120c06 docs(docs): DroneCAN ESC and ark 6rt RC fix (#28503)
* DroneCAN ESC armingstatus and relnote

* Shrink ard6xrt images

* docs(docs): Fix up RC section of docs

* docs(docs): IO module docs include protocols
2026-09-02 13:09:03 +10:00
Alex KlimajandJacob Dahl ed93e5c87c feat(boards): add the ARK FMU-v6XRT (#27161)
* ARKV6X-RT Initial Commit

* icm45686 yaw 270

* iis2mdc yaw 180

* fix(ark/v6x-rt): wrap FLASH_END macro body in parentheses

Fixes clang-tidy bugprone-macro-parentheses.

Signed-off-by: alexklimaj <alex@arkelectron.com>

* update(ark/v6x-rt): modify bootloader binary for enhancements

* feat(ark/v6x-rt): enable LSM6DSV80X IMU on SPI3

Enable the lsm6dsv driver, register the SPI3 chip select with the
LSM6DSV devtype, and start the driver with -T 80 to select the
LSM6DSV80X high-g variant (shared WHO_AM_I 0x73).

Signed-off-by: alexklimaj <alex@arkelectron.com>

* feat(ark/v6x-rt): start IIM-20670 IMU on SPI2

Rotation verified on bench (yaw 90). The driver comes with PX4 PR

Signed-off-by: alexklimaj <alex@arkelectron.com>
#27624; until it merges the start call fails harmlessly at boot.

* fix(ark/v6x-rt): correct SPI3 DRDY2 pin, clang-tidy parens, cleanup

- GPIO_SPI3_DRDY2_SENSOR3 pointed at GPIO_EMC_B2_09 (the buzzer pin); corrected to GPIO_EMC_B2_18 / GPIO2_IO28 per schematic
- parenthesize BOOT_DEVICES_SELECTION / BOOT_DEVICES_FILTER_ONUSB macro bodies (clang-tidy bugprone-macro-parentheses)
- set board_id / BOARD_TYPE to 62
- remove unused ENET INT/RST GPIO macros copied from fmu-v6xrt
- remove duplicate GPIO_VDD_3V3_SENSORS4_EN init-list entry and Configuration banner
- rename fmuv6xrt_* board functions, file headers, include guards, and Kconfig symbols to ark/v6x-rt

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* rename v6x-rt to fmu-v6xrt

* feat(ark/fmu-v6xrt): build the IIM-20670 driver for the SPI2 IMU

rc.board_sensors already starts iim20670, but the Kconfig symbol was left
as a TODO placeholder because the driver was not in tree yet, so the SPI2
IMU never came up. The driver exists now.

Depends on #27624 - the symbol is unknown to Kconfig until that merges.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): declare the IMXRT chip in the board config

Without it Kconfig falls back to ARCH_CHIP_UNSET and every configure warns
"ARCH_CHIP_UNSET was assigned the value 'y' but got the value 'n'".

Cosmetic only - the real chip selection comes from the NuttX defconfig via
CONFIG_ARCH_CHIP_MIMXRT1176DVMAA, and the image is byte-identical either
way. px4/fmu-v6xrt and nxp/tropic-community already declare it.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* feat(ark/fmu-v6xrt): calibrate FlexSPI DLL read strobe at boot

Port of PX4/PX4-Autopilot#28141 (9f4bc80006), which landed on px4/fmu-v6xrt.
The two init.c files were otherwise identical apart from board-specific
names, so this takes the change unmodified.

Corrects the ROM-provided DLL delay by finding the valid DQS sampling range
and selecting its midpoint, for reliable octal-DDR flash reads.

* fix(ark/fmu-v6xrt): declare the SPI2 IMU as an IIM-20670

The LPSPI2 entry still carried the ICM45686 devtype placeholder from before
the driver existed. SPIBusIterator matches a driver to a bus device on
devtype_driver, so iim20670 found no instance and the SPI2 IMU never came up
even with the driver built in.

Depends on #27624 for DRV_IMU_DEVTYPE_IIM20670, same as the Kconfig symbol
already enabled here.

Assisted-by: Claude:claude-opus-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): enable the INA226 by default

rc.board_sensors only starts a power monitor explicitly when one of the
SENS_EN_INA* params is set, and otherwise falls back to i2c_launcher
autostart. With SENS_EN_INA226 left at its 0 default the board always
took the fallback, which never produced a working instance, so the
board had no battery monitor at all.

ark/fmu-v6x already sets this. Verified on hardware: started this way
the INA226 on I2C1 0x41 reads 15.998 V against a 16.007 V bench supply.

Assisted-by: Claude:claude-opus-5[1m]
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): correct the zero-padded DRDY pin macros

GPIO_PIN05 and GPIO_PIN07 do not exist - the NuttX imxrt pin macros are
not zero padded (GPIO_PIN5, GPIO_PIN7). Three DRDY definitions named
them, so any translation unit that expanded GPIO_SPI2_DRDY1_SENSOR2,
GPIO_SPI6_DRDY1_EXTERNAL1 or GPIO_SPI6_DRDY2_EXTERNAL1 would fail to
compile.

Nothing expands them today: the SPI bus description in spi.cpp carries
its own port/pin pairs, and the only other reference is
GPIO_DRDY_OFF_SPI6_DRDY2_EXTERNAL1, which is itself unused. That is why
this has gone unnoticed. Found by writing a bench command that did use
them.

boards/px4/fmu-v6xrt/src/board_config.h has the same three typos and
needs the same fix separately.

Assisted-by: Claude:claude-opus-5[1m]
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): document the board's architecture and SWD flashing

The RT1176 has no internal flash and boots XIP from an external octal NOR
via a boot ROM that reads an FCB and IVT out of the image, which is enough
unlike an STM32 that the flashing procedure looks arbitrary without it.
Covers the differences, the dependencies, and the verified pyocd sequence
for the bootloader and the application.

* feat(ark/fmu-v6xrt): build the heater driver and regulate on the LSM6DSV80X

The heater (R34/Q1 on GPIO2_IO27) is populated and plumbed in
board_config.h but the driver was never built, so the IMUs ran at
ambient. The LSM6DSV80X publishes its high-g channel, whose zero-g
level moves 2 mg/degC (DS14764 Table 3) - an 0.8 m/s^2 walk over a
40 degC swing, enough to trip the accel consistency check - so bind
the heater to that sensor. HEATER1_TEMP stays at the driver default.

* fix(ark/fmu-v6xrt): place SubscriptionIntervalBase in ITCM

The ITCM include list still named uORB::SubscriptionInterval::{updated,copy},
which stopped existing when those methods moved onto SubscriptionIntervalBase<Lb0/Lb1>.
The wildcards fail open, so the two hottest uORB copies ran XIP instead of ITCM.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): float SPIX_SYNC so it cannot fight LSM6DSV INT2

The MCU pin was driven push-pull high into LSM6DSV80X INT2, which idles
low and is active-high. Same net as ark/fmu-v6x, which leaves the pad
as an input with pulldown.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): complain when the IMU hwtype is unknown

The three internal IMUs only start on ARKV6XRT000. A future FMUM id
would previously boot with mag and baro only and no indication why.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): default RC to CRSF on the RC port

COMMON_RC already builds the per-protocol UART drivers, but none of
them were bound to a port, so there was no RC until a user set
RC_*_PRT_CFG. Bind CRSF to the RC serial (300) and leave the
auto-detect rc_input driver out — PPM/DSM-bind is not wanted here.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* feat(ark/fmu-v6xrt): enable SPARTN framing and PPS capture

Parity with ark/fmu-v6x: build the GPS SPARTN framer so PointPerfect
corrections can be injected, and include pps_capture so a mixer
PPS_Input pin can timestamp GNSS TIMEPULSE.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): drive panic LEDs from the real phy_set_led

autoleds.c defined board_autoled_on/off against a local empty
phy_set_led stub because the real one in led.c was static, so
NuttX PANIC/ASSERT never lit an LED. Fold the autoled hooks into
led.c, matching ark/fmu-v6x.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* chore(ark/fmu-v6xrt): drop leftover Kinetis and unused board symbols

automount.c is still the FMUK66 SD automounter and is compiled out.
GPIO_PWM_IN names a pinmux that does not exist, PX4_I2C_BUS_MTD
contradicts mtd.cpp, the Boot Flash Kconfig choice is unread, and
the RUNFROMISRAM copy in imxrt_ocram_initialize.c does not compile
on this XIP board. Also point HW_REV/VER_SENSE at the ADC channels
they actually sample and fix the USDHC pin table.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* perf(ark/fmu-v6xrt): grow the logger RAM buffer to 128 KiB

The imxrt arch default is 64 KiB and the logger already sat at 96 % of
that at rest. The RT1176 has megabytes of OCRAM; another 64 KiB of
ring buffer is cheap insurance against SD write dropouts in flight.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* feat(ark/fmu-v6xrt): publish LPUART11 as the EXT2 serial port

LPUART11 is built as /dev/ttyS7 and brought out on the PAB UART4 pins.
Without CONFIG_BOARD_SERIAL_EXT2 the device node exists but nothing can
bind a protocol to it from the serial-port params.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): enable 64-bit off_t so SD files can exceed 2 GiB

Without CONFIG_FS_LARGEFILE, off_t is 32-bit: a single ULog cannot
cross 2 GiB and df/ls wrap on cards larger than 4 GiB. px4/fmu-v6xrt
gained this in 05be273a35; the ARK defconfig was forked before that.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): sync the FRAM MTD driver and actually erase it

The local copy never advanced the bwrite source, so a multi-page
param save repeated the first 128 bytes, and lacked the word-aligned
bounce buffer from e8a4304e1c. Pull those in from px4/fmu-v6xrt.

Erase was still wrong in both trees: `uint8_t buf[128] = {0xff}` only
sets byte 0, and BULKERASE issued one WREN for 256 page programs.
WEL clears after each write, so only page 0 was programmed. memset
0xff and WREN per page so `mtd erase` blanks the store.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): match ark/fmu-v6x UART buffer sizes

TELEM2 (LPUART8) and EXT2 (LPUART11) were on the NuttX 256 B default.
Copy the v6x sizes by port: console 180/1500, GPS1 TX 1500, TELEM2 RX
800, EXT2 600/1500.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): keep UAVCAN off CAN3, ESC on CAN2 only

PAB pinouts CAN3 but no ARK carrier breaks it out. FlexCAN3 stays built so a different carrier can bring can2 up.

Assisted-by: Grok:grok-4.6
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): drop i2c_launcher

SENS_EN_INA226 is defaulted on, so the auto-detect fallback is unused. Start INA from the param only, like ark/fmu-v6x.

Assisted-by: Grok:grok-4.6
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): keep SENSORS4 up and float BMP INT

SENSORS4 is the BMP390 analog rail, not the SE051. Cycling it off
while VDDIO (FMU_3V3) stays up skips POR. Leave it on after the
first enable. Configure I2C2_DRDY1 as a floating input; INT idles
push-pull low and is unused by the driver.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): start the IIM-20670 last

Sensor instances follow start order, and at equal priority the voter
keeps the lowest instance, so whichever IMU starts first is the primary
by default. The IIM-20670's gyro filter cannot be opened past 60 Hz,
which is several milliseconds of delay ahead of the rate loop; it is a
fallback, not a primary. Start the ICM-45686 first and the LSM6DSV80X
ahead of it.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(rt117x): define PX4_MAKE_GPIO_EXTI

pps_capture builds its GPIO with PX4_MAKE_GPIO_EXTI, which only the
STM32 micro_hal defines. On i.MX RT an EXTI pin is just an input that
imxrt_gpiosetevent() attaches to, so it is the plain input pinset. Needed
for CONFIG_DRIVERS_PPS_CAPTURE on ark/fmu-v6xrt.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* build(ark/fmu-v6xrt): state CONFIG_IMXRT_USDHC_DMA in the defconfig

It is the Kconfig default, so it was already on, but nothing in the
board tree said so and the question of whether SD ran PIO came up twice.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* build(ark/fmu-v6xrt): give the logger a 5000-byte stack

High-water 3092 of 3608 with the logger at 368 KiB/s, the tightest task
on the board. The RT1176 has 1.7 MB of SRAM to spend.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): add an IMU section to the README

Bus, start line, ODR, publish rate and full-scale per IMU, why the
publish rates differ, why the instances are ordered as they are, and the
two caveats that lived only in driver comments and PR text: the
LSM6DSV80X publishing its high-g channel, and the IIM-20670's 60 Hz
gyro filter.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): call out the LSM6DSV80X offset temperature coefficient

The heater exists for this die: its high-g zero-g offset moves ~2 mg/degC, so an accel calibration only holds at the temperature it was done at. Say so, and that calibration and flight both happen with the heater at its setpoint.

* docs(ark/fmu-v6xrt): add the ARKV6X-RT flight controller page

The target shipped with no user-facing page, so it was also absent from
the supported-hardware, PAB-compatible and Ethernet board lists.

Photo, store URL and the mechanical/electrical specs still need to come
from ARK.

Assisted-by: Claude:claude-opus-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): restructure the page to the current board-doc shape

The docs maintainer has been asking every recent board PR for the same
things: a Specifications block, a flow-control column on the serial
table, and Power, PWM Outputs, Radio Control, GPS & Compass and Debug
Port sections with anchors. Match that rather than the older ARKV6X
page, which predates it.

Assisted-by: Claude:claude-opus-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): mark the unpublished specs with TODO

Photo, product page, input voltage, current draw, dimensions and weight
are not public yet. Leave a marker where each belongs rather than a
silent gap, so a reviewer can see what is outstanding and the PR
checklist has something to point at.

Assisted-by: Claude:claude-opus-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): the heater is not specific to the LSM6DSV80X

Every IMU on every ARK board gets a heater; this die is only the most temperature-sensitive one, which is why the heater targets it.

* fix(ark/fmu-v6xrt): regulate the heater on the ICM-45686

HEATER1_SENS_ID pointed at the LSM6DSV80X because its high-g channel drifted 2 mg/°C. The driver now publishes that part's low-g channel (0.07 mg/°C), so the die that flies is the one to hold at temperature. The pad warms the whole board either way; this only picks the feedback sensor.

* fix(ark/fmu-v6xrt): single-IMU selection like ark/fmu-v6x

The imxrt arch defaults turn on multi-EKF (EKF2_MULTI_IMU 3, SENS_IMU_MODE 0), so the EKF2 selector picked the primary by test ratio and at rest it could land on any of the three IMUs. Override to the voter with one primary, as ark/fmu-v6x does.

* fix(ark/fmu-v6xrt): drop the Skynode TELEM2 mavlink autostart

rc.board_mavlink came along with the px4/fmu-v6xrt copy: on base ids 009-011 it starts mavlink at 3 Mbaud on TELEM2 and locks the port. Those ids are Skynode carriers; on an ARK carrier that ever reports one, TELEM2 would be silently taken. ark/fmu-v6x has no such file.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* feat(ark/fmu-v6xrt): whitelist the generic airframes like ark/fmu-v6x

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* chore(ark/fmu-v6xrt): align the driver and module set with ark/fmu-v6x

Add what v6x carriers can use: batt_smbus, payload_deliverer, pca9685_pwm_out (started on PCA9685_EN_BUS like v6x), and the ADIS16507 and SCH16T external IMUs; add the mavlink-dev variant and the rover HIWONDER_EMM. Drop what this board cannot use or does not want: battery_status (no analog battery channels, BOARD_BATT_V_LIST is {-1,-1}), local_position_estimator, septentrio.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* refactor(ark/fmu-v6xrt): name the eighth UART TEL4 like ark/fmu-v6x

The port was EXT2 after the px4/fmu-v6xrt copy, so the same carrier connector is SER_TEL4_* on ark/fmu-v6x and SER_EXT2_* here. One name across the product line.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): correct the PFD frequency comments

SYS_PLL2 PFD3 is 432 MHz, not 216 — the value FlexIO1 divides by 4 to
reach the 108 MHz that BOARD_FLEXIO_PREQ assumes for DShot timing.

Assisted-by: Claude:claude-opus-5[1m]
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* build(ark/fmu-v6xrt): default eth0 to static 192.168.0.4 like ark/fmu-v6x

The two ARK products should present the same ethernet identity. netman writes
the compiled-in default into the carrier EEPROM on first boot, so the v6XRT
left a fresh carrier on DHCP with a ~70 s fallback to 10.41.10.2, an address
nothing at ARK uses, while the v6X has been 192.168.0.4 since #24281.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* perf(ark/fmu-v6xrt): run the DShot cycle from ITCM

Same list as px4/fmu-v6xrt: up_dshot_trigger ran over XIP and its critical section measured 5.6 µs worst case on cache misses at 800 Hz.

Assisted-by: Claude:claude-fable-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): start the onboard baro unconditionally

SENS_INT_BARO_EN gated the BMP390 even though it is started as an external
sensor, so the parameter never meant what it says here, and it is being
replaced by CAL_BAROn_PRIO.

* fix(ark/fmu-v6xrt): receive RC on LPUART6 RX

The NXP v6XRT template single-wires on TX because its RC net is the TX pad. This board wires PAB X1-70 (carrier SBUS/RC pin 2) to LPUART6 RX.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* fix(ark/fmu-v6xrt): pin ICM-45686 as the primary IMU

The three IMUs run at equal voter priority, so the sensor voter selects
the primary by whichever validates first at boot and keeps it — a
non-deterministic race that on a test flight landed the primary on the
LSM6DSV80X instead of the ICM-45686. Seed the ICM's calibration slot with
a higher priority so selection is deterministic; the voter still fails
over to the other IMUs if it degrades.

Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(ark/fmu-v6xrt): add board photos and correct the user page

The remaining TODOs were the photos, store URL, and the v6x electrical/mechanical numbers. The IMU section and serial table still described the LSM6DSV80X high-g channel, a heater on that die, and EXT2.

Assisted-by: Grok:grok-4.6
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

---------

Signed-off-by: alexklimaj <alex@arkelectron.com>
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com>
2026-08-28 22:54:00 -06:00
UlliJohnSMS 59061867d5 docs(docs): add smartmicro rangefinder (#28274) 2026-08-27 15:42:41 +10:00
romain-chiap 258c510a2e docs(docs): reference to Genius Tools for PID tuning (#28272) 2026-08-20 15:00:13 +10:00
Silvan 1becdf229f docs: add more fixed-wing runway takeoff docs, especially for wheel control
Signed-off-by: Silvan <silvan@auterion.com>
2026-08-07 13:32:31 +02:00
Hamish Willee ae5ebc8a80 docs(docs): Flight review tools reorder alpabet. and compress Roboto images (#28163) 2026-08-06 11:30:27 +10:00
YvesSchoenberg d7e1372291 docs(log): add Roboto to flight log analysis tools (#28159)
Add Roboto to the Analysis Tools list on the Flight Log Analysis page,
after Flight Review. Roboto is a robotics data analytics platform with
native ULog support for automating flight log analysis across fleets.

Signed-off-by: Yves <yves.albers@gmail.com>
2026-08-06 11:05:08 +12:00
Hamish Willee 139fba2010 docs(docs): Remove orphan translation docs and images (#28146)
* docs(docs): Remove orphaned images

* docs(docs): Update _sidebar

* docs(docs): Remove orphan translations
2026-08-05 09:02:49 +10:00
cbb0badae7 feat(boards): add Amovlab Flycore support (#27407)
* board(amovlab): add Flycore FMU support

* board(amovlab): polish Flycore board port and docs

* Update boards/amovlab/flycore/src/hw_config.h

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Update boards/amovlab/flycore/src/hw_config.h

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* docs(docs): Subedit/prettier

* docs: expand Amovlab Flycore documentation

* docs: fix Flycore documentation links

* docs: add Flycore product image

* docs(docs): subedit

* docs: document Flycore connector types

* docs: clarify Flycore connector standard note

* boards: address Flycore bootloader and config review

* boards: update Flycore USB vendor string

* boards: update Flycore board ID

* docs: update Flycore board ID

* boards: update Flycore bootloader binary

* boards: update Flycore USB VID/PID

* Add Flycore license overview and update USB PID

* boards: enable pthread mutex types for Flycore

* boards: use allocated Flycore USB PID

* Apply suggestion from @hamishwillee

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-08-04 12:23:48 +12:00
maksimdrachovandHamish Willee da47a168a5 docs(gripper): add DroneCAN EPM setup guide (#28049)
* docs(gripper): add DroneCAN EPM setup guide

Signed-off-by: Maksim Drachov <maksim.drachov@outlook.com>

* docs(docs): subedit

* docs(dronecan): clarify gripper publications

* payload_deliverer: clarify gripper command type

* docs: convert FluxGrip image to PNG

* docs: fix FluxGrip image path

* Update src/modules/payload_deliverer/module.yaml

---------

Signed-off-by: Maksim Drachov <maksim.drachov@outlook.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-08-03 16:08:46 -07:00
Hamish Willee f68a3af4b6 docs(docs): tidy orphans etc (#28113) 2026-07-31 08:55:09 +10:00
jonas 6b03d30fb7 refactor(navigator): split mission_route_cache into its own PR 2026-07-27 08:28:45 +02:00
jonas 62c644465b feat(navigator): create the infrastructure for smart mission join and route-following RTL 2026-07-27 08:28:45 +02:00
Silvan Fuhrer 8424463102 feat(fw_mode_manager): Do first-order-hold altitude ramp also for go-to (#27747)
Instead of climbing/descending with max speed first and then fly straight, fly diagonally to new waypoint.
This aligns the behavior between Mission and Hold modes.
2026-07-23 15:00:54 +02:00
Vincello 656989b1dd docs(corvon_v5): fix labels in connectors diagram (#27893)
Fix swapped TELEM1/TELEM2 labels, CAN1_H pin name, I2C3 label
and a few typos.

Signed-off-by: holydust <holydust@live.ca>
2026-07-16 18:20:46 +10:00
Roman BapstandBalduin 40e61d2429 feat(navigator): Geofence Aware RTL (#27145)
Plan RTL paths that route around geofence boundaries — both inclusion
and exclusion zones — instead of flying straight through them and
breaching. The planner builds a visibility graph over the margin-inflated
geofence polygons and circles and runs Dijkstra to find the shortest
legal return path, falling back to a straight line to the destination
when no valid path exists.

Highlights:
- New reusable libraries: src/lib/dijkstra (generic shortest path) and
  src/lib/geofence (fixed-point geometry, polygon inflation, bitangent
  visibility); the RTL planner lives in navigator/RTLPlanner.
- Visibility graph keeps only bitangent edges and skips edges that poke
  into a forbidden region, greatly reducing edge-cost computation.
- Corner splitting is limited to sharp convex corners.
- Geometry validation: reject self-intersecting polygons and vertices
  outside the fixed-point range; centimeter fixed-point scaling keeps
  orientation tests exact and avoids drift at large distances.
- Failure handling: a Status enum replaces silent bool returns, and
  failures (unbuildable fence, planner capacity overflow, dataman load
  errors, NaN waypoints, destinations that breach the fence) are
  surfaced to the operator via MAVLink warnings/criticals; the planner
  falls back to a straight-line RTL.
- Destination updates are centralized in RTL::setRtlTypeAndDestination;
  the path is replanned only when the destination or geometry changes.
- VTOLs always use the fixed-wing margin (FW loiter radius).
- kMaxNodes is exposed as a Kconfig option (default 100); the feature is
  disabled on flash-constrained boards (FMUv4 and older, various F4/F7).
- Tests: unit tests for the Dijkstra lib, geofence geometry utils, and
  the avoidance planner, plus a MAVSDK SITL test flying an RTL through a
  geofence.
- Documentation: new "Geofence Awareness" section in the RTL docs.

Co-authored-by: Balduin <balduin@auterion.com>
2026-07-09 15:08:27 +03:00
Ramon Roche 2f459921f6 docs: add official PX4 developer kits and manufacturer program
Document the Official PX4 Developer Kit program: a new top-level
Developer Kits section listing the certified kits (ModalAI Starling 2
Max, DroneBlocks DEXI 5, Holybro X500 v2), a new DEXI 5 page, and a
manufacturer-facing page describing the program requirements, benefits,
and eligibility.

Restructure the hardware navigation so all certified kits live in one
place instead of being split across Complete Vehicles and Kits, drop
discontinued build guides from the sidebar (still linked from the kit
build guides page), and group the manufacturer guides under a new
Manufacturers section in Development > Hardware.

Signed-off-by: Ramon Roche <mrpollo@gmail.com>
2026-07-02 12:15:03 -07:00
Gennaro GuidoneandMatthias Grob b8c5f66af0 feat(manual_control): replace stick override threshold with double-flick gesture (#27041)
* feat(manual_control): trigger RC override on stick velocity

COM_RC_STICK_OV is now a velocity threshold (1/s) instead of a deflection percentage.
Default 3.0, range [1.0, 10.0]. A stick held statically cannot trigger override.

* docs(manual_control): update COM_RC_STICK_OV description for velocity-based override

* feat(manual_control): gate RC override with sign-consistency check

* fix(ManualControl): lower threshold and filter constant for RC override, add tests for MovingDiff

* refactor(commander): merge RC override params into COM_RC_OVR_SPEED

Replace the COM_RC_OVERRIDE bitmask + COM_RC_STICK_OV threshold with a
single float COM_RC_OVR_SPEED (stick override velocity, 0 = disabled).
Override now applies uniformly in auto and offboard modes.

- ManualControl: rename param, treat 0 as disabled (FLT_EPSILON guard)
- Commander: drop the per-mode bitmask gate and the RcOverrideBits enum
- param_translation: migrate COM_RC_OVERRIDE on import (enabled -> 1.0,
  disabled -> 0.0) and drop the unit-incompatible COM_RC_STICK_OV value
- docs: collapse the two params into one across the mode pages

* fix(manual_override): Move configuration to manual_control module

with MAN_OVERRIDE_SPD parameter and a negative value disabling the feature. All other logic stays in Commander.

* docs(releases): add release note for RC override rework (MAN_OVERRIDE_SPD)

---------

Co-authored-by: Matthias Grob <maetugr@gmail.com>
2026-07-01 14:59:52 +02:00
CUAV ChenandHamish Willee 73c51abfe3 feat(boards): cuav/x25-mega board support (#26664)
---------

Signed-off-by: Ramon Roche <mrpollo@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-06-29 19:04:51 -07:00
VincelloandHamish Willee 9ef2131d3b feat(boards): add corvon_v5 flight controller (#26286)
* add files

* add corvon_V5 docs

docs: fix connectors image path

* docs: address Copilot formatting suggestions

* Subedit

* docs: add radio control wiring details for corvon_V5

* Update docs/en/flight_controller/corvon_V5.md

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>

* boards/corvon: rename V5 subdirectory to v5

This renames the corvon_V5 board to corvon_v5 to conform to PX4 lowercase naming conventions as requested by @mrpollo. Renames target files, docs, and assets accordingly.

* Apply suggestion from @hamishwillee

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>

* docs: add DSU7 debug port pinout and warnings for corvon_v5

This addresses reviewer feedback to include debug port information, placed immediately after the Radio Control section as requested.

* Apply suggestion from @hamishwillee

* fix(boards/corvon_v5): remove unused heater and temperature_compensation

- heater: board has no IMU heater; fixes build after #26325 (requires HEATER_NUM)
- temperature_compensation: modern IMU doesn't need it, follow #27015

Signed-off-by: holydust <holydust@live.ca>

* docs(update): Subedit. Add pwm outputs and gps

* Update docs/en/flight_controller/corvon_v5.md

* Update docs/en/flight_controller/corvon_v5.md

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>

* docs(corvon_v5): add UART flow control, power details, fix broken links

* docs(corvon_v5): fix UART table typo

* fix(boards/corvon_v5): remove unused PX4IO macros. Board has no PX4IO co-processor

Signed-off-by: holydust <holydust@live.ca>

* Apply suggestions from code review

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>

* docs(corvon_v5): update board images

Signed-off-by: holydust <holydust@live.ca>

* fix(corvon_v5): drop unused dshot, fix can3 and adc comments

- Remove CONFIG_DRIVERS_DSHOT=y from default.px4board: DShot is not
  supported on this board (no IO timer is DShot-configured) and the
  docs already state it as unsupported.
- Fix ADC1_IN8 GPIO list comment from PB8 to PB0 (PB0 is the correct
  pin on STM32F765; matches GPIO_RSSI_IN definition below).
- Clarify CAN3 comment in nuttx-config board.h: the pins are unused
  on CORVON_V5 (no transceiver populated). manifest.c already marks
  CAN3 as not present.
- Update corvon_v5_pinout.xlsx 'All Pinouts' sheet so PA7 (HEATER)
  and PA8/PA15/PH4 (CAN3 RX/TX/SILENT) read 'Unused', matching the
  actual hardware.

Signed-off-by: holydust <holydust@live.ca>

* fix(corvon_v5): use MCS Electronics USB VID/PID

Set VID/PID to 0x16D0/0x152A (MCS Electronics) in the app defconfig
and regenerate the bootloader binary, replacing the 3DR FMUv5 IDs
inherited from the reference config.

Signed-off-by: holydust <holydust@live.ca>

---------

Signed-off-by: holydust <holydust@live.ca>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-06-29 14:37:40 -07:00
a1d8a605e8 feat(drivers): add Sony AS-DT1 distance sensor driver (#27769)
* Add Sony AS-DT1 Distance Sensor and Documentation

* Ensuring Rotation Parameter works

* Sony ASDT1 Sensor and Documentaiton

* Fixed formatting and added additional comments

* Forgot to stage 1 formatting issue

* fix(drivers): use AS-DT1 parameters consistently

remove the Sony-ASDT1 -R command line rotation, as well as some other small fixes. Updated the docs to reflect this as well.

* refactor(drivers): clarify Sony AS-DT1 variable names

---------

Co-authored-by: Sean Hickey <sean@ascendengineer.com>
Co-authored-by: Andrew Brahim <35986980+dirksavage88@users.noreply.github.com>
2026-06-29 14:33:20 -07:00
Gennaro Guidone 2a0e048171 feat(mc_att_control): feedforward filtered q_d derivative on rate sp (#27255)
Add a 2nd-order critically-damped attitude reference model whose angular-velocity output is fed forward onto the rate setpoint, removing the steady-state ramp-tracking lag of the pure-P attitude law. The model uses an exact closed-form discretisation, so it is unconditionally stable.

Parameters:
- MC_REF_W_N     reference-model bandwidth [rad/s]
- MC_REF_FF      feedforward gain [0..1]; 0 disables the anticipation
- MC_REF_FF_MAX  per-axis feedforward saturation [deg/s]

The commanded yaw rate is always fed forward at unity (it is a setpoint, not a model prediction), so MC_REF_FF scales only the error-driven anticipation and MC_REF_FF=0 is the exact legacy pure-P law. Shipped disabled by default to avoid changing behaviour on existing platforms; enable per-airframe. Includes docs and the updated controller diagram.
2026-06-26 10:57:48 +02:00
Alexis Guijarro e91f5af898 docs(boards/3dr/ctrl-n1): add 3DR Control N1 flight controller documentation (#27406) 2026-06-18 14:49:40 +10:00
Ramon Roche ea22f5479e docs(narinfc/h7): add flight controller documentation
Add hardware documentation for the VOLOLAND NarinFC-H7 flight controller
including pinouts, serial port mapping, PWM output groups, and analog
inputs. Fix version badge to v1.17 and clarify RC_IN is wired directly
to FMU via RC_INPUT driver.

Based on work by @vololand and @hamishwillee from PR #26542.

Signed-off-by: Ramon Roche <mrpollo@gmail.com>
2026-06-16 13:11:02 -07:00
Julian Oes 05db354ac9 feat(gz): update submodule, and add ridge docs (#27600)
* feat(gz): update submodule, and add ridge docs
2026-06-10 11:24:41 +10:00
VincelloandHamish Willee f808ed1560 feat(boards): add corvon_743v2 flight controller (#27569)
feat(boards): add corvon_743v2 flight controller + Documentation

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-06-08 17:42:26 -04:00
Julian Oes f94aedf1f0 feat(boards): add CBUnmanned H753-SOM flight controller (#27234)
* feat(boards): add CBUnmanned H753-Stamp flight controller

* Update board_id to 1302

* docs: update CBUnmanned H753-Stamp board docs

Apply review feedback: correct the I2C bus count (add internal bus),
clarify SPI (IMUs on a dedicated internal bus), note the debug console
alongside the user UARTs, and describe how the board is powered from an
external 5 V supply with separate battery voltage sensing.

Add the pinout image and a PWM Outputs section.

Signed-off-by: Julian Oes <julian@oes.ch>

* refactor(boards): rename CBUnmanned H753-Stamp to H753-SOM

Rename the board directory, build target (cbunmanned_h753-som), USB
product strings, docs page, asset directory and pinout image, and the
bundled bootloader binary from -Stamp to -SOM. The hardware is a
System-on-Module, so SOM is the accurate name.

Signed-off-by: Julian Oes <julian@oes.ch>

---------

Signed-off-by: Julian Oes <julian@oes.ch>
2026-06-03 06:40:19 +12:00
Hamish Willee ac4efcf83e docs(docs): Ark6s shrink images (#27477) 2026-05-27 17:47:37 +10:00
Jacob Dahl 773967b547 docs(arkv6s): add flight controller documentation (#27383)
* docs(arkv6s): add flight controller documentation

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>

* docs(arkv6s): add product photo and note single-IMU variant

Drop in docs/assets/flight_controller/arkv6s/ark_v6s_front.jpg
so the page renders the board photo it already references, and
align the intro with the upstream description by spelling out
that the V6S is the single-IMU variant of the V6X.

* docs(arkv6s): add bootloader UART note, fix arkv6x RAM typo

Add the bootloader serial port note (TELEM1-only in bootloader mode)
to the ARKV6S docs, matching the ARKV6X docs. Also fix the ARKV6X
MCU spec listing "1MB Flash" instead of "1MB RAM".

---------

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
2026-05-26 14:23:11 -06:00
Jonas Peroliniandjonas dd604072c4 feat(new_module): Static and moving vision-based target esitmator (Kalman Filter) (#23726)
Co-authored-by: jonas <jonas.perolini@rigi.tech>
2026-05-26 07:27:49 +10:00
65be196b9b docs(rovers): add hiwonder rover airframes and setup guide (#27333)
* rover: add hiwonder rover airframes

* docs: hiwonder rovers setup guide

* docs(docs): compress images

* docs(docs): prettier

* docs(docs): subedit

* docs(rover): add back tip about custom firmware install

* docs(rover): detail the hiwonder build / enable instructions

* docs(rover): fix airframe typo for ackermann

* docs(docs): Improve firmware section

---------

Co-authored-by: chfriedrich98 <chfriedrich@student.ethz.ch>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Ramon Roche <mrpollo@gmail.com>
2026-05-21 15:51:52 -04:00
Julian Oes f81559ec64 fix(Tools and docs): PX4 Pro isn't really a thing (#27366)
These are just leftovers, probably worth cleaning up.
2026-05-17 21:25:37 -06:00
Matthias Grob 0c0be00046 fix(commander): Remove parameter COM_DISARM_MAN 2026-05-04 16:55:48 +02:00
Matthias Grob eb06c7b7a9 refactor(commander): remove unused parameter COM_TAKEOFF_ACT (#26808) 2026-05-01 00:57:49 +02:00
Matthias Grob 5638ac53c7 refactor(commander): Remove COM_LKDOWN_TKO (#27262)
hardcoding its default 3 second time window.
2026-05-01 00:37:55 +02:00
Matthias Grob a061b8665b fix(commander): Remove COM_ARM_SDCARD (#27259)
hardcoding the default warning and respecting boards without SD card with a define.
2026-04-30 23:49:47 +02:00
Matthias Grob ffef31fb06 fix(commander): Remove COM_IMB_PROP_ACT (#27260)
and hardcode the default warning. The feature can still be disabled by setting FD_IMB_PROP_THR to zero.
2026-04-30 23:40:55 +02:00
Matthias Grob 5e86be131c fix(commander): Remove COM_OBC_LOSS_T (#27261)
hardcoding the default 5 second timeout.
2026-04-30 23:40:44 +02:00
Peter C. c838206024 docs(telemetry): Add Holybro sik long range to telemetry hardware documentaions (#26931) 2026-04-08 17:02:27 +10:00