cancel
Showing results for 
Search instead for 
Did you mean: 

Preferences

Pioneer
Pioneer

If you use multiple versions of NX is there a way to reference one location to use the same tool data, material data, shop docs etc instead of them residing in folders under the version install

Mike

NX 11.0.2.7
Win 7
4 REPLIES

Re: Preferences

Genius
Genius

This would be possible, but adds a lot of complexity.

It depends on the level of change (NX9, NX10 or just mainenance packs on the same level) that has been made to these files. For example, there have been no changes to these files from NX10.0.1 to NX10.0.2.

If e.g. a certain tool type got a new parameter in the new release, your tool export would not work. 

 

You really would have to know everything about the changes in the TCL, DEF and DAT files in the MACH/library/... folders.

 

I would expect someone who tries this would fail doing so.

 

Maybe using a external tool database could help in this case.

Best wishes,
Joachim

In production NX 11.0.1.11 D3

Re: Preferences

Esteemed Contributor
Esteemed Contributor

On other option is what someone else has done (IIRC):

They maintain their data in Excel, then have scripts to export to the tool files.

You could then write different scripts for each NX version you need to support

 

Yet another option:

I think (at least sometimes) there are scripts to upgrade existing libraries to new NX version formats.  If you maintain the "oldest" format, then just re-run the scripts to migrate the data upwards, that might work (as long as you don't need to specify anything only found in the newer version)

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: Preferences


Mike_R wrote:

If you use multiple versions of NX is there a way to reference one location to use the same tool data, material data, shop docs etc instead of them residing in folders under the version install


If you do any customization, the first thing I would mention is that you should not be using the files in the version install - you should make your own copy of the resource folder, and madify those files.

 

If there are no differences in the formats, you can have multiple releases point to the same files. For example, the tables for part material, tool material, and cut methods are very stable.

 

However, for something like the tool library, we make format changes almost every main release, due to new tool types and tool parameters. It is not only the .dat files you need to look at - the tcl and def files are modified to match the contents of the dat file. As @JSchraitle said, this is not likely to be easy, if possible.

 

For shop docs, you would need to test. We made several fixes in the releases after the excel templates were released, in both the tcl and core code. 

 

Mark Rief
Retired Siemens

Re: Preferences

Genius
Genius

Hello,

 

We work in the way @MarkRief say's we have a copy of the resource folder and any other folder we want to have custom information in and point environment variables to that location. 

 

This works well but as others say keeping on top of any changes that come through is a pain, also if like we have done you leave it to long and there have been too many changes made to be able to use the auto update scripts! you may have to go through the whole mapping your own tools in the new .tcl and .def files!

 

Hope this is of some help?

Regards

Dave
NX10.0.3MP13
NX11.0.1
Production
TC10
Vericut 7.3,7.4.1,8.0.2

Learn online





Solution Information