Switching from GRIP to SNAP or NX/Open

Forums: 

It looks like SNAP is (in part, anyway) meant to be a replacement for GRIP. Has anyone tried switching from GRIP to SNAP (or to SNAP + NX/Open)? If so, then ...
(1) How long did it take you to learn SNAP?
(2) What topics/areas were problematic?
(3) What areas/topics were pleasant?
(4) Have you tried converting any old GRIP programs, and, if so, how did it go?

Have you found any conclusive information since? I am interested in learning about this as well.

DHuskic
Nx 9 VB

> Have you found any conclusive information

Not here. But I have done some analysis of the differences, so I have my own opinions about how it would go. One big roadblock is that SNAP has no drafting or CAM functions, so you have to use the NX/Open functions, instead. Mixing SNAP calls and NX/Open calls is easy, but the NX/Open functions tend to be complicated. I haven't looked hard enough to find out just how complicated.

Another problem is that you need to use standard .NET functions to replace some GRIP functions (reading and writing files, for example). I suspect that people often won't realise this, so they'll waste time looking through the SNAP and NX/Open docs for functions that don't exist.

The big advantages of the switch are fairly obvious:
* Generation of programs by recording journals
* Creating modern block-based NX-style user interfaces
* Creation of newer features, like Datum Planes, Thicken, TrimBody, etc.
* A modern development environment, like Microsoft Visual Studio
* Easy access to standard programming tools, like the .NET libraries or Windows forms
* You gain skills that are useful elsewhere (outside of the NX world)

A migration guide appeared with NX10 that tells you how to move from GRIP to SNAP or NX/Open. It tells you a bit about how to use NX/Open CAM and drafting functions, and also how to use .NET functions for file handling. Don't know if it's enough, though. My GRIP programs were all very simple, so migrating them was easy.

There are several functions that are almost one-to-one correlations from GRIP to SNAP, e.g, line between two points. Problem is .. SNAP doesn't yet have a anything close to a sufficient number of functions..to do most automation projects you might have in mind. With SNAP.. you'll soon be forced to write additional functions in NX OPEN.. but if you know how to drive NX Open.. then why bother with SNAP. If you need some help converting GRIP to NX open, maybe give me a shout.

yukonstan

> if you know how to drive NX Open.. then why bother with SNAP

Because the SNAP functions are simpler and better documented. If you wanted to make an Extrude, would you rather call the NX/Open function or the SNAP function??

My advice is to mix. Use SNAP functions when they're available, and only resort to NX/Open functions when necessary. The mixing adds a bit of complexity, but still far easier than using NX/Open for everything.