Hello,
Last month, my company upgraded to TC 10.1.6 20160315, due to requirement to work with NX 11 from our customer.
Ever since the upgrade, we experienced few bugs, which we resolved most of them.
One serious bug which is not yet resolved, is the incorrect display of stylesheets for items...
Hello,
Recently we updated to NX 10.0.2 (it was 10.0.1 before), and now when we create new item in NX integration, we suddenly get a new "required" field called "partno". We also noticed that the item id is now referred as DB_PART_NO (which is not like it was before)
This field can be...
Have you tried using "Bridge" surface? it was really improved on the last few versions (I think on 8.5 or 9.0).
It is not as "stable" as through curves, or through curve mesh, but it's quite easy for use.
You can also try studio surface, which I see as a smart interpertation of through curve mesh.
I just checked - and couldn't find out which version is certified.
TC 10.1.4 20150421 64 bit
JRE 1.7.0_65 64 bit
NX 9.0.2.5 Rev K 09Sep15
NX 10.0.1.4 D4 27May15
Microsoft Excel 2010 version 14.0.7015.1000 32 bit
Jerry,
Thank you - it's quite good enough for now :)
Cowski,
I'm surprised it's not already in the standard symbols. Anyway we don't have direct access to Siemens so we need to do it through the local representative (complicated...)
Hi.
I've been looking for a way to make a "undefined corner symbol" like in ISO 13715
Example can be seen here:
http://www.en.technisches-zeichnen.net/technical-drawing/basics-02/edge-informatinos.php
Thank you in advance.
Hello,
When we open excel file from TC (by double-click on xlsx dataset), the computer freeze for long time, sometimes even needs restart.
It usually happens when there's a "unmanaged" excel process running, but sometimes also when there is no excel process at all.
The local integration...
There's no connection to the folder name. The error from "As saved" is due to the original location of the file in Daimler (we get the file from them...)
As for my local computer, this specific file is in D:\ , in the root directory.
Your "solution" may be relevant for a single file.
What if we...
Changing to As Saved issues the following error, shown on the picture attached:
Opening and saving to the folder, and then replacing component, issues another error, shown on another picture...
And the assembly navigator looks like this...
Hi.
We recently get NX files from Daimler.
For example, one delivery has the following files:
A1234.prt (assembly)
A1234_1.jt (geometry)
If we open the assembly on the Daimler Supplier Package, it creates a file called A1234_i_jt.prt, and it appears in the assembly navigator, but not on the...
Hi.
I'm not sure where is the right place for the question - here or in the NX forum...
We recently get NX files from Daimler.
For example, one delivery has the following files:
A1234.prt (assembly)
A1234_1.jt (geometry)
If we open the assembly on the Daimler Supplier Package, it creates a...
I checked it.
It is ALMOST what I wanted.
The only problem is that now the "integrated" NX is working on a different version than this one.
The dataset is still checked out on TC, and the file is on the work folder defined on TC options.
But I can still open the file from TC with the "open in...
That's exactly the question - How do I separate select the "base" components from the delta components?!?
I don't know which are the base and which are the delta.
And I have a few dozens of components.
The subcontractor is using different software.
I want to make it easier for him, so I want to make him a "base" file (multi-body is also OK) with the common components.
And in addition 3 different files for the "delta" of each configuration.
These are actually 3 different variants of the same...
We use GM PDL (Supplier toolkit) and Daimler's supplier package.
The problem is mainly with Daimler (I didn't try GM yet, but we work most of the time on the native NX, and on Daimler's package)
I tried using semicolon, and also tried to use comma. Both doesn't work.
The question is can I use a...
It is too complicated. Using the import and export assembly outside teamcenter is very complicated for most users.
In the CATIA integration it saves the files in the CATUII folder.
But on NX it works "online" and if the connection to TC server is lost then the file won't save.
Unfortunately the environment variable trick doesn't work with some configuration (we have some supplier packages that doesn't read the SPLM_LICENSE_SERVER correctly and issues error messages).
Is there any way to use it with license file control?
I need this for exporting the assembly to a subcontractor, and he can't use arrangements.
I want to make him 4 files. one file for common, and 3 files for "deltas".
Can you explain how to do this with arrangements?