Message ID 205 and 207
Altair EmployeeAnswers
-
Hi Pat_s
at the end of the .out file does it say 'normal termination'?
can you please send us the outfile or paste it here?
0 -
Thank that you want to help me.
For more informations, I try to built a model which is similar to the tutorial RD-3150: Seat Model with Dummy using HyperCrash.The Outfile looks so:
CYCLE TIME TIME-STEP ELEMENT ERROR I-ENERGY K-ENERGY T K-ENERGY R EXT-WORK MAS.ERR
0 0.000 0.7611E-06 NODE 25381 0.0% 0.000 0.3968E+19 0.000 0.000 0.000
ANIMATION FILE: boden_neu_047A001 WRITTEN
ANIMATION FILE: boden_neu_047A002 WRITTEN
WARNING INTERFACE 4
NODE 21024 DE-ACTIVATED FROM INTERFACEMESSAGE ID : 205
** RUN KILLED : ENERGY ERROR LIMIT REACHED
MESSAGE ID : 207
** RUN KILLED : TOTAL MASS ERROR LIMIT REACHED
** CPU USER TIME **
#PROC CONT.SORT CONT. F ELEMENT KIN.COND. INTEGR. I/O TASK0 ASSEMB. RESOL
1 .2310E+00 .1910E+00 .1960E+01 .1359E+01 .1430E+00 .8200E-01 .3320E+00 .5250E+00 .5010E+01** CUMULATIVE CPU TIME SUMMARY **
CONTACT SORTING.............: .2310E+00 4.61 %
CONTACT FORCES..............: .1910E+00 3.81 %
ELEMENT FORCES..............: .1960E+01 39.12 %
KINEMATIC COND..............: .1359E+01 27.13 %
INTEGRATION.................: .1430E+00 2.85 %
ASSEMBLING..................: .5250E+00 10.48 %
OTHERS (including I/O)......: .6010E+00 12.00 %
TOTAL.......................: .5010E+01 100.00 %** MEMORY USAGE STATISTICS **
TOTAL MEMORY USED .........................: 32 MB
MAXIMUM MEMORY PER PROCESSOR...............: 32 MB
MINIMUM MEMORY PER PROCESSOR...............: 32 MB
AVERAGE MEMORY PER PROCESSOR...............: 32 MB** DISK USAGE STATISTICS **
TOTAL DISK SPACE USED .....................: 2714 KB
ANIMATION/TH/OUTP SIZE ....................: 2714 KB
RESTART FILE SIZE .........................: 0 KBELAPSED TIME = 5.96 s
NORMAL TERMINATION
USER BREAKTOTAL NUMBER OF CYCLES : 970
If in my modell is only the initial velocity, everything is working. But if there is an imposed velocity there are the errors.
0 -
pat_s
Please check if there is any intersection and/or penetrations in your model. this could be one of the reason.
make sure there are no intersections and/or penetrations after positioning the dummy.
also, please make sure the normals of the contacts are facing each other.
0 -
I checked the intersections and penetrations with Quality -> Check Tree selection and with Contact Interface. There are non. I think the normals are facing each other.
Thanks for your hints, that direction was right. Now I deleted the contact interface between the dummy and the seat and the computer is still calculation.
In the next step, i'll try to define an new contact interface, i hope that will work.
0 -
I think I found my fault. I changed the zero mass of the Dummy and without this zero mass it works.
Is this possible? Why is that the problem?0 -
I am not sure whether the dummy mass is a factor for the error. but in general momentum is calculated based on the mass and velocity of the dummy.
the error could be of many factors like wrong contacts, loading time period, etc..
if you get the error again, try the following:
leave the dummy with recommended time steps and re-run.if there are any modifications made, make sure you check for initial penetrations before you run the model.
0