You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am operating a VTOL based on PX4 firmware version 1.15.2 or later. After setting WV_EN to enable and executing MAV_CMD_DO_VTOL_TRANSITION to transition from multicopter mode to fixed-wing mode, the following issues occurred:
Mission failure: Unable to reach heading within timeout.
After the mission failure, the vehicle did not transition to fixed-wing mode and remained in multicopter mode.
To Reproduce
Set up a VTOL running PX4 firmware 1.15.2 or later.
Enable the WV_EN parameter.
Execute a VTOL transition mission:
3.1. Perform a back transition (fixed-wing to multicopter).
3.2. Then execute another transition to fixed-wing mode.
Expected behavior
Issue observed:
4.1. The aircraft's nose is not aligned with the next mission waypoint direction.
4.2. The same "Mission failure: unable to reach heading within timeout" error occurs.
4.3. The nose direction does not change as expected during the transition.
Additional findings:
5.1. When the WV_EN parameter was disabled, the issue did not occur, and the transition proceeded as expected.
5.2. In version 1.14.0, the logic was designed to control yaw during transition, even when the weather vane (WV_EN) feature was enabled. However, starting from version 1.15.0, some logic statements have been removed or modified.
Identified Code Changes
6.1. Mission.cpp → Logic has been removed or modified.
The following lines have been removed:
pos_sp_triplet->current.disable_weather_vane = true;
pos_sp_triplet->current.disable_weather_vane = false;
6.2. PositionSetpoint.msg → The message has been removed.
The following statement has been removed:
bool disable_weather_vane
6.3. FlightTaskAuto.cpp → The code has been modified.
The following statement has been modified:
_weathervane.setNavigatorForceDisabled(_sub_triplet_setpoint.get().current.disable_weather_vane);
After applying the above modifications, MAV_CMD_DO_VTOL_TRANSITION successfully executes the transition even when WV_EN is enabled on PX4 version 1.15.0 or later.
Describe the bug
I am operating a VTOL based on PX4 firmware version 1.15.2 or later. After setting WV_EN to enable and executing MAV_CMD_DO_VTOL_TRANSITION to transition from multicopter mode to fixed-wing mode, the following issues occurred:
To Reproduce
3.1. Perform a back transition (fixed-wing to multicopter).
3.2. Then execute another transition to fixed-wing mode.
Expected behavior
Issue observed:
4.1. The aircraft's nose is not aligned with the next mission waypoint direction.
4.2. The same "Mission failure: unable to reach heading within timeout" error occurs.
4.3. The nose direction does not change as expected during the transition.
Additional findings:
5.1. When the WV_EN parameter was disabled, the issue did not occur, and the transition proceeded as expected.
5.2. In version 1.14.0, the logic was designed to control yaw during transition, even when the weather vane (WV_EN) feature was enabled. However, starting from version 1.15.0, some logic statements have been removed or modified.
Identified Code Changes
6.1. Mission.cpp → Logic has been removed or modified.
The following lines have been removed:
pos_sp_triplet->current.disable_weather_vane = true;
pos_sp_triplet->current.disable_weather_vane = false;
6.2. PositionSetpoint.msg → The message has been removed.
The following statement has been removed:
bool disable_weather_vane
6.3. FlightTaskAuto.cpp → The code has been modified.
The following statement has been modified:
_weathervane.setNavigatorForceDisabled(_sub_triplet_setpoint.get().current.disable_weather_vane);
Screenshot / Media
Flight Log
https://logs.px4.io/plot_app?log=1db2b97a-d16c-4097-a82a-be04ed17c649
Software Version
PX4 v1.15.2 Ver.
Flight controller
Holybro X6, SITL
Vehicle type
Hybrid VTOL
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: