Instance-level scope in Family Tables
Instance-level scope in Family Tables
(OP)
Hello everybody. I ran into a small problem that I can't quite work out.
Say I had a cylinder with a face A as a generic model for a family table. In one instance model I extrude a smaller cylinder out from face A, and in another instance model I cut a square hole into face A.
Is there a way to limit the scope of the instance models so that I can define different datum planes at both the surface of the square hole and the surface of the smaller cylinder with the same name? You know, sort of like "private" datum plane, if you will. Pro/e acts as if i declared it a "public" datum plane, and won't let me use the name twice.
I appreciate you guys' help.
-I Dabble in Modeling
Intern
Picatinny Arsenal, NJ
Say I had a cylinder with a face A as a generic model for a family table. In one instance model I extrude a smaller cylinder out from face A, and in another instance model I cut a square hole into face A.
Is there a way to limit the scope of the instance models so that I can define different datum planes at both the surface of the square hole and the surface of the smaller cylinder with the same name? You know, sort of like "private" datum plane, if you will. Pro/e acts as if i declared it a "public" datum plane, and won't let me use the name twice.
I appreciate you guys' help.
-I Dabble in Modeling
Intern
Picatinny Arsenal, NJ





RE: Instance-level scope in Family Tables
RE: Instance-level scope in Family Tables
We want to test a configuration where the flange is machined off like this: <
The geometry around the apex of the cone isn't exactly a point, and it's complex. Plus, both cones have to be toleranced with GD&T, so there has to be a better way than to create an entirely new model. All the features in the geometric tolerancing are to reference the base surface of the cone - Datum A. Do you see what I'm getting at? Is there any way at all to restrict features to instance level?
Again, thank you for your help.
RE: Instance-level scope in Family Tables
--
Fighter Pilot
Manufacturing Engineer
RE: Instance-level scope in Family Tables
RE: Instance-level scope in Family Tables
RE: Instance-level scope in Family Tables
--
Fighter Pilot
Manufacturing Engineer
RE: Instance-level scope in Family Tables
Sorry to come off like I wasn't listening, by the way. I sort of felt like I miscommunicated what I was trying to do, I guess.
RE: Instance-level scope in Family Tables
--
Fighter Pilot
Manufacturing Engineer
RE: Instance-level scope in Family Tables