{"id":27517,"date":"2015-04-10T16:07:19","date_gmt":"2015-04-10T16:07:19","guid":{"rendered":"https:\/\/www.padtinc.com\/2015\/04\/10\/taking-nastran-input-files-into-ansys-mechanical-via-external-model-in-ansys-16-0\/"},"modified":"2022-03-24T22:51:44","modified_gmt":"2022-03-24T22:51:44","slug":"taking-nastran-input-files-into-ansys-mechanical-via-external-model-in-ansys-16-0","status":"publish","type":"post","link":"https:\/\/www.padtinc.com\/2015\/04\/10\/taking-nastran-input-files-into-ansys-mechanical-via-external-model-in-ansys-16-0\/","title":{"rendered":"Taking NASTRAN Input Files Into ANSYS Mechanical via External Model in ANSYS 16.0"},"content":{"rendered":"

\n\t\"nastran-ansys-external-model-tn\" <\/picture><\/a>I found another very nice enhancement to version 16.0 of the ANSYS Workbench\/ANSYS Mechanical toolset.  If you happen to have a NASTRAN input file (.dat, .nas, and .bdf) that you need to get into ANSYS Mechanical, no longer do you have to use FE Modeler in ANSYS Workbench to perform the translation.  In fact, not only can you move the NASTRAN model into ANSYS Mechanical, but you get the existing mesh as well as newly-created geometry that can be used for boundary condition application, etc.  As with most translations from one FE tool to another, you can’t expect everything will be translated.  However, this new technique can be an incredible time saver in addition to giving us capabilities to continue and augment simulations that were previously performed in NASTRAN, now in ANSYS.\n<\/p>\n

\n\tHere is an example of this new procedure.  (Note that we don’t have NASTRAN here at PADT, so I couldn’t create a generic sample of a NASTRAN model in NASTRAN.  Instead, I created a model in ANSYS, then converted it into NASTRAN using ANSYS FE Modeler to get a NASTRAN input file for the purpose of this exercise.)\n<\/p>\n

\n\tOnce I have the NASTRAN input file that I need to convert into ANSYS Mechanical, I launch ANSYS Workbench 16.0 and insert an External Model branch.  I then click the … button to browse to the NASTRAN input file.  In this case, the file is NASTRAN.nas.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f1\" <\/picture><\/a>\n<\/p>\n

\n\tNext, I drag and drop a new analysis type block into the Project Schematic.  In this case, it was a modal analysis.  Note that you can’t drop this onto the Setup cell in the External Model block as you might expect.  You set it up as a separate block and establish the link in the next step.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f2\" <\/picture><\/a>\n<\/p>\n

\n\tNext, we drag and drop the Setup cell from the External Model block onto the Model cell of the Modal analysis block.  This establishes the link from the NASTRAN model to the new Modal analysis.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f3\" <\/picture><\/a>\n<\/p>\n

\n\tWe also need to right click on the Setup cell in the External Model block and select Update to get a green checkmark in that cell:\n<\/p>\n

\n\t\"nastran-ansys-external-model-f4\" <\/picture><\/a>\n<\/p>\n

\n\tNotice that there is no Geometry cell in the resulting Modal analysis block.  If all goes well, there will be geometry within the Mechanical model that can be used for selection purposes (in addition to the mesh that comes in from NASTRAN). \n<\/p>\n

\n\tNext we open the Mechanical editor by double clicking on one of the cells in the Modal analysis blocks (other than the Engineering Data cell).  It may take several minutes to bring in the NASTRAN model depending on the size of the NASTRAN model.  The Mechanical window doesn’t really let you know that it’s working, but if it’s sitting there with nothing being displayed, it’s probably churning away at bringing in the NASTRAN mesh and creating surface geometry on it.\n<\/p>\n

\n\tHere is what the Mechanical window looks like after the mesh is read in and geometry is automatically created.  This is the mesh from the NASTRAN file, but in this case both solid and surface geometry is also present.  It’s not guaranteed that everything will come across.  I’ve seen contact elements come through for certain types of contact but not for other types of contact for example.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f5\" <\/picture><\/a>\n<\/p>\n

\n\tThe next image shows that geometry was created that can be used for the purposes of inserting fixed supports, just as if the geometry had come in from a CAD system.  Note that the NASTRAN input file had NO geometry, just finite element entities.  ANSYS is creating the geometry for use in Mechanical from the information in the NASTRAN input file.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f6\" <\/picture><\/a>\n<\/p>\n

\n\tFinally, after manually creating a needed contact region, I was able to solve the modal analysis, demonstrating that further simulation can be performed in ANSYS Mechanical from this model which originally came from NASTRAN.\n<\/p>\n

\n\t\"nastran-ansys-external-model-f7\" <\/picture><\/a>\n<\/p>\n

\n\tSo, the main take away here is that with version 16.0 of ANSYS, we can take a NASTRAN input file and through the use of the External Model block, go directly into ANSYS Mechanical.  Not only do we get the nodes and elements as well as other finite element entities from the NASTRAN model, but if all goes well we get geometry that facilitates further processing within ANSYS Mechanical.\n<\/p>\n

\n\tWe certainly hope this new capability makes it easier for you to perform additional simulations in ANSYS when the starting point is a NASTRAN model.  The other formats documented for version 16.0 are ABAQUS, Fluent input files, and ICEM CFD input files.<\/p>\n","protected":false},"excerpt":{"rendered":"

I found another very nice enhancement to version 16.0 of the ANSYS Workbench\/ANSYS Mechanical toolset.  If you happen to have […]<\/p>\n","protected":false},"author":4,"featured_media":27518,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2323],"tags":[1024,511,1073,1074],"post-podcast":[],"_links":{"self":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/27517"}],"collection":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/comments?post=27517"}],"version-history":[{"count":0,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/posts\/27517\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/media\/27518"}],"wp:attachment":[{"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/media?parent=27517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/categories?post=27517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/tags?post=27517"},{"taxonomy":"post-podcast","embeddable":true,"href":"https:\/\/www.padtinc.com\/wp-json\/wp\/v2\/post-podcast?post=27517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}