You are not logged in.
Pages: 1
I use Vericut in conjunction with Pro/E and want to get feedback as to how to best use the two together.
First subject: I want to save a Vericut session for future use/playback. Since the interface uses the same name each time (cgtpro.stk, etc), is there a way to 'rename in session' the different components so they remain the same rather than getting clobbered the next time I call Vericut from inside Pro/E?
Thanks
John H. Durrant
ATK Launch Systems
Offline
I'm a Mastercam user but I think the interfaces are probably similar. The first thing I do after I start the interface is to save off the file under a different name. I usually add the letters VC after the original file name. Since the second file uses the same files (.usr, .tp ect) as the first, the second file gets updated with added tools or whatever. I will also add all my STL files for stock fixtures and design to the second file. The end result is: I will run the interface when necessary and after Vericut comes up, immediately go to recent files and call up my secondary file.
Hope this helps,
Creg
Offline
John,
To save the entire Vericut session, do Info>File Summary, select the Copy All Files icon (two floppy disks), browse and create a target folder. All files related (toolpath, parts, machine, etc) are copied to a single location. This is also the best way to upload a file to CGTech if you have a problem.
For Pro/E users, here's a trick that I discovered:
If you set your Machine Name in the Workcell exactly the same as the name of your Vericut machine/control files and place a copy of the Vericut .mch and .ctl file in the folder in which your ProE files are created (usually the START IN folder if you use Intralink) then when you run an NC Check the Vericut machine is automatically loaded. For example, if your Vericut machine is called Okuma.mch and the control Okuma.ctl, set the Machine Name in ProE to OKUMA and place copies of the Vericut files in the folder in which all the *.stk, *.fxt, etc files are created. Vericut will launch and load the machine and control at the same time, so you have just to select Play and you are running.
Also for ProE users, there is an undocumented enhancement in Wildfire 2.0 M050 - the GAUGE_Z_LENGTH parameter is automatically incorporated into the Gage Offset field of the Vericut Tool Manager... what a help!
Regards
Peter Brown
Jarvis Products Corp
Offline
Pages: 1