Numerical Problem Size limits with a model that should run

  • Last Post 19 October 2017
jonnyflowers posted this 09 October 2017

I am attempting to run a simulation that has 6636 nodes, It will not run no matter what I do because it has the error "The version size limits( NODES )have been exceeded."

Can someone please help me out with this?


  • Liked by
  • Sergey
Order By: Standard | Newest | Votes
vganore posted this 09 October 2017

If you are using our ANSYS student product or teaching product then it has a nodes/elements limit of 32k for structural. Could you please post screenshot of your error + statistics area which shows nodes and elements?

jonnyflowers posted this 09 October 2017


Screenshots attached below


vganore posted this 09 October 2017

Looks like you have meshing elements/nodes under control. What about geometry? How many bodies have you generated? How many systems are you using under workbench?

Sergey posted this 17 October 2017

I have few requests from students facing the similar "numerical limit" issue. The most simple way to reproduce the problem is to exceed the specified limit (32k) at least once, and in the following runs the numerical limit error will pop up with no respect to the actual size of the model. Duplicating the project or clearing generated data or closing the workbench or restarting the pc do not solve the problem. However, if you duplicate the Model cell and make a new Setup cell, it works fine. So the issue seems to be seat somewhere in the Setup cell of the project. Still have no idea how to avoid the error without redefining loads and supports. I also have requests regarding the error about geometry size limits in DM. However, I found no info regarding the limits existing for student version of DM.

vganore posted this 17 October 2017

Strange. Let me find out. About Design modeler (DM) geometrical limit, it can handle-

Maximum number of bodies=50,

maximum number of faces=300

  • Liked by
  • Sergey
Dbendix posted this 18 October 2017

i am having the same problem


jonnyflowers posted this 19 October 2017

The issue definitely has nothing to do with anything exceeding limits at the moment, I may have exceeded this during an initial run, so what Sergey said seems likely, it could be as simple as a variable not being reset in the setup cell.