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
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
We have been trying to get the PX4 Vision to fly autonomously in an indoor environment. We have an Optitrack system setup and are able to send commands and fly autonomously (such as flying a square through a list of waypoints via the setpoint_position/local topic). We are trying to include the PX4-Avoidance package but are finding that the drone does not 'execute' the commands when given. What I mean is that the drone will generate a setpoint_position/local message but it is not carried out by the PX4 Vision. Additionally the PX4 Vision does not generate rotation messages to face the goal and is always fixed to the direction it is currently facing (if I manually turn the drone, for example, the orientation of the messages will match this new orientation, i.e. keep it as is).
This is only occurring in the physical drone, and not in the Gazebo simulations. We are running ROS Melodic.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have been trying to get the PX4 Vision to fly autonomously in an indoor environment. We have an Optitrack system setup and are able to send commands and fly autonomously (such as flying a square through a list of waypoints via the setpoint_position/local topic). We are trying to include the PX4-Avoidance package but are finding that the drone does not 'execute' the commands when given. What I mean is that the drone will generate a setpoint_position/local message but it is not carried out by the PX4 Vision. Additionally the PX4 Vision does not generate rotation messages to face the goal and is always fixed to the direction it is currently facing (if I manually turn the drone, for example, the orientation of the messages will match this new orientation, i.e. keep it as is).
This is only occurring in the physical drone, and not in the Gazebo simulations. We are running ROS Melodic.
The text was updated successfully, but these errors were encountered: