Unexpected random rotation of trunk in unitree AI #2568
Unanswered
gokulmk-12
asked this question in
Asking for Help
Replies: 1 comment
-
Hello, It is hard to explain this completely without information about the control, but this kind of behaviour can easily emerge in situations like this, where there is kinematic redundancy (i.e. there are many different qpos/qvel/qfrc vectors that can satisfy requirements at task level such as tracking the foot positions). Lacking compensation, overall body configuration may drift while still satisfying constraints. You can counteract this by adding a regularization term in your control that resolves redundancy in favour of more neutral body poses, or additionally also trying to track a desired body height/orientation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Intro
Hi!
I am an undergraduate student, using mujoco for my project on quadruped locomotion on uneven terrains.
My setup
I am using mujoco with python bindings, and the xml files were cloned from mujoco menagerie
My question
I am trying to implement a torque controller for swing leg and stance leg in trot gait. I modified the unitree A1 xml to suit for torque control mode. After writing the code for the trot gait, the tracking is pretty good, but i am stuck in a situation where the torso rotates randomly . I have attached a video below for your reference. The red marker is the thing which is supposed to be tracked.
Initially i felt that it was something to do with the freejoint component in the xml. So i tried increasing the stiffness and damping to compensate this rotation, which worked. my question, is this the way to remove the random roation of the torso ? Also i feel i messed up the xml conversion from position to torque control, i just copied it from go2 with minimal changes. Please do let me know where i have went wrong. I have attached the xml below.
torso_failure.webm
Minimal model and/or code that explain my question
If you encountered the issue in a complex model, please simplify it as much as possible (while still reproducing the issue).
Model:
Full A1 XML
Beta Was this translation helpful? Give feedback.
All reactions