-
Notifications
You must be signed in to change notification settings - Fork 7
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
[WIP] Velocity Based Cartesian Controller for Arm #182
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add new packages to CI (see pr template)
nit: use TODO(<github user>): <comment>
. ides will highlight it differently
uwrt_arm_cartesian_controller/include/uwrt_arm_cartesian_controller/visibility_control.hpp
Outdated
Show resolved
Hide resolved
uwrt_arm_cartesian_controller/include/uwrt_arm_cartesian_controller/visibility_control.hpp
Outdated
Show resolved
Hide resolved
ret.twist.angular.y = 0; | ||
ret.twist.angular.z = 0; | ||
ret.header.stamp = rclcpp::Time::now(); | ||
// younes todo whats the name of the arm's base frame ret.header.frame_id = "foo"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see #173
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if im reading the xacro right the name of the arms base frame is called base link. wanted to confirm that this is right bc that name is typically reserved for a robots mobile base (ie the chassis link)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is rn. it should be changed. @meshvaD
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ill use the current name for now. @meshvaD can u pls lmk when u merge the change into master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you actually need to hard code link names? They could be loaded ad parameters (ex. End effector link and arm base link)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just changed it
uwrt_arm_cartesian_controller/src/uwrt_arm_cartesian_controller.cpp
Outdated
Show resolved
Hide resolved
ROS_INFO_STREAM("***Listing HW Interfaces: ***"); | ||
// Get joint handles for all of the joints in the chain | ||
/*for (std::vector<KDL::Segment>::const_iterator it = kdl_chain_.segments.begin(); it != kdl_chain_.segments.end(); ++it) | ||
{ younes todo wut is this? wut is joing handles wut is command_interfaces |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ros control stuff. joint handles = handles for the joints(it doubles as the name of the joint). command interfaces is the interfaces that the arm supports. in thjs case, u should validate that the interfaces are all vel interfaces or else throw an error
uwrt_arm_cartesian_controller/src/uwrt_arm_cartesian_controller.cpp
Outdated
Show resolved
Hide resolved
uwrt_arm_cartesian_controller/src/uwrt_arm_cartesian_controller.cpp
Outdated
Show resolved
Hide resolved
959a9db
to
7a320ff
Compare
still very much a wip. would still appreciate any feedback though