Male Threads (simplified) in part families

[NutAce]

Hello all,

I was just wondering how you guys handle Male Threads (simplified) when they are changed in Partfamilies.
Just altering the shaftdiameter isnt't changing the Threadsize and the other way around (change the threadsize) isn't working either...

Any workarounds?

Using NX8.5 Switching to NX9 shortly

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[aluminum2]

I believe there are other parameters you have to change as well. such as major diameter, pitch, minor diameter and shaft size. I looked at the UN/UNJ thread data and used the equations to make my own threads. The NX threads are nominal and have no use to the manufacturing world.

 

[JohnRBaker]

Attached is a Family Table part that I created years ago when I was developing one of our early fastener libraries. This is a model of a Hex Socket Head Screw which of course has a 'male' thread. Normally these files are created without the detailed threads for performance reasons. To turn the detailed threads on, simply edit the expression 'Thread' from '0' to'1'. If you look at the expressions you will see how the threads are controlled and if you look at the family table spreadsheet you'll see which expressions are needed to control the size of the threads.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[NutAce]

Thank you John for the nice example.

It is basically confirming what I already concluded...you need to recreate the threadtables in your part family spreadsheet.
I had this discussion during the Beta test event here in Zürich as well. The testlead over there was expecting it should be no problem to have the same functionalities as with the threaded hole features. After all it wouldn't be anymore different than A Synchronous modeling action which is stacked upon the original feature (in this case an extrusion or boss)


Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[JohnRBaker]

As you you've alluded to, this could be done in the same way as we've done Female threads and you're correct. And for the record, we are aware of this and it's on our list for when we update the male thread function in some future version of NX, but until then, the approach that I used in the example part I posted is about as good a solution as we can offer at this time.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[NutAce]

Thanks John,

Indeed, I think the best way for now would be to recreate the thread table in the PF spreadsheet.

I also came up with the idea to create a Dummy Threaded Hole (no bolean) and use it's feature expressions (Pitch,angle, minor and major diameter) to control the manual entries for the Male Thread.
In such a way I can control the Dummy Threaded hole feature in the part family spreadsheet which in sequence would then control my Male threads...

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5