Revision history [back]

You do not need Gazebo when you are working with the real hardware. Ideally, your packages should be set up so that they are agnostic to the vehicle running as a simulation in Gazebo or as real hardware.

Gazebo is not a visualisation tool, so when running the real hardware you should not expect Gazebo to respond.

Gazebo is providing joint position information and publishing transforms based on its simulation of the vehicle's bodies and joints. For your hardware, you will need to provide this information yourself. For example, you could put an encoder on the joint so that you can publish the position of the pivot between the powered vehicle and the trailer. You should publish this information to the `/j

When rviz has the position of a joint (the pivot) relative to its parent link (the powered vehicle) and the position of the child link (the trailer) relative to the joint, then having the angle of the joint allows rviz to display the motion of the child link.

To get the trailer's pose relative to the vehicle, you will need to use the joint angle to

You do not need Gazebo when you are working with the real hardware. Ideally, your packages should be set up so that they are agnostic to the vehicle running as a simulation in Gazebo or as real hardware.

Gazebo is not a visualisation tool, so when running the real hardware you should not expect Gazebo to respond.

Gazebo is providing joint position information and publishing transforms based on its simulation of the vehicle's bodies and joints. For your hardware, you will need to provide this information yourself. For example, you could put an encoder on the joint so that you can publish the position of the pivot between the powered vehicle and the trailer. You should publish this information to the `/j/joint_states topic. The URDF tutorials have a good tutorial on how to do this. (For testing your URDF in rviz, you can use the joint_state_publisher GUI tool, which will mimic the joint position moving.)

Once you have the joint state being published, you need to publish the updated transforms to /tf. The robot_state_publisher node can do this for you automatically. It reads in your URDF and looks for new joint states, then publishes the updated transforms automatically.

When you get transforms flowing, everything will magically start working. rviz has the position will display your articulated vehicle in its correct state, and you will be able to get the pose of a joint (the pivot) the camera relative to its parent link (the the powered vehicle) and the position of the child link (the trailer) relative to the joint, then having the angle of the joint allows rviz to display the motion of the child link.

To get the trailer's pose relative to the vehicle, you will need to use the joint angle to