![]() ![]() Some people make the sketch at the part level, and that removes the circular reference, but can create other problems. Layout is somewhere in between, because the sketch (layout sketch) is at the assembly level, and part 1 and part 2 can reference the sketch in the assembly. There is always the danger of creating circular references, or daisy chained references that require multiple passes to get everything rebuilt properly. So each reference in part 2 contains links to part 1 and assembly 1. So the reference between part 1 and part 2 contains the assembly file. Top down (in-context) is where parts reference one another in an assembly. Well, the assembly references the part, that's the extent of the references. ![]() Layout is really just an intermediate step between top down and bottom up.īottom up has no references. I don't know anything about that, but I think there is more to it than just a name in Pro. Skeleton techniques, as far as I know, started in Pro/E. It's just a really bad idea to give things like LAYOUT and PDM proper names when generic names also exist for something very similar. That feature is different from the assembly based sketch. It was in the standard SW training material from way back.Īnd then SW confused things by creating an assembly feature actually called Layout. Layout sketch has been around for a long long time as part of the software. ![]() There's a reason people ask what SSP is - because it's not really a thing. SSP is really just layout sketch technique. I may annoy some people saying this, but it's true. If you have Sketch symmetry, that centerline can be tied to the Symmetry Plane within multiple sketches for different purposes. What about multiple knobs, or asymmetry, or such? Duplicate the Right Plane with an identical Symmetry Plane and maybe even a third Lateral Knob Plane. In your drawer example, you seem to begin with the assumption that you will have one knob and it will be centered on the symmetrical plane. Then, I can relocate or flip one without affecting the other and everything else tied to the other. For example, I have a plane to determine position (Coincident, Distance) and a second identical plane to determine orientation (Parallel) which usually applies accessibility or clearances to operator handles. Unless I'm dissecting and altering the SSP, it stays hidden.ģ.b. Folders in the SSP should match default assembly folders, for greatest ease. If it begins to expand past the vertical capacity of my feature tree, I can cluster meaningful portions of the references into categorical folders. I select mate references from the tree, by name, and not in the visual workspace. I love Clutter! I name things appropriately so I can find it. I make sure that components have appropriate internal reference entities to accept useful mates upon planes and axes in the SSP.ģ.a. That's a darn good metaphor that I should remember. This means that "stem" items are entirely on the SSP refs, "branch" items are partially on the SSP refs, and "leaf" items are only related to the "branch" it is on. I mostly use Planes in the SSP for driving primary mates, and secondary mates can be tied to the primary part. Almost everything in my SSP assemblies is a purchased part, except for pipe, steel weldments, and maybe some custom parts like a containment shielding panel. This one is easy for me, and may not apply to your use. You can always implement new references within the SSP to adapt to what you had not expected.Ģ. Effective SSP, in my opinion, relies on your assessment of what variables need to be adaptable, and which are driven along with the adaptive ones. Expectations can sting: what did I expect to change, and what did I expect not to change? I am usually surprised by which is which. No, if this is a single thing produced once with the capability to change based on customer or design feedback. Yes if you will be making multiple variations of it, particularly in production volume. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |