Inverse Kinematics Solver Service
The robot software provides a simple Position Inverse Kinematics (IK) Solver as a ROS Service. Specify a desired Cartesian coordinate and orientation for an Endpoint (in world x,y,z space), and the solver will return a set of joint angles that will get the arm there - or return an Invalid state if the pose is unreachable. An optional seed to start looking for solutions around can be specified as a joint angle configuration.
Note that the service takes an array of requests, and similarly returns an array of results with corresponding indexes. Similarly, optional seeds for each Endpoint request can be provided in a corresponding array of the same size as the requests array. This multiple array structure is a common structure used in ROS and explained in the sensor_msgs/JointState message.
SolvePositionIK Service [srv]
pose_stamp(Required) - an array of geometry_msgs/PoseStamped requests, each defining the Cartesian <x,y,z> Position and Quaternion orientation of the Endpoint in the
seed_angles- an array of joint configuration seeds to start searching for solutions around, corresponding to each request in
pose_stamp, where each individual seed is defined as a JointState message with the joint names and positions filled for all the arm Joints (so
seed_anglesis an array of arrays).
seed_mode- specify the IK solver strategy for what types of seeds to use. By default (
SEED_AUTO), the solver will iterate through the different strategies, starting with the user provided seed if it exists, until a solution is found. However, by explicitly setting the
seed_modeto a specific mode, the solver will only return whether it was able to find a solution using that type of seed. The different mode types are defined as constants in the message (default: SEED_AUTO):
int8 SEED_AUTO = 0 int8 SEED_USER = 1 int8 SEED_CURRENT = 2 int8 SEED_NS_MAP = 3 int8 seed_mode
use_nullspace_goal(Required) - for each IK request, tells whether it should use the nullspace goal in bool type.
nullspace_goal- if use null space goal, providing the full set or subset of joint angles, it will be the null space goal. The message type will be sensor_msgs/JointState.
nullspace_gain- the gain used to bias toward the nullspace goal. Must be [0.0, 1.0], type in float64, if empty, the default gain of 0.4 will be used.
tip_names(Required) - tip name for each pose IK.
result_type- will be a corresponding array of uint8's, which will be -1 if no valid IK solution was found for the given Endpoint request; it will be -2 if IK solution is in self collision. otherwise, it will be negative and correspond to the type of seed eventually used that gave a valid solution. These values correspond to the constants in the message used to specify
jointswill contain joint solutions corresponding to each Endpoint request. Note that you should always check the
result_typefield to see if a valid joint solution was found, as invalid joint solutions can be returned in this array.
This service allows users to solve for basic IK joint angle solutions or perform workspace validation. The service will use a number of seeding strategies to find a solution. These strategies can be specified explicitly or just use the default to find the first solution in the possible methods. Optionally a Joint configuration can optionally be provided as a seed to the Solver.
Check Inverse Kinematics Solver Example for more details.
Forward Kinematics Solver Service
The robot software also provides Forward Position Kinematics (IK) Solver as a ROS Service, joint positions(s) to request Forward-Kinematics joint solutions for
tip_names(Required) - tip name for each pose FK in string type.
pose_stamp- solution(s) per FK call,
isValid- will be a corresponding boolean which will be True if a valid endpoint solution was found for the given joint positions request.
Check Forward Kinematics Solver Example for more details.