I have been struggling with surface geometry from Inventor. It is really not useable in any FEA software. I have written the below script which runs on its own (not within Mecway). It will read a .stp file, fragment all the surfaces and then save the file.
The revised .stp file can be opened in Mecway and intersecting components should share the same nodes along an intersection but the will not be connected. If you use the merge nodes tool on Mecway the mesh will be one continuous mesh.
I asked AI for a spring model maker and here's what it made. It is an external python script that generates Gmsh inputs and then a Calculix input file. To run, I use Python 3.11.2, and you need to add the gmsh package. I find this thing very handy!
I have been long time looking for a nice GUI for Code-Aster. I have been using Salome-Meca, but always find it too tedious to use. In the first half of this year I established the working principle of a bridge between Mecway as pre-/post processor and Code-Aster as a solver. That structure proved to work. After that I didn’t have time to spent on it until last week. My son is programming a lot with Claude Code, and this week he didn’t have time to use it because of his homework 😊. So I was allowed to spent his weekly limit. Unfortunately, it worked out quite well and I decided to unlock more of Code-Aster than I normally use. As a result, the MecwayAsterBridge grew quiet large in capabilities. You can find it here: https://github.com/trednuK/MecwayAsterBridge
I have added a lot of validation checks and documentation. However, since it is build by AI, it still needs human verification to find edge cases which only appear in daily use.
Enjoy using it and please let me know if you have any suggestions or find some bugs.
Comments
The revised .stp file can be opened in Mecway and intersecting components should share the same nodes along an intersection but the will not be connected. If you use the merge nodes tool on Mecway the mesh will be one continuous mesh.
I find this thing very handy!
The inputs are hard coded at the bottom
wire_diam=1.12345,
major_diam=15.0123,
active_pitch=10.98765,
active_turns=4.0,
dead_turns=1.0,
ground_ends=False,
mesh_size=0.3
The ground ends doesn't work properly so I leave it False. It's easy enough to use scale in Mecway to flatten the ends to approximate a grind.
I have been long time looking for a nice GUI for Code-Aster. I have been using Salome-Meca, but always find it too tedious to use. In the first half of this year I established the working principle of a bridge between Mecway as pre-/post processor and Code-Aster as a solver. That structure proved to work. After that I didn’t have time to spent on it until last week. My son is programming a lot with Claude Code, and this week he didn’t have time to use it because of his homework 😊. So I was allowed to spent his weekly limit. Unfortunately, it worked out quite well and I decided to unlock more of Code-Aster than I normally use. As a result, the MecwayAsterBridge grew quiet large in capabilities. You can find it here: https://github.com/trednuK/MecwayAsterBridge
I have added a lot of validation checks and documentation. However, since it is build by AI, it still needs human verification to find edge cases which only appear in daily use.
Enjoy using it and please let me know if you have any suggestions or find some bugs.
Kind regards,
Kundert