A Y direction force or displacement on the Y=0 edge is not symmetric so you can't use symmetry there. You would have to model at least one more segment.
Contact will have problems with constraints on the same nodes. I usually suggest high-stiffness…
I'm sorry, there's a mistake in the tutorial.
To correct it, add displacement, stress, etc. to the solution before solving.
What's happening is there's only a Temperature solution variable so that's all it generates. If there's nothing (like at th…
I agree with Disla that laminate would avoid this problem. Several approaches are:
* Laminate material
* Common nodes with shell offset on the skin elements
* Shells connected by bonded contact
* Solids
Laminate has risks with sandwich m…
Excuse me, I didn't notice the word triple before. Yes, the middle one should be the master.
The problem here is the constraints on the corner are also on contact slave nodes which it can't do. I would probably extrude a thin strip of high stiffnes…
Yes, that's fine if the meshes are the same or similar. Just when there are big differences in element size, some nodes can get missed if they're the wrong way around.
Shared nodes are usually easiest and most accurate if you have the meshes for that. But you can also use contact with the bonded option in either solver. The Constraint equations option works the same in both solvers because it's exported to CCX as …
You can position the element nodes with a sum of half-thickness separation and use bonded contact with the Constraint equations option.
The master surface should have a coarser mesh so that all master nodes belong to a face that has a slave node at…
Those colors seem to be controlled by Windows but I don't know how to change it. For me, the selected one is white, not grey like yours. Perhaps confirm this by looking at the Properties dialog for a file in Windows and see if it has the same low co…
It's not intended to be used this way so I might not change it. I imagine a solution would be to have the model open then import a .frd file and it would prompt if you want to use the components/orientations/named selections/etc. from the model. But…
Hard to know what's wrong. Here are the files I tried it on and it works. I made the shape of the model different in .liml file and .frd solution to make it clear that it didn't really solve it.
Here's how you can make it import the solution from test.frd. After setting it up like in the picture, have the input model in the modeler with the components/etc. and saved as test.liml then click Solve and it'll import a copy of test.frd as the so…
Yea, like Sergio said, Mecway stores that information internally when you click solve and puts it back together with the solution afterwards. It doesn't read any group information from the .frd file, which won't always be the same as components in M…
It appears to be reading it correctly according to the value at one node.
EDIT: I just noticed there are multiple values for each node, as you can see in the listing below. That must be the problem.
It's hard to tell because the forum might have removed spaces from your post but the .frd file is fixed format and each number has to be in the correct column. If that doesn't help, could you attach the .frd file or email it to me?
Oh, that's worse than not supported, it's broken. Thanks for letting me know. I'll try to fix the crashing but don't think I'll be able to add support for it because it seems to be too different from newer versions since the list of installed Alibre…
I haven't made any effort to support older versions and don't know if it's trivial or very difficult. I guess you tried it and it didn't work? Any error message?
The formula in the solution only uses values from the same time step it puts the result in so it can't do the difference between time steps, sorry.
However, you should be able to export the Table to Excel and use that to calculate all nodes and all…
How did you sum the displacements of two modes?
If you created a new solution variable for that, then it won't be used for the deformed view by default but you can set it in Solution -> Deformed view settings.
If you modified the existing displ…
Node values are the average of the element values for that node of the elements sharing the node.
For shells, element values are calculated at Gauss points, then extrapolated to nodes.
For solids, element values are calculated directly at the node…
I don't quite understand. Do you want to transfer temperature from the solution to use for thermal stress? Is it piezoelectric for voltage output? Or temperature dependent electrical properties?
The file you sent has the same number of nodes in the…
@cwharpe Mecway has a new formulation for hex8 (incompatible modes). The old formulation (standard) is over-stiff in bending so it's hopeless for this type of problem. The new one not as bad still somewhat over-stiff for high aspect ratios like this…
Nonlinear quasi-static with an initial imperfection can be more accurate than linear buckling and allows you to include contact and explore the sensitivity to imperfections.
They're not really disconnected. At sharp corners, CCX connects expanded shell elements with knots (MPCs) instead of shared nodes, so they still transfer forces normally.
It seems to have 4 parts but not in an assembly. Maybe you could turn it into an assembly using CAD then either open it directly if that works, or use File -> Split STEP assembly.
In the next version (29), the Split STEP assembly tool will be a…
Sorry about that. You don't need to feel like a goofball since Mecway makes it very unclear why it's not working. There are quite a lot of reasons each solution variable can not be there and the "What's wrong?" message only identifies two of them, w…
Hello Disla
Regarding axisymmetric element faces, I don't want the rest of the GUI to interpret anything defined in the CCX branch because it'll become confusing as to what things it understand and what it doesn't.
For mass flow rate at end nodes,…