Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multirotor mixers 6dof #1

Closed
wants to merge 48 commits into from
Closed

Multirotor mixers 6dof #1

wants to merge 48 commits into from

Conversation

jlecoeur
Copy link
Owner

@jlecoeur jlecoeur commented Nov 5, 2017

No description provided.

@jlecoeur
Copy link
Owner Author

jlecoeur commented Nov 5, 2017

Short video demonstrating "Go to location". Missions also work.
short video

Mixers: List geom files in CMakeLists.txt

Mixers: add option to normalize like legacy script

Fix py2 compatibility
Mixers: add quad_x, quad_h, quad_plus

Mixers: add quad_deadcat

Set quad_deadcat.toml according to dimensions of SK450 deadcat

Mixers: add hex_x, hex_plus, hex_cox and hex_t

Mixers: add geoms octa_x, octa_plus, octa_cox

Mixers: add wide geoms

Mixers: add tri_y and twin_engine geoms

Mixers: add dodeca geoms

Mixers: Add geom quad_x_pusher
quad_vtail: reverse prop direction (same quad_h) to combine yaw torque induced by propellers and yaw torque induced by tilted rotors.
@Jaeyoung-Lim
Copy link

What is the status of this PR? I am very intrested on building a airframe for it!

@jlecoeur
Copy link
Owner Author

@Jaeyoung-Lim very outdated !

Hopefully PX4#13351 and PX4#13519 will make it soon into master.
Then, the only thing left to port will the changes made in the MC position controller (1690ec3).

🤞

FYI @RomanBapst @bresch @dagar

@Jaeyoung-Lim
Copy link

@Jaeyoung-Lim Pretty awesome! Do you think it would make sense to add 3d force setpoint support for MC position / attitude controller? or do we need a separate Omnicopter attitude controller?

@jlecoeur
Copy link
Owner Author

jlecoeur commented Nov 19, 2019

Now that we have the work queues, it is relatively cheap to separate processing steps into modules.

What would make sense IMO would be to always provide 3D force setpoint in the position controller, then have different "mapping" modules convert it to attitude + 3D thrust based on the current airframe.

  • for multirotors, it would provide attitude setpoint just like now + a thrust setpoint aligned with the Z body axis
  • for omnicopters and VTOL, it would provide attitude + 3D thrust
  • for fixed wing, we can also think of converting the 3D force setpoint into attitude and forward thrust

@Jaeyoung-Lim
Copy link

@jlecoeur Thanks for the insights! I would be really excited to see fully actuated systems being enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants