import of parameters of proe wf5

[Ghirarduzzi.G]

time ago I started designing a car and then set the start parts (asm, prt, smt) without worrying too much about the parameters to insert, also because I didn't know well what would be then of real necessity when I should have inserted the values in a cartiglio and especially because at that time I had decidedly other things to think about. ok I could at least insert the standard parameters that good or bad always go well (signor, date, etc.) but they would have been in any case a small part.
today I have the machine practically finished and I need to insert the parameters in the models to make them then automatically fish from the table put cartiglio.
Since I would like to avoid doing it manually for all parameters I have to insert (28) for all machine components (about 150), I would like to know if there was a possibility to do it automatically (otherwise it means about 4200 parameters).
I have clearly changed the various start parts for the future, I do not know if it can help for the present. In practice what I would like to do is this: I created a model using a start part, today the start part has changed, I would like to recover the information of the new start part and possibly delete the information of the old start part.
I hope I have explained my problem exhaustively. Wait for answers!
Please... help me!

 

[Prof.]

there would be a way using relationships together helping with excell to compile them.
But I've never used it, I do some evidence, and I'll let you know.

 

[Prof.]

then if from the main axieme you go on the relationships (instruments > relations), you will notice that selecting the internal features of the parts will show on screen the parameters of such features followed by : and a progressive number (e.g. d12:6).
normally in pro-and that number after the two points (which we can call id of the component) is always an equal number for the parts and an odd number for the sub-assiems and are progressive numbers that respect the order with which you mounted parts and sub-assiem.
well known for the parts id starts from scratch.
then in the relationships of the assieme you can write (for example):

Your_parameter_1:0="try"
your_parameter_2:0=10
your_parameter_3:0=yes
Your_parameter_1:2="try"
your_parameter_2:2=10
your_parameter_3:2=yes
Your_parameter_1:4="try"
Your_parameter_2:4=10
Your_parameter_3:4=yes

if you do this by increasing the number after the two points up to a random number but high enough to cover all your components you will see that it will award those parameters to all your parts.
It will only give you a mistake in the relationships for which you do not find the id in your set, but this will erase it and you are appropriate.
You better write your excell reports by helping you with the concatenation function and copying everything in the axieme relationships.
I hope I've explained clearly, let me know.
Bye.

p.s. attached you will find an example excell file.

 

[simra]

I did not try to use it but it really seems to me an interesting motlo method. ...

 

[Ghirarduzzi.G]

Thank you!
Although it seems to me that then time saved in automatism is then necessary to spend it to clean up relationships in the various models.
and then how does the system behave when the model is on multiple levels?
in the sense that I have a main set in which there are subaxes, which in turn contain a mix of subaxes and parts.
What happens when you get down to level?
Anyway, I'm trying.
thanks in any case for the trouble and for the answer.

 

[Prof.]

the relationships you have to write only in the main assembly and once you apply the gates.
If you write them properly they will create parameters in sub-axis and parts of any level.
Bye.

 

[Ghirarduzzi.G]

It works!
but alas not for the elements of family table.
and this could be expected since I clearly have instances in the axioms of the various generics while the parameters should be included in the generics.
patience! I manually entered the parameters in various generics and went ahead with the procedure. Now it looks okay!
the only thing I didn't understand is because some instances of some family don't regenerate properly in the parameters managed by relationship.
in the sense that I have the relationship that tells me that the file code must be the same as the model name and for some strange reason some instances have to regenerate them manually and then save them.
The absurd thing is that it does it in a random manner on instances. that is only on some and not on others. Mah!