Content Center Threads Issue

[Anonymous]

I'm trying to add some swage nipples to the content center with cosmetic threads.

Initial Part w Cosmetic NPT
 I included tapers on my base part with npt thread engagement length.

 Initial Sketch

When i create the family table and assign the correct Thread#:Type and Thread#:NominalDiameter, the NominalDiameter does not change when i place the part. i get the following warning.

Family TableFamily ParametersNPT Error
Placing from content center everything works fine except the Threads. The thread size is the initial size that it was published with.

CC Generated PartEdit: this is inventor 2019

Then when i go back into the family table, Nominal diameters are overridden as expressions

overriden

[JamieVJohnson2]

I find that when this typical error happens, it is because I am asking inventor to create a part that has a modeling issue.  Such as you specify a size that causes two faces to cross each other (outer diameter becomes smaller than inner diameter).   In that case, most sizes will work but one or some will not, because when I modeled it, I made the wrong design assumptions.  If you start with the iPart, then set all the dimensions into the iPart Table, then generate all the parts to review BEFORE you upload it to the Content Center, you should be able to catch, and see the errors in question.

[Anonymous]

So as a test, I took the standard Inventor content center built in ANSI pipe with threaded ends  and picked a size and saved a copy on my desktop.

I reconfigured the test pipe using Tube and Pipe and assigned it to the Nipples category.

I rebuilt the family table to match the default inventor pipe with threaded ends and assigned the table parameters to the model parameters.

So technically this should be a copy and paste from Pipe > Conduits to Fittings>Nipples.

I go to place the new Nipple and i still get the same thread error.

[JamieVJohnson2]

So the error is a lack of response, but not an actual pop up message? Or two separate errors, one lack of response, and as a result at times a popup message?

First, Look at the Family Properties, Parameter Mapping.  The Category Parameters list the values provided by the category, and the Template Parameters map the Table Columns to the Template Parameters (verify this is setup right).

Second, I want you to look at Family Table, the column in question, and rightclick over the header and pick the Column Properties option to verify it is attached to the proper parameters.  Values can be attached to the parameter several ways.  Data can be mapped from its original name (which may not be its visible name, aka caption), or as an Expression this table hosts, or mapped directly to an Inventor Property found in the template file.  With all these options it can be easy to loose track of where the data is or isnot coming from.

[Anonymous]

The test pipe i used was a 4 NPS, so original dimensions were for a 4NPS pipe that had 4NPT ends.

The original family table for pipe with threaded ends, is a string and does not use an expression but an input (fractional same size NPT as NPS). when its mapped in the parameter table to the model, its mapped as Thread1:Type & Thread1:NominalDiameter and the other end is Thread2:Type & Thread2:NominalDiameter.

i recreated my test nipple by creating the same columns as the default and made sure they were the correct string/real values. I opened the excel table from the default inventor pipe w/ threads and highlighted everything. I then copy and pasted this data into the new test nipple excel table, so everything is identical.

I reassinged the parameters to the model.

When i go to pick a size, lets say a 2 NPS pipe, it gives the correct OD, the correct Thread length, the correct thread type, but incorrect thread size, it gives 4NPT. I place another size NPS and overall dims are correct but it is still 4NPT.

I might just give up on having cosmetic threads and just show a taper on the outside body of the pipe.

[JamieVJohnson2]

From when I setup cc files, I ran into similar issues.  I found there were duplicated columns in one situation where the actual data being pushed was from a different column than I expected.  The other issue was that the template file had a property that I renamed.  Instead of using the renamed property, it recreated the original property.  That sounds more like your problem, because the recreated property no longer had a table driven value, and stayed put at the template's original dimension.

[Anonymous]

soo... i figured out how to get the threads to work and its kind of bull**** tbh.

If you want cosmetic threads on a part, you cannot publish a part and fill in the property tables, you need to start off with an iPart and batch publish and for some reason. even though the parameters are mapped to the same variables and have the same values, this seems to work.