Merge latest changes from indigo and kinetic, fix build problems in kinetic.
Add "simu" configuration parameter, that toggles whether to send multiple points in the trajectory or not.
While sending multiple points, then testing with UR5, robot stuttered while moving. On the other hand, without spamming multiple points into trajectory, simulated robot didn't move in Gazebo. Solution was to make it configurable.
Wait for TwistStamped jog message also, addition to JointState messages, because both are needed for moving jogging.
Add 1 second sleep before entering main trajectory publishing loop. Necessary, because when receiving noisy data, filter needs some cycles to stabilize. At least in Gazebo environment without this sleep, the robot jumps very suddenly at the start of moving with noisy data, seemed dangerous.
Tested on UR5 hardware and also in simulation environment, Gazebo.
Tested on UR5 hardware and also in simulation environment, Gazebo.