I opened this file using GraphiX but, apart from PrePoMax, both FreeCAD and ccx2paraview converter failed to process it. Are there any unusual element types or other non-standard features in this analysis ? Can you also share the input file or describe this simulation ?
The model contains a crack. The element faces located on the two opposite crack faces have the same location (they overlap). The model is valid and CalculiX can process the input. I can provide the inp file that will create the frd.
use case7_cracked.inp to duplicate the issue that I am seeing on my side. If I try to import case7_cracked.inp, PrePoMax complains about *SURFACE definition. There is a chance I did not use correctly *SURFACE however I do not see the mistake that I made in *SURFACE definition and CalculiX did not complain about it.
This msh file has a strange structure. There are no keywords in it and just some weird lines with numbers. Was it generated in GraphiX ? Does it work there ?
I opened this mesh in FreeCAD but I can confirm that it can’t be imported to PrePoMax. As explained in that thread linked above, the .inp file importer still has some limitations, especially when it comes to input decks created in other preprocessors. The problem with the .frd file opening is likely also related to the way this crack was modeled.
I modified my input data to define element sets (*ELSET). I am collecting elements with the same side where I need to apply an uniform pressure under different element sets.
For example, *ELSET, elset=appliedLoad_S4 will contain all elements where side 4 needs to be used to apply a distributed load.
I am making use of these element sets to assign uniform pressure using *DLOAD. When I load the inp file in PrePoMax, the program complains about my *DLOAD assignment:
I cannot figure the failure reason. If I assign the same loading in the GUI, the Keywords in the log file are identical with the ones used in my input file.
PrePoMax only supports ACSII .frd files. Your file is binary. To get an ASCII .frd file you have to use the keywords *Node file and *El file instead of *Node output and *Element output.
Matej, yes - the ASCII format was fixed. You are referring to an old thread.
My current issue is *DLOAD assignment as described in the last thread. maybe I should open a different thread to avoid confusion.