How to insert Assembly (containing iLogic) inserten in main assembly

How to insert Assembly (containing iLogic) inserten in main assembly

Anonymous
Not applicable
502 Views
2 Replies
Message 1 of 3

How to insert Assembly (containing iLogic) inserten in main assembly

Anonymous
Not applicable

I have some questions about Vault and iLogic.
Because I made an assembly containing iLogic (1x form, 2x rule). I have processed the parameters in the ipt file. The assembly is set up for use of the frame generator. I made this assembly because it allows us to save a lot of time on engineering. Now I have tested the assembly and it works properly, but now I have started testing it as an assembly in a main assembly. In addition, this assembly must be able to be placed in the mail assembly in several variants. Now I tested this last by copying the main assembly into the VAult (Basic) with the copydesign function. But if after inserting into the main assembly, only the height parameter works. The rest are unresponsive, and at the moment I don't know why this is happening and so I get stuck. hopefully someone can help me on the right track and I can continue with this journey of discovery in iLogic.
The questions I have are:
- What is the best way to handle an assembly with iLogic?
- Is copydesign via Vault the right way to create variable?
- How can I best place it in the main assembly? Because would like to place this as an assembly.

Hopefully someone has an idea how to fix this?

Thank you in advance for the help.

Regards, Joop

0 Likes
Accepted solutions (1)
503 Views
2 Replies
Replies (2)
Message 2 of 3

A.Acheson
Mentor
Mentor

@Anonymous 

You ask very good questions. I know only a little of ilogic use in assemblies and haven’t push it’s use because of the time it can take to jump on this learning curve. 

I can only think of trying to trouble shoot it piece by piece. Do you know which assembly the parameter are failing to activate? Show some screen shots, I am guessing there is a ilogic that has lost its static occurrance name reference during the file name change. Were all files used in the code have there occurrance name change to static? Can you show some code where the problem area may be?

 

Have you tried the ilogic copy process in the assembly? And did it have better results? 

If this solved a problem, please click (accept) as solution.‌‌‌‌
Or if this helped you, please, click (like)‌‌
Regards
Alan
0 Likes
Message 3 of 3

Anonymous
Not applicable
Accepted solution

Hello,

the reason your Ilogic doesnt work with copy design is simple, the part file names change while the ilogic uses the same old references. so the best way to handle iLogic in assemblies is to change the occurence name. this wil give the part a stable name while the underlaying file name can be changed without a problem. 

 

1. right click on part

2. click iProperties 

3. change name under occurrence to a simpel name.

4. change the reference in iLogic to the same name.

 

your iLogic is as stable as can be. this process is called "Normalizing" your assembly and is very usefull when you're designing something to be used more then once.

 

if its not clear pm me, 

 

grts

 

Siem

0 Likes