Joint dialog: say why picks on one component make no joint (#1367)
The Joint and As-built Joint dialogs explain why picks make no joint and offer Create Components from Bodies when every pick is on one component; joint.create and joint.as_built suggest component.from_bodies. Labels in all catalogs. Fixes #1239.
This commit is contained in:
1 parent
6fbb1c5d91
commit
4674f0a61c
14 files changed
+174
-10
No files matched your search
@@ -28,6 +28,13 @@ made. Contact sets stop motion where bodies would pass through each other,
|
||||
**Motion Study** keys joint values along a timeline, and **Interference** shows overlapping
|
||||
volumes in red.
|
||||
|
||||
A joint moves one component against another, so its two picks must be on different components.
|
||||
A STEP file with several parts often comes in as bodies of one component, and picks on two of
|
||||
those bodies make no joint. The Joint and As-built Joint dialogs say so under the picks and offer
|
||||
**Create Components from Bodies**: each picked body gets a component of its own and stays where it
|
||||
is, the picks are kept, and the joint previews. `joint.create` refuses such origins with the same
|
||||
advice.
|
||||
|
||||
Joints may close a loop, as in a four-bar linkage or a slider-crank. When one joint of the loop
|
||||
is driven, the other joints in the loop follow so that every joint still meets, and the
|
||||
mechanism stays in the assembly mode it started in (an open four-bar does not flip to the
|
||||
|
||||
Reference in new issue
Block a user