June 20, 2021 at 2:43 pmisooSubscriber
Recently i have been experiencing a strange problem with Mechanical APDL, regarding to radius/thickness ratio with pre-integrated sections;
- I provide several pre-integrated user defined shell section via SSPA,SSPB,SSPD,SSPM commands and assign those to individual surfaces using selection,
- Yet, solver does a thickness/radius check before solution and raises errors and aborts solution
- Element Shape checking was turned off via SHPP,OFF command, yet solver keeps checking element shape and raising errors then aborting solution
- As the last option, i have used the exact section properties which MAPDL gives as output of the SLIST,FULL command (for a section which solution processes and produces results without any shape errors). Solution is aborted with GENS, while it process with casual section definition command which sets a thickness value.
A few questions;
How does Mechanical APDL conduct element shape check routine (thickness/radius) in case of user-defined shell sections which an actual thickness value is absent (all thichkness value seems as "1" , which is in meters, in error lines) ?
My shell section integration is consistent and fits to the theory and gives accurate results via external solvers but why Ansys Mechanical APDL does not accept it to be valid?
Why Ansys does not pass Element shape checking (except of nodal and property consistency and availability), despite of its being turned off by user?
Further attempts to diagnose, I have also used ESCHK command to view problematic elements yet those were not in abrupt shape, passes casual shape check (jacobian, aspect ratio etc) but fails curvature radius/thickness criteria (eventhough shape checking is turned off) and solution aborts.
Best Regards.June 21, 2021 at 10:03 amisooSubscriberI have further analyzed the process and i figured out the solver uses "unit" length in place of pseudo-thickness to check element shape validity,if user-generated section is used. So if user is working in milimeter, the assumed thickness is 1 milimeter for a any shell element, while it is 1 meter if user is working on meter scale.
And in my opinion this is a possible bug.
June 29, 2021 at 11:38 am1shanAnsys EmployeeCould you try issuing the command - /NERR,,99999999 and see if this solves the issue?
June 29, 2021 at 2:27 pmisooSubscriberI did also try that command and it does not resolve the issue.
Viewing 3 reply threads
Ansys Innovation Space
- You must be logged in to reply to this topic.
Simulation World 2022
Check out more than 70 different sessions now available on demand. Get inspired as you hear from visionary companies, leading researchers and educators from around the globe on a variety of topics from life-saving improvements in healthcare, to bold new realities of space travel. Take a leap of certainty and check out a session today here.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.Trending discussions
- How to calculate the residual stress on a coating by Vickers indentation?
- An Unknown error occurred during solution. Check the Solver Output…..
- Saving & sharing of Working project files in .wbpz format
- Solver Pivot Warning in Beam Element Model
- Understanding Force Convergence Solution Output
- Colors and Mesh Display
- whether have the difference between using contact and target bodies
- The solver engine was unable to converge on a solution for the nonlinear problem as constrained.
- What is the difference between bonded contact region and fixed joint
- Massive amount of memory (RAM) required for solve
Top Rated Tags
© 2022 Copyright ANSYS, Inc. All rights reserved.Ansys does not support the usage of unauthorized Ansys software. Please visit www.ansys.com to obtain an official distribution.