Closed NickN-Eng closed 4 years ago
I've just commented line 1028 through 1043 of file EulerBernoulliBeamHelper.cs
and this issue is fixed.
Not sure, but i think did add those lines to fix another issue.
Anyways this is the result for your code:
Thanks for the quick response!
Have had a look at the version history and you made this update in Commit 872e35b2 07/11/2019 13:37:47 "update".
I dont fully understand how GetLoadInternalForceAt() works, but as part of this update, you removed this:
...and added:
Do you remember why you made the change?
I hope commenting out lines 1028->1043 doesnt break something else!!
I've added the unit test for this issue:
BriefFiniteElementNet.Tests.BarElementUniformLoadsTests.LoadInternalForce_uniformload_eulerbernoullybeam_endrelease()
This way if any other changes break this issue, we'll understand.
Cheers epsi1on!
Hi epsi1on,
First of all, a big thank-you for the work you have done on this project!
I was wondering if the BarElement Start/EndReleaseConditions were supposed to be working? Alternatively, it may be an issue with the internal forces (I am using GetExactInternalForceAt()).
In the problem below, I have defined a simply supported beam with 1kN/m uniformly distributed load. However, instead of fixing the Start/End NODES, I am setting the EndReleaseConditions. I have fixed the Rz of one of the beam ends so that the bar is fully constrained.
The internal forces are incorrect. The support reactions are correct.
I want to set the EndReleaseCondition on the bar, instead of the node constraint because I want to torsion ally restrain the beam in it's own axis. For example, if I had a diagonal beam in 3D, I cannot restrain the beam in pure torsion (local Rz) through nodal restraints - nodals restraints are in global coordinates.
Code is below: