By the way, if you're willing to write some input by hand (AI can do it) and be cautious verifying the results, you might consider the Mystran solver that's included with Mecway. It has more of these connector type elements from Nastran like CBUSH (…
Here's an example of a connecting beam (purple) that provides vertical (Z) and transverse (Y) connection but is free in longitudinal displacement (X) and all 3 rotations.
You could use high-stiffness beam elements aligned vertically with released rotational DOFs (flexible joint on beam) at both ends to allow movement in only one direction. For free movement in both directions, it reduces to a truss element.
Constrai…
Normally, Mecway converts the on-axis elements to triangles and they're OK. One way this problem can happen is if the original node was slightly on the opposite side of the axis.
Is there an error message in the status bar? You could try to turn down Resolution in Tools -> Options -> Contour plot.
Or if you can manage to attach the file (maybe clear solution and/or zip it), I'll try to reproduce it.
Yes, it's not in Mecway yet. The reason is that von Mises only seems to be available at the midsurface, not top or bottom. You could write a formula to obtain those from the components or principal stresses.
When you click the button to pick OpenRadioss, pick the directory above exec, not exec itself because it needs the other directories at the same level as exec. Then Mecway should set the environment variables and two exe paths appropriately. I think…
Hello denissps
The +Z and +Y View orientation options are just a convenience for things like the default view orientation, the row of red icons and clicking on the triad arrowheads.
Mirror with the Z option should mirror about a plane parallel to …
A few problems:
- Mecway doesn't make an ELSET called Default. I added one using a Named selection.
- Mecway generates its own *BEAM SECTION keyword blocks which conflict with yours. I added modify keyword .
- U1 is not for non-linear analysis. I c…
I don't think a true RBE3 is possible in CCX. From what I understand, *DISTRIBUTING is just a kind of pre-processing step to convert point forces and moments applied directly to the reference node into forces (and moments?) on the surface nodes.
CC…
Yes, if I add another solver, I think it would probably be Code Aster. Not sure about Opensees or OOFEM because I haven't heard about them very much.
Using the same mesh could be the problem and you might need to refine it for CCX.
Instructions are here: https://mecway.com/forum/discussion/1012/improving-performance-of-ccx-solver/p1
I prefer option 4 - compile it but it can be much easier to download it from dhondt.de. The link is hidden in the sentence "For an update of the …
Hello JJ. The initial velocity is only applied to the surface of one part. The rest of it defaults to zero velocity and that quickly averages out to very slow in the solution.
You can also make a TYPE424 contact using the GUI contact item if you do…
Hello JJJ
Nonlinear shells for the internal solver are not a priority, sorry.
I'm surprised at that 60% error. You might need more refinement with the CCX shells. Also make sure the mesh is quad-dominant, not linear triangles.
You can also use th…
Hello Sarvesh
If you mean changing the value of, say, a prescribed displacement, you can do that by entering a formula that's a function of time (t), or as a table.
If you mean turning constraints on or off, CalculiX can do that but not natively t…
Can you identify if there are solid elements in the mesh file or not? That would indicate if it's a Gmsh issue or a Mecway issue.
Or perhaps use Gmsh through Mecway's Meshing parameters where it has default settings to import a solid mesh.
That example is a bit artificial with effectively zero material bending stiffness so that it all comes from the tension, which is also why it needs X,Y constraints everywhere. You could use real material properties instead and omit all the interior …
Although you don't want shared nodes between the SHS and web, would you tolerate sharing the nodes of all 3 parts by modelling them all as beams with element offset to define their relative positions? This is a technique you can use to build up a be…
Sorry you're having such a struggle with Mecway. It looks like it still doesn't have the features you need.
However, I'm concerned about any possible bugs so I do hope to somehow identify the cause of this difference.
>without any MPC and no lo…
@sofien_73 I mean delete or suppress features like all the released DOFs or all the point masses or big parts of the mesh until it agrees with ROBOT. That way, you can isolate what's causing the difference.
I'd delete half the model repeatedly until you're left with something very simple but still different from ROBOT. That should show what's causing it.
Mecway's beams do have torsional rotational inertia, so is that turned on in Robot?
You can enter formulas in the direction vector components. Use y and -x for the X and Y components respectively to constraint in the circumferential direction about Z. Use a separate displacement constraint for the axial displacement.
@ahjiuhdotcom There must be 3D solid elements in the solution. So stress linearization won't work for axisymmetric with the internal solver but will with CCX where the output is the expanded thin solid wedge. Does that help?
Otherwise, if the line …