I don't understand the black lines problems but in case they are the edges of solid expanded beam elements, you can turn that off by requesting axial force in the solution and it outputs line elements for beams. They'll still have uncolored parts wh…
With quasi-static, you have to ramp the loads yourself (eg. "123 * t" for linear ramping or "123 * t^2" for gentler quadratic ramping), otherwise they're immediately on which is bad for convergence.
Is it saying there are too many increments? If yo…
Oh cracks opening makes sense why it would be slow. What are you using as a material model? If the stress-strain curve has a sharp knee in it, that's certainly something it can struggle with.
It sounds like you might not be using quasi-static. I wo…
Lots of possible reasons, especially if there's contact, rotations of 90 degrees or more, or if it's buckling or has plastic material. Could you attach the file or email it to me privately?
I don't know any good reason. Probably I wasn't confident in how to validate it (should it also cause a Coriolis force?) and not many people asked for it.
Yes. Mesh tools -> Move/copy and Rotate/copy do that. You can also translate by dragging one of the selected nodes with the mouse and snapping it to another node to move the whole part.
Yes, that should be OK if you're just looking for stress over one cycle. Use:
Analysis settings:
- CCX
- Nonlinear Static 3D
- Quasi-static
Meshing parameters:
- Maximum element size 30 mm works but the default doesn't.
Support with Node-surface …
@disla, I seem to remember you found some problems with very high strains in linear materials before?
Although that's usually physically unrealistic, in this case, the mechanical strain is near zero so I'd say it should be a reasonable approach.
M…
Wow. I never knew there was any way to get rotational DOFs in equations! It's a bit of a pity that you have to keep one unused to put the dummy constraint on so it probably can't really be done automatically, but excellent discovery nonetheless!
It might be too complicated. I'm trying to reduce it to the core problem (attached).
I noticed that it does sort of solve if you add a "no extra contact step" in the CCX branch of the outline tree. The film is still flapping around but it's winding…
Which element it chooses isn't defined, sorry. It might be highest or lowest element numbers but might change in future.
I do have to sort out that selecting hidden elements problem though.
It seems like you can't have the master and slave directly opposite each other. My guess is it might see that as penetration and try to push them apart.
All I can think of is to make 2 or 3 separate contacts in repeating stripes so the master for o…
It solved with the dent in the larger plate flattened out (set to y=0). I wonder if there's buckling happening around there leading to poor/no convergence. Is this something you're expecting or want to capture?
With the dent in place, it solved a l…
Versions 24 and 25 install ccx/ccx_win64_mkl_pardiso_source_2.21.zip (numbers instead of xx) in the application's installation location. Compiling that produces both the ccx.exe distributed with that version of Mecway, and ccx_mkl.exe which is the s…
It's possible that turning off mixed precision (PASTIX_MIXED_PRECISION=0) takes away all the speed benefits of PastiX. I hadn't checked that. If you don't set it, it'll probably be faster but there's a risk of wrong results in some cases.
A lot of …
It didn't finish solving in either 24 or 25 for me. It's possible you have a different version or build of CCX used by 24. 25 would have defaulted to the built-in one when it was installed.
That's probably the contact state file (.cel) which can be huge and slow to load.
To prevent it being created, before solving, have only the field variables you want in the solution, and not contact state. If there's nothing there, Mecway automatic…
What I did:
* Changed the tension force from nodes to faces to make it uniform.
* Adjusted the X position of one side of the film's nodes so the elements are square, not parallelogram. This might not have been needed.
* Ramped the tension for…
That's usually what causes it, but in this case, it's an unused node (876). Nodes without elements don't go through to the solution in CCX so delete it before solving.
CCX sometimes fails such large rotations at specific angles. You can work around it by altering the time step from 2 s to say 2.1 s and it seems to avoid whatever problem it got stuck on.
You can't have a time-dependent displacement on the same node as the time-dependent rotation. That's a limitation of Mecway. You also can't have constraints on the surface of node-surface coupling, which is a limitation of CCX.
A workaround is to e…
You're right, it doesn't have sufficient constraints.
Beware that the pinned support only pins one point even if you apply it to two nodes. If you want two pinned supports, either use two of them or 3 displacement constraints on two nodes.
There's…