-
Notifications
You must be signed in to change notification settings - Fork 41
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
[pr2eus] Set joint-action-enable from argument for creating kinematics-simulator #473
base: master
Are you sure you want to change the base?
[pr2eus] Set joint-action-enable from argument for creating kinematics-simulator #473
Conversation
Thank you for your PR @tkmtnt7000 The original problem is we cannot create Kinematics Simulator in spot-interface. Since spot-interface does not use follow_joint_trajectory_action, jsk_pr2eus/pr2eus/robot-interface.l Lines 243 to 250 in 27066da
In this case, jsk_pr2eus/pr2eus/robot-interface.l Line 1017 in 27066da
So we cannot create Kinematics Simulator in jsk_pr2eus/pr2eus/robot-interface.l Lines 190 to 221 in 27066da
|
@708yamaguchi |
Just for clarification, you want to have the option to start the Kinematics Simulator while connected to the real robot or just be able to use it when working offline? |
I assume the latter one. |
Being so, is there no alternative to autonomously detect if connected to the real robot and set The arm controller is listed as FollowJointTrajectoryAction, is this wrong or something like a dummy code? https://github.com/jsk-ros-pkg/jsk_robot/blob/master/jsk_kinova_robot/kinovaeus/kinova-interface.l#L70 |
As you said, kinova arm uses FollowJointTrajectoryAction.
We are referring to spot robot that does not have kinova arm. |
So, for spots without kinova the default-controller is null https://github.com/sktometometo/jsk_robot/blob/develop/spot/jsk_kinova_robot/kinovaeus/kinova-interface.l , and therefore this loop jsk_pr2eus/pr2eus/robot-interface.l Line 240 in 27066da
joint-action-enable remains as the default value of t .
It seems to me that it would make sense to set Maybe merge this now and then later on think on how we could better conciliate robots with no joint controller to the robot-interface? (e.g. overwrite :simulation-modep, etc) |
Certainly, it may be good to think about how to deal with robots no joint controller for the future. (because it's not that I want this to be merged soon for my thesis....) |
how about override :add-controller?
|
In this pull request,
joint-action-enable
variable can be set from the argument.This change allows robots that do not support
follow_joint_trajectory
to set the(send *ri* :simulation-modep)
value correctly (such as Spot) , so that kinematics-simulator can be used.The new keyword argument is named
joint-action-enable
, which is the same name as:joint-action-enable
in the member function.jsk_pr2eus/pr2eus/robot-interface.l
Line 1016 in 27066da
It seems complicate things. I couldn't think of a better name for the variable, so if someone hits on a better name (or should change the name), please let me know.
cc:@708yamaguchi