Skip to content

Commit 3713493

Browse files
committed
add note about mesh limitation
1 parent de1141e commit 3713493

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/src/urdf.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,10 @@ Multibody.urdf2multibody
3232

3333
## Limitations
3434
The URDF import currently has the following limitations:
35-
- Sensors are not imported
36-
- Transmissions are not imported
35+
- Sensors are not imported.
36+
- Transmissions are not imported.
3737
- `friction` is not translated, but `damping` is translated to a 1D `Damping` component attached using an `axisflange`.
38+
- Meshes are not fully supported yet, they will be imported as generic shapes (inertial properties are imported).
3839

3940
## Structure of the translated model
4041
URDF does not store the transformation implied by links in the link itself, instead, the links store visual and inertial geometry information, while the translation between frames is implied by the origin of the following joint(s). Therefore, we do generally not make use of the `r` argument to bodies, and let this be arbitrarily set. The transformation between two joints is instead encoded as a `r` and `R` arguments to each joint, where joints are wrapped in `URDFRevolute` and `URDFPrismatic` components respectively. Internally, these wrapper components are comprised of a transformation, [`FixedTranslation`](@ref) or [`FixedRotation`](@ref), followed by the actual joint. The interface to these special joints are identical to their non-wrapped counterparts, i.e., they have the `frame_a` and `frame_b` connectors as expected. Due to this approach, we always connect to the `frame_a` connector of links/bodies and let `frame_b` be unused.

0 commit comments

Comments
 (0)