PTC Creo GRANITE Interoperability Kernel
Copyright © 2016 PTC Inc.
Introducing PTC Creo Granite gPlugs for improved interoperability
- How to Use gPlugs with PTC Creo Parametric
- How to Use gPlugs with Other PTC Creo Granite Based Applications
- Download the Available gPlugs
- gPlug Developer Notes
The gPlug is a simple plug-in (.dll) supplied by the Granite licensed software vendor of an application that can be used to create CAD models. The gPlug facilitates model-based communication between heterogeneous PTC Creo Granite applications. gPlugs are useful in any CAD environment and allow diverse applications to recognize other CAD files in their native format and with associative benefits. PTC Creo Granite eliminates the need to translate to or from neutral files and manage those neutral files as well, by directing the target application to the location of the geometry, topology and relevant metadata in a model file.
If PTC Creo Granite kernel is used to author or store the model CAD data, then the data is streamed directly to the target application. If the model is not stored as PTC Creo Granite data, then the non-native gPlug will convert the data during runtime. PTC Creo Granite reduces the time, energy and data required to move models between the various applications in any product development process.
The approaches described in the previous paragraph reference two different types of gPlugs namely, the native gPlug and the non-native gPlug. Native gPlugs can open files that already have embedded Granite data and always consist of a single .dll file. Non-native gPlugs can open files that contain other proprietary model definition. Non-native gPlugs often are composed of more than one .dll and are much larger in size than the native gPlugs. The following table provides some details on the available gPlugs:
|Raindrop Geomagic||Native gPlug|
|Alias (.wire)||Non-native gPlug|
See the readme.txt file included in the gPlug package for the support version and other details.
How to Use gPlugs with PTC Creo Parametric
Both PTC Creo Parametric and PTC Creo Elements/Pro 5.0 support gPlugs.
Granite applications have their own ways of designating gPlugs to open the supported files. Use the configuration option pro_gplug_dir to specify the directory or folder where the gPlugs will be available for use by PTC Creo Parametric and PTC Creo Elements/Pro 5.0. You can add a maximum of two gPlugs in the gPlug folder. The gPlugs are interchangeable as long as the user starts a new PTC Creo Parametric session after changing the gPlugs in that directory.
To summarize, the key steps to use gPlugs with PTC Creo Parametric are:
- Download the desired gPlugs. See the section on Download the Available gPlugs for more details.
- Install them with other required files and libraries (for non-native gPlugs) to a folder (directory) on the local machine or supporting network.
- Edit the PTC Creo Parametric Configuration Options.
- Add or set the configuration option pro_gplug_dir to the name of folder using the full path to the desired gPlugs.
- Review the gPlug readme files and make the necessary changes. For example, modify the path variable for the Alias gPlug.
- Keep GRANITE dlls of specified version (if required- e.g. for Alias gPlug) in path.
- Start PTC Creo Parametric.
- Click File⇒Open to view the Granite Application File listing inclusive of the gPlug interoperability.
What should you do if the file types from the gPlug(s) do not appear in the File⇒Open list?
- Check that the configuration option pro_gplug_dir includes the correct location of the gPlug
- Make sure you start PTC Creo Parametric session after setting or changing the configuration option
- Check that the gPlug folder has no more than two gPlug .dlls
What should you do if you cannot open a specific file?
- Check that the file is of a version supported by the gPlug
- Check that the required changes by certain gPlugs have been made
If you have any questions about using gPlugs with PTC Creo Parametric please log a call online by selecting Granite as the Product, or contact Granite Technical Support.
How to Use gPlugs with Other PTC Creo Granite Based Applications
PTC Creo Granite applications can have their own ways of hosting gPlugs to open the supported files, yet they must follow a set of protocols when hosting gPlugs. The only substantial variation is how and where each application looks for the gPlugs. Please note that when using non-native gPlugs, one must make sure that the hosting application uses Granite .dlls that are compatible with those required by the gPlugs. Refer to the readme.txt files that are available with the gPlugs.
To open the supported files using gPlugs:
- Download the desired gPlugs
- Install them together with other required files and libraries to a place as specified by the hosting application
- Run the required setup if any as required by the gPlugs
- Start the hosting application and look for supported files
For technical support, please contact the company that designs and manufactures the hosting software application.
Download the Available gPlugs
- Alias gPlug for reading .wire files up to Alias 2014 (Built on GRANITE 8.0) — can be used only with PTC Creo Parametric 2.0 only.
Windows 32-bit (zip, 11.8MB)
Windows 64-bit (zip, 14.2MB)
- Alias gPlug for reading .wire files up to Alias 2015 (Built on GRANITE 8.0) — can be used only with PTC Creo Parametric 2.0 and PTC Creo Parametric 3.0
Windows 64-bit (zip, 14.1MB)
- Alias gPlug for reading .wire files up to Alias 2016 (Built on GRANITE 9.0) - can be used only with PTC Creo Parametric 3.0 (M080 or earlier) and GRANITE 9.0 (M080 or earlier) only.
Windows 64-bit (zip, 19.1MB)
- Alias gPlug for reading .wire files up to Alias 2017 (Built on GRANITE 9.0) - can be used only with PTC Creo Parametric 3.0 (M100 or later) and GRANITE 9.0 (M100 or later) only.
Windows 64-bit (zip, 20.2MB)
gPlug Developer Notes
All PTC Creo Granite based applications can leverage multiple gPlugs using the PTC Creo Granite SuperPlug mechanism. Please contact Granite Technical Support to obtain an example implementation in C++ using the SuperPlug.