Automatic Layer Set-up

[Jamziee]

Hi Guys,

We are upgrading to NX4 and was wondering if there is a way (other than using templates) to load a layer configuration into a part file when first created (similar to customer defaults in NX4).

We have template files with all the layers set-up, but getting some engineers into the practise of using them is proving a little difficult. If we could automatically load them in when a new file created, I think we could change their working practises.

Many thanks,

Andy.

---------------------
(Using: UG NX2)
Design Draughtsman
Biomet Ltd

http://www.biomet.co.uk

 

[Dave K]

I'm not sure exactly how it was done, but at a previous employer they had it setup like this: When you select File-New, a window popped up, asking you which template you wanted, after selecting one, you could then give it a name.

Not much help, but I do know its possible.

-Dave
Everything should be designed as simple as possible, but not simpler.

 

[Jamziee]

Thanks Dave,

This could prove useful. If anyone out there knows how to create the suggestion above (or anything similar), please let me know.

Many thanks in advance,

Andy.


---------------------
(Using: UG NX4)
Design Engineer

 

[cowski]

One way to do this is with a grip program that uses a "user exit". You can specify certain commands in UG that will automatically run a grip program that you write. "New", "Save As...", "open spreadsheet", "reposition component" are a few examples of user exits.

There is probably similar functionality in the new journaling available in NX3 and above.

 

[csbk]

If you go the program route and you are not in TCE, I would recommend not using a Save As template but a program that creates the data or import from template so as to take advantage of the UID protection in the file and the objects start in the current NX Kernel and the template would not leave refilled history in every part.

Or am I missing something UGS members?

 

[JohnRBaker]

If you're talking about being able to 'transfer' the layer setup, meaning the various layer categories and which layers are assigned to which category, you can do that by creating an empty part file that has all of those categories defined.

Now open up the existing file that you want to inherit these categories, and just do a File/Import/Part... using the previous 'empty' part file for the import. Your existing part will now inherit all of the predefined categories from the your 'empty' part.

Also, you may notice that views can also be transfered in this manner so if you've got some special views you want to move to an existing file you can do that as well.


John R. Baker, P.E.
Product "Evangelist"
NX Product Line
UGS Corp
Cypress, CA

http://www.ugs.com

 

[ewh]

John's method is how we fix files that were created without using our seed parts. Only problem is that what layers the differing geometries are on don't usually agree with the catagory names. It works well for adding correct attributes though.

 

[JohnRBaker]

You're correct, this will no FORCE geometry to move from one layer to another, but at least you can get all your layer 'names/categories' assigned per your standards.


John R. Baker, P.E.
Product "Evangelist"
NX Product Line
UGS Corp
Cypress, CA

http://www.ugs.com

 

[DavidTolsma]

Create a journal file then compile it with a user exit of new part. Now when you create a new file the "compiled" journal file will run and create your layers, categories, etc.. The benefit is you don't have to be a programmer to do this. Just know how to compile.

Example on how to compile a journal file at:

http://www.plmexchange.net/1205200591

PLM Exchange

http://plmexchange.net

http://groups-beta.google.com/group/NX_CAX/