-
Notifications
You must be signed in to change notification settings - Fork 1
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
Limitations about ROS drivers for KUKA iiwa robot #46
Comments
motion too slow (iiwa stack)It seems that effect of cartesian pose command is less than the joint position command in KUKA iiwa robot controller. We can test something related with this.
Reference |
wrong ttd (iiwa stack)We use the This caused that we can't use the cartesian pose command which needs determined time. We need a script to test it. |
TimeoutAfterGoalReach (iiwa stack)Depending on our iiwa_stack version, when switching between different control modes, the But if you just update the parameters of the current control mode, it will not work, because of the current iiwa_stack implement. This will not call the |
Switching control modes caused exception (iiwa stack)More details, see iiwa_stack #120. This is related with the safe operation in impedance mode and switching control mode. (The Law III of Asimov) Possible solutions: import static com.kuka.roboticsAPI.motionModel.BasicMotions.positionHold;
// or
import com.kuka.roboticsAPI.motionModel.PositionHold; In /*
* Continuously updating the commanded position to the current robot
* position If this is not done, when setting the stiffness back to
* a high value the robot will go back to that position at full
* speed: do not try that at home!!
*/
motion.getRuntime().setDestination(robot.getCurrentJointPosition()); Temporay Solution: Reference
|
Plan to use grl and iiwa_stackDifference
Why?TODO
|
Teaching and Demonstration using KUKA LBR iiwa
|
Control Robot with kuka-isir/rtt_lwr |
Reference
The text was updated successfully, but these errors were encountered: