open draft native master model
open draft native master model
(OP)
Best wishes.
I'm working with nx10 native. My drawings are now in the same file as the model (stand alone).
I'd like to work with de reference drafts. The problem with this is the ease of copying projects (all file in the same dir).
Is it possible when working with reference drafts to copy them along with models? (for a new project….)
Is there a workaround available to open an reference draft when working in the model?
Kind regards,
Lars





RE: open draft native master model
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: open draft native master model
In SE a macro was available for opening draft file while in the model.
The thing the macro did was searching the file in the same dir the model is saved and opened the drawing.
Model and draft have the same name.
I'm aming in the same direction for a solution to open a draft file of a model?
Is this feasible ?
RE: open draft native master model
www.nxjournaling.com
RE: open draft native master model
grip or NX open ?
RE: open draft native master model
GRIP is a discontinued programming language, it was terminated way back. No further development.
But, it is the easiest language to learn if you have a hint of programming knowledge. ( You will need a special NX license to compile!)
The modern replacement can be said to be "NX Open".
NX open programs can initiate/start as a "Journal" which is equivalent to a Macro, - You record interactively the clicks that you want the journal to repeat. Then the journal can played as is, or developed further into a "full program".
The resulting Journal file can be , Preferences- User Interface- tools- Journal, ".vb" or C#/C++/Java/Python.
Regards,
Tomas
RE: open draft native master model
I have to disagree with the above statement.
In GRIP you have to use jump statements to do looping or branching. The liberal use of jump statements can lead to difficult to read/maintain "spaghetti" code. GRIP does not let you create your own functions within your code; you can create subprograms which do much the same thing, but these have to be coded and compiled in their own files then linked to your main program. GRIP keywords are limited to 6 (or was it 8?) characters long making for some convoluted, difficult to remember command names.
For the task at hand, finding the drawing file and opening it, the plain vanilla journaling tools will be more than sufficient. Most of the work will be looking through files and folders, which can easily be accomplished with the functions contained in the .net framework (assuming you are running on Windows).
If you are going to start writing more complicated programs for NX, I'd suggest you start with SNAP (if you have a license). SNAP streamlines portions of the NXOpen API, allowing for code that can be easier to write and maintain.
www.nxjournaling.com