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

Simultaneous dual-input control #4

Open
PeterBowman opened this issue Jan 11, 2020 · 3 comments
Open

Simultaneous dual-input control #4

PeterBowman opened this issue Jan 11, 2020 · 3 comments

Comments

@PeterBowman
Copy link
Member

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.

@jgvictores
Copy link
Member

Googled Decoupling control rpy, found papers such as "Decoupling control for a three-axis inertially stabilized platform used for aerial remote sensing" (https://doi.org/10.1177%2F0142331214557667).

Yes, the RMRC approach seems like a good first option.

@PeterBowman
Copy link
Member Author

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).

@jgvictores
Copy link
Member

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)):

  • Target is a differential away: use the Jacobian (small enough increment * timestep also works)!
  • The distance to the target is larger than a differential (or than a small enough increment): generate a trajectory in the C-Space and use RMRC!

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