start part conflicts

[mudassirkhan]

Hello Everybody,


We have two brands in our company. We have two start parts for each brand. One is following inch and other is following metric system.Recently our management has taken a decision to discard the brand following inch system and also its relative settings like start part etc. Now the main concern is that we had made all our proe parts as per inch start part. we have to convert all the settings in those parts as per the metric start part settings which also includes layers settings, parameters etc. Please guide me the best possible method to perform this task. Thanks in advance.


Mudassir Khan

 

[write2bush]

ARE U TALKING ABOUT THE MODELS YOU HAVE ALREADY CREATED, OR THE ONES YOU ARE GOING TO CREATE IN FUTURE.


REGARDS

 

[mudassirkhan]

Dear Bush,


we already have thousands of models created and we are worried how to change them as per metric settings.


Best Regards,


Mudassir Khan

 

[sdshriram]

Mudassir Khan


Try this,


edit....setup.......units...select CUSTOM.....SET.........OK


IT WILL WORK


SUDHIR

 

[venkateshraja]

Go to setup --> Units and change the units to mm, It will prompt for two options , one is same size another one is same dimensions, You can choose same dimensions, So that the dimensions does not vary ( That is 1 inch = 1 mm)

 

[ProE_Addict]

The biggest concern I'd have in your situation is relations and assembly constraints. If you have english relations in a model and convert it to metric, your geometry may change.


If you have a large number of files and have no relation issues, I'd recommend having an expert write a program to update your files in conjunction with ModelCHECK.


IfYOU need to update them and don't have this expertise,


-Set up ModelCHECK for the standard part you need.


-Correct any problems with relations.


-Create Mapkeys to change themodels.I'd recommend creating separate mapkeys initially to verify that each issue is resolved correctly (i.e. change units, delete/change layers, delete/change parameters, etc.). Once they seem to function appropriately, you could consider stringing them together.


You might want to create a backup each model and run a comparison on each part as well to make sure your geometry doesn't change due to unit conversion.


After you complete changes to a part, run ModelCHECK to verify accuracy with your intended file.


Good Luck!

 

[mudassirkhan]

Hello Everybody,


sdshriram,vekateshraja and proe-addict thank you so much for your replies. As per the first two replies i know that we can change inch to metric in that manner but the situation in my case is not only about changing units but aslo changing layer settings, parameters and whatever is included in the start parts.


Proe-addict had elaborated my point to a greater extent but we dont have that much expertise to write a program for this exercise. Anyway we dont have relations in many models except weight calculations.However i will go for ur another alternative of creating mapkeys and comparing accuracies. Can you please tell me how to string all the various mapkeys into one. Can we write some sort of batch file for that. Looking forward.


Thanks andRegards,


Mudassir Khan

 

[ProE_Addict]

mudassirkhan,


No need for a batch file if you are planning on using the mapkey route. You will, however have to open each file and execute the mapkey to make changes...


If you have experience creating mapkeys, it's the same as usual for each you create. After you have the various ones created, all you have to do is remove the key sequence andmapkey description from thenext mapkey in your sequence. This is usually the entire first line of the mapkey. Next, add a \ after the semicolon in the previous. For example:


If the following is the last line in the first mapkey sequence:


mapkey(continued) ~ Activate `modeldisplay` `ModDsply_PB_OK`;


Adda \after the semicolon.


For the second mapkey, delete the first line shown below and make sure that the remaining lines follow directly under the first mapkey sequence (no empty rows).


mapkey $F2 @MAPKEY_NAMEOpens Feature Operations Menu;\


mapkey(continued) @MAPKEY_LABELFeature Operations;~ Select `main_dlg_cur` `MenuBar1`1 `Edit`;\


The \ tells ProE to continue running additional menu picks or key strokes.


The last line of your mapkey sequence will end with just a semicolon.


It can take some time testing the big mapkey to make sure it functions properly. I suggest creating the individual mapkeys first and saving them to a separate file in case you have to go back. Also, you may want to copy a few parts to test before updating them all...


I've had to do this very thing at my last job when we worked with an outside source. When we received their files we have to update them to follow our standards.