Search the Community

Hi, I have a problem with the adjusted clicksmart plate using moveit. i used this repository: https://github.com/RethinkRobotics/sawyer_moveit/tree/clicksmart_moveit I have executed all the commands which are described, but in Rviz l6 is highlighted red and the moveit controller fails everytime. The collition geometry overlapps, so it has to be self-collision. Is there anything else i have to do? Thank you, Andreas

Hi. I want use the sawyer robot with moveit package, to generate obstacle avoid path. The tutorial works perfectky with or without your electric gripper. But with clicksmart, it cann't generate path. I am using this command(There is no options for clicksmart.) $ roslaunch sawyer_moveit_config sawyer_moveit.launch When launch finished, I can see the clicksmart pad at the right_hand link. But after that I tried to generate plan with random position, it failed with this log. How can I launch the sawyer model with clicksmart to use moveit?

Can somebody point me to where in the documentation I can find more detailed electrical information about the interface on the standard cuff and clicksmart plate. Also how these are linked to the software

Hello everyone, Was hoping someone could help me with a problem I'm having. I'm attaching a ~2.8 Kg load to Sawyer's end effector via the Clicksmart Plate, and I'm trying to use Moveit! in ROS to move the arm around while the payload is attached. In doing so, however, I encounter the following problems: 1) The arm often stops executing a trajectory early and the joint trajectory action server node gives the following error: Robot arm in Error state. Stopping execution. 2) The arm violates the path tolerances when executing the trajectory 3) The path executed is very very noisy My theory is that the motor controllers are not accounting for the added load on the end effector, which could definitely mess up the trajectory execution. I tried rebooting the robot in Intera Mode, and following the tutorial of setting up a custom end effector, but when I restart the robot in SDK mode, the robot still experiences the same problem . Anyone know how to fix this?