mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-11-22 14:19:57 +08:00
docs(releases): sync the v1.18 notes from main
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>
This commit is contained in:
1 parent
824dd4c75a
commit
6d1773f4c1
1 file changed
+160
-17
+160
-17
@@ -49,7 +49,8 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
|
||||
2. **Re-provision MAVLink signing.**
|
||||
Signing is now spec-compliant: it activates only when a valid key is present on the SD card, and the non-standard `MAV_SIGN_CFG` parameter has been removed. `SETUP_SIGNING` is accepted on any link but rejected while armed. If you used signing in v1.17, re-provision the key from your GCS and confirm it supports the standard flow.
|
||||
([PX4-Autopilot#26894](https://github.com/PX4/PX4-Autopilot/pull/26894))
|
||||
While signing is active, unsigned `ADSB_VEHICLE` and `COLLISION` messages are only accepted on links whose [MAV_n_MODE](../advanced_config/parameter_reference.md#MAV_0_MODE) is `ADS-B/Traffic (uAvionix)`, which is now the mode for any traffic receiver, FLARM included. Set this mode on the link of a traffic receiver that cannot sign.
|
||||
([PX4-Autopilot#26894](https://github.com/PX4/PX4-Autopilot/pull/26894), [PX4-Autopilot#29488](https://github.com/PX4/PX4-Autopilot/pull/29488))
|
||||
|
||||
3. **Migrate EKF2 fusion source selection.**
|
||||
`EKF2_EN_BOOT` is replaced by the [EKF2_SENS_EN](../advanced_config/parameter_reference.md#EKF2_SENS_EN) bitmask selecting which sensor fusion sources are enabled; fusion sources can additionally be toggled at runtime over MAVLink.
|
||||
@@ -84,21 +85,78 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
11. **Update AFBR-S50 startup scripts.**
|
||||
The `-r` command-line rotation flag is removed; set the mounting orientation via [SENS_AFBR_ROT](../advanced_config/parameter_reference.md#SENS_AFBR_ROT) instead.
|
||||
([PX4-Autopilot#27385](https://github.com/PX4/PX4-Autopilot/pull/27385))
|
||||
`SENS_AFBR_S_RATE`, `SENS_AFBR_L_RATE`, `SENS_AFBR_THRESH` and `SENS_AFBR_HYSTER` are removed with the distance-based range switching; rate and dual frequency mode are now set per module by [SENS_AFBR_PROF](../advanced_config/parameter_reference.md#SENS_AFBR_PROF), or explicitly with [SENS_AFBR_RATE](../advanced_config/parameter_reference.md#SENS_AFBR_RATE) and [SENS_AFBR_DFM](../advanced_config/parameter_reference.md#SENS_AFBR_DFM).
|
||||
([PX4-Autopilot#28454](https://github.com/PX4/PX4-Autopilot/pull/28454))
|
||||
|
||||
12. **Check the distance-aware return (remaining flight time) failsafe.**
|
||||
12. **Check the auxiliary global position source ID.**
|
||||
EKF2 can now fuse up to four auxiliary global position sources, and the `EKF2_AGP_*` parameters are replaced by a set per source, `EKF2_AGPn_*`.
|
||||
The values of `EKF2_AGP_CTRL`, `EKF2_AGP_MODE`, `EKF2_AGP_DELAY`, `EKF2_AGP_NOISE` and `EKF2_AGP_GATE` are migrated to the first set (`EKF2_AGP0_*`), which only fuses messages whose `id` field matches [EKF2_AGP0_ID](../advanced_config/parameter_reference.md#EKF2_AGP0_ID).
|
||||
If `EKF2_AGP_CTRL` was set, the migration sets `EKF2_AGP0_ID` to `1`: the ID that `GlobalPositionMeasurementInterface` sends by default, and that the message translation node gives messages from v1.17 clients.
|
||||
If your source sends another ID, set `EKF2_AGP0_ID` to it and reboot.
|
||||
The default of `EKF2_AGPn_NOISE` is now `1.0` m (`0.9` m in v1.17), so a vehicle on the old default takes the new one.
|
||||
Only bit 0 of `EKF2_AGPn_CTRL` enables fusion; bit 1 (vertical position) is reserved, so a value with only bit 1 set no longer enables horizontal fusion.
|
||||
([PX4-Autopilot#26306](https://github.com/PX4/PX4-Autopilot/pull/26306), [PX4-Autopilot#29351](https://github.com/PX4/PX4-Autopilot/pull/29351), [PX4-Autopilot#29204](https://github.com/PX4/PX4-Autopilot/pull/29204))
|
||||
|
||||
13. **Check parameter files saved on v1.17 before loading them.**
|
||||
PX4 migrates renamed parameters only when it upgrades the parameters stored on the vehicle.
|
||||
Loading a parameter file saved on v1.17 in _QGroundControl_ sets each parameter by name, so values saved under old names such as `EKF2_GPS_DELAY`, `EKF2_GPS_POS_X/Y/Z`, `COM_RC_OVERRIDE`, `MPC_LAND_RC_HELP`, `SENS_IMU_TEMP` and `SENS_TEMP_ID` are not applied: the parameters that replace them keep their current values (the defaults on a new or reset vehicle).
|
||||
`RC1_REV` to `RC18_REV` are now integers: _QGroundControl_ v5.1.5 and earlier load a saved `-1.000000` as `0`, so a reversed channel is no longer reversed ([QGC#15357](https://github.com/mavlink/qgroundcontrol/issues/15357)).
|
||||
_QGroundControl_ saves every parameter, so such a file also restores v1.17 values whose defaults changed, including `FD_ACT_EN` and `SENS_MAG_AUTOCAL` (see item 16).
|
||||
[Tools/migrate_param_file.py](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/migrate_param_file.py) converts such a file for v1.18: it applies the renames, writes `RC*_REV` as integers, drops the removed parameters, replaces the v1.17 RoboClaw output defaults, whose scale changed, and lists the other v1.17 defaults it keeps.
|
||||
After loading such a file, check the replacement parameters and the direction of every RC channel.
|
||||
([PX4-Autopilot#26833](https://github.com/PX4/PX4-Autopilot/pull/26833))
|
||||
|
||||
14. **Check the failsafe exceptions for auto modes.**
|
||||
Bit 1 of [COM_RCL_EXCEPT](../advanced_config/parameter_reference.md#COM_RCL_EXCEPT) and [COM_DLL_EXCEPT](../advanced_config/parameter_reference.md#COM_DLL_EXCEPT) was `Hold` and is now `Auto modes`.
|
||||
In v1.17 this bit ignored manual control or data link loss in Hold and Takeoff.
|
||||
It now also applies to the other auto modes, including Land, Return, Descend, Follow Target, Precision Landing and Orbit, and the upgrade does not change the stored value.
|
||||
Nothing changes for `COM_DLL_EXCEPT` in Land and Precision Landing, which ignore data link loss with or without this bit.
|
||||
If you set this bit and want the failsafe in those modes, clear it: this also removes the exception for Hold and Takeoff.
|
||||
([PX4-Autopilot#26228](https://github.com/PX4/PX4-Autopilot/pull/26228))
|
||||
|
||||
15. **Check `COM_PARACHUTE` if you require a parachute.**
|
||||
`COM_PARACHUTE=1` prevented arming in v1.17 when the parachute system was missing or unhealthy.
|
||||
It now only warns, and the upgrade does not change the stored value.
|
||||
Set [COM_PARACHUTE](../advanced_config/parameter_reference.md#COM_PARACHUTE) to `2` (Error) or higher to keep preventing arming.
|
||||
([PX4-Autopilot#27903](https://github.com/PX4/PX4-Autopilot/pull/27903))
|
||||
|
||||
16. **Review the checks that are now disabled by default.**
|
||||
[FD_ACT_EN](../advanced_config/parameter_reference.md#FD_ACT_EN) and [SENS_MAG_AUTOCAL](../advanced_config/parameter_reference.md#SENS_MAG_AUTOCAL) changed from `1` to `0`, and a vehicle on the old default takes the new one.
|
||||
Set `FD_ACT_EN` to `1` to keep the motor failure check based on ESC current and the disarm during spool-up when not all ESCs are armed, which v1.17 ran under the removed `FD_ESCS_EN`.
|
||||
`FD_ESCS_EN` also disarmed during spool-up when an ESC reported a fault, which v1.18 no longer does.
|
||||
With [COM_ARM_CHK_ESCS](../advanced_config/parameter_reference.md#COM_ARM_CHK_ESCS) at its default `0`, ESC offline and ESC fault reports no longer run: set it to `1` to detect them, which also prevents arming while an ESC is offline, reports a fault or has no telemetry.
|
||||
At `1` it also reports an offline ESC or any ESC fault, including temperature warnings and over RPM, as a motor failure, which triggers [COM_ACT_FAIL_ACT](../advanced_config/parameter_reference.md#COM_ACT_FAIL_ACT) in flight.
|
||||
In v1.17 an ESC fault never triggered `COM_ACT_FAIL_ACT`, so this also changes vehicles that already had `COM_ARM_CHK_ESCS` set.
|
||||
With `SENS_MAG_AUTOCAL` at `0`, an uncalibrated magnetometer no longer saves an initial calibration by itself, so calibrate it from the ground station.
|
||||
([PX4-Autopilot#26262](https://github.com/PX4/PX4-Autopilot/pull/26262), [PX4-Autopilot#26420](https://github.com/PX4/PX4-Autopilot/pull/26420), [PX4-Autopilot#27659](https://github.com/PX4/PX4-Autopilot/pull/27659))
|
||||
|
||||
17. **Check the distance-aware return (remaining flight time) failsafe.**
|
||||
`COM_FLTT_LOW_ACT` has been removed and its function is part of [COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT) again: option `3` engages Return mode when the remaining flight time is only just enough to return. All other options only warn.
|
||||
This restores the behaviour that `COM_LOW_BAT_ACT=3` had with otherwise default parameters in v1.12 to v1.16; v1.17 was the exception, as it disabled the distance-aware return by default (`COM_FLTT_LOW_ACT=0`).
|
||||
`COM_FLTT_LOW_ACT` is not migrated: if you use `COM_LOW_BAT_ACT=3` and do not want distance-aware return, change it to the new option `5`.
|
||||
See [Distance-Aware Return Failsafe](../config/safety.md#distance-aware-return-failsafe).
|
||||
([PX4-Autopilot#26955](https://github.com/PX4/PX4-Autopilot/pull/26955))
|
||||
|
||||
13. **Check the auxiliary global position source ID.**
|
||||
EKF2 can now fuse up to four auxiliary global position sources, and the `EKF2_AGP_*` parameters are replaced by a set per source, `EKF2_AGPn_*`.
|
||||
The values of `EKF2_AGP_CTRL`, `EKF2_AGP_MODE`, `EKF2_AGP_DELAY`, `EKF2_AGP_NOISE` and `EKF2_AGP_GATE` are migrated to the first set (`EKF2_AGP0_*`), which only fuses messages whose `id` field matches [EKF2_AGP0_ID](../advanced_config/parameter_reference.md#EKF2_AGP0_ID).
|
||||
If `EKF2_AGP_CTRL` was set, the migration sets `EKF2_AGP0_ID` to `1`: the ID that `GlobalPositionMeasurementInterface` sends by default, and that the message translation node gives messages from v1.17 clients.
|
||||
If your source sends another ID, set `EKF2_AGP0_ID` to it and reboot.
|
||||
The default of `EKF2_AGPn_NOISE` is now `1.0` m (`0.9` m in v1.17), so a vehicle on the old default takes the new one.
|
||||
([PX4-Autopilot#26306](https://github.com/PX4/PX4-Autopilot/pull/26306))
|
||||
18. **Check the IMU heater parameters.**
|
||||
The IMU heater now supports several instances, and its parameters moved to the first one: `SENS_IMU_TEMP`, `SENS_IMU_TEMP_FF`, `SENS_IMU_TEMP_I` and `SENS_IMU_TEMP_P` are now [HEATER1_TEMP](../advanced_config/parameter_reference.md#HEATER1_TEMP), `HEATER1_TEMP_FF`, `HEATER1_TEMP_I` and `HEATER1_TEMP_P`, and `SENS_TEMP_ID` is now [HEATER1_SENS_ID](../advanced_config/parameter_reference.md#HEATER1_SENS_ID).
|
||||
Stored values are migrated.
|
||||
`SENS_TEMP_ID=0` kept the heater from starting, while `HEATER1_SENS_ID=0` selects a sensor automatically, so a stored `0` becomes `-1` (disabled).
|
||||
([PX4-Autopilot#26325](https://github.com/PX4/PX4-Autopilot/pull/26325), [PX4-Autopilot#29354](https://github.com/PX4/PX4-Autopilot/pull/29354))
|
||||
|
||||
19. **Flash the new ARK FPV target for fixed-wing and VTOL.**
|
||||
To free flash, `ark_fpv_default` is now multicopter only.
|
||||
Fixed-wing vehicles need `ark_fpv_fw` and VTOLs `ark_fpv_vtol`, which leave out some system commands, including `sd_bench` and `listener`, to fit.
|
||||
A fixed-wing or VTOL vehicle flashed with `ark_fpv_default` has no fixed-wing or VTOL controller.
|
||||
([PX4-Autopilot#27906](https://github.com/PX4/PX4-Autopilot/pull/27906))
|
||||
|
||||
20. **Reflash the bootloader on Matek H743 and H743-Mini boards.**
|
||||
The PX4 bootloader for these boards identified as a Holybro Durandal (board ID `139`) instead of the Matek H743 (`1013`) that the firmware uses, so _QGroundControl_ refused to flash them.
|
||||
The bootloader now uses `1013`. Boards that already run the old PX4 bootloader need a bootloader built from v1.18 (`make matek_h743_bootloader` or `make matek_h743-mini_bootloader`) flashed over DFU: a firmware update alone does not fix them.
|
||||
([PX4-Autopilot#28654](https://github.com/PX4/PX4-Autopilot/pull/28654))
|
||||
|
||||
21. **Check that GCS and companion software leave unused command parameters empty.**
|
||||
PX4 now rejects a `COMMAND_LONG`, `COMMAND_INT` or mission item that sets a value other than `0` or `NaN` in a parameter (1 to 4) that the command does not use: commands are denied with `MAV_RESULT_DENIED` and mission uploads fail with `MAV_MISSION_INVALID_PARAMn`.
|
||||
([PX4-Autopilot#27541](https://github.com/PX4/PX4-Autopilot/pull/27541))
|
||||
|
||||
## Hardware Support
|
||||
|
||||
@@ -130,7 +188,7 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- Analog Devices ADIS1657x IMU driver. ([PX4-Autopilot#27239](https://github.com/PX4/PX4-Autopilot/pull/27239))
|
||||
- Analog Devices ADIS1650x IMU driver (ADIS16500/16501/16505/16507 family). ([PX4-Autopilot#27240](https://github.com/PX4/PX4-Autopilot/pull/27240))
|
||||
- ST LSM6DSV16X IMU driver, enabled as a probe-based alternative IMU on [Pixhawk 6C](../flight_controller/pixhawk6c.md). ([PX4-Autopilot#26951](https://github.com/PX4/PX4-Autopilot/pull/26951))
|
||||
- LSM6DSV 32X and DSK320X variant support in the ST LSM6DSV IMU driver. ([PX4-Autopilot#27523](https://github.com/PX4/PX4-Autopilot/pull/27523))
|
||||
- LSM6DSV 32X, DSK320X, 80X and 320X variant support in the ST LSM6DSV IMU driver. ([PX4-Autopilot#27523](https://github.com/PX4/PX4-Autopilot/pull/27523), [PX4-Autopilot#27625](https://github.com/PX4/PX4-Autopilot/pull/27625))
|
||||
- [Hiwonder 4-channel encoder motor module](../peripherals/hiwonder_emm.md) driver, enabled via [HIWONDER_EMM_EN](../advanced_config/parameter_reference.md#HIWONDER_EMM_EN) (started from `rc.rover`). ([PX4-Autopilot#27229](https://github.com/PX4/PX4-Autopilot/pull/27229))
|
||||
- TI ADS7128 I2C ADC driver. ([PX4-Autopilot#26471](https://github.com/PX4/PX4-Autopilot/pull/26471))
|
||||
- AUAV L60D support in the AUAV differential pressure sensor driver. ([PX4-Autopilot#27219](https://github.com/PX4/PX4-Autopilot/pull/27219))
|
||||
@@ -146,6 +204,13 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- [Pixhawk 6C](../flight_controller/pixhawk6c.md): RM3100 fallback for the internal compass. ([PX4-Autopilot#27299](https://github.com/PX4/PX4-Autopilot/pull/27299))
|
||||
- ModalAI VOXL 2: the separate board variants were merged into a single build, and PX4 for VOXL 2 is now packaged as a Debian package (`voxl-px4_*_arm64.deb`) that is built in CI and published with every PX4 release. ([PX4-Autopilot#26727](https://github.com/PX4/PX4-Autopilot/pull/26727))
|
||||
- ModalAI VOXL 2: INA226 and INA228 power monitor support, selectable via the `POWER_MANAGER` startup option, and the Lightware laser rangefinder driver enabled. ([PX4-Autopilot#26840](https://github.com/PX4/PX4-Autopilot/pull/26840), [PX4-Autopilot#27620](https://github.com/PX4/PX4-Autopilot/pull/27620))
|
||||
- ARK FMU-v6X: support for the ARKV6X-32X revision, with three LSM6DSV32X IMUs in place of the IIM-42653s. ([PX4-Autopilot#29769](https://github.com/PX4/PX4-Autopilot/pull/29769))
|
||||
- ARK FPV: support for the revision with an LSM6DSV32X IMU in place of the IIM-42653. Fixed-wing and VTOL now have their own build targets, `ark_fpv_fw` and `ark_fpv_vtol` (see the [Upgrade Guide](#upgrade-guide)). ([PX4-Autopilot#28512](https://github.com/PX4/PX4-Autopilot/pull/28512), [PX4-Autopilot#27906](https://github.com/PX4/PX4-Autopilot/pull/27906))
|
||||
- [Pixhawk 6X](../flight_controller/pixhawk6x.md): IIM-42653 IMU support on hardware revision 8, with an LSM6DSV fallback that starts only when neither the ICM-45686 nor the IIM-42653 is detected. ([PX4-Autopilot#27772](https://github.com/PX4/PX4-Autopilot/pull/27772), [PX4-Autopilot#29697](https://github.com/PX4/PX4-Autopilot/pull/29697))
|
||||
- Holybro Kakute H7 Wing: LSM6DSV IMU support. ([PX4-Autopilot#28780](https://github.com/PX4/PX4-Autopilot/pull/28780))
|
||||
- ARK FMU-v6X and ARK Pi6X: the IMU on SPI1, which the heater regulates, is now the primary IMU by default instead of whichever IMU validated first at boot. This applies to calibrations made after a fresh flash; a calibrated board keeps its stored priorities. ([PX4-Autopilot#28444](https://github.com/PX4/PX4-Autopilot/pull/28444))
|
||||
- Gear Up AirBrainH743: missions are stored in flash and survive a reboot. ([PX4-Autopilot#28505](https://github.com/PX4/PX4-Autopilot/pull/28505))
|
||||
- ADIS16507 IMU: `adis16507 status` reports the model, serial number and firmware version. ([PX4-Autopilot#29464](https://github.com/PX4/PX4-Autopilot/pull/29464))
|
||||
|
||||
### Notable Fixes
|
||||
|
||||
@@ -158,6 +223,23 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- PCA9685 PWM output board now uses the correct internal oscillator frequency, so configured servo PWM rates match the actual output. ([PX4-Autopilot#27425](https://github.com/PX4/PX4-Autopilot/pull/27425))
|
||||
- MAVLink OpenDroneID Basic ID messages are now forwarded to DroneCAN Remote ID peripherals. ([PX4-Autopilot#27274](https://github.com/PX4/PX4-Autopilot/pull/27274))
|
||||
- Analog battery voltage and current filters keep their state across parameter updates, so a parameter change no longer restarts them from zero and reports the battery as disconnected. ([PX4-Autopilot#28452](https://github.com/PX4/PX4-Autopilot/pull/28452))
|
||||
- PWM outputs are now driven low from reset until the output driver takes them, instead of floating with a weak pull-up. The pull-up kept AM32 ESCs in their bootloader on a battery-only boot, and a floating unassigned channel could pick up a neighbouring DShot signal and spin a motor. Capture channels that may carry a GPS PPS or camera signal stay inputs. ([PX4-Autopilot#28746](https://github.com/PX4/PX4-Autopilot/pull/28746))
|
||||
- Unplugging USB while connected over MAVLink, for example during a log download, no longer hardfaults the flight controller or corrupts the heap. ([PX4-Autopilot#29187](https://github.com/PX4/PX4-Autopilot/pull/29187))
|
||||
- DShot on STM32 now outputs the requested bit rate and duty cycles (it ran about 5% fast, with 33%/67% instead of 37.5%/75% high times), and extended DShot telemetry (EDT) is enabled reliably on Bluejay, BLHeli_S and AM32 ESCs. ([PX4-Autopilot#28511](https://github.com/PX4/PX4-Autopilot/pull/28511), [PX4-Autopilot#28436](https://github.com/PX4/PX4-Autopilot/pull/28436), [PX4-Autopilot#28438](https://github.com/PX4/PX4-Autopilot/pull/28438))
|
||||
- Bidirectional DShot rejects corrupted telemetry frames that previously passed the checksum and reported a false eRPM. ([PX4-Autopilot#29553](https://github.com/PX4/PX4-Autopilot/pull/29553))
|
||||
- InvenSense IMUs: invalid gyro FIFO samples are dropped instead of published as negative full scale, and the IIM-42653 reports its actual ±32 g / ±4000 dps range. FIFO clipping is now detected against the sensor's range, so the EKF's clipping handling also engages on ST, ADIS and BMI055 IMUs. ([PX4-Autopilot#28134](https://github.com/PX4/PX4-Autopilot/pull/28134), [PX4-Autopilot#28308](https://github.com/PX4/PX4-Autopilot/pull/28308), [PX4-Autopilot#28310](https://github.com/PX4/PX4-Autopilot/pull/28310))
|
||||
- ICM-45686: a single bad `WHO_AM_I` read after power-up no longer fails the probe. ([PX4-Autopilot#28319](https://github.com/PX4/PX4-Autopilot/pull/28319))
|
||||
- IIS2MDC magnetometer: the published temperature is read from the temperature registers instead of repeating the X field. ([PX4-Autopilot#28336](https://github.com/PX4/PX4-Autopilot/pull/28336))
|
||||
- AFBR-S50 rangefinders report their device type instead of an unknown device. ([PX4-Autopilot#29104](https://github.com/PX4/PX4-Autopilot/pull/29104))
|
||||
- NXP i.MX RT: each ADC is initialised, so the second ADC no longer stays unconfigured. ([PX4-Autopilot#28313](https://github.com/PX4/PX4-Autopilot/pull/28313))
|
||||
- `i2c_launcher`: `start -b <bus>` without `-t` no longer gives the INA226 an invalid battery index. ([PX4-Autopilot#28329](https://github.com/PX4/PX4-Autopilot/pull/28329))
|
||||
- NXP MR-VMU-TROPIC: the bootloader can be flashed from _QGroundControl_ again. ([PX4-Autopilot#29180](https://github.com/PX4/PX4-Autopilot/pull/29180))
|
||||
- Matek H743 and H743-Mini: the bootloader reports the Matek H743 board ID, so _QGroundControl_ can flash the boards (needs a bootloader reflash, see the [Upgrade Guide](#upgrade-guide)). ([PX4-Autopilot#28654](https://github.com/PX4/PX4-Autopilot/pull/28654))
|
||||
- DroneCAN time synchronization now works on SocketCAN boards (i.MX RT, Kinetis, S32K), where it silently did nothing. PX4 DroneCAN nodes report an unknown timestamp until they are time synchronized, and the flight controller maps node IMU, rangefinder and heading timestamps through the bus time base. ([PX4-Autopilot#28458](https://github.com/PX4/PX4-Autopilot/pull/28458), [PX4-Autopilot#28176](https://github.com/PX4/PX4-Autopilot/pull/28176))
|
||||
- DroneCAN GNSS receivers that send the 21-element covariance no longer feed EKF2 a wrong position covariance and a constant velocity covariance. ([PX4-Autopilot#28604](https://github.com/PX4/PX4-Autopilot/pull/28604))
|
||||
- DroneCAN GNSS jamming and spoofing states are no longer reported as unknown while a dual-antenna heading is valid. ([PX4-Autopilot#28847](https://github.com/PX4/PX4-Autopilot/pull/28847))
|
||||
- DroneCAN rangefinders take their orientation from the measurement. ([PX4-Autopilot#28199](https://github.com/PX4/PX4-Autopilot/pull/28199))
|
||||
- PX4 DroneCAN node firmware: `RestartNode` is answered before the node resets, a node without a valid heading reports a zero baseline so ArduPilot flight controllers do not use it as GPS yaw, and [CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) is the only node ID setting (0 reuses the ID the bootloader allocated; static IDs are 1 to 125). ([PX4-Autopilot#28966](https://github.com/PX4/PX4-Autopilot/pull/28966), [PX4-Autopilot#29002](https://github.com/PX4/PX4-Autopilot/pull/29002), [PX4-Autopilot#27644](https://github.com/PX4/PX4-Autopilot/pull/27644))
|
||||
|
||||
## Common
|
||||
|
||||
@@ -179,10 +261,14 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
| `COM_OBC_LOSS_T` | Timeout for missing heartbeats from the onboard computer is always 5 seconds (was the default). ([PX4-Autopilot#27261](https://github.com/PX4/PX4-Autopilot/pull/27261)) |
|
||||
| `COM_LKDOWN_TKO` | Takeoff failure detection always runs for 3 seconds (was the default). ([PX4-Autopilot#27262](https://github.com/PX4/PX4-Autopilot/pull/27262)) |
|
||||
|
||||
- [Serial Passthrough (MAVLink SERIAL_CONTROL)](../uart/serial_passthrough.md): new `serialpassthrough` driver enables MAVLink clients to read from and write to FC serial ports (TEL1/2, GPS1/2, TEL3/4).
|
||||
On STM32F7/H7 boards, ESC signal pins can also be written via a software bit-bang UART (device IDs 20–27): note that a bridge application is also required, so this functionality is not usable out of the box.
|
||||
- [Serial Passthrough (MAVLink SERIAL_CONTROL)](../uart/serial_passthrough.md): new `serialpassthrough` driver enables MAVLink clients to read from and write to FC serial ports (`TELEM1`/`TELEM2`, `GPS1`/`GPS2`, `TELEM3`/`TELEM4`).
|
||||
On STM32F7/H7 boards, ESC signal pins can also be written via a software bit-bang UART (device IDs 20–27).
|
||||
Host tools connect through a bridge application, such as [`Tools/mavlink_serial_bridge.py`](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/mavlink_serial_bridge.py) (it isn't part of the v1.18 release, but the version on `main` works with v1.18 firmware).
|
||||
([PX4-Autopilot#27605: feat(drivers): implemented serial passthrough](https://github.com/PX4/PX4-Autopilot/pull/27605)).
|
||||
- UAVCAN: firmware can now be flashed onto connected CAN nodes directly from the SD card. Place node firmware `.bin` files at the card root or in `/fs/microsd/ufw_staging/`; on boot the UAVCAN server migrates them into `/fs/microsd/ufw/`, tracks them in an `FW.db` database, and flashes any connected node whose firmware version does not match. ([PX4-Autopilot#27043](https://github.com/PX4/PX4-Autopilot/pull/27043))
|
||||
- [Distance-aware return failsafe](../config/safety.md#distance-aware-return-failsafe) (also known as "bingo fuel"): engaging Return mode when the remaining flight time is only just enough to return is now part of [COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT) `3` (the new option `5` opts out), instead of the separate `COM_FLTT_LOW_ACT`. See the [Upgrade Guide](#upgrade-guide). ([PX4-Autopilot#26955](https://github.com/PX4/PX4-Autopilot/pull/26955))
|
||||
- _QGroundControl_ no longer asks for a reboot after changing parameters that apply immediately, such as the gyro filters and the log rotation settings. ([PX4-Autopilot#29517](https://github.com/PX4/PX4-Autopilot/pull/29517))
|
||||
- Security hardening: out-of-bounds reads and writes, a format string bug and missing input checks were fixed in input parsing from external devices and links, including the Iridium SBD, HoTT, FT Technologies FT7, Sagetech MXS, MSP OSD and VectorNav drivers, DroneCAN battery and log messages, the CAN bootloader, Cyphal, Zenoh, the GPS NMEA, Ashtech and u-blox parsers, BSON parameter files, MAVLink FTP directory listings, external mode registration and arming check replies over uXRCE-DDS, and the `param select` command. ([PX4-Autopilot#29493](https://github.com/PX4/PX4-Autopilot/pull/29493), [PX4-Autopilot#28599](https://github.com/PX4/PX4-Autopilot/pull/28599), [PX4-Autopilot#29494](https://github.com/PX4/PX4-Autopilot/pull/29494), [PX4-Autopilot#28600](https://github.com/PX4/PX4-Autopilot/pull/28600), [PX4-Autopilot#28580](https://github.com/PX4/PX4-Autopilot/pull/28580), [PX4-Autopilot#28579](https://github.com/PX4/PX4-Autopilot/pull/28579), [PX4-Autopilot#28578](https://github.com/PX4/PX4-Autopilot/pull/28578), [PX4-Autopilot#29490](https://github.com/PX4/PX4-Autopilot/pull/29490), [PX4-Autopilot#28606](https://github.com/PX4/PX4-Autopilot/pull/28606), [PX4-Autopilot#29492](https://github.com/PX4/PX4-Autopilot/pull/29492), [PX4-Autopilot#29487](https://github.com/PX4/PX4-Autopilot/pull/29487), [PX4-Autopilot#29485](https://github.com/PX4/PX4-Autopilot/pull/29485), [PX4-Autopilot#29486](https://github.com/PX4/PX4-Autopilot/pull/29486), [PX4-Autopilot#29087](https://github.com/PX4/PX4-Autopilot/pull/29087), [PX4-Autopilot#29482](https://github.com/PX4/PX4-Autopilot/pull/29482), [PX4-Autopilot#28973](https://github.com/PX4/PX4-Autopilot/pull/28973), [PX4-GPSDrivers#232](https://github.com/PX4/PX4-GPSDrivers/pull/232), [PX4-GPSDrivers#235](https://github.com/PX4/PX4-GPSDrivers/pull/235), [PX4-Autopilot#28607](https://github.com/PX4/PX4-Autopilot/pull/28607), [PX4-Autopilot#28602](https://github.com/PX4/PX4-Autopilot/pull/28602), [PX4-Autopilot#28619](https://github.com/PX4/PX4-Autopilot/pull/28619), [PX4-Autopilot#28598](https://github.com/PX4/PX4-Autopilot/pull/28598), [PX4-Autopilot#28622](https://github.com/PX4/PX4-Autopilot/pull/28622), [PX4-Autopilot#28475](https://github.com/PX4/PX4-Autopilot/pull/28475))
|
||||
|
||||
## Control
|
||||
|
||||
@@ -192,10 +278,11 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- New [COM_FLTMODE_BOOT](../advanced_config/parameter_reference.md#COM_FLTMODE_BOOT) sets the flight mode the vehicle boots into before any RC input or mode command is received. Default is Hold; Manual, Altitude, Position, Mission, Stabilized, Takeoff, and external modes can also be selected. ([PX4-Autopilot#27641](https://github.com/PX4/PX4-Autopilot/pull/27641))
|
||||
- Stick inputs are now ignored while an arm or kill gesture is being held: during an arm gesture the throttle and yaw sticks are neutralized, and during a kill gesture all four channels are neutralized, so holding the sticks in the gesture corners no longer feeds spurious commands into the controller.
|
||||
- New [MPC_Z_ERR_MAX](../advanced_config/parameter_reference.md#MPC_Z_ERR_MAX) (default `1.0` m) caps how far the smoothed vertical trajectory may lead the vehicle, the vertical analog of `MPC_XY_ERR_MAX`. This suppresses altitude overshoots caused by a noisy altitude reference, such as a mission setpoint jittering as the home altitude estimate is refined in flight. ([PX4-Autopilot#27607](https://github.com/PX4/PX4-Autopilot/pull/27607))
|
||||
- Multicopter attitude control ignores an attitude setpoint with a zero, non-finite or overflowing quaternion, together with its thrust. A single such setpoint previously disabled attitude control until reboot. ([PX4-Autopilot#29008](https://github.com/PX4/PX4-Autopilot/pull/29008))
|
||||
- The control allocator zeroes non-finite torque setpoint components, which external producers over uXRCE-DDS or Zenoh could send, instead of turning every actuator output off. ([PX4-Autopilot#29156](https://github.com/PX4/PX4-Autopilot/pull/29156))
|
||||
|
||||
## Safety
|
||||
|
||||
- [Distance-aware return failsafe](../config/safety.md#distance-aware-return-failsafe) (also known as "bingo fuel"): engaging Return mode when the remaining flight time is only just enough to return is now part of [COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT) `3` (the new option `5` opts out), instead of the separate `COM_FLTT_LOW_ACT`. See the [Upgrade Guide](#upgrade-guide). ([PX4-Autopilot#26955](https://github.com/PX4/PX4-Autopilot/pull/26955))
|
||||
- Rotary-wing vehicles now support uncommanded altitude loss detection: if the vehicle descends more than [FD_ALT_LOSS](../advanced_config/parameter_reference.md#FD_ALT_LOSS) meters below its setpoint in altitude-controlled flight, flight termination (and parachute deployment) is triggered. See [Altitude Loss Trigger](../config/safety.md#altitude-loss-trigger). ([PX4-Autopilot#26837](https://github.com/PX4/PX4-Autopilot/pull/26837))
|
||||
- [Parachute health failsafe](../peripherals/parachute.md): extended [COM_PARACHUTE](../advanced_config/parameter_reference.md#COM_PARACHUTE) from a boolean into a configurable arming check and in-flight failsafe action parameter (Warning, Error, Return, or Land). The previously enabled value `COM_PARACHUTE=1` (Warning) now only warns without preventing arming; use `COM_PARACHUTE=2` (Error) or higher to prevent arming when the parachute system is missing or unhealthy. ([PX4-Autopilot#26918](https://github.com/PX4/PX4-Autopilot/pull/26918))
|
||||
- [GNSS check failsafe](../config/safety.md#gnss-check-failsafe): new failsafe that monitors the number of usable GNSS receivers with a 3D fix and their position consistency. The required number of receivers is set via [SYS_HAS_NUM_GNSS](../advanced_config/parameter_reference.md#SYS_HAS_NUM_GNSS) and the failsafe action via [COM_GNSSLOSS_ACT](../advanced_config/parameter_reference.md#COM_GNSSLOSS_ACT). ([PX4-Autopilot#26863](https://github.com/PX4/PX4-Autopilot/pull/26863))
|
||||
@@ -206,10 +293,14 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- Rejected missions now report the reason to the GCS (e.g. empty mission, dataman read failure) instead of failing silently. ([PX4-Autopilot#27254](https://github.com/PX4/PX4-Autopilot/pull/27254))
|
||||
- Arming with [RTL_TYPE](../advanced_config/parameter_reference.md#RTL_TYPE) set to `5` (safe points only) no longer requires a rally point to be uploaded: the vehicle falls back to returning to the home position when no rally point is defined. ([PX4-Autopilot#27773](https://github.com/PX4/PX4-Autopilot/pull/27773))
|
||||
- GCS connection-loss failsafe no longer triggers flight termination while the vehicle is disarmed, preventing a termination state from latching before or at arming after a ground station link loss. ([PX4-Autopilot#26820](https://github.com/PX4/PX4-Autopilot/pull/26820))
|
||||
- New [NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) option `7` (Hold without failsafe): on manual control (RC) loss the vehicle holds position but does not enter a failsafe state, so an external mode or offboard controller can keep commanding it. ([PX4-Autopilot#27792](https://github.com/PX4/PX4-Autopilot/pull/27792))
|
||||
- New [NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) option `7` (Hold without failsafe): on manual control (RC) loss the vehicle holds position but does not enter a failsafe state, so an external mode or offboard controller can keep commanding it. If [COM_OBL_RC_ACT](../advanced_config/parameter_reference.md#COM_OBL_RC_ACT) is a manual mode (the default, Position), a vehicle in Offboard mode without manual control now goes to Hold when its companion computer stops, instead of staying in Offboard. ([PX4-Autopilot#27792](https://github.com/PX4/PX4-Autopilot/pull/27792), [PX4-Autopilot#28961](https://github.com/PX4/PX4-Autopilot/pull/28961))
|
||||
- Control allocator now stops the motors when it receives a NaN thrust setpoint, instead of forwarding invalid values to the ESCs. ([PX4-Autopilot#26494](https://github.com/PX4/PX4-Autopilot/pull/26494))
|
||||
- The home position altitude filter receives its barometer time delta in seconds instead of microseconds. ([PX4-Autopilot#28415](https://github.com/PX4/PX4-Autopilot/pull/28415))
|
||||
- A mission that ends on an exhausted DO_JUMP no longer reports "Waypoint could not be read" at critical severity. ([PX4-Autopilot#28464](https://github.com/PX4/PX4-Autopilot/pull/28464))
|
||||
- With more than one battery, a battery that disconnects in flight no longer holds the [battery level failsafe](../config/safety.md#battery-level-failsafe) at the critical level when another battery reaches the emergency level, so with [COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT) set to `3` the vehicle now lands at the emergency level instead of continuing to return. ([PX4-Autopilot#29028](https://github.com/PX4/PX4-Autopilot/pull/29028))
|
||||
- Home is captured on the ground before the motors spin up, including when arming straight into a mission, so prop wash no longer disturbs the home altitude and a mission started at arming no longer uses a stale home altitude. ([PX4-Autopilot#27734](https://github.com/PX4/PX4-Autopilot/pull/27734))
|
||||
- Uploading a mission identical to the stored one restarts it from the first item. After a reboot such a mission previously reported itself finished immediately after starting. ([PX4-Autopilot#28775](https://github.com/PX4/PX4-Autopilot/pull/28775))
|
||||
- A geofence that fails to load is cleared and reported to the operator (new `GF_STATUS_FAILED`), instead of leaving a partly loaded fence active. ([PX4-Autopilot#28603](https://github.com/PX4/PX4-Autopilot/pull/28603))
|
||||
|
||||
## Estimation
|
||||
|
||||
@@ -225,6 +316,22 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- EKF2 can now use GNSS height as the height reference when GNSS is in dead-reckoning mode, provided it can start without requiring a reset. ([PX4-Autopilot#27766](https://github.com/PX4/PX4-Autopilot/pull/27766))
|
||||
- EKF2 now counts NED-frame external vision velocity fusion as a horizontal (NE) aiding source (and only counts vision position when it is in the NED frame), so vehicles aided only by vision velocity are no longer treated as dead-reckoning. ([PX4-Autopilot#27538](https://github.com/PX4/PX4-Autopilot/pull/27538))
|
||||
- The EKF2 selector no longer falls back to an instance whose vertical test ratio is already failing, which stepped the published altitude on every switch after a brief fault on the selected instance. ([PX4-Autopilot#28418](https://github.com/PX4/PX4-Autopilot/pull/28418))
|
||||
- EKF2 now caps the GNSS height observation noise at [EKF2_NOAID_NOISE](../advanced_config/parameter_reference.md#EKF2_NOAID_NOISE) only when no other height source is fused. With a barometer or another height source, a GNSS height with a poor reported vertical accuracy is no longer fused as more accurate than the receiver reports. ([PX4-Autopilot#29058](https://github.com/PX4/PX4-Autopilot/pull/29058))
|
||||
- EKF2 keeps the output predictor attitude correction in the earth frame. At high yaw rates, such as a multicopter spinning after a motor failure, `vehicle_attitude` previously diverged while the EKF state stayed correct. ([PX4-Autopilot#29062](https://github.com/PX4/PX4-Autopilot/pull/29062))
|
||||
- The IMU coning correction now uses the previous sample as in its reference, removing 83% instead of 21% of the coning drift at the default rates. ([PX4-Autopilot#29215](https://github.com/PX4/PX4-Autopilot/pull/29215))
|
||||
- An EKF2 origin set manually before position aiding now also places the global position there, so the Earth rate, gravity and magnetic field models no longer run at latitude and longitude 0 (and never recover on a flow-only flight). ([PX4-Autopilot#29237](https://github.com/PX4/PX4-Autopilot/pull/29237))
|
||||
- EKF2 checks the reported GNSS heading accuracy before resetting the heading to a dual-antenna GNSS heading, so a receiver still resolving its baseline can no longer align the heading to an inaccurate value. ([PX4-Autopilot#28846](https://github.com/PX4/PX4-Autopilot/pull/28846))
|
||||
- The `wind` topic publishes the sideslip innovation and its variance in the right fields. ([PX4-Autopilot#29080](https://github.com/PX4/PX4-Autopilot/pull/29080))
|
||||
|
||||
## Sensors
|
||||
|
||||
- Disabling the selected magnetometer at runtime (setting its [CAL_MAGn_PRIO](../advanced_config/parameter_reference.md#CAL_MAG0_PRIO) to `0`) now hands over to the next magnetometer without a sensor failure report, and a magnetometer disabled at boot no longer prevents those after it from being selected. ([PX4-Autopilot#28750](https://github.com/PX4/PX4-Autopilot/pull/28750))
|
||||
- Disabling the selected IMU at runtime (setting its [CAL_ACCn_PRIO](../advanced_config/parameter_reference.md#CAL_ACC0_PRIO) or [CAL_GYROn_PRIO](../advanced_config/parameter_reference.md#CAL_GYRO0_PRIO) to `0`) now hands over to the next IMU without a sensor failure report, including while the vehicle is armed. A re-enabled IMU reappears in `sensors_status_imu` and the IMU consistency check only once it publishes new data. ([PX4-Autopilot#28811](https://github.com/PX4/PX4-Autopilot/pull/28811))
|
||||
- [Thermal compensation](../advanced_config/sensor_thermal_calibration.md) for a magnetometer that reports no temperature now reads the barometer sample. Previously it read the accelerometer sample, which overran a stack buffer once a second and published the accelerometer y-axis value as the magnetometer temperature. ([PX4-Autopilot#28997](https://github.com/PX4/PX4-Autopilot/pull/28997))
|
||||
- External accelerometers and gyroscopes, such as a DroneCAN IMU, now default to Low priority (`25`, was `75`), so a new or uncalibrated external IMU no longer takes over from the on-board IMUs. Stored priorities are not changed. ([PX4-Autopilot#28594](https://github.com/PX4/PX4-Autopilot/pull/28594))
|
||||
- In the u-blox moving base modes ([GPS_UBX_MODE](../advanced_config/parameter_reference.md#GPS_UBX_MODE) `1` to `4`) the moving base and rover both run at 5 Hz, the u-blox maximum for a moving base, whatever the receiver model; a faster [GPS_UBX_RATE](../advanced_config/parameter_reference.md#GPS_UBX_RATE) is limited to 5 Hz with a warning. An X20P rover previously ran at 10 Hz and had no heading for the epochs its base did not observe. See [u-blox F9P heading](../gps_compass/u-blox_f9p_heading.md). ([PX4-Autopilot#28986](https://github.com/PX4/PX4-Autopilot/pull/28986))
|
||||
- With GNSS blending disabled (`SENS_GPS_MASK` `0`), the selected receiver is no longer throttled to the update rate of the slowest receiver. ([PX4-Autopilot#28998](https://github.com/PX4/PX4-Autopilot/pull/28998))
|
||||
- A barometer publishing at or below [SENS_BARO_RATE](../advanced_config/parameter_reference.md#SENS_BARO_RATE), such as a DroneCAN barometer, no longer feeds NaN into the barometer GNSS offset. ([PX4-Autopilot#29634](https://github.com/PX4/PX4-Autopilot/pull/29634))
|
||||
|
||||
## RC
|
||||
|
||||
@@ -249,6 +356,7 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
|
||||
- [Return mode VTOL Rally Point Approach Loiters](../flight_modes_vtol/return.md#vtol-rally-point-approach-loiters): VTOLs returning in fixed-wing mode can now use the approach loiter associated with the selected home/rally landing location (instead of home) to choose the most wind-aligned valid approach (if several are defined). ([PX4-Autopilot#27004: fix(navigator): rtl compute wind angle to select best land approach based on rally point location instead of home location](https://github.com/PX4/PX4-Autopilot/pull/27004))
|
||||
- Mission return modes keep a VTOL that is flying as a multicopter in multicopter mode instead of commanding a fixed-wing transition at return altitude, which could leave the vehicle armed instead of landing. ([PX4-Autopilot#28399](https://github.com/PX4/PX4-Autopilot/pull/28399))
|
||||
- A VTOL that switches to fixed-wing Offboard no longer briefly follows the last multicopter Offboard setpoint. ([PX4-Autopilot#29279](https://github.com/PX4/PX4-Autopilot/pull/29279))
|
||||
|
||||
### Fixed-wing
|
||||
|
||||
@@ -288,18 +396,28 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
([PX4-Autopilot#27251: fix(mavlink): Remove deprecated MAV_CMD_REQUEST_AUTOPILOT_CAPABILITIES](https://github.com/PX4/PX4-Autopilot/pull/27251), [PX4-Autopilot#27252: fix(mavlink): Remove legacy mavlink message requestors#27252](https://github.com/PX4/PX4-Autopilot/pull/27252))
|
||||
- MAVLink signing is now spec-compliant: signing activates only when a valid key is present on the SD card, `SETUP_SIGNING` is accepted on any link (not just USB) but rejected while armed, and signing can be disabled with a signed all-zero key. The non-standard `MAV_SIGN_CFG` parameter was removed and there is zero CPU/bandwidth overhead when signing is inactive. ([PX4-Autopilot#26894](https://github.com/PX4/PX4-Autopilot/pull/26894))
|
||||
- MAVLink FTP now maps the `@MAV_LOG` virtual directory (per the MAVLink FTP spec) to the flight-stack log root, so a GCS can browse logs without knowing the on-disk path. ([PX4-Autopilot#27151](https://github.com/PX4/PX4-Autopilot/pull/27151))
|
||||
- MAVLink FTP adds support for the `ListDirectoryWithTime` command, returning each file's last-modification time alongside the listing so a GCS can retrieve log timestamps without downloading the files (clients fall back to plain `ListDirectory` when unsupported). ([PX4-Autopilot#27542](https://github.com/PX4/PX4-Autopilot/pull/27542))
|
||||
- MAVLink FTP adds support for the `ListDirectoryWithTime` command, returning each file's last-modification time alongside the listing so a GCS can retrieve log timestamps without downloading the files (clients fall back to plain `ListDirectory` when unsupported). Directories are listed with size `0` and their modification time, as MAVSDK does. ([PX4-Autopilot#27542](https://github.com/PX4/PX4-Autopilot/pull/27542), [PX4-Autopilot#28628](https://github.com/PX4/PX4-Autopilot/pull/28628))
|
||||
- Fragmented `GPS_RTCM_DATA` messages are now reassembled before injection to the GPS receiver, with a compatibility fallback for older QGroundControl builds that omit the final zero-length fragment, fixing RTK correction handling for multi-fragment RTCM streams. See [RTK GPS](../advanced/rtk_gps.md). ([PX4-Autopilot#27084](https://github.com/PX4/PX4-Autopilot/pull/27084))
|
||||
- New `ESTIMATOR_SENSOR_FUSION_STATUS` MAVLink stream exposes per-sensor intended and active fusion bitmasks to the GCS. ([PX4-Autopilot#26739](https://github.com/PX4/PX4-Autopilot/pull/26739))
|
||||
- The mission protocol now resends `MISSION_COUNT` if no `MISSION_ACK` is received, recovering from a dropped `MISSION_COUNT` during upload. ([PX4-Autopilot#26872](https://github.com/PX4/PX4-Autopilot/pull/26872))
|
||||
- The MAVLink development dialect (`development.xml`) is no longer built into default targets; dedicated `mavlink-dev` build variants (fmu-v6x, sitl) are provided for prototyping unstable messages. ([PX4-Autopilot#25834](https://github.com/PX4/PX4-Autopilot/pull/25834))
|
||||
- Added support for the `MAV_CMD_DO_SET_GLOBAL_ORIGIN` command, letting a GCS set the global origin used to convert local to global position. Enabled in release builds. ([PX4-Autopilot#24697](https://github.com/PX4/PX4-Autopilot/pull/24697), [PX4-Autopilot#27789](https://github.com/PX4/PX4-Autopilot/pull/27789))
|
||||
- The `cellular_status` uORB message and MAVLink `CELLULAR_STATUS` stream gained extended fields for richer modem/link reporting. ([PX4-Autopilot#27760](https://github.com/PX4/PX4-Autopilot/pull/27760))
|
||||
- Commands and mission items that set a parameter the command does not use are now rejected (see the [Upgrade Guide](#upgrade-guide)). ([PX4-Autopilot#27541](https://github.com/PX4/PX4-Autopilot/pull/27541), [PX4-Autopilot#28659](https://github.com/PX4/PX4-Autopilot/pull/28659), [PX4-Autopilot#28732](https://github.com/PX4/PX4-Autopilot/pull/28732), [PX4-Autopilot#29758](https://github.com/PX4/PX4-Autopilot/pull/29758))
|
||||
- Added support for `MAV_CMD_DO_SET_SAFETY_SWITCH_STATE`. `param1` follows the MAVLink `SAFETY_SWITCH_STATE` enum: `0` (`SAFETY_SWITCH_STATE_SAFE`) activates safety and `1` (`SAFETY_SWITCH_STATE_DANGEROUS`) deactivates it. The v1.18 beta and release candidate builds used the opposite values, and the `VehicleCommand` constants are now `SAFETY_SAFE` and `SAFETY_DANGEROUS`. ([PX4-Autopilot#26079](https://github.com/PX4/PX4-Autopilot/pull/26079), [PX4-Autopilot#28948](https://github.com/PX4/PX4-Autopilot/pull/28948))
|
||||
- `SET_ATTITUDE_TARGET` with an unusable attitude quaternion or a non-finite thrust is dropped and no longer counts as the Offboard signal, so the Offboard loss failsafe takes over. A NaN thrust previously stopped all lift motors of a multicopter. ([PX4-Autopilot#29008](https://github.com/PX4/PX4-Autopilot/pull/29008), [PX4-Autopilot#29328](https://github.com/PX4/PX4-Autopilot/pull/29328))
|
||||
- MAVLink signing: `SETUP_SIGNING` is only applied when it is broadcast or addressed to PX4, so a key meant for a companion computer is no longer applied to PX4, and signing state is now thread safe, which closes a window where a message replayed on another link could be accepted. ([PX4-Autopilot#29536](https://github.com/PX4/PX4-Autopilot/pull/29536), [PX4-Autopilot#28697](https://github.com/PX4/PX4-Autopilot/pull/28697))
|
||||
- With signing active, a full-size signed frame is no longer sent without its signature, which made every MAVLink log streaming frame unparsable. ([PX4-Autopilot#29164](https://github.com/PX4/PX4-Autopilot/pull/29164))
|
||||
- With signing active, unsigned `ADSB_VEHICLE` and `COLLISION` are only accepted on links in `ADS-B/Traffic (uAvionix)` mode (see the [Upgrade Guide](#upgrade-guide)). ([PX4-Autopilot#29488](https://github.com/PX4/PX4-Autopilot/pull/29488))
|
||||
- Log requests (`LOG_REQUEST_LIST`, `LOG_REQUEST_DATA`, `LOG_REQUEST_END`, `LOG_ERASE`) and `TUNNEL` messages are only handled when addressed to this vehicle. On a link shared by several vehicles, a `LOG_ERASE` for one vehicle previously erased the logs of all of them. ([PX4-Autopilot#28585](https://github.com/PX4/PX4-Autopilot/pull/28585), [PX4-Autopilot#28597](https://github.com/PX4/PX4-Autopilot/pull/28597))
|
||||
- MAVLink FTP checks write access when a file is opened for writing, against the file being opened, and boards that store files in `/fs/flash` accept FTP writes again. Resent FTP replies are complete, and a lost Open reply for a file whose size ends in `5` no longer fails the transfer. ([PX4-Autopilot#28584](https://github.com/PX4/PX4-Autopilot/pull/28584), [PX4-Autopilot#28652](https://github.com/PX4/PX4-Autopilot/pull/28652), [PX4-Autopilot#28582](https://github.com/PX4/PX4-Autopilot/pull/28582), [PX4-Autopilot#29535](https://github.com/PX4/PX4-Autopilot/pull/29535))
|
||||
- A rangefinder peripheral on a link in distance sensor mode, such as the ARK DIST, ignores the `DISTANCE_SENSOR` messages the flight controller streams back, instead of republishing them as a second rangefinder. ([PX4-Autopilot#29454](https://github.com/PX4/PX4-Autopilot/pull/29454))
|
||||
|
||||
## Ethernet & Networking
|
||||
|
||||
- MAVLink over UDP on NuttX now sets a send timeout on the socket, so a saturated or stalled network link can no longer block the MAVLink sender indefinitely while waiting for IO buffers. ([PX4-Autopilot#26988](https://github.com/PX4/PX4-Autopilot/pull/26988))
|
||||
- The uXRCE-DDS client no longer stalls under high UDP load. ([PX4-Autopilot#26161](https://github.com/PX4/PX4-Autopilot/pull/26161))
|
||||
- A MAVLink UDP client that restarts from a new source port is picked up again once the previous client has been quiet for 3 seconds, instead of PX4 sending to the old port until reboot. Addresses set with `-t` or `-c` are never replaced. ([PX4-Autopilot#28518](https://github.com/PX4/PX4-Autopilot/pull/28518))
|
||||
|
||||
## ROS 2
|
||||
|
||||
@@ -313,13 +431,36 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
|
||||
### uXRCE-DDS
|
||||
|
||||
- uXRCE-DDS, add support for DDS `v3`, ROS 2 Lyrical and Rolling ([PX4-Autopilot#27597](https://github.com/PX4/PX4-Autopilot/pull/27597))
|
||||
- uXRCE-DDS topic bridging gained per-topic drain and unlimited-rate options, letting a topic be published as fast as it updates instead of at a fixed interval. ([PX4-Autopilot#27688](https://github.com/PX4/PX4-Autopilot/pull/27688))
|
||||
- [DDS version selection](../middleware/uxrce_dds.md#version-selection).
|
||||
Added support for DDS v3, ROS 2 Lyrical Luth and Rolling Ridley ([PX4-Autopilot#27597](https://github.com/PX4/PX4-Autopilot/pull/27597))
|
||||
- Topic bridging gained per-topic drain and unlimited-rate options, letting a topic be published as fast as it updates instead of at a fixed interval.
|
||||
([PX4-Autopilot#27688](https://github.com/PX4/PX4-Autopilot/pull/27688))
|
||||
- Added rate limiter to [`vehicle_attitude`](../msg_docs/VehicleAttitude.md) and [`vehicle_odometry`](../msg_docs/VehicleOdometry.md) topic publishers.
|
||||
([PX4-Autopilot#25792](https://github.com/PX4/PX4-Autopilot/pull/25792))
|
||||
- New uORB topics bridged.
|
||||
([PX4-Autopilot#27681](https://github.com/PX4/PX4-Autopilot/pull/27681))
|
||||
|
||||
| uORB | ROS 2 | Direction | Instance | Max Rate [Hz] |
|
||||
| ---------- | ------------------- | ------------ | -------- | ------------- |
|
||||
| `vtx` | `/fmu/out/vtx` | PX4 to ROS 2 | `0` | 1 |
|
||||
| `input_rc` | `/fmu/out/input_rc` | PX4 to ROS 2 | `0` | 10 |
|
||||
|
||||
- [Multi instance publication](../middleware/uxrce_dds.md#dds-topics-yaml).
|
||||
Added `instance` field to the `publications` section of `dds_topics.yaml` to control which uORB instance is published to ROS 2.
|
||||
Defaults to instance zero.
|
||||
([PX4-Autopilot#22350](https://github.com/PX4/PX4-Autopilot/pull/22350))
|
||||
- Added support for hardware flow control when using serial communication.
|
||||
**Note:** [Custom Micro XRCE DDS Agent](https://github.com/eProsima/Micro-XRCE-DDS-Agent/pull/407) build is required.
|
||||
([PX4-Autopilot#26209](https://github.com/PX4/PX4-Autopilot/pull/26209))
|
||||
- ROS 2 subscriptions can be demuxed into different uORB topic instances.
|
||||
([PX4-Autopilot#26305](https://github.com/PX4/PX4-Autopilot/pull/26305))
|
||||
|
||||
### Zenoh
|
||||
|
||||
- Zenoh publisher options (reliability, priority, congestion control, express) are now configurable, both as common defaults and per-publisher overrides gated by the `ZENOH_PUB_OPTION_OVERRIDE` build option. ([PX4-Autopilot#27157](https://github.com/PX4/PX4-Autopilot/pull/27157))
|
||||
- Added a Zenoh build variant (`zenoh.px4board`) for the ARKV6X flight controller. ([PX4-Autopilot#25887](https://github.com/PX4/PX4-Autopilot/pull/25887))
|
||||
- Added support for ROS 2 Humble and earlier.
|
||||
([PX4-Autopilot#26619](https://github.com/PX4/PX4-Autopilot/pull/26619))
|
||||
|
||||
## Simulation
|
||||
|
||||
@@ -330,11 +471,13 @@ For users upgrading from v1.17, please take a moment to review the following bef
|
||||
- MAVLink can now be bound to a specific network interface by setting the `PX4_NET_INTERFACE` environment variable. ([PX4-Autopilot#26385](https://github.com/PX4/PX4-Autopilot/pull/26385))
|
||||
- The simulated GPS (`sensor_gps_sim`) now supports failure injection via `MAV_CMD_INJECT_FAILURE` (`FAILURE_UNIT_SENSOR_GPS`) with off, stuck, and wrong modes, selectable per receiver. ([PX4-Autopilot#27396](https://github.com/PX4/PX4-Autopilot/pull/27396))
|
||||
- The simulated airspeed sensor (`sensor_airspeed_sim`) now supports off, stuck, and wrong failure injection via `MAV_CMD_INJECT_FAILURE`. ([PX4-Autopilot#27006](https://github.com/PX4/PX4-Autopilot/pull/27006))
|
||||
- Fixed lockstep scheduler races that could lose a wakeup or deadlock SITL. ([PX4-Autopilot#28885](https://github.com/PX4/PX4-Autopilot/pull/28885), [PX4-Autopilot#29061](https://github.com/PX4/PX4-Autopilot/pull/29061))
|
||||
|
||||
### Gazebo
|
||||
|
||||
- Add [ridge world](../sim_gazebo_gz/worlds.md#ridge) for testing terrain following with 1D lidar. ([PX4-Autopilot#27600](https://github.com/PX4/PX4-Autopilot/pull/27600))
|
||||
- The [gstreamer plugin](../sim_gazebo_gz/index.md) now supports streaming video from multiple cameras/vehicles simultaneously over UDP (base port plus instance offset); RTMP remains single-stream. ([PX4-Autopilot#27275](https://github.com/PX4/PX4-Autopilot/pull/27275))
|
||||
- The gstreamer camera plugin no longer grows memory without bound when the video pipeline stalls (which froze the host), reports pipeline errors, and falls back to x264 when the NVIDIA encoder fails. ([PX4-Autopilot#27873](https://github.com/PX4/PX4-Autopilot/pull/27873))
|
||||
|
||||
### SIH
|
||||
|
||||
|
||||
Reference in new issue
Block a user