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

Feature/impedance control #533

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from
Open

Conversation

LuigiPenco93
Copy link
Contributor

@LuigiPenco93 LuigiPenco93 commented Dec 13, 2024

  • Extracted impedance control related things from reference-spreading branch
  • added option to enable impedance control from RDX teleoperation panel and in behaviors in the hand pose action

Reference to impedance controller in TU/e paper:
Quadratic Programming-Based Reference Spreading
Control for Dual-Arm Robotic Manipulation With
Planned Simultaneous Impacts

@@ -380,22 +380,15 @@ public void executeDesiredArmCommand(RobotSide robotSide)
RDXBaseUI.pushNotification("Commanding arm jointspace trajectory...");
communicationHelper.publishToController(armTrajectoryMessage);
}
case TASKSPACE ->
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed taskspace without joints, as this is not the right way to control the arm and it's never worked.
As an external user, I want to either control the arm in jointspace or taskspace, with or without impedance control. The fact that the taskspace control is using a hybrid message shouldn't concern the user

@@ -31,6 +44,41 @@ public HandHybridJointspaceTaskspaceTrajectoryCommand(RobotSide robotSide, boole
this.taskspaceTrajectoryCommand.set(taskspaceTrajectoryCommand);
}

public HandHybridJointspaceTaskspaceTrajectoryCommand(RobotSide robotSide, boolean forceExecution, SE3TrajectoryControllerCommand taskspaceTrajectoryCommand,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these messages are not used for now, but will when replaying back or using a planner that can provide the gain trajectories and feedforward trajectories

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

Successfully merging this pull request may close these issues.

1 participant