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.

Config.pro settings

kman23

New member
<DIV>Recentlymy companystarted using Product View Express to view ProE assemblies and drawings. When we started doing this we had to change the settings in Config.pro to save assemblies as shaded and create snapshots for drawings. At the moment all new ProE CAD data can be viewed by product view express. If any of the older assemblies and drawings need to be viewed we need to open that assembly, save all the related parts, drawings and subassemblies again. This is avery as long as I have to processover10,000assemblies. My questions are -</DIV>
<DIV></DIV>
<DIV>1. Is there an easier way to solve the problem without going to another viewer?</DIV>
<DIV>2. Can I write a program/scripts that will automatically open all drawings,parts and assembly and save them again?</DIV>
<DIV>3. Can I write a program/script that will propogate the new setting in config.pro to the old assemblies?</DIV>
<DIV></DIV>
<DIV>Please let me know your thoughts and suggestions.</DIV>
<DIV></DIV>
<DIV>Regards,</DIV>
Edited by: kman23
 
Kiran,


If you are managing your Pro/E data in Pro/INTRALINK then you need to write a 1 time execution program that will checkout the assembly into a session of Pro/E (with the new config.pro setting), save it, then check it back into Pro/INTRALINK. This would be a mixed (Pro/TOOLKIT and Pro/INTRALINK Toolkit) simple asynchronous program. Otherwise if all of your Pro/E data is managed on the file system then the only part that changes is the checkout portion.
 
I think you can use Pro/Batch.

<h1>About Pro/BATCH</h1>
The Pro/BATCH user interface enables you to define your
batch session and schedule the execution of the command file.
You can upgrade files from a previous release of
Pro/ENGINEER to the current version of Pro/ENGINEER.
Pro/BATCH enables you to enter batch mode to create multiple
plot files, or export to other formats. Using the interface, or a command file
that you create, Pro/ENGINEER retrieves the appropriate objects and creates the
specified export files for them. You can also import CADAM data into
Pro/ENGINEER using Pro/BATCH.
The proigsutil conversion utility
enables you to convert a number of IGES files into parts or drawings.
Batch mode takes a list of objects from which to create
files, retrieves the objects, and creates the files without any further
interaction.
When running Pro/BATCH with the interface or the command
line,
<ul><li ="kadov-p-CTopic-Text-Bulleted">
License requirements and available modules remain
the same as for a regular Pro/ENGINEER session.
<li ="kadov-p-CTopic-Text-Bulleted">
Pro/BATCH does not remove a version number from an
input file. If you supply a version number, the system uses the file with that
version number; if no version number is supplied, the latest version of a file
is used.
<li ="kadov-p-CTopic-Text-Bulleted">
The configuration file in the working directory,
home directory, loadpoint directory, or startup directory is used when executing
a command file. The configuration file settings define the Pro/ENGINEER
environment and specify options that are required to perform a specific task
(for example, plotting or exporting to IGES, DXF, or VDA).
<li ="kadov-p-CTopic-Text-Bulleted">
The configuration settings remain the same for all
files created from the same batch job. Because the system also uses search paths
defined in the configuration file, objects need not reside in the current
directory.[/list]
When running Pro/BATCH with the command line,
<ul><li ="kadov-p-CTopic-Text-Bulleted">
If you press ENTER, the system accepts the default
value given within the brackets ([ ]).
<li ="kadov-p-CTopic-Text-Bulleted">
To exit Pro/BATCH while creating a command line,
type QUIT + ENTER + ENTER.[/list]
A log file is created for each Pro/BATCH session. The log
contains all of the executed commands as well as the exit code for the command
(SUCCESS or FAILURE).
 
Pro/BATCH can't talk to Pro/INTRALINK. All objects have to be on the local workstation. Same thing with Distributed Pro/BATCH.
 

Sponsor

Back
Top