Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
All,
I am currently working on some aerospace parts with aluminum honeycomb with all of those little hexagons. Does anybody have a good way of modeling these? They are almost like cookie cutters patterned thousands of times. I know that this will be quite memory intensive, however I do need to show some views with the honeycomb.
Sincerely,
Neal Rosenblum
Geometrix Engineering, Inc.
201 N. 13th Avenue
Hollywood, FL 33019
Ph: 954-920-2049
Fax: 954-920-9574
Cell: 954-649-9399
<u>neal@geometrixeng.c</u>
Neal,
I know of a convoluted technique which will reduce the number of features, and it requires surfacing. Below is a summary of the steps (refer to attached JPEG):
It may not work on a sheet metal part that requires a flat pattern. As I have been on SW lately, and created this example using Pro-E WF 3.0, there may be some differences on Pro-E WF 5.0.
Chris
In Reply to Neal Rosenblum:
All,
I am currently working on some aerospace parts with aluminum honeycomb with all of those little hexagons. Does anybody have a good way of modeling these? They are almost like cookie cutters patterned thousands of times. I know that this will be quite memory intensive, however I do need to show some views with the honeycomb.
Sincerely,
Neal Rosenblum
Geometrix Engineering, Inc.
201 N. 13th Avenue
Hollywood, FL 33019
Ph: 954-920-2049
Fax: 954-920-9574
Cell: 954-649-9399
<u>neal@geometrixeng.c</u>
With any large identical pattern which once done doesn't require much development, the aim is always to minimise the feature count to be regened. Chris' suggestion is good because the instances are simpler than their driving parent - also you can add features to the driving group and your surface set will update accordingly - if you pattern a group you cannot add elements to the driving group.
Another method is to model the honeycomb sheet in a seperate part file and then import it to the current model where it can be cut to size - Insert > Shared Data > Merge This will then be a neutral feature in the main model. If you know the honeycomb size is not going to change you could even break the Dependent link to the associated model.
Sean