-
Notifications
You must be signed in to change notification settings - Fork 1
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
Simultaneous dual-input control #4
Comments
Googled Yes, the RMRC approach seems like a good first option. |
Spoken again with @jgvictores, we concluded the RMRC would not allow us to perform continuous control as it depends on trajectory generation with a well-defined end-point (with zero velocity). |
Not completely sure about this. Think of the task as a change of pose (in the pos+ori sense, even though rather than SE(3) this C-Space is a much more restricted subset of SO(3)):
|
Out of two command/sensor parameters, we only perform closed-loop control on one of them (#3): the polar angle (inclinación). Attemps on replicating this procedure on the azimuthal angle (orientación) lead to undesired behavior, which we believe is rooted in the physical coupling between both coordinates.
Different alternatives have been proposed: MIMO, fuzzy (discouraged), neural networks, single-axis control (a.k.a. decoupling control)...
@jgvictores suggested we just give a try to the classical Resolved Motion Rate Control (RMRC) by Whitney. We embraced this solution at roboticslab-uc3m/kinematics-dynamics, see BasicCartesianControl.
The text was updated successfully, but these errors were encountered: