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

Impedance control in cartesian space #195

Closed
PeterBowman opened this issue Feb 1, 2023 · 2 comments
Closed

Impedance control in cartesian space #195

PeterBowman opened this issue Feb 1, 2023 · 2 comments
Assignees

Comments

@PeterBowman
Copy link
Member

As a follow-up to #194, let's add some spring-like behavior to the ftCompensation app now that it knows how to convert FT sensor data into cartesian force commands while performing gravity compensation.

@PeterBowman PeterBowman self-assigned this Feb 1, 2023
@PeterBowman
Copy link
Member Author

Done at 488028b. There is a lot of friction mainly in the elbow joint that should be somehow compensated in the low-level (roboticslab-uc3m/yarp-devices#261), but for now it seems to work well in orientations (Y and Z axes) with this configuration:

ftCompensation --from ftCompensation-stump.ini --mode wrench \
               --sensorName ch0 --sensorRemote /jr3 \
               --cartesianRemote /teo/leftArm/CartesianControl \
               --linGain 1 --rotGain 1 \
               --linStiffness 250 --rotStiffness 10 \
               --linDamping 0 --rotDamping 1

Note this could have been implemented as an add-on for the GCMP command in BasicCartesianControl. Such attempt was initiated in 6e78a53...b8ed4ca and explained in roboticslab-uc3m/yarp-devices#258, but discarded (for now) to focus on low-level joint impedance control.

@jgvictores
Copy link
Member

Just for the historic, and completely low priority, would a video be possible (maybe of this vs gcmp)?

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

When branches are created from issues, their pull requests are automatically linked.

2 participants