Yes, but i would stay away from GRIP as an automation tool.
GRIP has not been enhanced, except for plotting at NX3, since about V11! It is easy to use and can do simple things, but the real automation tool in NX is now journals and UG/Open API. There are still a few things that can only be done in GRIP, but I would expect those routines to be in the other tool boxes, soon.
"Wildfires are dangerous, hard to control, and economically catastrophic."
OPEN API, KNOWLEDGE FUSION
Hi I AM AT THE BEGINER LEVEL FOR UNIGRAPHICS KNOWLEDGE FUSION AND OPEN API AND I NEED SOME HELP FOR HEAD START SO CAN ANY ONE PLEASE MAKE SOME FAVOUR.
There's not a lot of documentation outside of what is provided with the product. Example of programs are always helpful. you would be looking for .GRS file types for grip, some may still be shipped with the product or in a zip file.
I don't know that grip would be my programming tool of choice to use with NX these days as it hasn't been kept up to date with changes over several past versions. The development was stopped prior to NX, and while it still works for many older and unchanged functions quite a few new parts of the system have no grip functionality. You might do better to look into some of the other NX Open programming tools based on C or visual basic programming languages.
Thanks Hudson,
I have another question,
We had a guy in our Designs for couple of weeks,he made some
.grx files for some special functions,how we make.grx files?
I have some .grs files,can I make them in to .grx? if so
could you please explain me.
A .grs file is a GRIP source file while a .grx is the executable. If you have the GRIP development license you can use what we call the GRADE utility, GRADE stands for GRIP Advanced Development Environment (however I would take the term 'Advanced' with a grain of salt as this utility was developed sometime around the mid- to late-80's and it hasn't really changed much in the passing years). You can access this tool by going to the Windows Start menu and going where NX appears on the list and navigate over to NX Tools -> NX Open Grip and this will launch GRADE which runs in a Windows command prompt window and follows the normal Windows command line rules and format. Note that from here you can navigate to folder(s) where your GRIP files are located, open the source file to edit it (I use Notepad but you can pick most any text editor). Once edited you then compile it and if it compiles with no errors, an intermediate file is created, a .gri file. Now you can create your programs using sub-routines also, each of which complies to a .gri file. Then you take the top level .gri and link it which produces the final GRIP executable, the .grx file.
Anyway, all of this is covered in the User Documentation, and once you get used it it, it all works pretty good.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
John answered it already, there is an executable license and a separate development license for GRIP which includes a linker and a compiler. The source that you write is a text file .GRS, the linker outputs .GRI files and the compiler makes the .GRX executables.
The same with different extensions is true of some of the other NX Open programming tools where in general you need two licenses to develop but only one of those if all you need to do is run the executable.
The exception to that rule is journal files which can be recorded from keystrokes, but also extended with visual basic programming to produce customizations that don't require any extra licenses. Naturally the scope may be reduced as compared with the C based stuff but at this point it is not within the scope of my knowledge to say what how and where they differ in capacity.
Hey I'd like some of the programming whizzes who occasionally posy here to follow up on this. People regularly post asking about Grip, and while John and myself both know and can help a bit with it, we have to recommend that for fresh starters you might as well learn one of the other languages. In fact I'm thinking of looking into it myself. But which is best. Who can advise me as to whether the Journaling cum VB programming tool is capable of handling what functions?
Actually, we are phasing out the need for special licenses to execute an existing program developed using NX Open tools. Now that does not mean that you won't still have to have licenses to use a program, but it will be the regular licenses that would have been needed if you were performing those same NX tasks interactively. For example, if you have an NX Open program that creates a sold model, while it's executing, when the calls are made that create the geometry, a regular modeling license will be required. This will be true for executing of any commands that would have required an applications license if done interactively.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
Slight correction to Hudson's last post: The compiler takes the .GRS, source code text file, and outputs an intermediate file, .GRI, which is read by the linker, sometimes with multiple .GRI files, to produce the executable file, .GRX.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Thanks for the correction I didn't even notice that I had the compiler and the linker steps in the wrong order. It tends to be all a bit memory lane for me these days I'm afraid. Looks like we're all moving onto bigger and better things since the future of programming for NX appears to be getting cheaper to not buy the extra licenses.
