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
Thank you for your question, and I apologize for not having the time to write a guide on real-world deployment yet. However, I am here to actively support you during your deployment process, and I hope this issue will assist others who wish to replicate it.
Currently, the SUPER publishes the committed trajectory in two ways.
The first and easier method uses position, velocity, acceleration, jerk, yaw, and yaw_dot from the following code snippet:
This can be input to the open-source PX4 high-level controller found here: PX4 Controller. Please note that the quadrotor_msgs may not be identical and could fail the MD5 check, causing ROS communication issues. We haven't tested it with px4ctrl, but copying PositionCommand.msg in mars_quadrotor_msgs to px4ctrl and recompiling the workspace may resolve this.
The second and more advanced method utilizes the published polynomial trajectory, which is suitable for an MPC controller. This allows the controller to evaluate multiple reference states along the trajectory for predictive control:
However, please note that the MPC module of SUPER is not yet open-sourced, but we plan to release it later this year. If you're interested in trying this method, you may need to implement it yourself in the meantime.
I will keep this issue open until I have time to create a comprehensive guide on real-world deployment. If you succeed and are willing to share your insights, I encourage you to document your experience here. I will reference this issue in the README to assist anyone looking to deploy SUPER on a real-world drone.
Thank you for your open source. Is the MPC part not open source? If we want to reproduce it, how can we replace it?
The text was updated successfully, but these errors were encountered: