Ceyhan Erdem
-
Content Count
196 -
Joined
-
Last visited
-
Days Won
11
Posts posted by Ceyhan Erdem
-
-
Hi Michael,
Yes the "union" command within BRep is a solid command. Therefore you should have a water-tight geometry.
Cheers
Ceyhan
-
-
Hi Michael,
Please find attached the updated model.
A boolean "Unite" operations is a solid operation. Therefore you should have your geometry water-tight. For each part I have added the "Close Planar Holes" operation which converted them to water-tight geometries and then created a new BRep in which I have performed the Union operation.
Cheers
Ceyhan
-
Hi Michael,
Is it possible for you to share the geometry if it is not confidential? It would be easier and faster for me.
Cheers
Ceyhan
-
Hi Daphne,
Within the project you have provided, I can see that no points were selected for the free form deformation operations.
When you select the necessary points and play with the design variable "Angle_Rotation" you will notice that any geometry the free form deformation is assigned to, will be modifying.
Cheers
Ceyhan
-
Hi Daphne,
Can you please share your project?
It is not quite possible to come to conclusions from the provided picture.
Cheers
Ceyhan
-
Hi All,
And also a simple case created for a case of a volute.
After having obtained the section, I move it to the principal plane and then calculate the necessary values.
Cheers
Ceyhan
-
Hi Karl,
Thank you for reporting the crash. I was able to recreate the problem.
Now there is a ticket created for the developers to figure out the root cause of the crash.
Cheers
Ceyhan
-
Hi Tran,
I guess within STAR-CCM+ there must be a way to hook or compile so called "User Defined Functions (UDF)" as it is the case in ANSYS Fluent. But I believe CAESES forum is not likely the best place to address this question unless you would like to parameterize the velocity definition.
Maybe you would be more interested to dig into STAR-CCM+ Forums?
Cheers
Ceyhan
-
Hi Chien,
Sorry for the late reply, I was on vacation.
Can you please send your project to erdem@friendship-systems.com, so that I can give a look?
Cheers
Ceyhan
-
Hi Ogbenna,
Sorry for my late answer, I must have missed the question.
Can you please uninstall the CAESES Act App that you are using for the time being and install the one within the link below,
Please do not forget to restart ANSYS after uninstalling the old version.
I can see that no geometry is being transferred meaning that either the BRep creation failed within CAESES or something is missing within your fsc file.
You can send your CAESES project file to erdem@friendship-systems.com including the fsc file, so that I can give a look.
Cheers
Ceyhan
-
And I have figured the problem with the unit update as well,
In fact it was a problem within the fsc script, that gave an error.
Please check your color labels within CAESES. Seems you have created a white space that is transferred to the fsc script as "/n"
Getting rid of the white space solves the problem.
Cheers
Ceyhan
-
Hi Anup,
Can you please check the attached picture?
I think within SpaceClaim clicking on the Zoom to Extends button will help you to visualize the geometry.
I have figured there is still a unit problem due to the fact that this is a surface body. Will fix this today.
Cheers
Ceyhan
-
Hi Anup,
Please find below the link for an updated version of the ACT App that would fix the SpaceClaim unit problem including some other little bugs.
Cheers
Ceyhan
-
Hi Anup,
Will check the case and let you know once I have a solution.
Cheers
Ceyhan
-
Hi Ogbenna,
Yes, you should be selecting the scope containing the geometry desired to be exported.
Cheers
Ceyhan
-
Hi Ogbenna,
Have you already checked the ANSYS ACT App tutorial within CAESES. You can find the mentioned document under;
Documentation Browser > Tutorials > ANSYS ACT App
or alternatively,
Documentation Browser > Help > ANSYS ACT APP > Integrations > ANSYS ACT App
If not, I highly recommend you to go over the document first.
You can create your Flow Domain within CAESES, assigning colors to let's say inlet / outlet / wall /interface etc.. boundary locations and then create a CAESES batch file which you will be using with the ACT App.
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi Ashesh,
I guess you are using an old version of CAESES.
Within the new version, which is the v4.4.2 the tutorials are updated accordingly.
In either case, you can find the mentioned curve under Curves within the toolbar between the object tree and the 3D viewer.
Please check the attached picture.
Cheers
Ceyhan
-
1
-
-
Hi MooSung,
Please check the attached modified project.
The modified simple feature might give you an idea how to use it.
Coming to your second question please check the picture below.
In this scenario when the value of N equals to 7, the argument H will be hidden in your created feature.
Note: you have created the argument N as FDouble, maybe you would prefer to assign it as FUnsigned
Cheers
Ceyhan
-
1
-
-
Hi Bastian,
In SpaceClaim there is a certain situation that we observe. When no color is assigned in CAESES; within SpaceClaim strangely one of the face assigned colors is directly assigned to the entire volume.
And that was the problem you were facing. In order to resolve the problem I will recommend you to assign a color to the entire BRep.
At the bottom of the BRep menu , under Display Options you can find the location where you can create/assign BRep body colors
However those colors assigned to each operation becomes a Named Selection for a face group
Note: This problem is not observed in DesignModeler
Cheers
Ceyhan
-
Hi Anup,
1) For the Named Selection creation within SpaceClaim, please go to;
File > Space Claim Options > File Options >general
and disable the option "Use SpaceClaim color tones when importing"
This is also mentioned in the Ansys ACT App tutorial file within CAESES
2) As Joerg has mentioned I would recommend not to use a polycurve since it will provide you a single loop.
Why don't you create a 3D model with a defined unit depth?
You will be able to assign named selections within CAESES. In the mesher you can create a mesh with single element in depth direction.
But also I would like to keep in my radar to find a way for transferring some specific curves/lines using ACT which can be distinguished and used in IcemCFD.
3) With the new upcoming CAESES version and the provided updated ACT App there will be the possibility for the user to transfer CAESES units to SpaceClaim/DesignModeler
Cheers
Ceyhan
-
Hi Bastian,
They should be updating simultaneously.
What kind of error messages do you get?
Maybe you can share some screenshots with me.
Cheers
Ceyhan
-
Hi Bastian,
Please check the attached tutorial for CAESES TurboGrid ACT App which is also included within CAESES.
In order to include several components, let's say n rows of rotor, m rows of stator what you have to do is to create n+m (in this case) TurboGrid export features within your project.
Please check and let me know if the problem is resolved.
Cheers
Ceyhan
-
Hi Carola,
Are you using the ACT app for CAESES within ANSYS workbench?
If so for each ANSYS DesignPoint you will have a separate CAESES Project with its related folders. At this point ANSYS is the tool that controls where the folders would be located.
Please let me know if you need further assistance.
Cheers
Ceyhan
Quadcopter propeller design
in Variation & Optimization
Posted · Report reply
Hi Justin,
Sorry for the late answer.
I would recommend you to perform the basic tutorials first so that you can have an idea how CAESES works. Then you can start using some Blade specific features that would enable you to create the desired geometry in a faster way.
You are highly encouraged to ask more specific questions with regards to parametric blade creation.
If you are planning to use ANSYS WB in conjunction with CAESES you can use the CAESES ACT App that comes with the CAESES installation files. You can also find the latest version of the ACT app within ANSYS ACT library.
Cheers
Ceyhan