Limitation: All nodes are imported as connections. Also, the intermediate nodes are imported as connections.
Workaround: To reduce the number of connections, the user can merge the divided girder into a single girder and delete the connections at the intermediate nodes. After synchronization, the internal forces are imported correctly, as if the girder were divided.
Limitation: Design Combinations cannot be imported; only General Combinations are allowed.
Workaround: All of the Design Combinations could be converted to the General Combinations by the CTRL+Copy and CTRL+Paste functions in the Combination Table.
Limitation: Concurrent forces in the joint.
For proper design, it is essential that the joint internal forces in the Connection app are in equilibrium. To achieve this, it is necessary to obtain the concurrent internal forces on all members for a given extreme. For now, it is not possible to obtain concurrent joint forces from MIDAS (both Civil NX and GEN NX) for envelope Load cases and Combinations through API.
Workaround: Use only a simple single-level Combination without envelope Load cases and Combinations, see the following limitation.
Limitation: Multilevel envelope combinations are not exported correctly to the Checkbot app. Only extreme absolute values from combinations are exported, leading to unbalanced forces at the connection.
Creating load combinations in MIDAS involves combining previously defined combinations (Add and Envelope). For now, the BIM link doesn’t allow importing these multilevel envelope combinations from GEN NX to Connection via Checkbot. For better understanding, see the table below.
Workaround: Use only a simple single-level Combination without other envelope load cases and combinations. The combinations have to consist only of linear load cases:
- Type Add – a combination type Add consists only of linear load cases or combinations type Add.
- Type Envelope – a combination type Envelope consists only of linear load cases.
Note: The combination CB3 is imported as a load case, so it is not automatically included in the Result Classes. It needs to be added manually.
Limitation: Envelope-type load cases, such as Moving load cases, Settlement load cases, and Seismic load cases, are not exported to IDEA StatiCa Checkbot.
Workaround:
For moving load cases, the user must create a linear load case that produces extreme internal forces at the connection (e.g., using the Moving Load Tracer feature), then use it in the add combination.
For settlement load cases, the user must manually set the specified displacement on the corresponding supports in each load case to obtain linear internal forces.
Limitation: Nodal loads cannot be imported; only internal force imports are available.
This limitation could cause unbalanced forces at the connection due to nodal loads entered directly at the node, which do not create internal forces on the members.
