cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Windchill Workgroup Manager - Siemens NX CAM

GianpaoloGallo
11-Garnet

Windchill Workgroup Manager - Siemens NX CAM

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

 

ACCEPTED SOLUTION

Accepted Solutions

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

View solution in original post

7 REPLIES 7

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... 

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

But!!!!! When I start NX with Wgm connected the assebly load options is overridden and it links directly only to the workspace....the additional path has to be uploaded manually.

 

I wonder if this could be done by setup.

 

Best regards

Gianpaolo

Ah, that's separate. That's an NX launch setting. 

 

There exists a load_options.def file where you define this. I suspect you have something like this (the top line specifically is the folder search paths). 

Dobi_0-1715358655722.png

You can save a different load_options.def file in your NX user defaults location (that's defined in the ugii_env.dat potentially, depending on how you manage your environment variables for NX) that will have your desired folders in that top spot along with the "fully load" setting. So when you launch NX, it'll launch with whatever you default load_options.def file you define. 

Something like this (in the ugii_env.dat): 

Dobi_1-1715358849901.png

 

Hi Dobi,

 

I know about the Load_options.def but inside of this doc there is not info about Windchill.

 

GianpaoloGallo_0-1715589126908.png

Once I login with Server manger ON - on line this option is changed and NX link the Workspace.

Then I manually have to add the second load path to fix it.

 

 

 

GianpaoloGallo_1-1715589332645.png

 

# custom_dirs.dat: Directories to search for Unigraphics customizations
#
# Copyright (c) 1999 Unigraphics Solutions, Incorporated
# Unpublished - All rights reserved
#
###############################################################################
#
#
# This file is used to specify directories which will be searched for
# menu files, toolbar files, dialog files or UDO libraries. The directories
# added here may or may not exist, to allow the same file to be used at
# multiple sites. When Unigraphics starts up, it will check each entry, if
# the directory does not exist, the line will be discarded as if it was a
# comment. Comments are allowed, and must start with a # in column one.
#
# Directories must be listed one per line, with nothing else on the line. The
# directory may include environment variables, by specifying $variable. If
# a $ is needed in a directory, it may be specified using $$, e.g.
# /users/my$$ would be the directory /users/my$. The file may be made to
# work on UNX or WNT, on WNT any / characters will be replaced by \.
#
# A #include construct is supported to include other files, to make it easier
# for individual users to customize their runtime environment. Finally the
# location of this file is controlled by the environment variable
# $UGII_CUSTOM_DIRECTORY_FILE which by default points to
# $UGII_DEFAULT_MENU_DIR/custom_dirs.dat. Customers with a number of
# customizations, or a number of third party products have two ways to set
# this up:
# 1. This is the preferred method. Create a file on a network drive
# that has lists all of the directories of the customizations. Then the
# environment variable UGII_CUSTOM_DIRECTORY_FILE can point to this shared
# file, so that all users will load the third party software. When a new
# software tool needs to be added in, the global shared file can be updated
# to give all users access to the new software.
#
# 2. Edit this file and add the directory to it. The problem with doing
# this is that different users will have local copies of the NX software,
# and so different files that need to be kept up-to-date.
#
# Customers should feel free to edit this file.
#
####################################################################
#
# Customer modifications can follow on here
#

C:\PTC\ROOT\WF_ROOT\.cadadapters\x86e_win64\ugnx1926

@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 🙂

 

 

 

Great!!! Many Thanks!

Announcements


Top Tags