Closed jgvictores closed 5 years ago
From @munozyanez on April 25, 2017 19:19
Corrected some issues about motor turn directions. Redone the xml openrave teo ( https://github.com/roboticslab-uc3m/teo-openrave-models ) definition for both legs according to real robot. Ready to pull request if no worries. Also redone DH for both legs according to new turn directions. Also ready to pull request.
From @munozyanez on April 25, 2017 19:21
But... the robot is still not moving correctly, next we will review the motor speeds for legs to avoid errors in that direction.
Okay, my main concern is to keep matching descriptions across files/repositories.
Kinematics:
Motor:
Could you please be very careful with this and keep updated and documented ??
From @munozyanez on April 27, 2017 10:58
I can update the drawings, but I will need the source files. Cant find in ( http://robots.uc3m.es/svn/TEOrepo/modelling/diagrams/editable/ ). Is there another place to look for apart from this one?
From @munozyanez on April 27, 2017 16:5
Ok, shall I pull request or just update the files?
I think its okay to update directly, just try to cross-reference as much as possible (mention this issue in commits, etc). A branch and merge --no-ff is good as well. Thanks!
From @munozyanez on April 27, 2017 18:36
Ok, done updates. All but https://github.com/roboticslab-uc3m/yarp-devices , as it seems to be deprecated. Not closing issue, because leg movement is still faulty. Maybe related with Absolute encoders signs in configuration files?
From @munozyanez on April 27, 2017 18:40
Sorry, I mean the files will be no longer in this repo, not that repo will be deprecated.
Duplicate/blocked by #39, affects many including #38.
I'm marking this as resolved via https://github.com/roboticslab-uc3m/teo-main/issues/39 and https://github.com/roboticslab-uc3m/teo-main/issues/38.
Our guide is https://github.com/roboticslab-uc3m/teo-developer-manual (all positive w.r.t. root).
From @munozyanez on April 20, 2017 19:25
Launching ´´yarpdev --device BasicTwoLimbCartesianControl´´ results in a faulty movement on teo. teoSim is working correctly with the same parameters.
Find below some points as example.
´´ New trajectory segment : 1->2, Segment index: 1
´´
Copied from original issue: roboticslab-uc3m/yarp-devices#115