please_dont_crash
Automotive
- Apr 21, 2020
- 25
Hi all,
Let me preface this by saying that I have almost no NX knowledge, so please don't be surprised if I'm asking for something obvious, or I don't even know basic NX terminology.
My goal is to have a script within NX that, when run, will go through an assembly, and export the (x,y,z) and (r,p,y) coordinates of specific parts of the assembly into a text file. The point of this script is to provide me with a quick way to get the coordinates of these parts, as they are currently changing a lot during development, and I need their coordinates for other uses. Getting these coordinates by hand is incredibly time-consuming.
The way I imagine this happening, is that I add a specially-named element to each of these bits of the assembly (a datum? A coordinate system?), and the script traverses the assembly tree looking for these specific elements, grabs the coordinates, and puts them in a file, hopefully with a column that identifies what each entry corresponds to.
What complicates matters is that these parts are not mated; they are currently free-floating and positioned by hand.
It's OK if the script has to be changed if one of these parts is deleted or another is added. In fact, I would expect that.
So what do you think? How would I go about this? What should I google and learn about?
EDIT:
Plan B is some way of making this (X,Y,Z,R,P,Y) information clearly visible for these specific parts somewhere in the NX interface. Something that can be easily selected, copied, and pasted somewhere else, without having to go through extra windows, click buttons, that sort of thing.
Thank you!
Let me preface this by saying that I have almost no NX knowledge, so please don't be surprised if I'm asking for something obvious, or I don't even know basic NX terminology.
My goal is to have a script within NX that, when run, will go through an assembly, and export the (x,y,z) and (r,p,y) coordinates of specific parts of the assembly into a text file. The point of this script is to provide me with a quick way to get the coordinates of these parts, as they are currently changing a lot during development, and I need their coordinates for other uses. Getting these coordinates by hand is incredibly time-consuming.
The way I imagine this happening, is that I add a specially-named element to each of these bits of the assembly (a datum? A coordinate system?), and the script traverses the assembly tree looking for these specific elements, grabs the coordinates, and puts them in a file, hopefully with a column that identifies what each entry corresponds to.
What complicates matters is that these parts are not mated; they are currently free-floating and positioned by hand.
It's OK if the script has to be changed if one of these parts is deleted or another is added. In fact, I would expect that.
So what do you think? How would I go about this? What should I google and learn about?
EDIT:
Plan B is some way of making this (X,Y,Z,R,P,Y) information clearly visible for these specific parts somewhere in the NX interface. Something that can be easily selected, copied, and pasted somewhere else, without having to go through extra windows, click buttons, that sort of thing.
Thank you!