NX5 drafting variables

Posted on May 27th, 2008 | 5025 commentshttp%3A%2F%2Fplmexchange.net%2Fnx5-drafting-variables%2FNX5+drafting+variables2008-05-27+11%3A31%3A25adminhttp%3A%2F%2Fplmexchange.net%2F%3Fp%3D502

<W@$SH_SHEET_NUMBER> – Sheet number of the current sheet

<W@$SH_NUMBER_OF_SHEETS> – Number of sheets in the current part

<W@$SH_SHEET_SCALE_NUMERATOR> – Numerator of the sheet scale

<W@$SH_SHEET_SCALE_DENOMINATOR> – Denominator of the sheet scale

<W@$SH_SHEET_SIZE> – Size of the current sheet

<W@$SH_SHEET_UNITS> – Units of the current sheet

<W@$SH_SHEET_PROJECTION_ANGLE> – Projection angle symbol of the current sheet

<W@$SH_MASTER_PART_NAME> – Master Model drawing sheet part name

<W@$SH_PART_NAME> – Sheet part name

Better Control the Data format database attribute sync from TcEng to NX

Posted on Mar 7th, 2008 | 5010 commentshttp%3A%2F%2Fplmexchange.net%2Fbetter-control-the-data-format-database-attribute-sync-from-tceng-to-nx%2FBetter+Control+the+Data+format+database+attribute+sync+from+TcEng+to+NX2008-03-07+22%3A58%3A42adminhttp%3A%2F%2Fplmexchange.net%2Fbetter-control-the-data-format-database-attribute-sync-from-tceng-to-nx%2F

Starting in Teamcenter Engineering 2005 SR1 MP3, they have added a new format string. In the “IMAN_BASE_DIR\lang\textserver\en” is a file for time. Add the following key:
<key id=”NXDefaultDateFormat”>%d-%b-%Y</key>  

Restart your Teamcenter Service and open your drawings now it will have the DDMMYYYY format. If you want other formats there are other variables to get different results.

Site Standards (Load Latest)

Posted on Feb 25th, 2008 | 4994 commentshttp%3A%2F%2Fplmexchange.net%2Fsite-standards-load-latest%2FSite+Standards+%28Load+Latest%292008-02-26+01%3A43%3A37adminhttp%3A%2F%2Fplmexchange.net%2Fsite-standards-load-latest%2F

Customer defaults has a site standards section under assemblies section.

You need to define your naming convention using regular expressions. In your case you have 6 digit part number with an ‘underscore’ two digit number.

An example Regular expression for your site standards would be: (each line represents each section in the site standards)
([0-9]{6})(|_[0-9]{2})
\1
\1(|_[0-9]{2})
\2

Set the rule to numeric.

Another example would be:
([dD]?[0-9]{2}[a-zA-Z]?[0-9]{5,7})(|([a-zA-Z]{1,2}))

which would be for parts in this type of series:
1234567
12345678
123456789
d1234567
d12345678
d123456789

1234567_a
12345678_a
123456789_a
d1234567_a
d12345678_a
d123456789_a

Set your load options to load latest (now available since you set your site standards).

2D Draw on the web and offline

Posted on Feb 7th, 2008 | 4980 commentshttp%3A%2F%2Fplmexchange.net%2F2d-draw-on-the-web-and-offline%2F2D+Draw+on+the+web+and+offline2008-02-07+14%3A02%3A40adminhttp%3A%2F%2Fplmexchange.net%2F2d-draw-on-the-web-and-offline%2F

First I’d like to say, I’m not a fan of AutoCad. Second I’d like to say I’m a fan of AutoDesk draw for the web. http://draw.labs.autodesk.com/ This allows you to draw in 2D on any of the standard web browsers (IE, Firefox, others). With out any downloads, installs etc. You can take this offline if you have Google Gears installed, which is a platform for taking web applications offline. You can save the files on their servers or your own. No signup just start drawing. Check it out.

NX/Manager

Posted on Jan 10th, 2008 | 4972 commentshttp%3A%2F%2Fplmexchange.net%2Fnxmanager%2FNX%2FManager2008-01-10+14%3A42%3A48adminhttp%3A%2F%2Fplmexchange.net%2Fnxmanager%2F

When you do a saveas from NX into Teamcenter Engineering, a Teamcenter variable comes into play. This is:

DATASET_saveas_pattern=${ItemID}/${RevisionID}

Which in Teamcenter 2005 (10) is stored in the database, found from Portal at: Edit -> Option… ->  Search (tab on bottom)

But what if your UGMASTER, UGPART, UGALTREP or other datasets have different naming conventions? Lets say you add a ‘Drawing’ text into the naming. The Save-As will fail. So to fix this you need to add DATASET specific saveas_pattern. This example is for UGPART datasets:

UGPART_saveas_pattern=${ItemID}-Drawing/${RevisionID}

Think of the DATASET_saveas_pattern as the global rules, and the specific dataset patterns as overrides.