Stuck? 
support@mecway.com
support@mecway.com
Mecway
FEA
Victor
About
- Username
- Victor
- Joined
- Visits
- 4,755
- Last Active
- Roles
- Administrator
Comments
-
That increment size of zero seems suspicious. I wonder if you've run into a bug with the time point accidentally coinciding with what the automatic increment put it at. When CCX exits abruptly, it's usually crashed, which you can imagine might happ…
-
Automatic time stepping does seem to have a problem of ignoring the loads so it can skip over big changes and then struggle to recover or ignore brief loads. What you've done by specifying time points to force it to evaluate at those sounds like a g…
-
Since it works at low speed, I'd ramp the speed - eg. enter it as "123 * t" instead of "123". Then you should see the solution up to the point of failure, if any. Turning off quasi static causes loads to be ramped automatically, so the sudden appli…
-
That's not normal. Though maybe if your model has a small mesh and large number of time steps, it could be slower due to possible overhead of calling Pardiso. It should be clearly faster with a big linear static model. Maybe it doesn't include the …
-
That's fantastic @harryvanlangen. I notice it seems to preserve the equal sizes of the elements, so it it kind of "wrapping" the mesh over the surface without stretching it more than it has to?
-
I don't have a clear idea of why it's like that. Though 20 and -20 are z at the ends of the path. 8 could be velocity - 20m/(8m/s)=2.5s to cover 20 m?. Here's an example of unittriangle. Now the constant in front means force instead of pressure and…
-
The solution isn't static, but the dynamic response is at too high a frequency to see much. Reduce time step size. A quicker way to make a moving load is using a function of both position and time. I've done that in the attached file using the heav…
-
No need. It's exactly the same archive.
-
Instructions for installing the compilers and other tools and building CCX are in here, reproduced below %programfiles%/Mecway/Mecway19/ccx/ccx_win64_mkl_pardiso_source_2.19.zip Instructions for building the following on Windows: 64 bit CCX wit…
-
@hooshsim have you tried compiling the CCX included with Mecway? That's the best option for big models if you don't have enormous amounts (~64GB) of RAM.
-
@disla what a clever workaround bonding a slice of the opposite mesh to make them match! Never heard of that before.
-
The elastic support is just linear springs so acts symmetrically in tension and compression. Version 19 (beta here https://mecway.com/download/mecway190_Beta5.msi ) has elastic compression-only supports for CCX which sounds like what you're looking…
-
I agree it's probably faster in typical cases to do something like that. I wonder about the worst cases though. What if the first 10 modes are all in the highest ND? Is that possible? Would it be much slower than finding all 10*ND modes? Maybe such …
-
Yea, I wondered about a heuristic. But what data can you build it from to be general enough? Maybe somebody comes along with a completely unexpected structure that looks like a Polish word used in English and it ends up performing worse than simply …
-
@disla, just a vague idea of an algorithm to find the lowest N modes: * Solve for 1 mode of each ND. * Pick the ND with lowest frequency mode and solve for an additional mode of that. * Repeat until you can confirm you have the lowest N modes…
-
@hooshim. bonded contact with internal solver should be about as good or better than *TIE. Does it not work if you turn off *TIE? Step by step instructions are included with the source code in Mecway's installation folder under ccx/ccx_win64_mkl_pa…
-
I haven't really been following this thread but a couple of thoughts: As I understand it, i8 allows the solver to use more than ~32 GB. Since you only have 16 GB, Windows would need to use disk swapping which will either completely destroy performa…
-
Thanks for the suggestion. It's come up before but I put it at low priority.
-
Sorry about the spam everyone. It started with an update to the forum software. I'm working on tightening up the new user registration.
-
374k nodes is just above the limit of what the default CCX included with Mecway can do. Download one with PastiX or Pardiso, or compile it using the source code distributed with Mecway to allow more nodes. Or you can use cyclic symmetry to reduce t…
-
Nonuniform stress is pretty common for shells. The two solvers use different formulations, each with their own approximations, so the details of their errors are expected to be different. In this model, the internal solver's quad8 seems to be about…
-
It just needs mesh refinement: 3543 nodes (your model): FoS quad8 = 1.8 FoS tri6 = 2.3 14050 nodes (after Refine x2): FoS quad8 = 2.1 FoS tri6 = 2.2 I have found, with the help of @disla, that the UV moment depends on the element node number order…
-
A 0 heat flux load really means 0 heat flux in addition to whatever else is there - conduction, other heat fluxes, convection, etc. So it has no effect. It's not a constrain that forces heat flux to be zero.
-
Yes, you should be able to just open or import the .vol file in Mecway.
-
From the manual, it looks like ENER and ELSE are just for mechanical energy in dynamics. Q = m*Cp*T is really heat added for temperature change T when Cp is constant, not total energy at temperature T. What do you mean by internal energy here? The…
-
Face and element selection really need cleaning up. Partial and full lassoing could be part of the solution. I almost exclusively use Select nodes with Show element surfaces off because it's more predictable and Edge detecting selection because it'…
-
That sounds like it made the surface mesh (its first step) but failed to make the solid mesh from it for some reason.
-
That "h" bug should have been fixed in v17. So please update to the latest one if you haven't. Otherwise, could you send me the file to find out why it's still doing that? However, it won't help the meshing and just show a generic error message. I…
-
Choose yes and it'll show you where the problems are. It might be hard to see the selected edges, so adjust the view options as needed.
-
That's amazing. Regarding importing the mesh, do they include *ELSETs, *SURFACEs, or anything that Mecway could merge with existing components/named selections when you import?
