Skip to main content
T
ThomasPhore1-Visitor
1-Visitor
May 16, 2012
Question

surface modeling: impossible to delete surfaces

  • May 16, 2012
  • 2 replies
  • 14262 views

I am doing a lot of stuff where I take surface geometry from various existing parts (solids) and combine them with new surfaces to create new parts that fit together with existing parts. But I am having a lot of issues in the step of taking existing surface geometry and trimming it down/merging it with new stuff to then be solidified.

Basically, when I take a complicated surface and try to trim it with a datum plane or whatever, lots of times little framents of the old surface don't go away like they are supposed to. So I have get quilts that are made up of disparate little pieces of surface. No matter how many different ways I try to get rid of the abberational surface bits, they seem to be impossible to get rid of. As a result of this, it's impossible for me to make new parts that incorporate needed existing surface geometry -- anytime I want to solidfy something, one or more of the involved quilts is invalid because of some invalid garbage that ProE considers part of the same quilt.

Anyone know what I am talking about? Anyone have any suggestions on how to avoid the problem?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

2 replies

J
James621-Visitor
1-Visitor
May 16, 2012

What I usually try to do is close up all surfaces into one volume and solidify in the shortest possible way I can. Then use solid type of operations to finish it up.

Replace copied surfaces with sketched curves if possible and then use extrude cuts.

Use seed and boundary selection type for copy operations so avoiding the possibility to miss any small surface.

If the surfaces come from imported data then making sure there aren't any bad surfaces is good idea.

Often merge is usually better than trim. Trims are more likely to fail if changes to the model occur.

To get rid of particular fragments of a quilt you can use remove feature while checking the leave open option in the dashboard menu.

Good luck.

T
ThomasPhore1-VisitorAuthor
1-Visitor
May 17, 2012

Can you tell me more about "remove feature"? I am not familiar with this. Your other suggestions all seem like very useful advice and general rules of thumb.

Can you tell me what a "bad surface" is though? I am not importing data, but I'm curious what a bad surface is exactly. And by closing up all surfaces as soon as possible, do you basically mean that you draw a bunch of curves to connect everything up into a couple big quilts? Just not sure what you mean by that exactly.

Unfortunately, the surfaces I am copying are very complicated and intricate, so they are basically impossible to duplicate by creating new features. So figuring out how to get the copied surfaces themselves to work is the only choice I have at the moment.

J
James621-Visitor
1-Visitor
May 17, 2012

Remove feature comes with WF4 or later versions of Creo and Pro/E.

http://learningexchange.ptc.com/tutorial/701/removing-a-surface-from-a-solid-or-quilt

Note the Leave Open option in the dashboard menu in this vid.

You can simply split a compound quilt into separate entities using copy feature in combination with remove feature.

About bad surfaces. At my work I sometimes I have an imported model that contains compound surfaces like corner radii and so on. With these I am unable to perform any parametric operation like trim, merge, copy and so on. They simply need to be replaced using boundary blend inside IDD while the IDD doesn't always tell that these surfaces are bad.

Corner radii in models cause never ending problem in data exchange.

If trimming, extending and merging of surfaces doesn't seem to work then I usually make a solid brick from extude and then try to use solidify operations to cut the solid.

If the surfaces are too complicated you can always use curves as trimming objects. And if parametric operations don't seem to work then style feature can always do the job.

What version of Pro/E or Creo do you use?

Could you upload one of your models with surfaces as a STEP file here?

Z
Zadyma1-Visitor
1-Visitor
May 24, 2012

Did you try to Edit Definition of the imported geometry?

Right click Imported Feature in Model Tree and select Edit Definition - you will get new pull down menu options.

Select Geometry, then Import Data Doctor. At this point you can select and delete any surface you don't need (one at the time, unfortunately).

once you exit IDD (Import Data Doctor) you can go to Feature Properties in Edit pull down menu and select Make Solid option

hope that helps

-Adam

T
ThomasPhore1-VisitorAuthor
1-Visitor
May 30, 2012

I should clarify that what I am generally doing is creating new parts from assembly mode using Insert>Component>Create>Part. I am not doing any importing or merging etc ways of sharing part geometry.

The problem comes when I try to copy big and complicated surfaces from one part in the assembly into another. The reason the surface is big and complicated, actually, is that it is one big copy of all the surfaces of a solid part. Sorry if I should have made this more clear earlier.

The way I am presently bringing data from one the "master" part to the new/child parts is by having a new/child part activated, going into the assembly model tree and selecting features from other parts, and simply doing Ctrl+C Ctrl+V. The surfaces that are producing garbage were first created originally (in the original parts) by selecting a face in the parent part, RMB>Solid Surfaces, Ctrl+C Ctrl+V. Then they I am copying the copied-surface feature over to each child part. I have to do this because the surface is complicated and basically impossible to duplicate from within child parts. The ironic? thing is that the complexity of the surface then seems to make it not work when I try to trim it down in the child parts.

I very much appreciate all the suggestions above and they will be very useful to me in other things now that I'm getting into doing lots of surface stuff. However, I still don't know what to do in this particular situation, because unless I'm wrong, the options of leaving out surfaces and using data doctor etc are not available here.

Any other suggestions? I will resort to creating IGESes and doing bunch of export and imports, but that seems like something I should only do if there really is no other way.

Terms & ConditionsAccessibility statement