User`s guide

Release 7.5 MADYMO Coupling Manual
version 5.0 and higher.
To enable restart, the following steps must be taken
1
1. Generate restart files for LS-DYNA and MADYMO by running a normal, non-restart job.
2. Optionally: generate a LS-DYNA restart input deck (see the LS-DYNA manual for more
information).
3. Generate a MADYMO restart input file (xml file). There is a template restart file in
<madymo_dir>/etc/etc/template_restart.xml
4. Submit the restart job with the -rst <restart.rst> command line option for MA-
DYMO, and the r=<D3DUMPxxx> command line option for LS-DYNA, where <restart.rst>
points to the MADYMO restart file and <D3DUMPxxx> to the dyna restart file, both gen-
erated in step 1. For an example restart startup script, see section
5.5
5.5.1 Restart Control
All remarks for normal coupling to LS-DYNA are valid for restart (see section 5.2).
Both MADYMO and LS-DYNA restart file are cumulative.
The restart frequency is controlled independently on both sides, but not communicated.
The user must make sure that the frequencies are equal. The frequencies are controlled
by the TIME_RESTART keyword in the MADYMO input deck and the *DATABASE_-
BINARY_D3DUMP keyword in the LS-DYNA input deck.
Please check the log file that both LS-DYNA and MADYMO restart at the same time-
point. Selecting the wrong LS-DYNA and/or MADYMO restart file (see above) can re-
sult in out-of-sync restart runs. The simulation aborts when it encounters an out-of-sync
simulation (and reports so).
The restart analysis starts at the rst timepoint saved in the restart file that is smaller
than the begin time of the restart analysis.
5.6 Limitations and Known Issues for indirect coupling
When the MADYMO end time is higher than the LS-DYNA end time, MADYMO can
write the terminate line twice to the log file, with the first line:
MADYMO TERMINATED NORMALLY.
and the second line:
MADYMO TERMINATED ABNORMALLY, because of ERRORS
1
The user may read MPP-DYNA where LS-DYNA is mentioned.
24