On this page
- How to set up load case numbering for Submod?
- Why does Submod say that it is not possible to find a node?
How to set up load case numbering for Submod?
Any local loads in the local model (submodel) has to use exactly the same load case numbers as in the global model, i.e. a 1:1 mapping.
Submod will fetch the displacements from the global model, and put these on to the local model for each load case in the global model. If these do not match the local loads, the displacements from the global model will not either match the local loads, thus giving wrong results.
This means that dummy, empty, load cases may need to be created to make sure that the wanted load cases match. Alternatively, in GeniE, the "FEM load case" number may be changed.
And, it is not possible to add more load cases into the local model, as these will end up with zero displacements (=fixed) on the boundary of the submodel.
Why does Submod say that it is not possible to find a node?
Version: All
The following message may be written to the file Submod.mlg, and may happen when Submod is trying to match the defined boundary nodes in the submodel with the global model.
*** ERROR RETURN FROM XHZ230 ***
ERROR FLAG =-100 NOT POSSIBLE TO FIND XI, ET AND ZE. VALUES NOT CONVERGING. XI,ET,ZE: 1.08290E+00 5.50330E-01 8.79095E-14 FOR POINT WITH COORDINATES X,Y AND Z: 2.36000E+01 -2.70000E+01 1.38000E+01
IF NODE IS FOUND LATER IN ANOTHER ELEMENT, DISREGARD THIS ERROR MESSAGE
The message is an early warning, saying that so far, searching in a specific element, Submod has not found the node in question. If you later find that all nodes are indeed matching, the execution should be okay:
Number of matching coupling-nodes ........: 411 Number of non-matching coupling-nodes .: 0
Of course, you should always check the deformation plot of the sub-model, for example in Xtract. The deformation on the boundary of the sub-model should match the deformation of the global model in the same area.