joint_trajectory_action.py depends on the robot Cuff interface in that it loads and checks the state of the Cuff during its command actions. There is currently no simulated ROS interface nor published topics in the simulator for this device, which causes the Cuff to fail to load, thus causing JTAS to fail to load, thus causing MoveIt to have problems when run against Gazebo.
In general, there might be a handful of minor interfaces, which are not relevant to the simulated robot and therefore do not have published topics in the sim launch, but cause hiccups b/c they are included in various examples.
IanTheEngineer
commented
6 years ago
joint_trajectory_action.py depends on the robot Cuff interface in that it loads and checks the state of the Cuff during its command actions. There is currently no simulated ROS interface nor published topics in the simulator for this device, which causes the Cuff to fail to load, thus causing JTAS to fail to load, thus causing MoveIt to have problems when run against Gazebo.
In general, there might be a handful of minor interfaces, which are not relevant to the simulated robot and therefore do not have published topics in the sim launch, but cause hiccups b/c they are included in various examples.