Cancel
Showing results for 
Search instead for 
Did you mean: 

disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

Hello, dear community,

I have 2 questions:

1) can I create 2 MUs in the dismantle station? How?
4.PNG
2) I tried to dismantle an existing compound (MU previously assembled from 2 MUs)
back into the original MUs, and set a higher level in the work plan. 
(because the plan includes an assembly and disassembly along the creation process before final assembly.)
To achieve this, I deleted the "big" MU and generated the 2 "small" MUs;
but it seems that the newly generated "small" MUs do not have the user-defined attributes
which I set up for this type of MU in the library. Why is that, and how could I possibly fix this?
1.PNGMethod re-creating the 2 components2.PNGuser attributes of the component (as it should be)3.PNGwarning that those attributes are voids

 

thank you very much for your help

 

12 REPLIES

Betreff: disassembly via Method, generating MUs with user attributes

Siemens Phenom Siemens Phenom
Siemens Phenom

Hello Hannes821,

 

first, .LO.HZ.GehäuseOT and .Lo.HZ.GehäuseUT are both class objects. I assume these parts already have the necessary attributes defined .

In line 18, after you delete the main part, you have to create the sub parts:

var part1 : object := GOT.create(targetObject)

Here you have to define the target object, where the sub part should be created.

After this, you can access the attributes of part1.

Hope this helps

Regards
GG

------------------------------------------------------------------------------------------------------
Did you like the answer? Then click the Thumbs Up button.
Did the answer solve your problem? Then accept the answer as solution

Re: disassembly via Method, generating MUs with user attributes

Phenom
Phenom

@ dismantle station

 

if you select the distmantle mode "Detach MUs", the previsiously assembled MUs will be split again

 

@ error message

 

You are showing the user attributes (of GehäuseUT)  as should be.

 

But the error occurs for GehäuseOT.

 

Even if the attributes are the same for both parts, PoistionimAP seems to be missing

 

 

Unbenannt.PNG

Re: disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

Thank you very much so far!

I simplified it a bit, but still, run in the error that the programme is puzzled about my user attribute
"PositionimAP". I will now look into using the dismantle station, I am a bit surprised it can "recognize"
the previously assembled MUs again? is that only the case if I attach one MU to another or does
this also work if I replace both MUs with a new one?

12.PNG13.PNG

Re: disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

To test the idea of disassembly I had, I made a test network.
1) the parts get assembled (destroyed) and a new MU is created.
2) the new MU is disassembled (destroyed) again and then I attempt to get both component MUs out again.
However, the disassembly station seems to allow me only to gain 1 new MU.
So I was already thinking of adding a bypass source...
or I missed a much more efficient way to solve this...
14.PNG

Re: disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

@simulator thank you, but if I detach the MU, it does not get split again here.
15.PNG

Re: disassembly via Method, generating MUs with user attributes

Phenom
Phenom

you need a further exit for disassembled parts.

Re: disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

Sorry, I think I do not understand what object or setting you refer to with the extra exit.
An exit strategy? 
4.PNG5.PNG

Re: disassembly via Method, generating MUs with user attributes

Valued Contributor
Valued Contributor

What you refered to earlier, GehäuseOT does have the same user attributes which play fine at other stations.
6.PNG

Re: disassembly via Method, generating MUs with user attributes

Phenom
Phenom

@ first issue self defined attributes

 

the error pops up because PositionimAP  is not defined

 

Unbenannt.PNG