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

Actuator Control in Real World #227

Open
ZifeiJiang opened this issue Sep 7, 2022 · 1 comment
Open

Actuator Control in Real World #227

ZifeiJiang opened this issue Sep 7, 2022 · 1 comment

Comments

@ZifeiJiang
Copy link

ZifeiJiang commented Sep 7, 2022

Hi Jaeyoung, 

I know you are an expert on Mavros controllers. I have googled about the mavros offboard control on internet. I have found examples of controlling the outer loop of a quad in offboard control mode, which sends body rate and attitude to px4, basically the same as in this repo. 

I am wondering whether it is possible to use actuator control in the real world. I have tested actuator control in SITL and it works fine.

Further more, is it possible to use the following uORB message from a companion computer with ROS2 or MavROS in real world? I think this can enable user to bypass the built in mixer and send rotor speed commands directly.

image

Thank you very much!

@ZifeiJiang ZifeiJiang changed the title Actuator Control Actuator Control in Real World Sep 7, 2022
@Jaeyoung-Lim
Copy link
Owner

@ZifeiJiang In principle there is nothing stopping you from using actuator control.

However what you need to be careful is the timedelay of sensor measurements to actuator commands that require a round trip to the companion computer. This requires you to have a very fast and reliable link between the companion computer and firmware. Normally the time delay introduced by the link is large enough to degrade the performance when doing offboard control with actuator setpoints

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

No branches or pull requests

2 participants