The following video of a presentation by Leo Greene at the 2018 Spring Event can be viewed in your browser.
Often promised, rarely delivered, MBD has generated a lot of excitement lately. Learn some of the basics and uncover some of the considerations of Model Based Definition. Recorded live in front of a regional user group at Flywheel in Winston-Salem, NC using Creo Parametric 4.0
With over 20 years immersed in the improvement and implementation of product development systems and processes Leo is an expert in leveraging the benefits of Complex Geometry, Surface Model Development, Large Assembly Management, as well as Photorealistic 3d Rendering. He is available for Engineering Consulting Services and/or Custom Creo Training.
Mark was previously the Creo, Windchill, and License Administrator for the x86 Server team at Lenovo in the Research Triangle Park. In addition to providing administrative support for these tools, he also maintained a website for the Creo User community at Lenovo and developed application customizations to help the engineers do their jobs more efficiently. He had been in this role since December 2012 and prior to that was a mechanical engineer designing electronic system packages at IBM, Solectron, C-MAC and Nortel Networks. In his spare time he enjoys playing board games with the family and working in his church.
In an assembly with many components, can you window around several components and assign them to a specific layer? Wildfire had this ability but Creo 2.0 doesn’t seem to support.
Jason Osborne, TE Connectivity
Answered by: Gavin B. Rumble, PE
Odd, this Window Select functionality DOES seem to be identical in Wildfire 4 and Creo 3. I would also add that in neither case does it actually seem to be the slightest bit useful! I may be missing something, but the only options seem to be to Ignore the selected item(s) or Add it to a NEW layer. I almost NEVER would want to do the latter.
What exactly are skeleton models used for? What are the true benefits?
Jess Lawrence, Newell Rubbermaid
Answered by: Gavin B. Rumble, PE
Skeleton models may have grown out of a best practices from the 90’s whereby a part was populated with datum and surface features and called a “map part” . These would be assembled early in the Model Tree and would be used to hang parts on or even drive geometry.” Later, this functionality was added to Advanced Assembly as Skeleton models, with many new capabilities. The short answer is, “Skeleton models are automatically added to the top of the Model Tree and are used to hang parts on or even drive geometry”. Continue reading What are skeleton models?→
(Q1) If you copy a part from an assembly to use in a different assembly, can you break its relation to the original assembly and skeleton? (Q2) Or does the relation to the original skeleton not copy across?
When replacing components in an assembly that was made by Pro/PROGRAM, how do you manage references and make sure you get rid of references to parts that no longer exist in the assembly?
by Steven Goulet, JTEKT/KOYO
Answered by Gavin B. Rumble, PE
Assuming you are not using Pro/Notebook (Layouts), then you will need to research, understand, and edit/modify as follows in the model (both assemblies and parts):
First, check the Program…Tools tab>Model Intent>Program…which has an INPUT section, RELATIONS section, EXECUTE section, and ADDS section. Any references to your deleted and/or added model need to be addressed. The INPUT section really is just a Parameter declaration and is not component specific so it usually won’t cause you problems. The RELATIONS are accessible from either the Program editor or the standard RELATIONS editor. Look for references to your deleted model such as D41 = D18:39. The EXECUTE section is misnamed…it should be called “pass the parameter”, as it drives parameter values from the current assembly down into a sub-assembly or part. Delete or re-write these commands to accommodate the model replacement. Finally, search (Ctrl-F) the ADDS to see if the component has Program code wrapped around it (such as and IF and ENDIF). These will need to be deleted and later recreated (if required) for the new component.
Now that the Program is “neutered” with respect to the component swap, make your assembly changes as you normally would.
As noted above in step one, re-create the desired Program code to then properly drive the new model(s).
It should be said that the above is not for the faint of heart…it gets very complicated sometimes.
Finally, it should also be said that the Program capabilities themselves can sometimes be used to achieve such a component swap. Family Tables and Interchange assemblies required.