Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Predefined Field in Shells vs. Solids issue

Status
Not open for further replies.

Alexander Koss

Automotive
Apr 8, 2020
24
0
0
DE
Hello

Recently I have encountered a big issue with predefining a temperature field in my Model. I am working on a coupled temp-displacement simulation, with an already meshed model (orphan mesh). As it seems, whenever I create a predefined temperature field for the model, the solids act normally, the temperature is transferred from the initial to the thermal step. But with shells, they seem to always try and go back to temperature 0, causing significant strain in the model. What could be the issue here?
 
Replies continue below

Recommended for you

Check msg and dat files for warnings. Which type of shell elements do you use and are there any boundary conditions applied to these shells ?
 
I looked into the msg and dat files, one thing in the dat file that seems suspicious is the following line:

*shellsection, elset=ASSEMBLY_ShellPart, temperature=2, material="HC340XD"
*solidsection, elset=ASSEMBLY_SolidPart, material="AlSi12Cu1"

This temperature=2, I never set any boundary condition regarding that. There is just 1 boundary condition, which fixes both shell and solid in place, and the predefined temperature field of T=10. Do you know by any chance where this "temperature=2" could come from? Keep in mind, this mesh was inherited from another model.
 
This parameter indicates the number of equally spaced points through the thickness at which the initial temperature is defined.

Try defining initial temperature for shells this way:
- in the shell section editor leave default integration "During analysis" and temperature variation "Linear through thickness"
- in predefined field editor select "Direct specification" and "Constant through region"
 
When I set the temperature to be 10, the solids keep it the way it is supposed to be. In the shells the temperature drops almost instantaneously, and settles at 0.8333 degrees. If I set it to -10, it settles at -0.8333. I can't really see the issue in the model definition though, it is the first time something like this happened.
 
What is the value of temperature for shells in 0 frame ? If it’s 10 and drops in subsequent frames then probably some kind of BC/interaction is unintentionally applied to the shells. If it’s lower than 10 in 0 frame already then something is wrong with the definition of initial conditions.
 
For the sake of finding this issue, I tried deactivating all interactions. The weird behavior of shell elements remains the same, even when there are no interactions in the model. At the same time, solids would have probably had a similar issue, if interactions were to blame for the issue
 
Can you paste just the *Initial conditions keyword here (with all parameters and data lines) ?

Try refining the mesh and increasing the number of integration points through thickness for shells.
 
I have changed the number of integration points. All that's changed is the temperature the shells sink to, now it's at around 0.4 degrees.
Here are the Initial conditions:

** Name: T0 Type: Temperature
*Initial Conditions, type=TEMPERATURE
TestSetAll, 10.

The set includes all Nodes in the solid and shell
 
Try changing this keyword so that the value is specified for all integration points through thickness. For example if you have 5 points use:

*Initial Conditions, type=TEMPERATURE
TestSetAll, 10, 10, 10, 10, 10
 
Status
Not open for further replies.
Back
Top