Best Replacement for Grip?

[Jamziee]

Hi Guys,

We have just upgraded from NX2 to NX4. We have previously used a GRIP function for automating a plot function (written by another engineer).

We have had several problems in converting the GRIP routine to NX4. So, I'd like to look into writing a program using the methods supported by NX4.

So what are the methods I can use? So far, I have read in the forum references to Macros, Journals, C++, Visual Basic, .NET, etc. and I am a little confused as where to start and what the differences are.

I don't mind if the language is a little involved as I am willing to spend the time learning.

Many thanks,

Andy.




---------------------
(Using: UG NX4)
Design Engineer

 

[jackley]

What exactly are you automating in the plot function?

Just curious really.

Justin Ackley
Designer
jackley@gmail.com

 

[Jamziee]

Hi Justin,

It's actually a plot to file function that places a file on our system so that it can be viewed by our in house drawing viewer.

In NX4, we can't seem to get the grip routine to "Print to file", only to "Print to printer only" option (i.e. the default setting in File\Plot\Plot...).

If you have any suggestions, they would also be greatly received.

Many thanks,

Andy.

---------------------
(Using: UG NX4)
Design Engineer

 

[jackley]

There are several people on here that know GRIP quite well. Maybe once they read this thread, they'll offer up some opinions.

I just set up different profiles in the plot menu and click 'print to file'. Since NXplot has changed drastically since NX2.0.

Justin Ackley
Designer
jackley@gmail.com

 

[Xwheelguy]

Andy,

What's the file type that is being output and viewed in the viewer? You might be able to just set up a plotter/printer to output to file only and not have to worry about GRIP at all. I'm positive you can do this for a PostScript file, but I'm not sure about other print to file types.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[DavidTolsma]

To answer your original question regarding what language to use and the differences. I would not use Macro's because they are version dependent. NX3 introduced NX/Open which is the common API layer. All languages are equally and consistently covered when going through this common API. Journaling uses this common API. So if you can do what you need in Journaling and play back successful then you can take that journal file and add additional logic to the code. The language you choose doesn't matter, which ever language works on your platforms you need to support.

If you only have windows machines then .Net would be a good fit, VB.net or C# whichever language is more formiliar.

If you have a mixed Unix/Windows environment then maybe java

If you have some C++ libraries that you want to use then C++ is the right choice.

vb.net is the only language that you can playback in NX without compiling on the Windows Platform

-Dave
PLM Exchange

http://plmexchange.net

http://groups.google.com/group/NX_CAX/