Assemblies

Assemblies collect and organize sub-assemblies and components into hierarchal data structures which are intended to reflect the data structure of the product being modeled. Furthermore, components are intended to be organizational containers for the geometry and FE idealization of physical parts which make up the product. Assemblies are created, edited, and deleted from the Model browser and are shown under the Assembly Hierarchy folder. The Assembly Hierarchy folder shows a list of assemblies which can be expanded to show the components organized within those assemblies. The Assembly Hierarchy folder also shows a list of components which are currently not organized into any assembly at the bottom of the Assembly Hierarchy folder.

Components can be organized into an assembly using drag and drop technology within the Model browser. Components can be organized into more than one assembly. Therefore, components are not mutually exclusive to an assembly. To organize a component into more than one assembly drag and drop with the control key depressed. In general it is not recommended to organize components into multiple assemblies if it can be avoided.

Assemblies have a display state, on or off, which control the display state of all components organized within the assembly in the graphics area. The display state of an assembly can be controlled using the icons next to the assembly in the Model browser. Geometry and element display states can be controlled separately for assemblies. See components for the display state rules of components.

Assemblies also have an active and export state. The active state of an assembly controls the display state of the assembly and the listing of the assembly and its components in the Model browser and any of its views. If an assembly is active, then its display state is available to be turned on or off and the assembly and its components are listed in the Model browser and any of its views. If an assembly is inactive, then its display state is turned off permanently (and hence also its components) and the assembly and its components are not listed in the Model browser or any of its views. If a find operation "finds" an inactive assembly, that assembly will automatically be set to active.

The export state of an assembly controls whether or not that assembly, including all components organized within the assembly, are exported when the custom export option is utilized. The all export option is not affected by the export state of an assembly. The active and export states of assemblies can be controlled using the Entity State browser. See components for the active and export state rules for components.

Operations performed on an assembly do not affect the components collected within the assembly. For example, if you delete an assembly, the components in the assembly are not deleted, but are instead returned to the list of components which are currently not organized into any assembly.

The data names associated with assemblies can be found in the data names section of the HyperMesh Reference Guide.

Solver Card Support for Assemblies

Because MADYMO uses a hierarchical data structure, it is crucial to set up the correct hierarchy in HyperMesh using the Assembly panel. The MADYMO hierarchy requires:

•	one root assembly of the type MADYMO

•	one assembly of the type SYSTEM, subtype REF_SPACE

•	assemblies of the type FE_MODEL must be placed in an assembly of the type SYSTEM

•	collectors of the type PART must be placed in an assembly of the type FE_MODEL

•	multibodies must be placed in an assembly of the type SYSTEM

For newly-created elements, the parent in the hierarchy is derived from the related elements or attributes, or set manually on the card image. For imported elements, the parent is usually set according to the value found in the imported file.

