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

[Iron] - Possible bug in cartesian compliance controller - fast rising force #171

Open
firesurfer opened this issue Jan 24, 2024 · 1 comment

Comments

@firesurfer
Copy link

Hi @stefanscherzinger as requested yesterday I also open a bug about the fast rising force issue we encountered in our setup.

Information

Ubuntu 22.04
Commit: 4b5daab
Used controller: Cartesian compliance controller

Controller yaml:

cartesian_compliance_controller_top_magnet_gripper:
  ros__parameters:
    end_effector_link: "ur_top/magnet_gripper/attach"
    robot_base_link: "ur_top/base_link"
    ft_sensor_ref_link: "ur_top/tool0"
    compliance_ref_link: "ur_top/magnet_gripper/attach"
    joints:
      - ur_top/shoulder_pan_joint
      - ur_top/shoulder_lift_joint
      - ur_top/elbow_joint
      - ur_top/wrist_1_joint
      - ur_top/wrist_2_joint
      - ur_top/wrist_3_joint

    # Choose: position or velocity.
    command_interfaces:
      - position
        #- velocity

    stiffness:  # w.r.t. compliance_ref_link
        trans_x: 8900.0
        trans_y: 900.0
        trans_z: 900.0
        rot_x: 40.0
        rot_y: 40.0
        rot_z: 40.0

    solver:
        error_scale: 0.68
        iterations: 2

    pd_gains:
        trans_x: {p: 0.015, d: 0.001}
        trans_y: {p: 0.019, d: 0.001}
        trans_z: {p: 0.021, d: 0.001}
        rot_x: {p: 0.3}
        rot_y: {p: 0.3}
        rot_z: {p: 0.3}

We are already in contact (while using the cartesian compliance controller) when we decide to stop. Command the current position and a force of 1N downwards (in the plot the y axis)
The actual stiffness values used during the motion where: [1.0, 100.0, 5000.0, 190.0, 190.0, 1.0] (same order as above). We set them at runtime.

image

You can clearly see the point at which the force starts rising super quick into the direction of the axis we command the force to. (Y axis, up down, X axis in/out of the object we are in contact with)

@stefanscherzinger If you want to debug this issue I can probably also provide additional information about our setup via mail.

@stefanscherzinger
Copy link
Contributor

@firesurfer

I'm going through older issues. Is this still relevant, i.e. does this still happen in your setup?

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