Skip to content

Commit 65ffee7

Browse files
committed
Additional world detail
1 parent 99be635 commit 65ffee7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/operate/mobility/motion-concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,9 +44,9 @@ You configure your machine's frames once, and Viam keeps track of the frames as
4444
This means you can send motion service commands using a consistent coordinate system, regardless of where the components are at a given time.
4545

4646
You must configure frames before you can use the motion service.
47-
For example, if you want to command an arm to move to coordinates of `(300, 0, 0)` millimeters, you first need to define the origin `(0, 0, 0)` and the directions of the x, y, and z axes of the {{< glossary_tooltip term_id="world-frame" text="world" >}} coordinate system to give your coordinates meaning.
47+
For example, if you want to command an arm to move to coordinates of `(300, 0, 0)` millimeters, you first need to decide on the origin `(0, 0, 0)` and the directions of the x, y, and z axes of the {{< glossary_tooltip term_id="world-frame" text="world" >}} coordinate system to give your coordinates meaning.
4848

49-
You then define the arm's `frame` to describe its position and orientation relative to the world.
49+
You then define the arm's `frame` to describe its position and orientation relative to the world frame.
5050
If you also have a gripper component, you define the gripper's `frame` to describe its position and orientation relative to the arm, so that when the arm moves, the motion service knows where the gripper is as well.
5151

5252
### Visualize components and frames

0 commit comments

Comments
 (0)