Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Trail Files

shakman

New member
hi i m using pro e WF 2.0 M040 for 2 years, is there any guy who can help me in telling me about TRAIL files that proe generates during its sessions.


thanks in Advance
 
Well you asked a very good question, everything or every information is avaialble in the proe documentation you recieve with pro/engineer software.


The trail files are generated in commercial versions only, and can be read in the commercial versions only.


Trail files are generated for every instance that you use the pro/engineer software, they are design specific files that tells you everything you did. it is a sort of script files. with these you can design templates and customise them specific to your company and in config file you can tell software where to store them for troubleshooting purpose. i always store them in different folder that i have specified in config.pro.


you can have a look at the scripting of the files by opening them with text format and see the various changes, that follows your specific design routines in that special intance of the pro/engineer session, that how you controlled the design.


well i must say it is very good tool in case of accidental crash, to backup data, to customise the design and design variable.


to look at the file first create the part in proengineer and then quit. the specific trail file it created rename it to something else and try to play it in another session of proengineer, you will see the every step you followed to make that design. itis quite facinating sometimes.


here i could tell you only this info, if you want more then you will find this info in any good proenginner book or its documentation.


good luck.
 
Not true: I'm using the trail file to great power and effect on an educational version.





This is WF3 though.





I'm basically using it to update variables, after they are transmitted by email, a macro kicks in that saves the body of the email in the file directory and then runs a modified trail file to get the variables into the parameter table.





Trust me, educational versions have the trail files too!





-AS
 

Sponsor

Back
Top