Skip to content

Commit 99320fa

Browse files
committed
add limitations and internals
1 parent 7d1f362 commit 99320fa

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/src/urdf.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,4 +26,13 @@ include(out) # Include model, perform simulation and plotting
2626

2727
```@docs
2828
Multibody.urdf2multibody
29-
```
29+
```
30+
31+
## Limitations
32+
The URDF import currently has the following limitations:
33+
- Sensors are not imported
34+
- Transmissions are not imported
35+
- `friction` is not translated, but `damping` is translated to a 1D `Damping` component attached using an `axisflange`.
36+
37+
## Structure of the translated model
38+
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)