Env. variables and Patterns 3

[ugusernx3]

I am a fairly new user of NX3. I have been to the Practical App class and the Drafting App class within the last few weeks, and am attempting to create patterns for our company.

I have all the part files for the Titleblock sizes we use, and I have one (11x17) saved as a pattern. I can even import this pattern as a pattern into a drawing.

I am trying to figure out how to specify the Pattern Directory I have created, but don't know where to find the Environment Variables. I read about 10 other threads on the same "Disappearing patterns" problem, but do not know where to specify this variable. If someone can lead me down the correct path, I'd appreciate it very much!!

Thank you!
Branden
TQS Inc.
Roy, Utah

 

[Dave K]

In the ugii_env.dat file:

# UGII_PATDIR is used to locate pattern files when they are retrieved.
UGII_PATDIR=

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

 

[ewh]

First, save a copy of the ugii_env file for backup. Open the ugii_env.dat, Edit -> Find and type in "pattern". This will locate the line of text for you. You then define the path as Gunman suggests. You will have to remove the "#" before "UGII_PATDIR=" to activate it (not the "# UGII_PATDIR is used to locate pattern files when they are retrieved." comment line, but the next one). The correct path is up to you, where ever you keep your pattern files.

 

[ugusernx3]

Well, found the file, found the line, input my map to the file, but still no pattern. I get an insertion point indicator, and a solid outline, but no pattern?

Any ideas why?

Thanks folks for your reply's so far, hopefully I can get this figgerd out soon!

Branden

 

[ewh]

As an examply, here is how my path is defined:

# UGII_PATDIR is used to locate pattern files when they are retrieved.
UGII_PATDIR=\\boe-files1\UG_FMT\patterns\

 

[ugusernx3]

Ok, I am ok with the path, I must have something done incorrectly with the actual pattern.

Thank you so much for your help!
Have a great day, I'm going to get back to my trial and error!!!

Branden

 

[Shadowspawn]

ugusernx3,

Art thou sure you saved WITH pattern data turned on? <File> <Options> <Save Options> <Save Pattern Data...>

Regards,
SS
CAD should pay for itself, shouldn't it?

 

[ugusernx3]

That option (pattern data only) refers to the drawing the pattern is brought into correct? and once I change it, it'll always stay that way until I change it back?

Status thus far:
1. Changed the path for pattern dir in the ugii_env.dat file
2. Created a pattern in a pattern directory (to keep them separate)
3. Checked the option to Save Pattern Data Only

Ok, I'm stuck now.

 

[ewh]

"pattern data only" should be checked when saving the actual pattern file, not the file that the pattern is brought into.

 

[Shadowspawn]

ugusernx3,
EWH is correct, and I should have explained it a little clearer. Thanks EWH for clearing this up btw...

Anyway, let us know if your still having problems

Regards,
SS
CAD should pay for itself, shouldn't it?

 

[DavidTolsma]

NX has some prebuilt formats in the pallet area. Drag these onto the drawing and it will place the geometry in there. This is an alternative to using patterns. Since patterns can't be exported out to customers nicely without them getting your pattern also and setting the variables. Otherwise they will only see the views with no pattern information. The work around for this is to explode the pattern, but then what is the point to having a pattern.

Patterns are similar to an assembly. If you change the pattern the files that point to the patterns will update when loaded. Exploding this breaks this connection.

PLM Exchange

http://plmexchange.net

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

 

[ewh]

plmexchange is correct. To get around this, we do not send drawing files to our customers, but send cgm's along with a parasolid of the part(s) instead.

 

[DavidTolsma]

I would suggest using JT files instead of parasolids. I understand your customers may not be using JT yet but the benefits outweigh the change. Another way to save time on your end is to use WAVE to make parametric link to your original part or assembly and only send that file to the customer. They will have the geometry but not have the original file. So they can't steal your model logic. Also when you want to give them an update, just open the WAVE file, update features and save and resend. This also has the downstream benefit of not breaking assemblies as much because the ID will remain the same. Even though I would use Datum planes and axis to mate components, but that is a different topic.

-Dave
PLM Exchange

http://plmexchange.net

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

 

[Dave K]

If you "expand pattern" before sending the file to a vendor, it will include the format pattern. I would do a "save as", and rename the file, keeping your original with the linked pattern. Then Format-Pattern-Expand Pattern on the new file.

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

 

[ewh]

We use parasolid because some of our customers are "in house" and use SolidWorks.

 

[DavidTolsma]

Can SolidWorks open a NX Part file?


-Dave
PLM Exchange

http://plmexchange.net

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

 

[ewh]

It is supposed to be able to, but it fails more often than not.

 

[ewh]

And worse, since we do not yet have a capable PDM system in place, SW places copies of the parts it manages to open in the same location as the original part. This gets to be a real headache when someone uses it to open a large assembly. Parasolids seem to be a quick and easy solution.