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
Describe the bug
Triggering RTL when publishing to trajectory_setpoint topic in Offboard Mode vehicle continues to subscribe to the topic and makes vehicle unstable.
To Reproduce
Steps to reproduce the behavior:
Publish to /fmu/trajectory_setpoint/in within Offboard Mode
Trigger RTL
Vehicle attempts to RTL while still setting position setpoint using the topic /fmu/trajectory_setpoint/in
Eventually vehicle returns to home but does not disarm and continues to point toward /fmu/trajectory_setpoint/in
Expected behavior
My understanding is that triggering RTL should ignore /fmu/trajectory_setpoint/in from Offboard Mode. Shown below are the comparison between publishing to /fmu/trajectory_setpoint/in and not publishing to the topic during RTL.
Log Files and Screenshots
Drone (please complete the following information):
Based on V1.12.3
Pixhawk 4
**Additional Context
This behavior was identified from issue #18983
The text was updated successfully, but these errors were encountered:
Currently there's a bug with trajectory_setpoint being published by both offboard and flight_tasks I fixed it in this PR #18318 but it's still waiting review
Describe the bug
Triggering RTL when publishing to
trajectory_setpoint
topic inOffboard Mode
vehicle continues to subscribe to the topic and makes vehicle unstable.To Reproduce
Steps to reproduce the behavior:
/fmu/trajectory_setpoint/in
withinOffboard Mode
/fmu/trajectory_setpoint/in
/fmu/trajectory_setpoint/in
Expected behavior
My understanding is that triggering RTL should ignore
/fmu/trajectory_setpoint/in
fromOffboard Mode
. Shown below are the comparison between publishing to/fmu/trajectory_setpoint/in
and not publishing to the topic during RTL.Log Files and Screenshots
Drone (please complete the following information):
**Additional Context
This behavior was identified from issue #18983
The text was updated successfully, but these errors were encountered: