Raj,
Everything looks okay, except, I think your step 4 proe command should actually point to the batch file that launches Proe...
C:\ptc\proe2001\bin\proe2001.bat
That may be the whole problem. If that doesn't work, you may just have to use brute force and open each instance...
I hope I...
I tested it without saving out each "instance.prt" file and it worked. It output 3 *.igs files and I then imported one .igs to validate it was successful.
We typically open our family table instances without initially opening the generic and we've never saved them out as instance .prt files...
Raj,
I believe the "Pro/e command" runs proe in the backround and should always point to the "proe2001.bat" file that launches pro from your proe loadpoint. This should not change and the proe2001.bat file should remain in its original directory location. I'm not sure exactly what to use for...
So sorry, I incorrectly stated the above response (I have 8 month old triplets and I'm running on fumes because they're teething!!!)
I think the Pro/engineer command should always point to pro/e>>bin directory. Instead, you can copy the pro_batch.bat file and your test batch file to your...
There is a help file "Suggested Technique for Using Pro/BATCH to Create a Plot File" on PTC website that may help.
In the space designated "Pro/Engineer Command:" type in the entire path to the location of proe2001.bat file.
For example,
C:\Program Files\proe2001\bin\proe2001.bat
The above...
I quickly tried this and it seemed to work with part files. I would imagine it could also work with assemblies. Try running Pro/BATCH. I know you can make *.igs and *.stp files, but I don't know if you can make *.neu files with it.
Manually make your batch file...Open the family table...
Max,
You can specify the thread note format parameters in the hole table files under the CALLOUT_FORMAT. You can customize the note format to fit your needs. I believe there is an *.htm file on your C: drive that relates to this topic. I've listed the link below.
C:\Program...
