Go back to Olaf Corten's Home Page or learn more about Olaf Corten <
olafc@molding.fico.nl>========================== O C U S =================================== Olaf Corten's Utilities Set for Pro/ENGINEER and Pro/PDM users version 5.0 03-11-2000 ========================== O C U S =================================== This archive consists of utilities for Pro/ENGINEER and Pro/PDM users. This is a FREE set of UNIX csh-scripts and more. I have written them in all these years working with Pro/E and Pro/PDM and they have helped me a lot getting the maximum out of both packages. Scripts included: o ProEngineer (Pro/E startup script showing available licenses; very usefull in environments with multiple machines and licenses). o ProENGINEER (stripped down version of ProEngineer script) o Pro_Purge (handles very large directories; moves files to dumpster; with parameter for number of models to retain). o Pro_Clean (recursive Pro_Purge). o where_used (find out where model is being referenced). o model_ref (show references to other models). o pdm_search (Creates a Pro/PDM trail file to search an object and perform specific tasks on them) o purge_database (A Pro/PDM Database purge utility through trail files) o convert_expanded_to_single (convert an expanded Pro/PDM bom to single bom files for each assy). o assy_bom (List Bill Of Materials for given assembly) o drw_model (show references of a drawing). o pro_bom_ls (scans the latest BOM file for parts and sub-assemblies and shows all models with the same name in the working dir). o assy_find (Creates a BOM for an assembly and shows all files with the same name recursive from the current directory or in all directories in a given file). o model_text (Shows internal feature names of a model like parameters, notes, datum names and simplified reps.). o pro_trail_retrieve (show the directories from which the models in session are retrieved). o pro_prev_directory (create a trail file with a change dir to your previous directory; use with mapkey micp) o pro_resume_feature (create a trail file which resumes first suppressed feature found; use with mapkey frf) o pro_bench (Creates a trail file which enables you to perform a benchmark test between different machines) o pro_scrsave (Creates a snapshot image of your current Pro/E window regardless of its size or position) o create_retrieve_trailfile (create a trail file which retrieves a list of models; other options are available like: export, forced regenerate and save). o create_instance_trail (Creates a trail file which saves all instances of a given generic part as an independant Pro/E model with geometry; It can also handle generic drawings) o demomakemovie (utility to create snapshot movies; with thanks to Frank Rood) o dupl_dir (check two directories for duplicate Pro/E models). o chck_config.pro (checks your config.pro for duplicate options, unknown options, for duplicate or conflicting mapkeys and it checks the nesting level of the mapkeys) o cat_tab (list a family table file in readable output). o pro2pov (converts a Pro/E .slp render file to a POV-Ray .pov file; with thanks to Korhan Tekin) o pov_scene (Creates a default POV-Ray scenery file for a .pov file created with pro2pov). o strip_pdm_data (removes all Pro/PDM data from Pro/E objects) and many more .... As an extra you get: o menu_def.pro file which uses some of these scripts. o config.pro upgraded to R2000i and a logically build set of approx. 1000 mapkeys (let's make this the world standard...) o config.win which uses some of those mapkeys. o .auxchestrc file which adds buttons to your toolchest to startup different versions of Pro/E. o An example color.map file. ======================================================================== HISTORY: See HISTORY file. DESCRIPTION: See DESCRIPTION file. PLATFORM: The scripts have been tested on Silicon Graphics IRIX 6.2 with Pro/E Release 2000i (build 2000270). The scripts have been tested and run on Silicon Graphics IRIX 6.2. Most of them should run OK on other UNIX flavors. Try them and find out yourself.If a script does not work try to repare it and/or contact me with a description of the problem, your (proposed) solution, your UNIX environment and Pro/E release and build code. INSTALLATION: The sub-dir OCUS has been created when you installed the archive. In this directory you will find this README, a DESCRIPTION and HISTORY file, a scripts sub-dir and a config sub-dir. The first thing you should do is make sure the scripts are located in a directory which is included in your path. You can do this by adding the OCUS/scripts directory to your PATH environment variable (1) or by placing the scripts in a directory which is already included in your path (2): (1) Add the following line to your .cshrc file: set path=($path $HOME/OCUS/scripts) If this does not work for you, read the documentation from your computer and find out how you can change the PATH environment variable automatically at login. (2) See paragraph: CONFIGURATION If you run the scripts and get a 'Permission denied' error message change the permission mode of the files to 755. e.g.: % cd $HOME/OCUS/scripts % chmod 755 * CONFIGURATION: You will probably have to edit some of the scripts for your own use. Do not let this stop you from using them. Most edits you should perform deal with company configuration and are fairly simple. o Some OCUS scripts call other OCUS scripts so the first script needs to know where to find the other script. The scripts assume they are installed in $HOME/OCUS/scripts. If you installed them in another directory you will have to change this in the scripts. You can use the script pro_replace to do this: e.g.: If you have installed the scripts in a sub-directory /usr/data/scripts you will have to change all entries $HOME/OCUS/scripts to /usr/data/scripts in these scripts. The command: % pro_replace '$HOME/OCUS/scripts' '/usr/data/scripts' * will do this for you. o The scripts also assumes the trail files are saved in a /usr/local/trail directory. If this is not the case change it as follows: e.g.: If your trailfiles are saved in a sub-dir WORK of your $HOME directory you will have to change all entries /usr/local/trail to $HOME/WORK in these scripts. The command: % pro_replace '/usr/local/trail' '$HOME/WORK' * will do this for you o Read the DESCRIPTION file to see what scripts need to be configured. Just open the script you want to configure with your favourite editor and see which parameters need to be reconfigured (See for example the script ProEngineer). o Common parameters used in the scripts are: SCRIPTS_DIR Directory where you install these scripts LS_COMMAND Command to generate a one column ls output EDIT_COMMAND Command for your windows editor. The scripts asume your favourite editor is "jot". If you use another graphical editor you can change it in all scripts at once with the following command: % pro_replace '"jot"' '"YOUR_EDITOR"' * o You may add the following global parameters to your .login file. If they exist they will be used by a few scripts. PROE_STARTUP_DIR Directory from which you startup Pro/E. PROE_TRAIL_DIR Directory where trail files are written. WINEDITOR your favourite editor. e.g.: setenv PROE_STARTUP_DIR $HOME setenv PROE_TRAIL_DIR /usr/local/trail setenv WINEDITOR zip o Most scripts give extra information with the -h option. e.g. dupl_dir -h USE PRO_RENAME AND PRO_REPLACE WITH EXTREME CARE BECAUSE THESE ALLOW YOU TO CHANGE FILES. CONFIG DIRECTORY: In the config directory you will find several files which you can use to modify your sytem configuration. o menu_def.pro: Many mapkeys are executed from the UTILITIES menu defined in this menu_def.pro file. Add these buttons to your own menu_def.pro file or put this file in your HOME directory. o config.pro In this file you will find an example of a company wide mapkey set. It is a large set (allmost 700 mapkeys), but they are logically build. See the config.pro file for the rules I used to build this set. Add this file to your own config.pro file and run the OCUS utility chck_config.pro to check for duplicate mapkeys. o config.win: Many mapkeys and scripts are executed from the Pull Down menu defined in this file. Put this file in your startup directory. o ocus.auxchestrc If you place this file in your HOME-directory and rename it to .auxchestrc, buttons will be added to your toolchest (SGI only?) to startup Pro/ENGINEER with the OCUS utility ProEngineer. Edit this file to suit your company's licenses. o Configuration files for environment settings. Two configuration files are added which toggle your environment settings on or off. These are being called via two mapkeys described in the config.pro file (mapkey $F11 and mapkey $F12). Note that these files are supposed to be placed in your /usr/data/config directory. If you place them somewhere else, edit the config.pro file: % pro_replace '/usr/data/config' 'other_directory' config.pro o plotters/origin_move.cdcl The origin_move.cdcl file in the plotters sub-dir is used by the plot script. This is a Calcomp specific CDCL file which is used to change the y-origin of a drawing on a sheet. The plot script assumes this file is installed in /usr/data/config. If you installed it somewhere else change it in the plot script with the command: % pro_replace '/usr/data/config' 'other_directory' plot NOTE: Some of these scripts will search the ASCII Pro/E model files. So if you store your Pro/E models *compressed* some scripts might not work. Scripts like bom_file, drw_model and where_used search only the header of the file (which is not compressed) so these are not affected by this config.pro option. You can turn compression of with the config.pro option: COMPRESS_OUTPUT_FILES NO TIPS: o Some scripts have long or complex names. If you use these commands a lot create links for easy use: e.g.: The following command creates a linkfile wu to the script where_used: % ln -s where_used wu AUTHOR: Written by Olaf Corten, The Netherlands. A Mechanical Engineer with a University Degree and experience with Pro/ENGINEER and as a CAD-admini- strator on Silicon Graphics workstations since the beginning of 1991. I have switched to NT in the summer of 2000, but still use a lot of these utilities on our old Unix boxes. If you want to learn more about me, check out my Home Page with an extensive OCUS section, a WHO AM I section and a Pro/E section with Tips & Tricks and links to several other Pro/E related sites. You can also easily donwload all OCUS related HTML-pages to add them to your own Intranet. The OCUS utilities are provided courtesy of my current and previous employers. Employers (all in the Netherlands): Previous: Nucletron Research B.V. (3 years) Mijnssen International Engineeers B.V. (0.5 year) ATAG Verwarming B.V. (2 years) Current since july 1996: Fico Molding B.V. Nijverheidstraat 14-16 6914 AD Herwen The Netherlands tel: +31 316 243668 fax: +31 316 243700 E-Mail: olafc@molding.fico.nl or ocorten@knoware.nl Home Page: http://www.knoware.nl/users/ocorten I am the CAD Supervisor for Fico Molding BV. This is a subsidiary of Fico B.V. Fico Molding Systems BV developes back-end IC-Manufacturing systems (to package a chip). Fico Trim & Form systems (another subsidiary of Fico BV) developes the machine after the Mold machine. Fico B.V. has approx. 800 employees world wide. The engineering department of Fico Molding has 21 Pro/E licenses for 30 constructors on Compaq NT's. We also use COSMOS-M, Pro/MECHANICA MOTION and Structure and AutoCAD. Our PDM systems are Pro/PDM, Matrix and BaaN. FEEDBACK: I would very much like to here from you. Please tell me who you are what you do and how you like these utilities. I hope that by providing useful utilities to others that all will benefit and that others will do the same. If you have comments or suggestions please contact me via E-Mail (or the above mentioned address or fax). DISCLAIMER: ################################################################################ # Permission to use, copy, modify, and distribute this software and its # documentation for any purpose, without fee, and without written agreement is # hereby granted, provided that the following two paragraphs appear in all # copies of this software. # # IN NO EVENT SHALL OLAF CORTEN OR HIS EMPLOYER BE LIABLE TO ANY PARTY FOR # DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT # OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF OLAF CORTEN OR HIS # EMPLOYER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # # OLAF CORTEN AND HIS EMPLOYER SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, # BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR # A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, # AND OLAF CORTEN OR HIS EMPLOYER HAS NO OBLIGATION TO PROVIDE MAINTENANCE, # SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. # # This Software is NOT supported by Parametric Technology Corporation. ################################################################################ |