Revision history [back]

The way that ROS defines orientation is with something called a quaternion. They're a good way to represent orientation as they're less ambiguous than roll, pitch, and yaw. But, they have the drawback of being a little difficult to understand. Here's a tutorial that someone wrote to help you understand them.

Now, on to the meat of your question. The reason that you can't generate a path with those components is because if you want to send an orientation equivalent of roll = 0, pitch = 0, and yaw = 0 you need to have the w = 1, not 0. The way that you have the quaternion is not valid.

Many people choose to generate an orientation in roll, pitch, and yaw and convert it to a quaternion. That tutorial will show you how to do this.

Here's another question that should help.

The way that ROS defines orientation is with something a mathematical concept called a quaternion. quaternion. They're a good way to represent orientation as they're less ambiguous than roll, pitch, and yaw. But, they have the drawback of being a little difficult to understand. Here's a tutorial that someone wrote to help you understand them.

Now, on to the meat of your question. The reason that you can't generate a path with those components is because if you want to send an orientation equivalent of roll = 0, pitch = 0, and yaw = 0 you need to have the w = 1, not 0. The way that you have the quaternion is not valid.

Many people choose to generate an orientation in roll, pitch, and yaw and convert it to a quaternion. That tutorial will show you how to do this.

Here's another question that should help.