Copies docs/en/releases/1.18.md from main at 83960122a5 (#29843), which
now holds everything this branch's copy had plus the notes edits made on
main since the branch was cut. Seven of those notes commits were never
backported, so the file is synced whole instead of cherry-picked.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* fix(gps): run a moving base and its rover at 5 Hz on every board
PX4-GPSDrivers f6f5c2d89a (PX4/PX4-GPSDrivers#244, with the style pass of #245): a moving base and its rover must share one navigation and measurement rate, and u-blox caps a moving base at 5 Hz on the F9P and the X20P. With the board defaults (F9P 5 Hz, X20P 10 Hz) a mixed pair was mismatched and the X20P rover reported no heading for the epochs its base never observed.
Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* docs(gps): moving base and rover share one navigation rate
The driver now holds both to 5 Hz in the moving base modes; the pages say so and tell the reader to leave GPS_UBX_RATE at 0.
Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
---------
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
(cherry picked from commit b12d17f632)
The submodule points at the port of PX4/PX4-GPSDrivers#244 to that repo's release/1.18 branch.
* fix(mc_att_control): ignore invalid attitude setpoints in the reference model
Since the reference model (2a0e048171, PR #27255) the controller tracks _q_ref,
which is integrated from its previous value and only snapped to the setpoint on
the first call. A single attitude setpoint with a zero or non-finite quaternion
(normalizing a zero quaternion gives NaN) therefore makes _q_ref NaN for the rest
of the boot: every later setpoint is ignored, the rate setpoint stays NaN and the
vehicle has no attitude control, even after a mode switch. Before the reference
model the controller used q_d directly, so a bad sample only lasted one cycle.
One MAVLink SET_ATTITUDE_TARGET with q = [0, 0, 0, 0] in Offboard reproduces it
in SIH: vehicle_rates_setpoint stays NaN and the vehicle no longer responds to
the sticks after switching to Position mode.
Ignore setpoints and heading-reset deltas that are zero or non-finite, keeping
the last valid reference, and snap the reference to the next valid setpoint if
it ever becomes non-finite.
Signed-off-by: Isak Åslund <isak.aslund@airolit.com>
* fix(mc_att_control): drop the whole attitude setpoint when its quaternion is invalid
When the controller rejects an invalid quaternion, the thrust and timestamp
from the same message were still applied. The vehicle then flew the last
valid attitude with thrust from a message that cannot be trusted.
setAttitudeSetpoint() now returns whether the setpoint was accepted. The
thrust and the setpoint timestamp are only updated when it was. Keeping the
timestamp also gives the next valid setpoint the true dt since the last
accepted one.
Signed-off-by: Isak Åslund <isak.aslund@airolit.com>
* fix(mc_att_control): reject overflowing quaternions and drop invalid SET_ATTITUDE_TARGET
Review follow-ups:
- Validate the setpoint through its norm. A quaternion with a finite component
above ~1.8e19 (e.g. q = (1e20, 0, 0, 0)) passed isAllFinite(), its norm
overflowed to inf and normalizing it gave a zero quaternion. As the first
setpoint this made the reference NaN for the next setpoint. One finite norm
check rejects NaN, inf, zero and overflow.
- Drop the ref_valid / dt finiteness recovery branch: with every input of the
reference model validated it cannot be reached, and it costs flash.
- Drop the adaptAttitudeSetpoint() guard: no estimator publishes an invalid
delta with a changed reset counter, and it only protected the reference,
not the yaw setpoint and StickYaw that use the same delta.
- MAVLink SET_ATTITUDE_TARGET: drop a message with an unusable q before
publishing offboard_control_mode. Otherwise a companion streaming only
invalid quaternions keeps the offboard heartbeat alive and the vehicle holds
the last valid tilt and thrust indefinitely without triggering
COM_OF_LOSS_T.
Signed-off-by: Isak Åslund <isak.aslund@airolit.com>
* docs(offboard): note that SET_ATTITUDE_TARGET with an invalid q is dropped
Since the previous commit, such a message no longer counts as the offboard
signal, which is a behavior change MAVLink users can see. Also name the 1e-3
norm threshold in the setAttitudeSetpoint() doc, and point the MAVLink and
controller checks at each other: if the MAVLink threshold were lowered below
the controller's, messages the controller drops would keep offboard alive.
Signed-off-by: Isak Åslund <isak.aslund@airolit.com>
---------
Signed-off-by: Isak Åslund <isak.aslund@airolit.com>
(cherry picked from commit 7902349f7a)
* fix(ekf2): keep v1.17 auxiliary global position settings on upgrade (#29351)
* fix(parameters): migrate EKF2_AGP_* to EKF2_AGP0_*
The auxiliary global position parameters became per-source EKF2_AGP<n>_*
parameters in #26306 without a translation, so on an upgrade from v1.17
the stored EKF2_AGP_CTRL, _MODE, _DELAY, _NOISE and _GATE are dropped as
unrecognised. Move them to the first slot.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
* fix(ekf2): mark EKF2_AGPn_ID as reboot required
The sources are created when EKF2 starts, for the slots whose ID is not
zero, so a changed ID only takes effect after a reboot.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
* docs: explain EKF2_AGPn_ID for auxiliary global position
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
* fix(parameters): set EKF2_AGP0_ID when migrating a v1.17 AGP source
Migrating EKF2_AGP_* alone fuses nothing: a slot with ID 0 has no source. v1.17 messages had no ID, but a v1.17 source now arrives with ID 1 either way, from the message translation node or as GlobalPositionMeasurementInterface's default, so a non-zero EKF2_AGP_CTRL also sets EKF2_AGP0_ID to 1.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
---------
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com>
(cherry picked from commit b3cee891b2)
* fix(ekf2): gate the auxiliary global position fusion on bit 0 of EKF2_AGPn_CTRL (#29204)
The parameter is documented as a bitmask but was only tested for non-zero, so bit 1 alone (vertical position, which has no fusion path) enabled the horizontal fusion. Gate on bit 0 and document bit 1 as reserved.
Fixes#29153
Assisted-by: Claude:claude-fable-5-1
(cherry picked from commit 77c04dcc4c)
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
* docs(releases): note the new EKF2_AGPn_NOISE default
Only stored values are migrated, so a vehicle on the v1.17 default of
0.9 m takes the new default of 1.0 m.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
---------
Signed-off-by: A.Burak Tektas <15087318+Abtektas@users.noreply.github.com>
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com>
Co-authored-by: treston <jonhhjackson@gmail.com>
* fix(dataman_client): keep request topic advertised on client teardown
* fix(uorb): keep shared topics advertised on publisher teardown
Single-instance publications share one advertised flag, so destroying one
publisher must not hide updates from the others.
Keep automatic unadvertising in PublicationMultiBase and remove the
DatamanClient workaround. Cover surviving publishers and instance reuse,
and reset retained input samples between test cases.
Tested: make tests (215/215), make format.
Signed-off-by: jonas <jonas.perolini@rigi.tech>
Assisted-by: Codex
* docs(uorb): correct unadvertise comments and document teardown
The unadvertise comment claimed it has no effect on single-instance
topics, which is how one publisher's teardown came to hide the others.
State what clearing the shared flag does, and document that only
PublicationMulti releases its instance on destruction.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: jonas <jonas.perolini@rigi.tech>
* test(uorb): keep test cases independent of retained samples
A destroyed single-instance publication now leaves its last sample
visible, so ManualControlTest, test_prec_takeoff and mixer_module_tests
passed only in declaration order and failed under --gtest_shuffle.
Reset with an inert sample where one exists, otherwise unadvertise the
test's own publications, and drop module outputs left over from a
previous case.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: jonas <jonas.perolini@rigi.tech>
* fix(boards): drop the PublicationBase destructor from the ITCM lists
The destructor is now trivial and no longer emitted, so itcm_check.py
fails on the missing section.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
---------
Signed-off-by: jonas <jonas.perolini@rigi.tech>
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
Co-authored-by: jonas <jonas.perolini@rigi.tech>
Co-authored-by: Jacob Dahl <dahl.jakejacob@gmail.com>
(cherry picked from commit e146fe4cc6)
Backport adaptation: release/1.18 has no PublicationMultiBase (main's
4791b70c15 out-lined PublicationMulti), so the destructor that frees the
instance goes into PublicationMulti<T> and Publication.cpp is unchanged.
The ITCM entries for agam/ark fmu-v6xrt and the navigator tests
test_mission_route_cache.cpp / test_prec_takeoff.cpp are dropped: those
files are not on release/1.18. TEST_VTEPosition.cpp uses release/1.18's
_uav_gps_pub (main renamed it _uav_gnss_pub).
Assisted-by: Claude:claude-opus-5-5
Co-authored-by: Jonas Perolini <74473718+JonasPerolini@users.noreply.github.com>
* fix(drivers/uavcannode): make CANNODE_NODE_ID the sole node ID policy
The startup bootloader_app_shared_write() never reached the bootloader:
it only accepts App-signed data and invalidates the shared region on
every boot. The only consumer was uavcannode itself on a restart
without a reset (nsh stop/start), where the persisted bus_speed=0 made
the CAN driver init fail and left the node off the bus. The bootloader
learns our node ID exclusively through the firmware update handoff in
cb_beginfirmware_update, which already carries the static ID.
CANNODE_NODE_ID now overrides the bootloader handoff only when nonzero,
so the default (0) reuses the ID the bootloader already allocated
instead of running allocation a second time. The handoff is ignored
unless it carries a valid bitrate, healing regions poisoned by firmware
that wrote bus_speed=0. Max is 125 because 126/127 are reserved for
debug tools by DroneCAN convention, matching UAVCAN_NODE_ID.
* fix(drivers/uavcannode): harden bootloader handoff validation
Invalidate the shared region whenever it was read valid, not only when
the handoff is accepted, so stale data cannot linger on boards whose
bootloader never invalidates it. Require a plausible bitrate (the
CANNODE_BITRATE minimum) rather than nonzero: the canbootloader alt-app
update path can hand off bus_speed = CAN_UNDEFINED (999). Reword the
invalid-param error, which claimed dynamic allocation while keeping the
bootloader handoff.
---------
(cherry picked from commit 0524a374d9)
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
An Offboard vehicle without manual control, the companion computer
setup that NAV_RCL_ACT 7 "Hold mode (no failsafe)" was added for,
stayed in Offboard when its companion stopped. #26289 made the
Offboard loss fallback into Position mode use the NAV_RCL_ACT action
instead when manual control is lost, since Position mode needs it.
Value 7 maps that action to None, because Commander switches to Hold
on its own, but that switch only fires while a manual mode is flown.
So the vehicle kept flying its last setpoint, with a velocity
setpoint that means flying off, and nothing was reported.
The replacement now maps None to Hold, which is what value 7 promises,
and the action cascade escalates to Return and Land from there when
Hold cannot run. The manual control loss trigger itself is untouched
and still takes no failsafe action for value 7.
In SITL with the sih quadcopter, no manual control and a velocity
setpoint stream that stops, main kept flying at 0.9 m/s for the whole
12 s watched. With this change the vehicle is in Hold 1.4 s after the
stream stopped. Both changes are in v1.18.0-rc1.
Assisted-by: Claude:claude-fable-5-1
(cherry picked from commit 68a2124f5c)
Signed-off-by: Saibernard Yogendran <bernie97@seas.upenn.edu>
* docs(releases): add v1.18 notes for five backported fixes
The estimator selector, VTOL mission return, analog battery filter,
home altitude filter and mission end fixes are on release/1.18 now,
this adds their entries to the release notes.
Assisted-by: Claude:claude-fable-5
* MOve entries
* docs(releases): add the v1.18 note for the position controller filter fix
#28534 merged onto release/1.18 after the first five entries.
Assisted-by: Claude:claude-fable-5
---------
(cherry picked from commit fe87271f9c)
Signed-off-by: Saibernard Yogendran <bernie97@seas.upenn.edu>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
* fix(ci): attach FMU bootloader .bin to GitHub releases
Releases only shipped `_bootloader.px4`, the USB uploader envelope. SWD recovery needs the raw `.bin` at 0x08000000.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* fix(ci): do not attach unused bootloader .px4
USB flashing would write it into the application slot. SWD uses the raw .bin.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* fix(ci): omit bootloader SBOMs from GitHub releases
GitHub Releases glob artifacts/**/*.sbom.spdx.json. Bootloader metadata dirs are not a recovery artifact.
*_bootloader_* variants (e.g. bootloader_secureboot) stay omitted: those images are baked with in-tree test keys.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* docs(bootloader): point SWD recovery at the release .bin
Match the cannode pre-built blurb. The .px4 envelope is not the SWD image.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* docs(bootloader): scope release .bin to SWD programmers
gdb load needs ELF program headers. The release image is a raw .bin for ST-Link / CubeProgrammer / OpenOCD, and only in-tree *_bootloader targets are attached.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
---------
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* fix(ci): publish flashable CAN node firmware
Release packaging only collected .px4 files, which the DroneCAN bootloader cannot flash.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* fix(ci): attach canbootloader .bin as the SWD image
The cannode bootloader is a raw .bin for st-flash, not a .px4 envelope.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* fix(ci): drop cannode.zip from release assets
The target-named .uavcan.bin and _canbootloader.bin files are the flashable images; the zip only duplicated them.
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
---------
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
* docs(releases): fix malformed SIH wind PR link in v1.18 notes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): draft v1.18 release notes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): mark v1.18 beta and add changes merged since the draft
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): add v1.18 upgrade guide, hardware fixes, and section structure
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): resort v1.18 major changes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): link sensor and peripheral docs pages in v1.18 notes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): describe new boards and highlight serial passthrough in v1.18 notes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): fold standalone sensors section into hardware and common
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): fill v1.18 ethernet section with networking fixes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): merge ROS 2 and middleware sections with DDS and Zenoh subsections
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): group vehicle-type notes under vehicle-specific section
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): reorder v1.18 other-changes sections by topic group
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): drop other-changes wrapper heading in v1.18 notes
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): organize debug-logging subsections and add infrastructure section
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* docs(releases): fix main.md template wording and mark v1.18 beta in sidebar
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
---------
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
The --viewer path (tee MAVLink frames to UDP and enable the
HIL_STATE_QUATERNION/HIL_ACTUATOR_CONTROLS streams so Hawkeye could
render an SIH flight live) was never validated end to end: Hawkeye
never actually rendered from it. Rather than ship an unproven feature,
drop it.
Removes px4bench.attach_viewer_tee (and its function-local socket use),
the flight_mission --viewer/--viewer-port args, the viewer tee call and
the stream-enable block, and the now-unused --board-dev arg that only
fed those stream commands. The SIH flight logic, firmware gate,
storage/serial tests, and the arming gate are unchanged. README and the
bench testing docs page drop the Hawkeye section and all --viewer
mentions.
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
The flight test is now part of the default suite; both the bench README
and the bench testing guide said it ran separately. Update the sequence
description, the risk map and suite tables (storage_stress and
flight_mission rows, serial_loopback for fixtures), the SIH sections
(probe-and-skip, the typed 'arm' confirmation, --allow-arming for
automation), the production section (--allow-arming on the line,
serial_loopback with a jumper on the fixture), and the firmware gate
--build description (bench capability report with variant and config
line recommendations). Storage threshold defaults are justified where
the flags are documented.
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
New page in Platform Testing and CI covering px4bench: why on-hardware
verification exists alongside SITL and CI, the firmware traceability
gate, the bench test inventory, the SIH hardware-in-the-loop flight
test with Hawkeye, baseline comparison for upgrade regression and
golden-unit workflows, production end-of-line usage, and CI
integration. Linked from the section index and the sidebar.
Signed-off-by: Ramon Roche <mrpollo@gmail.com>
* feat(FlightTaskAuto): add RC yaw override during Auto modes
* feat(FlightTaskAuto): disengage RC yaw nudge on flight-mode switch
* docs: document MPC_AUTO_RC_YAW in MC Auto mode pages
Describe the RC yaw nudge (MPC_AUTO_RC_YAW) on the Mission page.
Add parameter rows to the Hold and Land pages where MPC_LAND_RC_HELP takes
precedence over it for yaw, and document MPC_LAND_RC_HELP there too.
* feat(FlightTaskAuto): updated param description to warn against COM_RC_OVERRIDE disabled
The long description recommends to have a switch on the RC to change to Position mode
* fix(FlightTaskAuto): unified yaw nudging with new MPC_AUTO_NUDGING parameter
* docs(FlightTaskAuto): MPC_AUTO_RC_YAW and MPC_LAND_RC_HELP parameters were replaced by the unified MPC_AUTO_NUDGING bitmask
* fix(parameters): migrate MPC_LAND_RC_HELP to MPC_AUTO_NUDGING bit 1
* docs(1.18): move stick override and add nudging changes
---------
Co-authored-by: Matthias Grob <maetugr@gmail.com>
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>