-
Notifications
You must be signed in to change notification settings - Fork 239
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
Unitree Go1 is leaning #16
Comments
I'm happy that you like this repo. Your figure and plots are very convenient for me to find and solve your problems. I have encountered some issues like yours in the A1 platform. The problem could be solved by joint calibration. My A1 isn't calibrated so well when out-of-shell that it's visible to the naked eye (movement asymmetry even with the built-in controller). You can communicate with the engineer in Unitree Robotics, who will tell you how to recalibrate the joint. |
Thank you, I'll reach them |
@abrobotics, je ne serai pas contre un peu d'aide, si vous avez 2 secondes 😋 |
@elpimous Hello, have you solved this problem? |
@liukaishu Hey, not yet. Mr qiayuanliao is helping me, cool. You are welcome to help too. Thanks |
@abrobotics @elpimous hello,brother,have u solved this problem? |
Hey, @zhuiyuehun |
Hey, I would like to get some information on the issues in the leaning of the robot. I did these in simulations such that there would be no hardware problems. Stance Leaning Go1 Robot stance Trot Drift The same drifting can be seen with the a1 robot when trotting. Question |
Stance LeaningThe joint velocity provided by the gazebo is biased, even when the robot is standing statically. You can double-check by plotting the velocity value and position value of the knee joint - the position remains the same value but there is a constant value in velocity. So this may cause stance leaning. I think I can differentiate the position instead of using the velocity provided by the gazebo directly to solve this problem. Trot DriftThe contact, joint velocity, joint position, and the filter itself all have the error or basis, so it's unavoidable. |
Hello, I am also trying to apply this controller on Unitree Go1. Can you give me some suggestion on how to modify this package to make it suitable for Go1 robot? Should I change the unitree_sdk which is suitable for Go1? |
Hi @AndrewZheng-1011 @abrobotics, Have you found a way to improve the trot drifting ? Joint calibration ? This is the original stance position from Unitree : We can observe that the hips' angles are perfectly flat and that there is a fairly good spacing between the rear legs. Both front and rear legs seem to converge towards the inside of the robot ("V-shape" configuration). This behaviour can also be observed in Gazebo. I think drifting could be improved if the angles of the hips were flatter. What do you think ? |
Hi all, However, it didn't affect the drifting. I tried to modify the MPC weight matrix Q to add more penalty on the x and y positions but no luck with that. The robot keeps drifting backwards and ends up falling on its own. @elpimous @AndrewZheng-1011 @abrobotics Any ideas guys ? Thank you very much for your help ! |
Sorry, mi not at this point for now... |
@lucasbrodo |
Hi all, Calibrating joints did help but there was still some stance leaning and trot drift. I managed to operate the Go1 robot during trials, but the motion still wasn't perfect. Unfortunately, I finished my work on this project and I am no longer working on Unitree Go1 robot. Thank's yall and good luck :) |
@lucasbrodo |
Hello, thank for this repository, it helps a lot!
I have a problem when I launch the controller on Unitree Go1:
I robot is not flat, and when I trot, the rear right (RR) hip seems to be lower that the others.
the most shocking behavior is that the robot limps to the right whereas the command is simply forward or backward (you can see in this video).
You can see that the RR foot force is different from the others:
Can you help with this ? I don't know if it's from IMU covariance, some hardware flaws or IMU/Joint bad calibration maybe.
The text was updated successfully, but these errors were encountered: