1782 Commits
Author SHA1 Message Date
Bogdan Beju - NXP 0e0f3ce8a2 docs(boards/nxp_mr-tropic): Add docs for NXP MR-VMU-TROPIC (#29602) 2026-11-21 15:25:05 +11:00
Ramon Roche 3de5e83add docs(releases): add a v1.18 introduction and how to get the release
The v1.18 notes opened with a single line pointing at v1.17. The new
introduction describes what the release changes for operators and
integrators, and the new section explains how to fly, simulate, build
and integrate with v1.18, including the published containers, which the
notes never mentioned.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
2026-11-20 15:34:16 -08:00
Jacob Dahl 309b338b0b feat(boards/ark/fpv): analog OSD on the external SPI port (#29916)
* fix(atxxxx): fail the probe when the chip doesn't answer

probe() logged a VM0 mismatch but returned the SPI transfer status, so with nothing on the bus the driver started anyway.

* feat(boards/ark/fpv): analog OSD on the external SPI port

OSD_ATXXXX_CFG 1 or 2 starts atxxxx on SPI6 for a MAX7456-compatible OSD such as the ARK OSD. It stays off by default, since many use that port for an external IMU.

* docs(ark_fpv): set up an analog OSD on the SPI or TELEM port

The board can carry an analog OSD on either port, and neither is on by default.
2026-11-19 17:16:47 -07:00
PX4BuildBot adad90119f docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-19 18:35:44 +00:00
Jacob DahlandAndrea Bernasconi d04e5623f6 feat(gnss): compare receivers in sensors, limit divergence in commander (#29604)
* feat(sensors/gnss): report how far each receiver is from the selected one

Commander compared the receivers itself, reading the sensors module's antenna offsets and comparing samples taken at different times. The sensors module has the receiver-to-slot matching and the corrected sample times, so it now publishes each receiver's disagreement with the selected one on sensors_status_gnss, horizontally and vertically.

The other receiver is moved along its velocity to the selected sample's time. The antenna baseline is rotated with the attitude, so swapped or misplaced antennas show once the primary estimator's heading is aligned. Before that only the distances are compared, since the yaw is arbitrary.

Co-authored-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
Assisted-by: Claude:claude-opus-5-5

* feat(commander): limit the GNSS divergence with COM_GNSS_H_MAX and COM_GNSS_V_MAX

The divergence gate came from the receivers' reported accuracy floored with EKF2_GPS_P_NOISE, so it was hard to predict and read another module's parameter. Commander now takes the disagreement from sensors_status_gnss and applies fixed horizontal and vertical limits. Three times the receivers' combined reported accuracy still widens them, so standalone receivers don't warn on default parameters.

Before arming a divergence is reported at once and clears after 2 s of agreement. In flight it has to persist for 2 s.

Co-authored-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
Assisted-by: Claude:claude-opus-5-5

* fix(commander): keep the GNSS divergence limits fixed

Widening the limits to three times the receivers' combined reported accuracy made them floors, not limits. With the default GNSS_REQ_EPH and GNSS_REQ_EPV the gate opened to 12.7 m horizontally and 21 m vertically before arming, and to about 210 m in flight once a receiver fell back to the relaxed checks. The limits now apply as set, with defaults of 5 m and 10 m so standalone receivers don't warn.

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

* fix(commander): don't take an unknown GNSS disagreement for agreement

The sensors module leaves the disagreement unknown when the two latest samples are more than 0.5 s apart, while both receivers stay healthy. Commander treated that as nothing to compare, so a divergence before arming cleared for that check and an arm request could pass, and in flight the 2 s timer restarted. It happens on any gap over 0.5 s from a healthy receiver, and on 2 Hz receivers whose latencies differ. An unknown disagreement now keeps the state and its timer. A divergence still clears at once when there is no healthy pair to compare.

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

* docs(commander): swapped GNSS antennas hide behind a moving-base heading

The moving-base heading takes its offset from the same antenna positions. With swapped antennas the heading turns by 180°, and the expected baseline turns with it, so the divergence check sees agreement.

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

* docs(commander): reword the moving-base heading caveat

The sentence didn't say plainly that a moving-base heading from the same receivers stops the check from detecting swapped antennas.

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

* docs(commander): fold the moving-base caveat into the swapped-antenna conditions

The caveat read as a repeat of the alignment sentence. It is one more condition for detecting swapped antennas, so it now sits with the others.

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

* refactor(gnss): rotate the antenna baseline with the attitude as it is

The heading gate kept a limit below twice the antenna baseline from reporting a divergence before the heading aligned. With a mag the heading aligns before the receivers turn healthy. A heading from the same two receivers can't reveal swapped antennas anyway. The gate also never opened with an external INS, since only EKF2 publishes estimator_status_flags. Dropping it saves 168 B of flash on fmu-v2. The attitude age limit goes with it, since the last published attitude is a better guess than level and facing north.

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

---------

Co-authored-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
2026-11-19 11:28:20 -07:00
PX4BuildBot 4e44c822c9 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-19 16:17:26 +00:00
Marco Hauswirth 829f0f412e feat(sensors): keep calibrating the baro on the GNSS altitude until arming (#29876) 2026-11-19 17:10:35 +01:00
Mathéo Taillandier e1e1122af5 feat(simulation): enable airspeed sensor failure injection on gazebo too (#29210)
* feat(simulation): enable failure injection on gazebo sensor too

* docs(failure_injection): remove added dot
2026-11-19 12:58:23 +01:00
PX4BuildBot 48814f9409 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-19 08:29:47 +00:00
Matthew Charles Vladislav Busel 5c1a57d6d5 feat(simulation): add a differential rover to SIH (#29852)
* feat(simulation): add a differential rover to SIH

Add SIH_VEHICLE_TYPE 6 (Rover Differential) and the
10048_sihsim_rover_differential airframe, so rover_differential runs
headless with `make px4_sitl_sih sihsim_rover_differential`.

The model is a unicycle: each wheel is driven towards the ground speed
its motor command asks for (2 m/s at full command, matching
RO_MAX_THR_SPEED) up to its traction limit, and a lateral force keeps
the wheels from slipping sideways. Motor 1 is the right wheel and
motor 2 the left, as in the gz differential rover.

Closes #29838

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

* docs(simulation): explain the forces in the SIH differential rover model

Label the longitudinal force block and the force, moment and drag
outputs of generate_rover_differential_dynamics(), as suggested in
review. Comments only, no change in behaviour.

Assisted-by: Claude:claude-opus-5-5
2026-11-19 09:22:21 +01:00
Hamish Willee 6911bf9f56 docs(peripherals): explain where the MAVLink instance count comes from (#29895)
PX4-Autopilot#29573 let boards set the number of MAVLink instances, but
the MAVLink peripherals page didn't say how that number is set or what
limits it.

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

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
2026-11-19 16:49:49 +11:00
abhijith 5d9263851e feat(mavlink): let boards set the number of MAVLink instances (#29573)
* feat(mavlink): make the MAV_x instance count a per-board Kconfig option

MAV_x_* params and rc.serial were fixed at 3, though up to 6 MAVLink
instances can run. CONFIG_MAVLINK_NUM_CONFIG_INSTANCES (default 3) sets it;
extra instances take instance 2's defaults.

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>

* feat(boards/agam): enable 5 MAVLink instances on the v6X-RT

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>

* docs(releases): add per-board MAVLink instance count to main release notes

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>

* fix(mavlink): share main's --board-config in the instance count generators

main already passes the boardconfig as --board-config to generate_params.py,
so the duplicate option failed every build after a rebase. Both generators now
read it through the shared load_board_config. Kconfig caps the count at 5,
or 3 on constrained-memory boards, leaving a channel for USB, and list
defaults keep their length check unless the count comes from Kconfig.

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>

---------

Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
2026-11-19 12:58:56 +13:00
PX4BuildBot 36572dfd1c docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 23:57:57 +00:00
Julian Oes 1c279adf75 docs(gps): add newer CubePilot GNSS modules and a Here4 page (#29861)
The docs only covered the discontinued Here2/Here+ and linked Here3
externally with a wrong receiver name. Add Here3+, Here4 and HerePro to
the RTK and DroneCAN lists, linking CubePilot's docs.

Add a Here4 page with what is needed to get it working on PX4: the one
CAN port the firmware supports, enabling the barometer (off by default
on the Here4), updating it from the SD card, and the mandatory
bootloader bulletin.

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

Signed-off-by: Julian Oes <julian@oes.ch>
2026-11-19 12:51:02 +13:00
Julian Oes caf8944d5f docs(cubepilot): use CubePilot name and drop connector/standards note (#29828)
- Rename remaining Hex/HEX/ProfiCNC references to CubePilot, including
  page file names (old pages redirect).
- Use the CubePilot spelling consistently.
- Remove the note on the Cube Black page advising against it for
  standards and patent reasons.

Assisted-by: Claude:claude-opus-5-5
2026-11-19 12:51:01 +13:00
Matthias Grob c2875ad6a2 perf(nuttx): build the NuttX libraries with parallel make jobs
Each NuttX library and the apps are built by a make invocation that
ninja treats as a single opaque custom command, so they compiled one
file at a time.

Run them through a wrapper that honours a job count given to the
toplevel build (e.g. `make px4_fmu-v5x_default -j1`), which reaches it
through MAKEFLAGS, and otherwise uses the number of CPUs available to
the process. Unlike CMake's logical core count, nproc respects docker
--cpuset-cpus. A load limit keeps the concurrently running NuttX makes
from oversubscribing the host.

Mark the toplevel cmake build recipe as a sub-make with '+'. GNU make
before 4.4 (e.g. Ubuntu 22.04/24.04) passes its jobserver as pipe file
descriptors, which it otherwise closes for that recipe, leaving the
NuttX makes to fall back to serial builds.

Mention how to disable parallel builds in the docker docs.

Assisted-by: Claude Code (claude-opus-5-5)
2026-11-18 18:45:15 +01:00
Matthias Grob 6d43f6e807 docs(parameters): document the parameter member naming convention
The DEFINE_PARAMETERS example used member names that make check_format now rejects, and the convention itself was never written down.

Assisted-by: Claude:claude-opus-5-5
2026-11-18 18:40:12 +01:00
PX4BuildBot a1e336967d docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 15:26:14 +00:00
Jonas Perolini baa4742bad feat(vtol_att_control): detect pusher failures in multicopter mode (#29631)
Assisted-by: Codex
2026-11-18 16:18:48 +01:00
PX4BuildBot b65610b7bd docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 14:03:24 +00:00
PX4BuildBot 269554ad7c docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 12:59:45 +00:00
Marco Hauswirth 3bd1839a72 feat(ekf2): support up to two optical flow sensors 2026-11-18 13:52:41 +01:00
PX4BuildBot 9e34d7bba1 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 10:13:41 +00:00
Matthias Grob eaff7221eb feat(failure_detector): pause the tilt check after a VTOL skips the back-transition
Replaying about 150 logs found false positives only on standard VTOLs
after a quad-chute, with the tilt error above 60° for up to 1.75 s
while recovering from fixed-wing flight in multicopter mode.

All VTOL types switch to multicopter without back-transition on a
quad-chute, detected or commanded, and when a front transition is
aborted. The check now pauses for 5 s after such a switch instead of
raising the threshold for all VTOLs, so it protects the rest of the
multicopter flight.
2026-11-18 11:02:27 +01:00
Matthias Grob b5e65cfbfd feat(airframes): keep the tilt failure check enabled on the omnicopter
The tilt check compares against the attitude setpoint, which the
omnicopter publishes and tracks at any orientation, including upside
down. Disabling the check is no longer needed for it to fly.
2026-11-18 11:02:27 +01:00
Matthias Grob fa877566a4 feat(failure_detector)!: rename the tilt parameters to FD_TILT_ERROR
The tilt check limits the error from the attitude setpoint, which the
FD_FAIL_R name no longer describes. FD_FAIL_R becomes FD_TILT_ERROR,
now a float, and FD_FAIL_R_TTRI becomes FD_TILT_ERROR_T.

The old roll and pitch limits and trigger times meant something else,
so they start at the new defaults instead of being taken over. Only a
check disabled for both roll and pitch stays disabled, as -1.
2026-11-18 11:02:27 +01:00
Matthias Grob 15abdd0946 feat(failure_detector)!: check tilt error against the attitude setpoint
Checking the absolute tilt from level conflicts with the vehicle's own
tilt limits: the threshold can be set below the maximum tilt, and
external modes that tilt further than the autopilot's limits trip the
check, so they can't benefit from its crash detection.

Compare the tilt with the attitude setpoint's tilt instead, falling back
to level without a recent setpoint, e.g. on rovers. Before arming the
setpoint is level, so a vehicle lying on its side still can't arm. The
tailsitter transition exception is no longer needed because the
transition setpoint is in the multicopter frame. The default trigger
time goes from 0.3 s to 1 s so that fixed-wing stick reversals, which
pass through a large error at a limited roll rate, don't trigger it.

Also reset the tilt hysteresis while attitude control is off, so a
pending trigger from before e.g. Acro can't skip the trigger time when
attitude control comes back on.
2026-11-18 11:02:27 +01:00
Matthias Grob 7f83c28400 feat(failure_detector)!: check tilt instead of roll and pitch separately
Checking roll and pitch against separate limits misses a combined
tilt: 45° roll with 45° pitch is a 60° tilt but stays below both
default 60° limits. Euler angles are also unreliable near 90° pitch
and when inverted.

FD_FAIL_R and FD_FAIL_R_TTRI now set the maximum tilt and its trigger
time. FD_FAIL_P and FD_FAIL_P_TTRI are removed without migration
(see the Upgrade Guide). The check is disabled with -1; 0 still
disables it for existing setups. In FailureDetectorStatus, fd_roll
and fd_pitch are replaced by fd_tilt.
2026-11-18 11:02:27 +01:00
PX4BuildBot 9db647d5d3 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 09:12:00 +00:00
Jonas Perolini bab12fc267 fix(navigator): RTL type 6 keeps Home over a farther rally point (#29812)
When the battery estimate did not reach Home, type 6 took the closest
rally point even when it was farther away than Home. Return compares
destinations only by straight-line distance, so it has no reason to
prefer a rally point that is farther away than Home, and return.md says
type 6 falls back to Home unless a rally point is closer. Returns
started by the distance-aware battery failsafe hit this case.

Compare the rally points with the distance to Home, as type 6 already
does without a battery estimate.

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

Signed-off-by: jonas <jonspero@me.com>
2026-11-18 10:05:33 +01:00
PX4BuildBot bd06ff372a docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-18 08:45:36 +00:00
Andrea BernasconiandAnil Kircaliali 70a735246f fix(failsafe): let GNSS loss recover during the Hold delay (#29814)
* fix(failsafe): allow GNSS loss to recover during the Hold delay

A GNSS failure that clears during the COM_FAIL_ACT_T Hold still latched
Return or Land, because COM_GNSSLOSS_ACT uses the OnModeChangeOrDisarm
clear condition. The vehicle then abandoned a mission it could have
continued.

If the failure clears while the vehicle is still holding, the action is
dropped and the user-intended mode continues, e.g. the mission resumes.
Once Return or Land has started, it stays latched as before. With
COM_FAIL_ACT_T=0 there is no Hold, so nothing changes.

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

* fix(failsafe): restart the Hold delay after a failure clears during it

When a failsafe cleared during its Hold delay, the remaining delay kept
counting down. A new failure within that time did not reload it and only
got what was left, so it could Return almost without a Hold.

Reset the delay once no failsafe is pending, so that the next failure
gets the full COM_FAIL_ACT_T again. This applies to every failsafe.
Repeated failures still escalate: the start delay shrinks while a Hold
is active and refills at a quarter of that rate.

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

* revert(failsafe): keep the remaining Hold delay after a failure clears

This reverts commit 5e9a8e8a14.

Restarting the delay for every new failure changed how a flapping
condition is handled, for every failsafe and not only GNSS. Without the
reset, a failure that comes back keeps the delay left over from the
previous one, so the action still fires on time. With it, only the start
delay escalation limits the flapping, which can take much longer, or
never fire if the condition is active less than a fifth of the time.

Keep the PR scoped to letting GNSS loss recover during the Hold.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* fix(failsafe): only clear GNSS loss during the Hold delay before Return starts

_current_delay is shared between failsafes. If another failsafe with a
delay is added on the same update as GNSS recovers, it re-arms the delay
and the GNSS Return or Land that was already running got removed.

Also require that the selected action is not beyond Hold yet.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

---------

Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
Co-authored-by: Anil Kircaliali <anil.kircaliali@auterion.com>
2026-11-18 09:38:57 +01:00
52c4777580 docs(boards): add Accton Godwit G-FH7 flight controller page (#28830)
* Add new board "accton_godwit gfh7"

* Adjust the spacing.

* docs(boards/accton-godwit): Add support for the accton-godwit_gfh7 flight controller documentations.

* docs(boards): align Accton Godwit GFH7 page with board template

Bring the new GFH7 page in line with the flight controller page
template and the board's own configuration, so readers can wire and
set up the board from it:

- Fix image paths (all images were broken) and resize/compress the
  images; split the tall wiring diagram into two.
- Use PX4 port labels and /dev/ttyS* devices in the serial port table
  instead of ArduPilot SERIALn numbering, matching default.px4board.
- State 8 PWM outputs (PWM9 only drives NeoPixel LEDs), with DShot,
  bidirectional DShot and timer groups.
- Explain how to enable CRSF/ELRS on the ELRS connector, since only
  S.BUS is started by default.
- Add the standard notes and missing sections (Power, CAN, OSD, SD
  card, debug port), the _default build target and QGC tip.

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

* add voltage description.

* modify doc description about UART、pinout.

* modified UART settings

* modified UART device description

* docs(boards/accton-godwit): tidy GFH7 voltage ratings section

Give the section its own heading and anchor, name the battery input after the VBAT pins, and drop the battery ratings that contradict each other (48V maximum vs 12S, and an undamaged range below the operating range) until the manufacturer confirms the values.

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

* docs(boards/accton-godwit): note GFH7 ships with PX4 bootloader

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

* Modify these messages:
1.RCDGV pad group.
2.Voltage Ratings info.

* modified message:
1. UART port description
2. Telemetry Radios description

* docs(boards/accton-godwit): match GFH7 page to the new serial port labels

#28817 moves the PX4 RC port to the SBUS connector (UART5), labels the
ELRS connector (UART4) TELEM/SERIAL 4 and the receive-only ESC telemetry
UART (USART1) EXT2, and fixes the 12 V enable polarity. Update the radio,
serial port mapping, power and debug build notes to match.

Assisted-by: Kiro:claude-opus-5.5

* chore(boards/accton-godwit): drop GFH7 board files from the docs branch

The board port is reviewed and updated in #28817. The copies here had
already drifted from it (for example TEL3 on /dev/ttyS7, which does not
exist), so keep this pull request to the documentation only.

Assisted-by: Kiro:claude-opus-5.5

* docs(boards/accton-godwit): document the GFH7 ELRS default and IMU heater

#28817 makes CRSF/ELRS on the ELRS connector the default RC input, turns
S.BUS off by default, and adds the IMU heater (off by default). Update
the radio, serial port mapping and debug build notes to match, and add
an IMU Heater section that explains how to enable it.

Assisted-by: Kiro:claude-opus-5.5

* docs(boards/accton-godwit): add GFH7 block diagram

Review on #28830 asked for a block diagram of the main components
(sensors, power supply), as required by the board support guide.

Assisted-by: Kiro:claude-opus-5.5
Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards/accton-godwit): note GFH7 boots in Stabilized mode

The board sets COM_FLTMODE_BOOT to Stabilized instead of the PX4
default of Hold, so users should know which mode they get on power-up
and that a mode switch overrides it.

Assisted-by: Kiro:claude-opus-5.5
Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards/accton-godwit): fix GFH7 debug port tables

* docs(boards/accton-godwit): list GFH7 OSD debug pads in board order

* docs(accton-godwit_gfh7): reference QGC board recognition PR in tip

Point the Building Firmware tip at mavlink/qgroundcontrol#15212 so it is accurate until QGC recognises GFH7.

* docs(boards/accton-godwit): fix GFH7 review issues

The block diagram named the wrong secondary IMU, the firmware tip linked
a QGC PR that was closed unmerged, and the S.BUS pin on the D-VTX
connector (shown in the pinout) was undocumented. Also tidy the
telemetry and debug port sections to the style guide.

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

* docs(boards/accton-godwit): clarify GFH7 voltage ratings and label SBUS connector

Describe the 13V figure as the minimum for the 12V camera/VTX rail instead of a tested operating minimum, drop the unmeasured USB operational range, and relabel the UART5 connector in the block diagram as SBUS.

Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards): reorder Accton Godwit GFH7 page to match board template

Match the flight controller page template so the page reads like other
board pages, and keep the images in a folder named after the page.

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

* docs(boards): tidy Accton Godwit GFH7 page and add release note

Address the remaining editorial review findings so the page matches the
board template and other board pages, and list the new board in the
release notes.

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

* docs(boards): rename to G-FH7 and address review questions

Rename the reader-facing board name from GFH7 to G-FH7 in the board
page, sidebar, manufacturer list, and main release notes.

State the battery input as up to 12S LiPo, note that the IMU heater
current is calculated from the resistor value (not measured), correct
the UART5 wiring for the SBUS and A-VTX connectors, and link the
IST8310 datasheet.

Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards): update G-FH7 pin definition image

Replace the pinout with the updated drawing that labels UART5_TX on the
A-VTX connector and UART5_TX/UART5_RX on the SBUS connector.

Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards): tidy G-FH7 UART5 wording and block diagram battery label

Put the S.BUS setup line first in the SBUS receiver bullet, so "To use
it" refers to the receiver rather than the A-VTX TX pin, and shorten the
UART5 serial table cell and the duplicated heater current note.

Change the block diagram battery label from "4~12S" to "Up to 12S",
since the authors confirmed there is no verified lower limit and the
page now says "Up to 12S LiPo".

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

* docs(boards): document G-FH7 A-VTX control and VTX driver

The A-VTX TX pin is the SmartAudio/Tramp control line, shared with
UART5_TX on the SBUS connector. Document how to use it (VTX_SER_CFG set
to Radio Controller) and that it can't be used together with an S.BUS
receiver on the SBUS connector.

Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* docs(boards): fix G-FH7 RC, buzzer and wording review issues

Tell readers to disable CRSF when enabling DSM or GHST, since CRSF is
on TELEM/SERIAL 4 by default, and note that DSM receivers can't be bound
from PX4 because the board defines no SPEKTRUM_POWER. Say the BZ output
needs an active buzzer, because the board drives it as a plain GPIO.

Also define DFU, PPS and VTX at first use, link parameter setting, use
"co-processor" for the OSD consistently, fix ambiguous references in
the OSD and debug pad text, and narrow the debug-build ELRS limit to
the ELRS connector.

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

* docs: G-FH7: remove VTX control, apply ADC/power monitoring suggestions

PX4's VTX driver swaps RX/TX on the RC port (no RC_SERIAL_SWAP_RXTX on
this board), so SmartAudio/Tramp would not come out on the A-VTX TX pin.
State that PX4 does not use that pin instead.

Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>

* Update docs/en/flight_controller/accton-godwit_gfh7.md

* Update docs/en/flight_controller/accton-godwit_gfh7.md

* Update docs/en/releases/main.md

* docs(accton-godwit_gfh7): address review feedback

Apply remaining Hamish review suggestions on the G-FH7 board page:
clarify the switchable 12 V BEC output, note serial flashing over TELEM only,
expand GHST as TBS Ghost, warn that 3.3 V DSM receivers need a separate supply,
and match the OSD SWD pad wording to the FMU debug table.

* docs(boards): tidy G-FH7 interface, power, BOOT and ESC wiring text

Move the Interface Summary under Pinouts to match the board page
template, note that current monitoring needs setup, name the board's
BOOT button, and describe the ESC wiring diagram as it is drawn
(4-in-1 ESC on the ESC connector only).

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

* docs(boards): flatten G-FH7 images onto white for dark mode

The board drawings were black line art on a transparent background, so
in dark mode the lines all but vanished against the dark page.

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

* docs(boards): drop space between value and unit on G-FH7 page

PX4 prefers no space between a value and its unit symbol (3V, not 3 V).

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

---------

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
Signed-off-by: g945643frankie <g945643@oz.nthu.edu.tw>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: g945643frankie <g945643@oz.nthu.edu.tw>
Co-authored-by: g945643frankie <106499958+g945643frankie@users.noreply.github.com>
2026-11-18 18:34:48 +11:00
PX4BuildBot dc0cf5ec2e docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-17 17:43:09 +00:00
Ramon Roche 83960122a5 docs(releases): add v1.18 notes for fixes and changes since rc1
Covers what landed on release/1.18 after v1.18.0-rc1 and was missing from
the notes, and restores the distance-aware return upgrade item that only
the release/1.18 copy had (#29620), so main is again a superset of it.

Adds upgrade items for the heater parameter rename, the ARK FPV
fixed-wing and VTOL targets, the Matek H743 bootloader board ID and the
strict MAVLink command parameter checks, and amends the signing, AGP and
parameter file items.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
2026-11-17 09:01:09 -08:00
PX4BuildBot b534b2a0b0 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-17 15:21:24 +00:00
PX4BuildBot a6814cc7b6 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-17 09:46:03 +00:00
Andrea Bernasconi 67f5c57e9a feat(GNSS): Introduce kinematic consistency check (#29660)
* feat(gnss): check that the position change matches the velocity

A receiver computes its position from the code (time of flight) and its
velocity from the Doppler shift. Multipath and other degradation hit the
two differently, so a degraded receiver's position change stops matching
its velocity, often before its reported accuracy shows it. The existing
drift checks compare the two only at rest on the ground.

The new strict check filters the position change rate minus the mean
velocity over about 1 s and fails above GNSS_REQ_POSVEL, also in flight,
so the selection prefers another receiver that passes. It is off by
default (GNSS_CHECK bit 12) until the threshold is tuned on logs; the
filtered value is logged in sensors_status_gnss either way.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* fix(gnss): skip the position step at a fix type change in the consistency check

When a receiver starts or stops applying differential or RTK corrections,
its position steps by up to a few meters in one epoch while the Doppler
velocity is unaffected. That is a new solution, not degradation, and it
shouldn't demote a receiver that just reached RTK fixed. On a 10 Hz log
with DGPS dropping in and out, these steps drove the filtered value to
4.5 m/s; without them it peaks at 0.8 m/s, during a real vertical drift.

Only the interval spanning the change is skipped and the filter keeps its
state, so a receiver that keeps switching isn't blind for longer.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* refactor(gnss): Reduce check description

* fix(GNSS): Make the feature enabled by default but with more margin

* fix(gnss): restrict the position/velocity consistency check to horizontal

Receivers that don't report the vertical velocity failed the check on any
climb. Merge the consistency tests into fewer cases.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* refactor(gnss): mark the position/velocity consistency check as horizontal

The check only compares the horizontal position change with the horizontal
velocity. Name the parameter, flags and status field after that, so that a
vertical counterpart can be added later as GNSS_REQ_VPOSVEL / CHECK_VPOSVEL.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* refactor(gnss): rename the position/velocity check to kinematic consistency

HPOSVEL read like a check on position and velocity separately, next to
HDRIFT and HSPEED. "Kinematic consistency" names the property being
tested and leaves room for a vertical counterpart (VKIN). Messages,
flag comments and the parameter's long description keep the plain
wording, since "kinematic" alone can be read as RTK.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

---------

Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
2026-11-17 10:38:26 +01:00
PX4BuildBot e5fd8c1655 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-17 01:09:09 +00:00
Hamish WilleeandJulian Oes 4d755a614f fix(mavlink): Make MAV_CMD_SET_ACTUATOR scale properly in missions (#27336)
* fix(mavlink): scale DO_SET_ACTUATOR params 5/6 in mission items

MISSION_ITEM_INT carries params 5/6 in the int32 x/y fields, so the actuator
5 and 6 values (-1..1) only arrived as -1, 0 or 1, and an unset (INT32_MAX)
value drove the actuator to saturation instead of leaving it unchanged.

Scale them by 1e7 like COMMAND_INT does, map unset to NaN, and encode them
the same way on download.

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Signed-off-by: Julian Oes <julian@oes.ch>
Assisted-by: Claude:claude-opus-5-5

* docs(navigator): list all supported mission commands

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>

* fix(mavlink): keep ARM_DISARM and AUTOTUNE params on global-frame download

A global-frame mission item zeroes param1-4 before filling in the
command-specific ones, and COMPONENT_ARM_DISARM and DO_AUTOTUNE_ENABLE
had no case there. An uploaded "arm" (param1 = 1) therefore downloaded
as "disarm" (param1 = 0).

Signed-off-by: Julian Oes <julian@oes.ch>
Assisted-by: Claude:claude-opus-5-5

* fix(mavlink): ignore unset COMMAND_INT x and y individually

COMMAND_INT x/y were only treated as unset when both were INT32_MAX. A
DO_SET_ACTUATOR setting only actuator 5 (y = INT32_MAX) therefore set
actuator 6 to 214.7, saturating it, instead of leaving it unchanged.

Map each of x and y to NaN on its own when unset, which also covers
INT32_MIN from a NaN converted to int.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julian Oes <julian@oes.ch>
Co-authored-by: Julian Oes <julian@oes.ch>
2026-11-17 10:45:39 +13:00
PX4BuildBot dc7b9011cb docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-16 10:56:16 +00:00
Silvan FuhrerandMahima Yoga 18f0524791 fix(commander): continue fixed-wing mission takeoff without position (#29719)
* fix(commander): continue fixed-wing mission takeoff without position

A fixed-wing vehicle losing its position estimate during Takeoff mode keeps
climbing wings-level (FW_POSCTRL_MODE_AUTO_TAKEOFF_NO_NAV), because fixed-wing
Takeoff mode does not require a position. During the takeoff item of a
mission, the mode fallback instead checked the Mission requirements and
escalated to Descend.

Check the mode fallback against the Takeoff mode requirements while a
fixed-wing vehicle flies the takeoff item of a mission, so both behave the
same. Once the takeoff item is done, the mission requirements apply again.

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

* feat(commander): add FW mission takeoff state to failsafe simulator

The failsafe state now distinguishes the takeoff item of a fixed-wing
mission, which only needs the Takeoff mode requirements. Expose it in the
simulator so this fallback can be tried out there too.

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

* Update docs/en/flight_modes_fw/mission.md

Co-authored-by: Mahima Yoga <mahima@auterion.com>

* Update docs/en/flight_modes_fw/mission.md

Co-authored-by: Mahima Yoga <mahima@auterion.com>

---------

Co-authored-by: Mahima Yoga <mahima@auterion.com>
2026-11-16 11:49:11 +01:00
PX4BuildBot 5a7f3ab512 docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-16 08:02:23 +00:00
Mathéo Taillandier 336eafd0c5 fix(drivers): fix wrong RPM in UAVCAN ESC telemetry (#29580) 2026-11-16 08:55:04 +01:00
PX4 Build BotandCrowdin Bot c4b8f107ae docs(i18n): PX4 guide translations (Crowdin) - zh-CN (#29802)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-11-15 11:31:22 +11:00
PX4 Build BotandCrowdin Bot c3c6b24b07 docs(i18n): PX4 guide translations (Crowdin) - uk (#29801)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-11-15 11:31:09 +11:00
PX4 Build BotandCrowdin Bot 035df89164 docs(i18n): PX4 guide translations (Crowdin) - ko (#29800)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-11-15 11:30:51 +11:00
aaronfullerandHamish Willee 53afcc82b2 feat(boards/avianautomata): add Avian Automata 305AP flight controller (#29689)
* feat(boards/avianautomata): add 305AP flight controller

Add the Avian Automata 305AP: STM32H743, two IMU slots that accept
either an LSM6DSV16X or an ICM-45686, BMP581 barometer, MMC5983MA
magnetometer, two CAN buses and eight motor outputs plus docs. 

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

---------

Signed-off-by: Aaron <aaron.s.fuller@gmail.com>
Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-11-13 17:42:06 -05:00
PX4BuildBot 0bd95058aa docs: auto-sync metadata [skip ci]
Co-Authored-By: PX4 BuildBot <bot@px4.io>
2026-11-13 10:31:53 +00:00
Andrea BernasconiandHamish Willee db94ca49db feat(failure_injection): add wrong, garbage and drift IMU failures (#29601)
* feat(failure_injection): add wrong, garbage and drift injection for gyro and accel

Corrupt the addressed IMU's samples on all three axes: wrong adds a
constant bias (SYS_FAIL_{G,A}_BIAS), garbage uniform noise within
+-SYS_FAIL_{G,A}_NOISE and drift a bias growing by SYS_FAIL_{G,A}_DRIFT
per second since injection. Applied to both the plain and FIFO driver paths.

* refactor(failure_injection): handle IMU failures in process_imu()

Mirror process_gnss(): resolve the mode once, run the generic Off / Stuck
first and only then apply the Wrong / Garbage / Drift offset, so the Stuck
cache keeps the uncorrupted sample and a later Stuck never replays a
drifted one. Drop the second process() on the integrated FIFO report, which
cached the already-corrupted report. The offset is still computed before
Off so drift_start is reset while the sensor is off.

* docs(failure_injection): align IMU failure docs with code

The Syntax section did not list drift and described garbage as
uninitialised-memory output, while gyro/accel garbage adds bounded noise
to the real measurement. Also match the new parameter descriptions to
the wording of the existing SYS_FAIL_* parameters.

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

* fix(failure_injection): add drift RC mode and clarify bias param text

* refactor(drivers): Drop extra comment

* test(mavsdk_tests): add SITL test for IMU failure injection

Fly the SIH quad through gyro and accel bias, noise and drift with the
default SYS_FAIL_{G,A}_* magnitudes and check it holds altitude.

Holding altitude alone also passes when the injection never reaches the
sensor data, so the test also checks that the IMU noise level jumps
while noise is injected and returns once cleared. Bias and drift are
not checked in the data: the rate controller and the estimator react
to them and partly hide them in flight.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

* test(mavsdk_tests): inject IMU failures through MAVSDK 4.2.0

MAVSDK-Python 4.2.0 adds FailureType.DRIFT (mavlink/MAVSDK#3211), so the
IMU failure test no longer needs to send a raw MAV_CMD_INJECT_FAILURE
with its own copies of the unit and type values. Use the tester's
inject_failure() like the motor failure tests, and bump the mavsdk pin
so the new type is available.

Assisted-by: Claude:claude-fable-5-2
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>

---------

Signed-off-by: Hamish Willee <hamishwillee@gmail.com>
Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
2026-11-13 11:24:05 +01:00