Please enable JavaScript to view this site.

Navigation: 2. 3D Modelling > Assembly > Movable sub-assemblies

Working with movable sub-assemblies

Scroll

Movable subassemblies: general information

The mobility of sub-assemblies in the current assembly is controlled by the Make Movable command. It is included in the context menu of sub-assemblies. Calling this command for a sub-assembly makes it moveable, which is displayed by a check mark near this command. Next call revokes the ability to move sub-assembly.

Before allowing mobility for a sub-assembly the software checks if the original model for this sub-assembly contains any moveable components (sub-assemblies). If moveable components are present, they will become moveable in the current assembly too.

You can disable mobility for any component in the current assembly by calling the Make Movable command from its context menu.

Changes in mobility in the current model are not transferred to the original assembly, and vice versa.

Working with movable sub-assemblies

1.Make the sub-assembly movable. To do this, select it in the Design Tree and invoke the Make Movable command from the context menu.
Next to the subassembly icon in the Design Tree, the symbol will appear. Matings of components for the subassembly will be added to the assembly. They appear in the Assembly Design Tree in the Matings section and are marked with the icon .

2.If required, exclude from calculation the mates that interfere with the movement of sub-assembly components in the current assembly. For more details on excluding objects from calculation...
If a mating with a value range is specified, there is no need to exclude it from calculations, as the components of the movable sub-assembly can move within the defined range.

You can quickly find a required sub-assembly in the matings assembly, using the Viewing Object Relationsarea.

3.Perform the necessary actions to place the components of the current assembly — create matings, move or rotate the components, etc.

Notes on using moveable sub-assemblies

You can make a subassembly movable or, conversely, disable its mobility only if it is fully loaded. The Make Movable command is unavailable for subassemblies with any other type of loading. For details about component load types...
If the load type of a movable subassembly changes, the subassembly remains movable, and its mates remain available for operation within the assembly

instances of array, the base instance of which is a movable subassembly, also represent movable subassemblies. You can disable mobility for any of array instances.

Huge arrays of moveable sub-assemblies make assembly mating system too complicated, therefore we do not recommend to use such arrays.

Specifics of creating mirrored and symmetrical subassemblies:

While creating mirrored and symmetrical copies of movable sub-assemblies, the movable sub-assemblies are also obtained. You can later disable mobility for original sub-assembly and/or for its mirrored or symmetrical copy. Any changes in mobility for the original sub-assembly are not transferred to its copies.
Components of a movable sub-assembly may be linked by matings to the components of the current assembly. Those matings are not copied into sub-assemblies created by mirroring. You need to create matings manually for components of those sub-assemblies.

You can’t set the rotation angle while creating mirrored version A movable subassembly is obtained, the components of which are associated with the components of the original subassembly by matings of Dependent position type (see Automatic overlaying of matings when creating a component by mirroring section). Those matings are added to the assembly. The mirrored version of the sub-assembly does not contain any other matings.
To allow the components of the subassembly to move, exclude the Dependent Position mate from the calculation in the current assembly and apply the necessary mates (for example, the Symmetrymate).

If the option of mirroring a movable subassembly is selected as Save mirrored component in file, the merging creates a new assembly file. The mobility state is not transferred to the file.

© ASCON-Design systems, LLC (Russia), 2024. All rights reserved.