-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEM: Unidentified CalculiX error when applying a rigid body constraint to an edge/vertex #14130
Comments
On my system there is no error but no result (.frd file is empty).
Effectively, removing the rotational degree of freedom generates the result. |
@marioalexis84 Ok, right, thanks. I'll update the documentation then. The same seems to be true for vertices (the ccx manual doesn't cover it though so I'm not sure how to describe which DOF needs to be fixed but in any case, it also depends on the location of the RED NODE). I guess the issue can be closed then, right? |
yes, it can be closed |
Ok, closing. I just wonder why it worked with standalone CalculiX. Maybe this limitation was fixed without notice in the newest version or it’s another case of inconsistent behavior of CalculiX. |
It's hard to say without debugging CalculiX properly. The documentation says "an error will occur" but is not very specific about the error. |
Is there an existing issue for this?
Problem description
Normally, rigid body constraint is applied to faces. But it is (and should be) possible to apply it to edges and vertices as well. However, when doing so, I get a strange CalculiX error:
CalculiX finished with error 4294967295.
The whole output looks like this:
Click to expand
I've noticed the
OverflowError
message at the top.The input file is generated correctly, it works when I submit it using standalone CalculiX. Then I can even import it back to FreeCAD.
I've tried with the ccx binary provided with 0.22 dev as well (this one is 2.17 as it's taken from 0.21.2 stable) but the issue persists.
RB_error.zip
@marioalexis84 Do you know what might be causing this?
Full version info
Subproject(s) affected?
FEM
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: