×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

FATAL MESSAGE 4129 Zero Area Element

FATAL MESSAGE 4129 Zero Area Element

FATAL MESSAGE 4129 Zero Area Element

(OP)
For starting I context, I have a FEM with 2 primary submodels that are broken out into separate include files. Each of the two parts runs without issue on their own (free-free modes, fixed modes, and random vibe cases). When running together the two parts are connected by a ring of CBEAMS representing a bolted interface. When I attach the two however, the job fatals and I run into an error message I am not familiar with. Despite my best debugging efforts I have not been able to overcome it.

The message is repeated 20-30 times, though not identically every time. The messages are:
*** USER FATAL MESSAGE 4129 (GP6)
The Area of Element XXXXX is Zero.

Where the "XXXXX" is a mixture of "*********", "0", or EIDs that either are CONMs or don't exist (mostly the latter).

I believe it has something to do with NSM region assignments or glued contact. I'm leaning that direction primarily because they have values specified by area. It would make sense if Nastran was incorrectly trying to assign those properties to a zero area element like a CONM2. The fact that the portion of the model with NSM and contact runs fine on its own has me stumped. It's also odd that it is calling out non-existent elements in the errors, but I verified there are no typos or misaligned columns.

I have verified there is no duplicate numbering or overlap in numbering 4 or 5 times now. I have tried forgoing the separate include files and just letting FEMAP merge the models into a single FEM (both by simply dragging decks in and using the built-in 'merge' command), but no change. I have tried re-setting up the contact from scratch numerous times.

RE: FATAL MESSAGE 4129 Zero Area Element

Dear Mr Rogers,
Without the FEMAP model in hand is difficult to know the source of the Simcenter NASTRAN error, if you post here I will take a look to it.
In cases like that where is not clear the reason of the error what I do is to delete portions of the model and run the Normal Modes/Eigenvalue Analysis (SOL103)to identify rigid body motions, or model errors, and so consecutively, till finding the error.
Best regards,
Blas.

~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48004 BILBAO (SPAIN)
WEB: http://www.iberisa.com
Blog de FEMAP & NX Nastran: http://iberisa.wordpress.com/

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login



News


Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close