Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Surface Merge

rakeshthacholi

New member
Hai All,


I would like to know the difference between surface intersect and join in surface merge command. And when these commands are to be used. Please advice me.


Thanks and regards,


Raakzz
 
If you want to solidifyfeatures built by surfaces you must first use surface merge to create a quilt of them.


If your surfaces are overlapping you must trim them and that is done with the intersect option (you will have more options to control the result while performing the merge)


If your surface edges are connected without overlap then you can use the join option to merge them.
 
Hai,


Thanx Ankarl. I have understood ur reply. But my doubt is that, where these two, ie. join and intersect fails. B'cos sometimes join fails and sometimes intersect fails and sometimes both can be used. I could not understand this behaviour of Proe. When does these two or either of these two fails? And when can both of these be used?


Thanx and Regards,


Raakzz
 
"... either of these two fail?"

Best to go instance by instance (if you have something on hand and can post?) but a general case would be when a good trim curve can't be created.

" ... when can both be used?"

I'd >think< that the only "valid" case would be where a Join would work (?). I did just a little testing once (and can't even remember what I was looking for or saw, so probably shouldn't even say this) but came away with the impression that if edges are coincident (e.g. no additional trim edges are needed) you're better off using the Join option.
 
Hai,


Thanx jeff.


Cud u plz tell me exactly where do these two fail. ie. when does join fail when intersect works and where does intersect fail when join works.
 
Without seeing a specific pair of surfaces or quilts I can only speculate and even then speculation is probably as good as it gets (and I ~am~ working with assumptions about the function itself).

"... when does join fail when instersect works ..."

When edges are not coincident; e.g. additional trim curves must be calculated.

"... intersect fail when join works ..."

I'd guess that attempts to create an intersection curve equivalent to the coincident edges is failing. Such a case might occur where edges are not coincident but near or within system accuracy settings and surfaces intersect near tangent. Creating "clean" trim curves can be very difficult for those conditions. The "cleanliness" of the surfaces themselves, the accuracy of existing manifold edges, vertices, etc. if intersecting quilts will also factor in.

Additional factors might include ...
__ Pro/E's ability to trim surfaces using incomplete intersections.
__ Existing GeomChks.
__ Model accuracy settings.

As I said, it's probably best to consider these on a case by case basis as it's a little complicated to attempt a one-size-fits-all answer. Got a specific instance at hand?
 
I look at it like this concerning intersectvs join<?:namespace prefix = o ns = "urn:schemas-microsoft-com:eek:ffice:eek:ffice" />


of course your actual example could be different.


1 join is more for surfaces where boundaries are the same or are already intersecting
2 Merge is more accurate where join is more forgiving in many cases
3 sometimes intersect don
 

Sponsor

Back
Top