gumby5000
Mechanical
- Jan 23, 2003
- 3
All,
I have a longstanding question/problem regarding the creation of family parts. I am creating models of
standard fasteners in our inventory using the family part tool. All is well with this method except for
symbolic threads. There is apparently no way to add the thread callout from the thread feature into the
family part list. For example for a family of hex nuts, my family part spreadsheet might look like this:
Part_name width thickness thread
1 .438 .226 1/4-20_UNC
2 .500 .273 5/16-18_UNC
3 .562 .337 3/8-16_UNC
There's no problem with the expressions "width" and "thickness", but "thread" cannot be defined as an expression because "1/4-20_UNC" is a string and cannot be evaluated.
The only work around that I've found is to define the symbolic thread manually using extra expressions like "major_dia", "minor_dia", etc. and add them to the family table. It works, but it seems really silly to add this information in manually when it's already in the thd_english.dat file and could be just a table look-up.
Any thoughts or suggestions?
Thanks!
gumby5000
I have a longstanding question/problem regarding the creation of family parts. I am creating models of
standard fasteners in our inventory using the family part tool. All is well with this method except for
symbolic threads. There is apparently no way to add the thread callout from the thread feature into the
family part list. For example for a family of hex nuts, my family part spreadsheet might look like this:
Part_name width thickness thread
1 .438 .226 1/4-20_UNC
2 .500 .273 5/16-18_UNC
3 .562 .337 3/8-16_UNC
There's no problem with the expressions "width" and "thickness", but "thread" cannot be defined as an expression because "1/4-20_UNC" is a string and cannot be evaluated.
The only work around that I've found is to define the symbolic thread manually using extra expressions like "major_dia", "minor_dia", etc. and add them to the family table. It works, but it seems really silly to add this information in manually when it's already in the thd_english.dat file and could be just a table look-up.
Any thoughts or suggestions?
Thanks!
gumby5000