Jump to content

Ceyhan Erdem

Moderators
  • Content Count

    196
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by Ceyhan Erdem


  1. 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.xml
    Linux:            /vXXX/Addins/ACT/bin/Linux64/TransferTypeDirectPropertyAccessList.xml

    Add the highlighted line:

    <TransferTypes>
    .....
    <TransferType>FEMSetup</TransferType>
    </TransferTypes>

     

    Cheers

    Ceyhan


  2. 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.

     

    Cheers

    Ceyhan

    RW11RearWingProfile.fdbc.tar.gz


  3. Hi Suraj,

     

    After some checks on the created stator blades I have figured out that the distribution of the control points on the created airfoil curve was changing drastically at some point.

     

    This was creating a problematic surface that might lead to failed solid creation.

     

    The bug is already solved in the new version which will be released soon. Meanwhile I can provide you a workaround.

     

    Please find attached the project file with the updated feature definition.

     

    post-467-0-26462700-1516972104_thumb.png

     

    post-467-0-51080700-1516972144_thumb.png

     

    Note: please update the thickness file path in the feature definition accordingly

     

    Cheers

    Ceyhan

    propulsor_v2.fdbc.tar.gz


  4. Hi Suraj,

     

    Please find attached the updated project file.

     

    One thing that I have figured was that the parameter "chord" in the feature definition was named as Xchord which I have changed it back to chord.

     

    Not a cause but I have also added a string parameter where you only have to specify your input file path. It would be easier in case you change the file location instead of editing the feature definition.

     

    Please update the stringParameter inputPath accordingly and let me know if you still have some problems.

     

    Cheers

    Ceyhan

     

     

    stator_engine_v2.fdbc


  5. Dear Mr. Suraj Pawar,

     

    This is a case caused by the visualization parameter of the curve being relatively low.

     

    If you increase the " Render Resolution " value within the related curve's menu, you will observe that the way the curve looks will be smoother.

    By the way this does not affect the geometry when it is exported.

     

    For your second question, do you want somehow extrude your profile not along a line but along a curve?

    If it is the case, you can simply define your extrusion profile and then under " Surfaces ", create a "Sweep Surface" 

     

    Cheers

    Ceyhan

    post-467-0-46284900-1503068678_thumb.png


  6. Hi Amin,

     

    I checked your file and seems changing the parametrization to "unit speed" for the total contour did the trick.

    For both start and end profile curves please try to change the parametrization value from default to unit speed. You can find it if you expand the "general" menu.

     

    Please let me know if you experience any problem.

     

    Cheers

    Ceyhan

    • Upvote 1

  7. Hi David,

     

    Please find attached the fdb file prepared for the propeller using your blade profile.

     

    What it does basically is; importing your blade profile data, creating a curve and separating it into two, providing a pressure side and a suction side curve.

     

    By using these two curves it obtains the thickness and the camber curves.

     

    Afterwards the written feature definition, which replaces these two lines with parametrically defined ones, willl help you achieve your goal I guess.

     

    Please note that on the meta surface and BRep there exist some warnings caused due to the trailing edge cusp, which I left as is intentionally. You can handle them when you decide on a way to blend the trailing edge.

     

    Cheers

    Ceyhan

    post-467-0-38232300-1466618644_thumb.gif

    post-467-0-53199100-1466618650_thumb.gif

    airfoil_parametrization.zip

    post-467-0-55379500-1466620188_thumb.png


  8. Hi David,

     

    Please find attached the .fdb file created with respect to your point data.

    Please note that I removed the first line within the point cloud data, leaving only the coordinates.

     

    The feature definition within the case basically loops over the data, creates an interpolation curve seperating the suction side and the pressure side of the airfoil.

     

    By the way you can set the T.E gap in function of the airfoil blending position and the blade radius, for example you can obtain the camber within CAESES, using the suction and pressure side curves and afterwards trim the airfoil with a line which is normal to camber using a certain parameter which is defined wrt camber or chord length.

     

    Cheers

    Ceyhan

    airfoil_parametrization.fdb


  9. Hey,

     

    May I ask how you export the surface?

    I would recommend you to create BRep from your surface and then within the related menu play with the tessellation variables like Max. 3d Edge Length or Angle Tolerance.

     

    You can reach the documentation about BReps and the tessellation by pressing F1 while in the related menu.

     

    Cheers

    Ceyhan

×
×
  • Create New...