CreOS SDK
The CreOS SDK allows you to interact with Avular robots
 
Loading...
Searching...
No Matches
joint_state.hpp
Go to the documentation of this file.
1
8namespace sensor_msgs::msg {
33public:
34 // This is a message that holds data to describe the state of a set of torque controlled joints.
35 //
36 // The state of each joint (revolute or prismatic) is defined by:
37 // * the position of the joint (rad or m),
38 // * the velocity of the joint (rad/s or m/s) and
39 // * the effort that is applied in the joint (Nm or N).
40 //
41 // Each joint is uniquely identified by its name
42 // The header specifies the time at which the joint states were recorded. All the joint states
43 // in one message have to be recorded at the same time.
44 //
45 // This message consists of a multiple arrays, one for each part of the joint state.
46 // The goal is to make each of the fields optional. When e.g. your joints have no
47 // effort associated with them, you can leave the effort array empty.
48 //
49 // All arrays in this message should have the same size, or be empty.
50 // This is the only way to uniquely associate the joint name with the correct
51 // states.
52
54
55 std::vector<std::string> name;
56 std::vector<double> position;
57 std::vector<double> velocity;
58 std::vector<double> effort;
59};
60} // namespace sensor_msgs::msg
ROS message class definition for JointState.
Definition joint_state.hpp:32
ROS message class definition for Header.
Definition header.hpp:17
message definitions of the sensor_msgs package
Definition battery_state.hpp:8