Inventor – Weld Gap nominal parameter

I’d like to see a way to get the Frame Generator tools to access the parameters.  I am a top down kind of guy, and like using extrusions and dependent sketches for my frame skeletons.  I derive almost everything to keep all my parameters centrally located. 

The design I am currently engaged in was started without some specs, and after receiving them I find that he builder does not want any weld gapping.  So I have to run through every weld and remove the gaps.

It would be nice to set the gaps a local parameter that is factored from a derived parameter, like ‘NomWeldGap = MatThickness * NomWeldGapFactorl’ or something similar.  This way I can change the NomWeldGapFactor in the skeleton, and all the gap would alter in relation to their individual material thicknesses. 

Civil 3D – Part Builder Context Solution Part 2

Part Builder Context Solution Part 1

Ok, at last, the end of the journey.  We covered getting the model values out of an existing part.  The remaining issue lies with what to do now that we have a mandatory context added to the structure type.  Each time we create a new form of that structure type, that variable will be added to the Part XML file with all the other OEM required variables, such as "SHBTh".  This would not be a problem except that we still cannot get our non-OEM variables forced into the part model parameters.

As you may recall from earlier discussions, adding an existing catalog parameter to the model parameters is verboten.  Consequently without some assistance, each new part would require yet another context parameter to be created in the list.  Eventually the list of copies of the same variables would be ridiculous.

What we did figure out is that we can link a required context parameter that is created in the part XML, to a parameter we used in the model parameters. 

The basic outline is as follows:

• Create the new part, using the proper structure type. 
• Validate the part and save it.
• Create the model to its completion, adding any model parameters as needed.
• Configure the Required Context Parameter to be a range or a list as desired.
• Save the part and exit.
• Edit the Part XML, and change the MODEL parameter’s equation to equal the Required Context Parameter.
• Save the file and perform a catalog regen, and a catalog validation.
• Check the part validation file to confirm all is well.  If it says there is a duplicate parameter, return to the Part XML, find the parameter definition that is a duplicate, and delete it so that only one parameter definition remains

Civil 3D – Part Builder Context Solution Part 1

I stated previously that David Neill gave me an idea.  A simple switch that had not been useful previously.  The problem was that I had just not returned to it after so many new ideas.  Thanks David!!  I guess collaboration works huh.

It took a while.  I had beaten this up over and over.  I did not want to rerun it all.  Through the frustration, I just kept thinking there is no way David is crazy.  Eventually, I got the combination right. 

This article proceeds with the premise that everyone is familiar with part builder to some degree, and has an existing part that needs to be made variable.  If not, I have a load of info already to use to catch up.

I did say multi part.  Don’t worry, there are only 2 parts.  The first is what David ad I worked to beat, and the second is when that wasn’t good enough for me.

Part 1 – Getting our existing Parameters into  structure that allows later adjustments.

Part 2 – Getting the Catalog require parameters BACK INTO the model.

I have rewritten this 3 times.  Please forgive me if it is a bit shabby.  It is all starting to run together now.

The old problem

We have been fighting an old issue of customizable parameters.  We can make he basic parameters such a height, width, etc. adjustable in the Civil 3D environment, but not specific feature parameters that we need.  Say like the angle of a structure slope.  After working so hard on a structure, who wants to be stuck with a limitation.  David and I did get some ranges and lists to come through, but we couldn’t do it on a consistent basis…until now.

I will go through and identify the major portions of this adjustment.  As I do I will discuss the issues, and explain the edits.  We will be changing things as we go.  This is not a tutorial, but more of an explanation, and a few warnings that have not been made clear elsewhere.

We will focus on the following:

• Some basic information about the Catalog
• Getting into the Part Builder Catalog in 2010
• The Custom Switch
• The Model Variables
• The Context
• The Named Parameter
• The thing that hides Successes and Failures the most
• Validation

Civil 3D – Part Builder Part 6

Back to Part 5

Backup your model

Before we begin, I seriously and strenuously suggest you back up your model.  Don’t do the saveas (which is fine I suppose), but instead use Windows explorer to copy the .DWG and .XML files to a backup location. The VISTA path to these items is C:\ProgramData\Autodesk\C3D 2009\enu\Pipes Catalog\US Imperial Structures\Inlet-Outlet-Custom\

Map the User Parameters to the Application

You may remember the parameters that were handed down when we verified the structure a few sessions ago.  These ‘handed down’ parameters are those that the application uses in it’s controls, and were assigned when we used the Part Configuration Undefined Bounding Shape.  Without these, the structure cannot be modified. These parameters are SHBTh, SHBW, and SVPC, which are the Thickness, Base Width, and the Vertical Pipe Clearance respectively. We used the user parameters (like bThick) to buffer our equations from the application controls, and to make it easier to understand when reading the parameter list.  When we go back to make changes, we can disconnect the application parameters, and toy with our user parameters, and then attach them when we are done.

Let’s set these values before we proceed farther.  Edit the Model Parameters as follows:

SHBTh = 6

SHBW = 24

SVPC = 24

Now we have given something solid to these values, we can map these to the user parameters we created.

bThick = SHBTh

bWidth = SHBW

Now that the parameters have been set, we need to change the bounding shape to be a box.  Right now, the application will only display the structure as a 3D solid, and many styles will not display

this.  To simplify your model in some cases, we need the bounding shape to be a box.