Supported Cards	Solver Description	Supported Parameters	HyperMesh Notes
CHAR_MOD	Scaling and shifting parameter of a characteristic on a global level.	CHAR, DAMP_COEF_SCALE, HYS_SLOPE_SCALE, ELAS_LIMIT_SCALE, DAMP_COEF_SHIFT, HYS_SLOPE_SHIFT, ELAS_LIMIT_SHIFT	Defined on the card of the parent element
CONTROL_AIRBAG	Parameters to control airbag model behavior.	THERMC, BLOCK_FLOW, AMBIENT_PRES, AMBIENT_TEMP, AMBIENT_DAMP_COEF	Defined on the card of the parent FE_MODEL.
CONTROL_ALLOCATION	This element allows the memory size allocated to MADYMO, given in integers, real numbers and characters, to be set. The number of processors to be used in the solution can also be specified.	NR_PROC, l_SIZE, R_SIZE, C_SIZE	Defined on the MADYMO card.
CONTROL_ANALYSIS	Control element for inputting time domain analysis data relevant to the multi-body solver. Used to set analysis duration, size of time step, tolerances and ramp functions.	TIME_START, TIME_END, TIME_STEP, ANALYSIS_TYPE, INT_MTH, RAMP1 & 2, RACO1 & 2, CONSTRAINT_TOL, CONTACT_TOL, CONTACT_MAX_ITER, USE_FE_TIME_STEP	Defined on the MADYMO card.
CONTROL_FE_MODEL	Defines Rayleigh damping and mass lumping method for the parent FE model.	ALPHA_COEF, MASS_LUMP_MTH, ALPHA_FUNC, ALPHA_REL_BODY	Defined on the card of the parent FE_MODEL.
CONTROL_FE_TIME_STEP	Specifies the range of acceptable values for the FE model time step, and parameters used by the program to automate time step size.	REDUCTION_FACTOR, CRITICAL_ELEMENTS, MIN_STEP, MAX_STEP, TIME_INT_MTH, NR_OF_CYCLES	Defined on the card of the parent FE_MODEL.
CONTROL_IMM	Parameters to control the IMM method	BASED_ON, TIME_WINDOW, ELAPSED_TIME, MAX_STRETCH_PRINT CHECK_REF_MESH, EPS_REF_MESH, DYNAMIC_RELAX	Defined on the card of the parent FE_MODEL.
CONTROL_OUTPUT	Specifies which output data are to be written and the frequency with which this is done. Also defines how often restart output is written.	FILTER_IGNORE, PADDING_TIME, SCALE_FACTOR_ANI, TIME_START_OUTPUT, TIME_STEP, TIME_STEP_ANI, TIME_STEP_RESTART, WRITE_DEBUG, WRITE_FEMESH, MAX_FILE_SIZE	Defined on the MADYMO card.
FE_MODEL	Finite element model	CONTROL_FE_MODEL CONTROL_FE_TIME_STEP CONTROL_AIRBAG CONTROL_IMM FUNC_MOD CHAR_MOD INITIAL_PART SCALING	type = FE_MODEL comps = references to related PARTs and CONSTRAINT.RIGID_FEs Assemblies and multibodies should be left empty.
FUNC_MOD	Scaling and shifting of functions on a global level.	FUNC, X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT	Defined on the card of the parent element.
MADYMO	MADYMO XML Root element	card image = MADYMO comps = references to related BELTs and CONTROL_SYSTEMs assems = references to the SYSTEM.REF_SPACE and any SYSTEM.MODELs	Multibodies should be left empty.
RUNID	Enters a short text description of the analysis, and contains MADYMO product information.	n/a	Defined on the MADYMO card.
SCALING	Scaling of coordinates.	SCALE_TYPE, NODE_LIST, REF_NODE, X_SCALE, Y_SCALE, Z_SCALE	Defined on the card of the parent FE_MODEL.
SYSTEM.MODEL	Parent element for model definition data	card image = SYSTEM comps = references to related BELTs assems = references to related FE_MODELs multibodies = references to related BODYs	Select MODEL. Select the INITIAL.FE_MODEL check box and specify the number of related INITIAL.FE_MODEL elements to add.
SYSTEM.REF_SPACE	Parent element for reference space definition data	card image = SYSTEM assems = references to related FE_MODELs	Comps and multibodies should be left empty. Select REF_SPACE. Select the INITIAL.FE_MODEL check box and specify the number of related INITIAL.FE_MODEL elements to add.

Supported Cards	Solver Description	Supported Parameters	HyperMesh Notes
ASSEMBLIES		n/a

Supported Cards

Solver Description

Supported Parameters

HyperMesh Notes

MBSYS /

Describes an assembly of multibodies

TITLE

H_POINT

Supported Cards	Solver Description	Supported Parameters	HyperMesh Notes
/SUBSET	Describes the subsets.	n/a

Assemblies

Assemblies

Assemblies

Supported Cards

Solver Description

Supported Parameters

HyperMesh Notes

Supported Cards

Solver Description

Supported Parameters

HyperMesh Notes

Supported Cards

Solver Description

Supported Parameters

HyperMesh Notes

Supported Cards

Solver Description

Supported Parameters

HyperMesh Notes

See Also: