-
Content Count
196 -
Joined
-
Last visited
-
Days Won
11
Posts posted by Ceyhan Erdem
-
-
Hi Bastian,
Are you using TE cut-off within the feature?
Cheers
Ceyhan -
Hi Bastian,
Can you please send your project to erdem@friendship-systems.com?
I will give a look and try to figure out the problem.
Cheers
Ceyhan
-
Hi Vahid,
I am sorry but within a Feature it is not possible to rename an already created object.
In the Feature definition the objects are named during compile time only.
Maybe you would like to do workaround by creating an imagecurve with the name you would like to assign.
Cheers
Ceyhan
-
Hi Vahid,
Please follow the procedure below;
Close all CAESES instances.
Remove the following files:
%PROGRAMDATA%/boost_interprocess/FS_LICENSE_SHM2
%PROGRAMDATA%/finterprocess/FS_LICENSE_SHM3
Start CAESES (without admin rights)Please let me know if the problem is resolved or not.
Cheers
Ceyhan
-
Hi Priyanka,
So you have a data set that you want CAESES to read it and create a hull form ?
Cheers
Ceyhan
-
Hi Chien,
Please find the attached simple project.
This might give you some idea about how the operations are defined. Besides that please check the sample "Axial Fan" under Documentation>Samples
For three airfoil sections, I have defined chord scaling, pitch, yaw and rake. This is just for illustration purposes to show how the steps are performed.
Of course you would like to perform those steps not one by one but using a Feature Definition, and as a result obtaining a Meta Surface.
Note: I have figured some errors in the code that I have attached earlier which are corrected
Cheers
Ceyhan
-
Hi Andreas,
Sorry for the late answer. Have tried so far the create the connection?
It should be compatible, creating no problems.
Please let me know if you encounter any.
Cheers
Ceyhan
-
Hi Chien,
Under Documentation Browser > Samples;
there is the Propeller Setup example. I will strongly recommend you to check the mentioned model and go over the Curve Engine, Meta Surface tutorials.
If you have any further questions, please do not hesitate to ask.
Cheers
Ceyhan
-
Hi Chien,
If you replace the translation to cylindrical transformation within the feature you can reach your goal. Maybe you would also be interested to introduce some skew pitch rake and scaling beforehand.
The Loft method within CAESES is a tight method.
Cheers
Ceyhan
-
Hi Chien,
Maybe you should start with a feature that reads your profiles.
Please check the attached simple project that reads airfoil data. Afterwards you can go over tutorial files that would improve your CAESES capabilities.
Cheers
Ceyhan
-
Hi Erkan,
Please check the attached project.
I have created two faces then added them to a BRep and used it for the fbrepsolidfromintersections operation.
That can give you an idea how to approach such a problem.
Cheers
Ceyhan
-
Hi Chien,
Would you like to use some profiles from a certain database for each section or use some Naca variations?
Cheers
Ceyhan
-
Hi Priyanka,
Please find the attached project.
changes made
an input argument of type Double for FOS
To the related Design Engine the base curve is assigned which is "section"
The coordinate system is changed to Y-(XZ)
And the project seems to be working.
Cheers
Ceyhan
-
Hi Priyanka,
As guessed the argument FOS is missing within the arguments list.
You can create a new argument named FOS of double type, which might solve the problem.
Cheers
Ceyhan
- 1
-
Hi Priyanka,
1) The input for the "Base Curve" within the Curve Engine, has to be in fact an attribute coming from the feature.
In your case, you are using the feature called "Aft Section" and you can find the available curves at the Drop Down List.
2) I can see that there are 7 errors, But from the console output it is possible to see only the last two. If you provide me a screen capture where I can see them all, I might be more helpful.
But most probably you forgot to define FOS or Beam as input argument.
Cheers
Ceyhan
- 1
-
Hi Erkan,
I can see from the code that the operation to trim the geometry is the one starting from line 250.
What you have to do is to change the input within the command
".setSource()"
so just create the surface that you desire to do the trimming before the fbrepsolidfromintersections operation and update the "setSource" respectively.
Please let me know if you still have problems.
I would also recommend you to go over the tutorials, once you have a basic understanding it may be easier to understand the samples.
Cheers
Ceyhan
-
Hi Simone,
Please check the sketches below,
This might give you an idea about the concepts of constant radius and constant distance.
For variable radius, Please check the attached project.
One point to mention is that the variable radius filleting is still under development.
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi Simone,
Please find the attached the project where the fillet creation wrt colored faces is performed.
Do not forget that in CAESES, colors can be assigned within BRep for each operation.
So I have created an operation "add sources" where a color is assigned to first face (let's say first_face_color),
then a second "add source" operation; adding the second face and assigning a color (let's say second_face_color)
Finally I can perform the fillet operation between the two colors (first_face_color, second_face_color)
Please let me know if you have further questions.
Cheers
Ceyhan
-
Hi Tariq,
Under Documentation Browser > Samples , you can find the "Propeller Setup" sample.
Maybe you would like to give a start with that model which will give you some guidance on how to build a propeller model.
Cheers
Cehan
-
Hi Helen,
Can you please attach your feature?
Cheers
Ceyhan
-
Hi Simone,
You can easily create loops and do your calculations in Caeses using Feature Definitions .
In your case; for each section, you can do your internal optimization and fit your sectional area by updating your created parameters.
I would recommend you to check "Effective FPL" which gives a detailed information about Feature Programming Language.
You can find the mentioned file under Documentation Browser > Tutorials > Content of Features.
Cheers
Ceyhan
-
Hi Karl,
Can you please check the attached project file.
It is a quick approach and I didn't play much with it but you can further develop it.
I have added two feature definitions;
- one for creating curve orientation consistency, f_revise_curves
- and the other for the tongue surface creation, f_tongue
Please check and let me know if you encounter any problems.
For your question about the subdivided trim edge, I would assume that there is tangency discontinuity which is causing the edge to be subdivided.
But you can easily get the trimmed edge group using the command,
your_BRep.getEdgeFrom(operation index where the trim happens)
Cheers
Ceyhan
-
Hi Karl,
I will check your model and return to you as soon as possible.
Cheers
Ceyhan
-
Hi Favour,
From what I see, I can say that you have no input arguments defined in your feature definition.
According to the CAESES_NavCad_Connection_Documentation.pdf, (page9) you should be having three input arguments within your feature definition.
Those are;
precision
sections
draft
As soon as you include them your definition should be free of errors.
Cheers
Ceyhan
coupling CAESES with seakeeping software
in Software Connections
Posted · Report reply
Hi Andreas,
If the mentioned tool that you would like to couple with CAESES has the capability to run script files or run in batch mode, then the connection should be quite straight forward.
Please let me know if you need further assistance.
I will recommend you to check the Software Connection tutorials within CAESES and the batch scripting commands of "Maxsurf Motion" within its manual.
Cheers
Ceyhan