CreOS SDK
The CreOS SDK allows you to interact with Avular robots
 
Loading...
Searching...
No Matches
multi_d_o_f_joint_state.hpp
Go to the documentation of this file.
1
8namespace sensor_msgs::msg {
34public:
35 // Representation of state for joints with multiple degrees of freedom,
36 // following the structure of JointState which can only represent a single degree of freedom.
37 //
38 // It is assumed that a joint in a system corresponds to a transform that gets applied
39 // along the kinematic chain. For example, a planar joint (as in URDF) is 3DOF (x, y, yaw)
40 // and those 3DOF can be expressed as a transformation matrix, and that transformation
41 // matrix can be converted back to (x, y, yaw)
42 //
43 // Each joint is uniquely identified by its name
44 // The header specifies the time at which the joint states were recorded. All the joint states
45 // in one message have to be recorded at the same time.
46 //
47 // This message consists of a multiple arrays, one for each part of the joint state.
48 // The goal is to make each of the fields optional. When e.g. your joints have no
49 // wrench associated with them, you can leave the wrench array empty.
50 //
51 // All arrays in this message should have the same size, or be empty.
52 // This is the only way to uniquely associate the joint name with the correct
53 // states.
54
56
57 std::vector<std::string> joint_names;
58 std::vector<geometry_msgs::msg::Transform> transforms;
59 std::vector<geometry_msgs::msg::Twist> twist;
60 std::vector<geometry_msgs::msg::Wrench> wrench;
61};
62} // namespace sensor_msgs::msg
ROS message class definition for MultiDOFJointState.
Definition multi_d_o_f_joint_state.hpp:33
ROS message class definition for Header.
Definition header.hpp:17
message definitions of the sensor_msgs package
Definition battery_state.hpp:8