Converting PCOMP/PCOMPG to PCOMPP
Hi,
Is there a simple way to convert a PCOMP/PCOMPG composite model into PCOMPP?
Which allows me to easily changing the stacking sequences?
Best,
Jerome.
Best Answers
-
0
-
hello @jerometeoh ,
“WOUND” is used to represent the filament winding process, where typical coverage of a “ply” can have all of spatially varying thickness and orientation on a spatially varying number of layers.
WOUND today is usually populated from external manufacturing software. It’s just a datastructure though, and if your company has a manufacturing process from which they want to pass data which is spatially varying (including number of layers per “ply”), it can be populated via script.
Hope that helps,
Michael
1
Altair EmployeeAnswers
-
0
-
Michael,
Thank you for this.
I cannot find the script in my pc.
But I think I found out that as I am using HyperMesh 2023.1.
Looks like I can just execute 'absorb' within the composite browser, it should yield the same result?
Best,
Jerome.
0 -
Hello @jerometeoh ,
did you download the script available as attachment in th elink I shared with you?
Best Regards,
Michael
0 -
Hi @Michael Herve_21439 ,
I just found the script, it is useful thank you! I like how it executing it one-by-one.
I was trying to use this to convert PCOMP to PCOMPP for some filiment winding pressure vessel application. I am wondering if you ever do that?
Also, how do people typically use 'wound' ply type?
0 -
Very thank you for the script!!
0 -
hello @jerometeoh ,
“WOUND” is used to represent the filament winding process, where typical coverage of a “ply” can have all of spatially varying thickness and orientation on a spatially varying number of layers.
WOUND today is usually populated from external manufacturing software. It’s just a datastructure though, and if your company has a manufacturing process from which they want to pass data which is spatially varying (including number of layers per “ply”), it can be populated via script.
Hope that helps,
Michael
1 -
@Michael Herve_21439 thank you for the clarification!!
0
