Hello again Creo fans!
I've been encountering a lot of migration type work requests lately and there always seems to be issues with the data that is trying to be put into Windchill. I have taken it upon myself to start making some high level scripts to get you going in regards to cleaning up your data before you get it into Windchill. The first of (many?) scripts to come deals with regeneration errors and locating missing components. Check it out and stay tuned for more.
Welcome back everybody!
It has been quite some time since I last posted some Creo 4.0 with PowerShell magic and I had the craving to invest more time into it. Today, I would like to introduce you to a PowerShell function that can be used to automate the exporting of family table instances to stand-alone files.
I have seen many customers faced with this issue when they first start using Windchill. They realize that they can search parameter values in Windchill and they either have never used them or they have but have not designated them. Usually, they check everything into their new system and tell everyone to update parameters as they modify files. We all know that will take forever and can be very stressful.
For Part 3, I am going to show you how to automate adding, updating, and designating parameters in your Creo files. I promise it will be faster than your mapkeys.
For part 2, I am going to show you how to automate exporting Creo files to some of the typical third party formats such as PDF, DXF, and STP.
Welcome Creo users/hackers!
There doesn't seem to be much out there when it comes to using PowerShell with Creo. I will shed some light on this topic and attempt to explain each line so that you can finally start automating Creo related tasks all on your own.
Part 1 of a multi-part series deals with the basics. You will learn how to install the appropriate toolkit, configure it to work, and do some basic tasks in Creo like opening a file.
PLM engineer while "on the clock", programmer, designer, dreamer all other times.