Skip to main content
12-Amethyst
April 30, 2024
Solved

Windchill Workgroup Manager - Siemens NX CAM

  • April 30, 2024
  • 1 reply
  • 5384 views

Once the connection server is online NX lost the key to use Manufacturing Part.
The NX properties are complitely ignored about NX Manufacturing template.
Template for part, assembly and drawing are ok. We lost only template for Manufacturing template
Any ideas about it?
Best regards

Gianpaolo

 

Attached you will see the different steps

Step 1-4 OFF line behaviour

Step 1 =  Server manger OFF - no server

Step 2 =  Open a CAD part

Step 3 =  create the manufacturing part

Step 4 = open the manufacturing part linked to CAD Step 2

 

Step 5-8 ON line behaviour

Step 5 =  Server manger ON - on line

Step 6 =  Open a CAD part

Step 7 =  create the manufacturing part

Step 8 = open the manufacturing part is not linked to CAD Step 2

 

Best answer by GianpaoloGallo

Great Dobi!!!!!

 

your advice works perfectly!!!!!

 

I missed in the assebly load options the custom folders where all the custom are uploaded. (Machine..etc...)

 

Great! Great Great!

Gianpaolo

1 reply

17-Peridot
May 10, 2024

This could have to do with your NX model tree... 

 

You have a lot of wavelinked bodies. Is your "Delay Model Updates" on? NX is particular about references - especially when it's connected to Windchill - and there are types of references Windchill doesn't (yet) support (like references from routing object geometries if you do tubing or harnesses). 

 

Are the bodies you're linking available in the workspace (and therefore available in the %PTC_WFS_ROOT% folder of your cache)? 

 

When you're opening your CAD, make sure to open with Assembly load options set to "Fully Load" too... 

GianpaoloGallo12-AmethystAuthorAnswer
12-Amethyst
May 10, 2024

Great Dobi!!!!!

 

your advice works perfectly!!!!!

 

I missed in the assebly load options the custom folders where all the custom are uploaded. (Machine..etc...)

 

Great! Great Great!

Gianpaolo

17-Peridot
May 13, 2024

@GianpaoloGallo 

 

That's all correct. 

Do you have a system admin or someone that controls your NX installation and launch? In our case, I control the site-wide load_options.def for the company and the users have an option to have their own. These separate out via Site/Group/User settings on the NX side via environment variables. 

 

You can also make those edits before you open a file. They will apply in session. 

 

What I'd do if I were you is make my own load_options.def file and save it somewhere and then point to it with an environment variable so that's the one that NX uses every time. 

 

First, when you launch NX go to assembly load options and get the settings the way you want them. 

Dobi_0-1715613966248.png

 

I would change the LoadOptions line to - load_from_search_dirs so that it only looks at the folders you define in the upper section of the menu. 

Dobi_2-1715614313337.png

 

At the bottom of the window there will be some options to save this file. Do that and note the location. 

 

Next, create an environment variable UGII_LOAD_OPTIONS and set the value as the address of the load_option.def file you created. 

This can either be done in the ugii_env.dat or in your environment variables directly. 

Dobi_1-1715614078243.png

 

Relaunch NX. 

It should now use your custom load_options.def by default every time you open a file. 

 

The custom_dirs.dat is fine. Means your WGM is connected 🙂