TAGGED: ansys-classic, ansys-workbench, beam
-
-
March 15, 2024 at 1:56 pmryan.aufdencampSubscriber
Hello,
I have a few models being imported into workbench from Ansys classic via the external model block. The classic models have beams with mesh section types (SECTYPE,#, MESH,...), but it seems workbench (2022R2) is integrating these beams into generic ASEC sections during the import. The mesh section type enables beam visualization and detailed section results, neither of which pre-integrated sections enable. I have verified the .cdb files contain the mesh callout and associated .sect beam mesh.
Both DM and SC seem to be able to pass on mesh beam subtypes, but I have yet to find a way to hand these off from classic. Does anyone know of a way to preserve the mesh beam sections during import? Are there any workarounds?
Thanks in advance!
-
March 18, 2024 at 8:10 pmGary_SAnsys EmployeeHello
In the Details of the Line Body Geometry:Cross Section (For Solver): This property displays when your Line Body includes a user-defined cross-section. It enables you to send user-defined cross-sections to the MAPDL solver as either a Pre-Integrated (default) cross-section or as a Mesh section. These options are specified in the Geometry preference category of the Options dialog.Selecting Pre-Integrated sends the integrated cross-section inertia properties, calculated in DesignModeler or Ansys SpaceClaim Direct Modeler, to the solver using the SECTYPE,,BEAM,ASEC command. The Mesh option sends the mesh section data, generated in DesignModeler or Ansys SpaceClaim Direct Modeler, to the solver using the SECTYPE,,BEAM,MESH command. The Mesh option enables you to post process results on the entire mesh section.-
March 20, 2024 at 3:46 pmryan.aufdencampSubscriber
Hi Gary,
Thank you for your response -
I am able to see this option when dealing with line bodies native to SC or DM, but it seems the external model block is pre-integrating beams during the import process.
i.e. if I import a .cdb or .dat with defined mesh beam sections (SECTYPE,,BEAM,MESH), the cross-sections come in as ASEC (pre-integrated) sections. If I open these same .cdb or .dat files in classic, the mesh beam sections are preserved. Are you aware of any settings that preserves the mesh sections types during external model imports?
-
-
March 20, 2024 at 8:42 pmGary_SAnsys Employee
It does not appear this capability to import MESH section types was ever implemented in the External Model import.
Supported Source File Commands
The application imports the following source file data/commands as line body/beam cross sections:CDB: The SECTION/REAL attribute defined with the element in the EBLOCK section.
BEAM, LINK and PIPE Types are supported.
The MESH Subtype is not supported.
-
March 20, 2024 at 9:31 pmryan.aufdencampSubscriber
I believe you're correct - thank you for looking into this, Gary.
I did manage to figure out a workaround, though it is a bit convoluted...documenting for posterity:
- Import external model file with oriented placeholder beams
- Tie the external model block into its own mechanical model block
- In a separate mechanical model block, create a library of beam sections in SC
- Assemble the mechanical model blocks from steps 2 & 3 into a new mechanical model block
- In the line body menu for the step 2 model, set Read Only to "No". This will allow edits in the assembly block level
- The line body cross-sections can now be set to any of the mesh beam sections created in step 3
- Offset beams as needed and make sure Cross Section (for solver) is set to "Mesh"
- Ensure "Beam Section Results" is set to "Yes" under the solution properties
-
-
- The topic ‘Workbench Import of Classic Model – Mesh Beam Issue’ is closed to new replies.
- ICEM CFD – Hexa mesh of a tapered wing with sharp trailing edge
- No mesh information was found in the input mesh file error
- CONVERTING STL FILE IN TO SOLID
- Element type definition – Ansys Workbench
- Varying ply angle in ACP
- ANSYS ACP Modelling Issue
- the matrix T in the cyclic symmetric formula!!
- Assiging one parameter as thinkness of few shell objects
- The meshing algorithm cannot find matching topology
- Connecting External Mesh and Beam Model in Ansys Workbench
-
1416
-
599
-
591
-
565
-
366
© 2025 Copyright ANSYS, Inc. All rights reserved.