Cancel
Showing results for 
Search instead for 
Did you mean: 

NXcustom for 11 questions

Gears Phenom Gears Phenom
Gears Phenom

We are running 4-tier Teamcenter.  First in the startup dos window I get a message about NTIER_ARG.  Should I be concerned?

DosWindow.jpg

 

Second, I have our custom File new templates working, except I am still getting one OOTB manufacturing template.  Where is this coming from?  It's not in ...NX110library\Templates\startup

 

Manuf_Tab.jpg

-Dave
NX 11 | Teamcenter 11 | Windows 8.1
7 REPLIES

Re: NXcustom for 11 questions

Gears Phenom Gears Phenom
Gears Phenom

From @GerritKoelewijn 's readme:

The following line in NX110custom\NX110library\custom_dirs.dat points to the Templates\startup folder.

$NX_CUSTOM_LIB\Templates

In this case you only need to place your custom pax files there. All other default Pax fiiles are
read from several OOTB ${UGII_BASE_DIR}\xxxx\Templates folders.

What if I don't want any other OOTB template files loaded?  do we have to remove them from every install of NX11?

-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: NXcustom for 11 questions

In your custom folder, the contents of your pax file should be merged with the OOTB pax file.

If a pax file with the OOTB name is found in your custom folder, it should REPLACE the OOTB.

Try placing a pax file with no entries (almost empty) named ugs_manufacturing_templates.pax (native) or nxdm_ugs_manufacturing_templates.pax (TC) in your custom folder along with your pax files.

Mark Rief
Retired Siemens

Re: NXcustom for 11 questions

Siemens Legend Siemens Legend
Siemens Legend

Hello Dave,

 

At this moment i cannot say if the missing NTIER_ARG is an issue.

I would need log files to see that.
If your Managed session is running without problems it should be fine.

 

Regarding your templates.

You can still use the mechanism where the Templates folder is explicitely defined.

That is the alternate (less preferred) option. You can find how to set that in the readme.

When using the method you have now, you should not start deleting files from the installation (it is not done to edit the install Smiley Happy )

As Mark already states, you can also make copies from the OOTB manufacturing Pax file and remove all the entires from there, and put that in the startup folder. When done correectly you will see that the Manufacturing tab will dissapear.

 

Regards,

Gerrit Koelewijn

Re: NXcustom for 11 questions

Gears Phenom Gears Phenom
Gears Phenom

OK, I'll ignore the NTIER_ARG for now.

 

As for the templates, since we have to CAM template tabs, one for each facility, I renamed one to the OOTB name, and all is well!!

 

Thanks!!

-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: NXcustom for 11 questions

Siemens Creator Siemens Creator
Siemens Creator

I get the same NTIER_ARG error , i know where this env is set but havnt run down the problem yet

You can control how the callout values in the NX Parts List are synchronized with the Teamcenter database.


Synchronize Callouts

By default, the NX callout values are synchronized with the Structure Manager Find No. (previously called sequence numbers). You can change this by specifying a value for the Callout Management customer default (see Teamcenter Integration Customer Defaults for additional information). The value that you specify is the title of an NX attribute.

This attribute title must be one that is synchronized with Teamcenter (i.e., with a note type defined in the Teamcenter database whose type matches the title). If there is no note type defined that matches the title, then an error message displays the first time Teamcenter Integration needs to use the value of this default.

The attribute specified by your default never actually exists in the NX data structure. When you create an attribute with that title, the setting of the attribute is intercepted. Instead of the usual action, the attribute CALLOUT is created or edited, and you enter its value. The corresponding note type in the Teamcenter structure is synchronized with the attribute titled CALLOUT. This is because NX requires the attribute CALLOUT to be present for use with callouts on drawings.

If you have specified an attribute other than DB_SEQUENCE_NO to be the callout attribute, then the Find No. in Structure Manager and the attribute DB_SEQUENCE_NO on NX components is synchronized. This means that when you load an assembly and the structure is updated from Teamcenter, attributes with this title appear on components and can be used in the parts list.


Note

The DB_SEQUENCE_NO attribute is entered in the Callout: Attribute Title field on the Teamcenter Integration for NX→User Attributes, All tab in the Customer Defaults dialog.


The figure below shows the mapping, by illustrating two drawings of the same assembly together with the corresponding BOM in Teamcenter. In Case 1, the callouts have been synchronized with the Find Nos. in Structure Manager. In Case 2, the callouts have been synchronized with the note DRAW_No in Structure Manager.

Be aware that in each case the attribute title CALLOUT corresponds to the required value in Structure Manager: in the first case with the Find No. field, and in the second case with the DRAW_NO note type.

Case 1:





NX

Teamcenter Structure Manager



CALLOUT

Structure Manager Find No.


Callout Management

DB_SEQUENCE_NO


Case 2:





NX

Teamcenter Structure Manager



CALLOUT

DRAW_NO


Callout Management

DRAW_NO


DB_SEQUENCE_NO

Structure Manager Find No.


Also be aware that in each case the attribute not used for the callout is held separately and its value corresponds to the appropriate Structure Manager value (DRAW_NO in the second case with note type DRAW_NO, and DB_SEQUENCE_NO in the first case with the Find No.).

Re: NXcustom for 11 questions

Siemens Legend Siemens Legend
Siemens Legend

I located the issue for the missing NTIER_ARG.

This variable is only set in the script that is run from the Rich Client.

You can indeed ignore the error.

To get rid of the message, you just add:

     set NTIER_ARG=4-tier

to the "Tc_NX110Manager.bat"

 

Regards,

Gerrit Koelewijn

Re: NXcustom for 11 questions

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

If you are running a 2-tier session, then the setting is wrong.

One needs to set this to the correct value.

In addition this is never set for 2-tier sessions.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide