Installation of Pro/ENGINEER Manual Publisher

(for WinNT or Win 2000 machines)

1. Install Pro/ENGINEER 2001. (2000i or 2000i2 are also valid Pro/ENGINEER versions) 2. Unzip the attached Pro/E_Manual_Publisher.zip to a directory (<OA_load_point>) 3. Run <OA_load_point>/bin/proe2pv_config and specify your Pro/ENGINEER command (here Pro/ENGINEER 2001 command is specified and create proepublish and proebatch checkboxes are selected) and select Setup. (Note that the Create ProeWorker checkbox is unselected)

4. Two scripts are now created (proepublish.bat and proebatch.bat). You can convert by using menus (proepublish.bat) within Pro/ENGINEER, or from a batch publishing script (proebatch.bat). If you want to load the data into Pro/E first and then publish using the menus, this allows you to specify different output directories and recipe files interactively. If you simply want to convert a number of Parts/Assemblies/drawings, or need to conserve memory, then you should do the batch conversion. 5. By default, the recipe file <OA_load_point>\bin\proe2pv.rcp specified in the launch script will be used for all conversions, and the output directory will be your conversion startup directory. This default recipe (<OA_load_point>/ recipe/proe2pv.rcp) will be used unless overridden by specifying it using Pro/E menus. 6. To convert using the Publish (menu) option, simply load the Pro/E Part/Assembly, and choose the Publish menu. Do not set a recipe and do not set an output directory. This is the fewest key clicks method. You can specify a directory, which will be relative to your conversion startup directory. Remember you can use the middle mouse button to accept your selection, which will be remembered during that Pro/E session for any following conversions. 7. To convert using the minimum amount of memory, the converters support a special mode when run in Batch mode. You need to use a recipe file with the Minimum Memory conversion enabled, and you have to run in Batch mode. (For introduction to recipe files, see the Pro/ENGINEER object Adapter documentation on 6.0 release CDs.) 8. To convert non-proe data using this adapter, first load it into Pro/E and then save it as Pro/E native data. (The new ATB import mechanism allows you to import many CAD formats directly into Pro/E, and save them as Pro/E Assemblies and Parts thereby allowing a standard Pro/E conversion to view many types of alien data. (Currently, Pro/E 2001 can directly read CATIA 4.2x Models and Sessions, ACIS, CADAM, VRML 2, STL, CGM, PDGS, Step, DXF, IGES, and Pro/Desktop without the need for any of the original applications!).

9. To convert using the minimum amount of memory, the converters support a special mode when run in Batch mode. You need to use a recipe file with the Minimum Memory conversion enabled, and you have to run in Batch mode. (For introduction to recipe files, see the Pro/ENGINEER object Adapter documentation on 6.0 release CDs.) 10. Begin the proebatch conversion by typing the command <OA_load_point>\bin\proebatch <file.asm> You can edit proebatch.bat file to specify various output options. Use proebatch.bat h on a MSDOS command prompt to see a list of these options and their argument. (Please see the Pro/ENGINEER Object Adapter documentation on release 6.0 Visualization CDs for these options.)

Conversion Troubleshooting
If the Publish menu does not appear in Pro/E once an Assembly is loaded, check in the Auxiliary Applications menu to see if the converter is present and enabled. If not, there is most likely a license or environment variable problem, or an error in protk.dat created in your conversion startup directory. If you have first imported data from an non-ProE format (and then saved it to Pro/E format of course), a log file of the same name as the new Pro/E Assembly/Part will be produced, showing how Pro/E imported the data. During any conversion, there are 3 files produced in the conversion startup directory that can help with troubleshooting. The first 2 are Pro/Es standard files : std.out and trail.txt. The third file is the conversion log-file, called either proepublish.log or proebatch.log depending on whether you used a Batch conversion or a Menu Publish conversion. If you run out of memory during conversion, as identified by memory allocation problems in the log-files, you should do a Batch conversion using the a minimum-memory mode recipe file.