User`s guide

MADYMO Coupling Manual Release 7.5
MADYMO
FE−code
MADYMO
FE−code
MADYMO
FE−code
FE−FE
MAD−MAD
FE−MAD
FE−FE
MAD−MAD
FE−MAD
FE−FE
FE−MAD
FE−FE
FE−MAD
FE−code
FE−MAD FE−MAD
FE−MAD
Data exchange
High performance network
Coupling library MADCL
Figure 1.2: Illustration of the communication through the coupling library MADCL.
When MADYMO dummy models are used in coupling it is recommended to use the extended
coupling. This is because the compliance of the dummy contact surfaces is not taken into
account in the basic coupling. However, the basic coupling generally runs more efficiently,
because less data needs to be communicated between MADYMO and the PARTNER.
Please be aware that this MADYMO release supports both basic and extended coupling for
direct coupling. The direct coupling however may not be supported by newer versions of the
PARTNER codes. Details for direct coupling are given in Tab.
1.1–1.4.
MPP coupling is supported by newer versions of the PARTNER codes. Details are given in
Tab. 1.5.
1.1.3 Simulation Control
• The simulation end time has to be defined both in PARTNER and MADYMO. When
defined differently in both, the simulation will end when the lowest end time is reached.
• The kinematic output time step in the MADYMO input file and the parameters of the
option in the PARTNER input file must be consistent. The combined output will be out
of phase, otherwise.
• For Direct Coupling define the number of CPU’s in the MADYMO input deck. If you
plan to run an SMP job, the number of CPU’s used by MADYMO and PARTNER must
be equal. MADYMO defines the number of CPUs, say #n, by NR_PROC in the XML
input file with
3