Hi Sccot
This I didnt now before.
I have trayed to do that in BOM table but changing in the Bulk Edit is similar convinient
Thank you very much, This is exactly what I need
I am appreciated !
Regards
Mat
Hi Sccot
This I didnt now before.
I have trayed to do that in BOM table but changing in the Bulk Edit is similar convinient
Thank you very much, This is exactly what I need
I am appreciated !
Regards
Mat
What are the requirements for proof that you are a student or faculty?
Student or Faculty ID ? Something else ?
Hi all,
Does anyone know if there is a setting to deactivate the auto creation of thread cut lines (Geman: Gewindeanschnitt) in NX?
When creating a thread hole, these lines will automatically be displayed in a section view. We want to deactivate these lines by default for specific drawings.
Default representation in NX:
Comparison: Solid Edge will not display these lines by default:
Regards,
Nico
Hi all,
Not sure if this is a NX or Teamcenter discussion, but I will try. I have tried to search for a solution but could not find the answer I am looking for. Perhaps I am searching the wrong thing or what I want is not a good way of doing things.
I am using NX11 with Teamcenter 11.
I trying to figure out if it is possible to do following: Below I have a figure showing assemblies and parts like you see in NX assembly navigator. When working in NX I want to have "dummy" assemblies (RED) to better organize the parts and subassemblies, but when I send assembly-1 to structure manager or add a part list in drafting the only thing I want to see is the parts and assemblies marked in GREEN.
If I can recall i did something similar in Inventor where I made the assembly phantom and/or promoted the children. Been a while so not sure what I did. Anyway, the assembly was removed from the BOM, but the children was included.
Possible to do something like this in NX?
Morning all,
I have recently moved to NX12 from NX9.0 and I seem to be having a few issues that is making NX12 a chore to use..
First is the point to point move function, or any move function for that matter. In an assembly in NX9.0 you could pick a cap head screw for example, open the move command, select point to point, click on the centre of the screw (ie the shoulder of the screw that butts up against the part being attached) and then click the bottom of the counterbore. NX9 would then move said screw to the desired hole - job done. I could pick both the screw and hole in any orientation with the shaded with edges view selected in NX 9.0.
Moving to NX12, im really struggling to select the centre point in any orientation with shaded with edges view. I can SOMETIMES get it by rotating my view right around so I am looking at the shoulder, but that doesent always work. The only way I'm reliabally able to select the centre pont is to keep switching to wireframe which allows the centre to be picked without any issue, then pick the bottom of the c/bore, screw moves and I can go back to shaded with edges.
The problem isnt just with point to point, its happening with all the "move" functions as well as "translate" functions - Very annoying!!
Secondly is the selection filter. On a number of occasions in the assembly I am working in the selection filter box goes blank so when hovering over a part it says "solid body in ##insertpartnumber##". I keep having to go up to the top on the drop down and select "no selection filter"...... Again another frustrating/pee you off feature of NX12.
Any help would be greatly appreciated on the above points.
Matt
Which server you are using?
is there any option in NX similar to "Pack and go" Option in Solidworks?...
Hi
not as OOTB (Out of the box) integrated into NX, but you have to customize your toolbar with a journal called Zip Assembly.
You can find all files in the zip on this thread.
wrote: 1) I think you are modifying an expresison, not an attribute?
or is the attribute linked to an expression?
2) If you add a 2nd copy of one of the PF members, and edit the C_angle, do both change to that angle?
I'm modifiying a attribute.
When I add the first instance of PF (NUMBER 1 in image above) the C_angle ATTR is inherited from the family(in another words, all PF members has 90 degrees as default angle) as you can see "Attribute is inherited from component part".
Then I add the second one (or a copy
But I can't get my macro work even if I don't modify any attribute. It's like NX can't recognize my PF custom ATTRS.
I'm starting to think that the problem is to read it at all
Best Regards
Without a total understanding of what you are trying to accomplish, To me it looks like you need the Mulit-Structure manager functionallity of Teamcenter.
Scott
On the move command make sure you turn on the option to "Allow Selection of Hidden Wireframe". In shaded mode this will allow the selection of things you know are there but cannot see. In the moive I did a move component and started with it turn off and could not pick the shoulder, then in wireframe in can pick the shoulder. I went back to shaded mode and then turn on the "Allow Selection of Hidden Wireframe" and was able to select the should that I can not see. My guess is that you had this turned on in NX 9 and the off in NX 12.
HTH,
Scott
Hello
Try the following:
As long as the curves on the parent body are selectable you should not see any issues.
By the way, I assume you know the formed shape of the part? Not all bends are 90deg of course.
Dave
With your assembly as the displayed part, run the journal below. It will report the component attributes. It will help verify that the attributes are on the components as you expect and it may provide a starting point for your own code.
Option Strict Off Imports System Imports NXOpen Imports NXOpen.UF Imports NXOpen.Assemblies Module Module2 Public theSession As Session = Session.GetSession() Public ufs As UFSession = UFSession.GetUFSession() Public lw As ListingWindow = theSession.ListingWindow Sub Main() Dim workPart As Part = theSession.Parts.Work Dim dispPart As Part = theSession.Parts.Display lw.Open() Try Dim c As ComponentAssembly = dispPart.ComponentAssembly If Not IsNothing(c.RootComponent) Then reportComponentChildren(c.RootComponent, 0) Else '*** insert code to process piece part lw.WriteLine("Part has no components") End If Catch e As Exception theSession.ListingWindow.WriteLine("Failed: " & e.ToString) End Try lw.WriteLine("component processing complete") lw.Close() End Sub Sub reportComponentChildren(ByVal comp As Component, ByVal indent As Integer) For Each child As Component In comp.GetChildren() '*** insert code to process component or subassembly lw.WriteLine(New String(" ", indent * 2) & child.DisplayName()) Dim userAttInfo() As NXObject.AttributeInformation = child.GetUserAttributes For Each temp As NXObject.AttributeInformation In userAttInfo lw.WriteLine(New String(" ", indent * 2) & "attribute title: " & temp.Title & ", attribute value: " & temp.StringValue) If IsAttributeOverridden(child, temp) Then 'lw.WriteLine(New String(" ", indent * 2) & "attribute title: " & temp.Title) lw.WriteLine(New String(" ", indent * 2) & "** value overrides part attribute") End If Next lw.WriteLine("") reportComponentChildren(child, indent + 1) Next End Sub Function IsAttributeOverridden(ByVal theComp As Component, ByVal theAttribute As NXObject.AttributeInformation) As Boolean 'if "inherited" = false, the attribute may be original to the component or it is overridden 'if the component's parent (part) has the same attribute, it must be overridden 'otherwise it must be new to the component Dim thePart As Part = theComp.Prototype.OwningPart Dim isOverridden As Boolean = False If Not theAttribute.Inherited Then If theAttribute.Array Then isOverridden = thePart.HasUserAttribute(theAttribute.Title, theAttribute.Type, theAttribute.ArrayElementIndex) Else isOverridden = thePart.HasUserAttribute(theAttribute.Title, theAttribute.Type, -1) End If End If Return isOverridden End Function Public Function GetUnloadOption(ByVal dummy As String) As Integer Return Session.LibraryUnloadOption.Immediately End Function End Module
The last post in this thread has a link to an NXzip. that uses 7zip
I still use UGzip more often out of habit though as its right in my File->Export menu ( using NXcustom)
I'm looking for methods that others are using to accurately check wall thickness where symbolic threads are being used. Curves get generated to show where the depth of the threads are. However the real geometry is set to the minor diameter thus not including the threads in the calculation. Any suggestions other than using detailed threads?
Now i'm able to read the attributes that I was looking for! And it will be a starting point to fix my code.
Thanks
Best Regards
Hello tok,
in the dummies parts you can "properties" and place "yes" on the atribute "PLIST_IGNORE_MEMBER"
aditionaly you can create a template for "new files" where you already have that atribute placed.
i dont know if there's better workaround. (this is the way i do)
Hi,
--- I have configured the nxtopvdirect translator on Dispatcher Module. The following error message is displayed and no jt is created: ERROR 1140 :Failed to load part: [Unable to create the export directory.
Below the complete log:
2018-06-28 14:31:38,687 INFO - Standard Input : ##### COMMAND IS "C:\swbase\plmsw\nx110\PVTRANS\run_ugtopv.bat" -single_part -config="C:\swbase\plmsw\tcdispatcher\Module\Translators\nxtopvdirect\tessUG_NX11_PROD_MULTICAD.config" -noupdate "-pim=yes" "-u=tsproxy" "-p=tsproxy"
2018-06-28 14:31:40,515 INFO - Standard Input : ============================================================================
2018-06-28 14:31:40,577 INFO - Standard Input : NX JT Export (version - NX1102 - Build date - Jul 24 2017)
2018-06-28 14:31:40,624 INFO - Standard Input : Copyright 2014 by Siemens Product Lifecycle Management Software Inc.
2018-06-28 14:31:40,687 INFO - Standard Input : 5800 Granite Parkway, Suite 600.
2018-06-28 14:31:40,734 INFO - Standard Input : Plano, TX 75024.
2018-06-28 14:31:40,796 INFO - Standard Input : USA.
2018-06-28 14:31:40,843 INFO - Standard Input : Phone: 1 (972) 987-3000
2018-06-28 14:31:40,906 INFO - Standard Input : Fax: 1 (972) 987-3299
2018-06-28 14:31:40,952 INFO - Standard Input : Web site: www.siemens.com\plm
2018-06-28 14:31:41,015 INFO - Standard Input : ============================================================================
2018-06-28 14:31:41,062 INFO - Standard Input :
2018-06-28 14:32:09,999 INFO - Standard Input : FCC interface version fms.11.2.3.20161119.00.
2018-06-28 14:32:10,061 INFO - Standard Input : Loaded implementation library 'C:\swbase\plmsw\tcroot\tccs\lib\FCCClientProxyDllv10064.dll'.
2018-06-28 14:32:10,124 INFO - Standard Input : FCC interface version fms.11.1.0.20150114.00.
2018-06-28 14:32:10,186 INFO - Standard Input : Loaded implementation library 'C:\swbase\plmsw\tcroot\tccs\lib\FCCClientProxyDllv10064.dll'.
2018-06-28 14:32:10,249 INFO - Standard Input : Looking for config file: C:\swbase\plmsw\tcdispatcher\Module\Translators\nxtopvdirect\tessUG_NX11_PROD_MULTICAD.config .... Found!
2018-06-28 14:32:10,296 INFO - Standard Input : Translator Log File created at: \\nas\swbase\plmtmp\Dispatcher\NX\FA00AAU00001_001.0001-PRIMO_ITEM_ThuJun281432102018_4528_infodba.log
2018-06-28 14:32:11,597 INFO - Standard Input : INFO 3115 :Received part [@DB/FA00AAU00001/001.0001]...
2018-06-28 14:32:11,652 INFO - Standard Input :
2018-06-28 14:32:11,686 INFO - Standard Input : INFO 3150 rocessing part [@DB/FA00AAU00001/001.0001]
2018-06-28 14:32:11,733 INFO - Standard Input :
2018-06-28 14:32:11,780 INFO - Standard Input : INFO 3175 :Loading [@DB/FA00AAU00001/001.0001] to [generate jt data]...
2018-06-28 14:32:11,827 INFO - Standard Input :
2018-06-28 14:32:13,546 INFO - Standard Input : ERROR 1140 :Failed to load part: [Unable to create the export directory. ]
2018-06-28 14:32:13,608 ERROR - The translation failed because the following error
in the Standard Input : ERROR 1140 :Failed to load part: [Unable to create the export directory. ]
2018-06-28 14:32:13,624 INFO - Standard Input :
2018-06-28 14:32:13,655 INFO - Standard Input : ERROR 1165 :There were errors in the translation process ***. Translation of the following parts generated these messages:
2018-06-28 14:32:13,718 ERROR - The translation failed because the following error
in the Standard Input : ERROR 1165 :There were errors in the translation process ***. Translation of the following parts generated these messages:
2018-06-28 14:32:13,733 INFO - Standard Input :
2018-06-28 14:32:13,780 INFO - Standard Input : ERROR 1170 :Errors/Warnings for the part: [@DB/FA00AAU00001/001.0001]
2018-06-28 14:32:13,827 ERROR - The translation failed because the following error
in the Standard Input : ERROR 1170 :Errors/Warnings for the part: [@DB/FA00AAU00001/001.0001]
2018-06-28 14:32:13,858 ERROR - The translation failed because the following error
in the Standard Input : ERROR 1170 :Errors/Warnings for the part: [@DB/FA00AAU00001/001.0001]
2018-06-28 14:32:13,874 INFO - Standard Input :
2018-06-28 14:32:13,905 INFO - Standard Input : ERROR 1175 :Error text: [Failed to load part: Unable to create the export directory. ], Error code: [940167]
2018-06-28 14:32:13,968 ERROR - The translation failed because the following error
in the Standard Input : ERROR 1175 :Error text: [Failed to load part: Unable to create the export directory. ], Error code: [940167]
--- Note: the same command, launched from a DOS shell, works fine:
C:\Users\infodba>"C:\swbase\plmsw\nx110\PVTRANS\run_ugtopv.bat" -single_part -config="C:\swbase\plmsw\tcdispatcher\Module\Translators\nxtopv
direct\tessUG_NX11_PROD_MULTICAD.config" -noupdate "-pim=yes" "-u=tsproxy" "-p=tsproxy"
============================================================================
NX JT Export (version - NX1102 - Build date - Jul 24 2017)
Copyright 2014 by Siemens Product Lifecycle Management Software Inc.
5800 Granite Parkway, Suite 600.
Plano, TX 75024.
USA.
Phone: 1 (972) 987-3000
Fax: 1 (972) 987-3299
Web site: www.siemens.com\plm
============================================================================
FCC interface version fms.11.2.3.20161119.00.
Loaded implementation library 'C:\swbase\plmsw\tcroot\tccs\lib\FCCClientProxyDllv10064.dll'.
FCC Interface Implementation fms.10.1.5.20170331.00 initialized.
FCC interface version fms.11.1.0.20150114.00.
Loaded implementation library 'C:\swbase\plmsw\tcroot\tccs\lib\FCCClientProxyDllv10064.dll'.
Looking for config file: C:\swbase\plmsw\tcdispatcher\Module\Translators\nxtopvdirect\tessUG_NX11_PROD_MULTICAD.config .... Found!
Translator Log File created at: \\nas\swbase\plmtmp\Dispatcher\NX\FA00AAU00001_001.0001-PRIMO_ITEM_ThuJun281440022018_2708_infodba.log
INFO 3115 :Received part [@DB/FA00AAU00001/001.0001]...
INFO 3150 rocessing part [@DB/FA00AAU00001/001.0001]
INFO 3175 :Loading [@DB/FA00AAU00001/001.0001] to [generate jt data]...
INFO 3155 :Loaded part file in [1.06] seconds
INFO 3610 :About to export data for component - mode is [4]
INFO 3165 uccessfully generated jt data for part [@DB/FA00AAU00001/001.0001] in [0.89] seconds
INFO 3110 :Total time for translation was [2] seconds
INFO 3180 :Translation of [1] component completed. All components translated successfully.
INFO 3000 :EXITING TRANSLATOR : Exiting this Translation Session !
I think I have not write permission on some folder where ugtopv try to create a temporary folder but I don't know where...
Any suggestion?
For example, with a factor 1.1,