Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
GPOST PDMLink Windchill Compatibility Integration
GPOST is packaged with Creo\NC but is not fully compatible with PDMLink requiring that the post processor files (3 files per post) reside at a local hard drive or network location.
I would like the ability to configuration manage these files.
I should have the ability to point at a wtpub location via my config.pro and the necessary files should be retrieved to workspace when/if necessary – similar to drawing formats, startparts, etc.
The workcell definition allows for a post processor ID to be defined – this could define the relationship/reference to a specific post processor which could drive retrieval of all associated files.
All post processor related activities should function normally, as they do when config.pro is pointing to a local/network location, including but not limited to the 3 following entry points:
SPR1450930 still applies:
Post Processor files should be made Wildfire workspace and Windchill aware. Currently post processing files need to be stored in local file location even though config option gpostpp_dir can be set to wtpub location. Effects MPM Process.
CS11101 – is not properly defined, does not address the need to specify a wtpub location, only mentions workspace which does not solve the problem.
I agree with Bryant, this is a setting that would make make managing post preccessor files a lot easier. Windchill can manage many different types of documents it is ironic that it cannot handle posts.
Note: If the Post Processor files do not exist in the Windchill Commonspace or Workspace, they can be imported into the Workspace as EPM Documents via Config allow_import_file_extension=<file_extension>
zyh - thank you but I have testing this hidden config option and found the following:
Summary:
Problem:
Possible improvements (either\or not both, I would prefer #1):