Mr. Matthew Wegener 0 Report post Posted April 13, 2018 Hello all,I have created a parameterized 2d drawing of a 4 element wing profile. I am trying to export these as surfaces so that I can utilize the ANSYS plugin to do a 2d flow simulation. However, when I try to export the surface, the .fsc file loads fine, but it seems to have trouble attaching the geometry. Any help is appreciated. Thank you,MattRW11RearWingProfile.fdbc Share this post Link to post Share on other sites
Jörg 29 Report post Posted April 13, 2018 Hi Matt, The relevant csv-files are missing to reproduce or test it.CheersJoerg 1 Share this post Link to post Share on other sites
Mr. Matthew Wegener 0 Report post Posted April 13, 2018 Hello,Sorry about that. The requisite files are now attached. CheersMattwingprofiledata.zip Share this post Link to post Share on other sites
Jörg 29 Report post Posted April 16, 2018 Hi Matthew, Have you checked the tutorial about the ANSYS ACT app? You can find it in the documentation browser: We recomment to use *.sat files for a correct automation process when using the app. I noticed that you try to export STL. At least, this is one thing that I can observe which might lead to problems. CheersJoerg Share this post Link to post Share on other sites
Mr. Matthew Wegener 0 Report post Posted April 20, 2018 Hello again,Yes I did watch the ACT app tutorial. I had initially used .sat, but recieved errors so I attempted to experiment. I updated the project to export as an .sat and loaded into ANSYS. I now receive the attached errors. Thank you,Matt RW11RearWingProfile.fdbc Share this post Link to post Share on other sites
Jörg 29 Report post Posted April 20, 2018 Hi Matt, We'll take a look at it. CheersJoerg Share this post Link to post Share on other sites
Ceyhan Erdem 15 Report post Posted April 20, 2018 Hi Matt, Within your project, in the feature definition "importpointdata" seems you were creating a tableViewer which in fact is a gui operation.When disabled everything began to work with no problem. Another remark is that within the same feature definition you have created an FBool with a name "visible" which is a used name by the system , already giving an error. I have changed that one with "show". Please let me know if you encounter any problems. Note: I have changed the folder structure, please do not forget to recreate your fsc file and close Caeses while workbench is running. CheersCeyhanRW11RearWingProfile.fdbc.tar.gz Share this post Link to post Share on other sites
Mr. Matthew Wegener 0 Report post Posted April 21, 2018 Hello, I exported the surface to Ansys, but I still seem to be getting an attach error, shown below. I attempted the import in DesignModeler, but it failed to read the file. Cheers,MattRW11RearWingProfile.fdbc Share this post Link to post Share on other sites
Ceyhan Erdem 15 Report post Posted April 23, 2018 Hi Matt, Can you please verify if you did the following change on your Ansys installation, as mentioned in the CAESES Act app installation instructions? In the installation directory, edit the following file:Windows: /vXXX/Addins/ACT/bin/Win64/TransferTypeDirectPropertyAccessList.xmlLinux: /vXXX/Addins/ACT/bin/Linux64/TransferTypeDirectPropertyAccessList.xmlAdd the highlighted line:<TransferTypes>.....<TransferType>FEMSetup</TransferType></TransferTypes> CheersCeyhan Share this post Link to post Share on other sites
Mr. Matthew Wegener 0 Report post Posted April 23, 2018 Hi Ceyhan,I can confirm that I did this. Share this post Link to post Share on other sites
Ceyhan Erdem 15 Report post Posted April 24, 2018 Hi Matt, This looks strange. I have no problems to make it work. Please let me know when you may be available, so that we can arrange a web-meeting and I can check your setup.You can send me an email to; erdem@friendship-systems.com CheersCeyhan Share this post Link to post Share on other sites
sisi 1 Report post Posted April 13, 2024 On 4/24/2018 at 12:05 AM, Mr. Matthew Wegener said: Hi Ceyhan, I can confirm that I did this. Hello, I would like to know how you solve this problem. My 2D model import to workbench does not include the named selection. Share this post Link to post Share on other sites