Applying iLogic rule per individual component of iAssembly

[jvankooij]

Hi all,

I'm trying to create an iAssembly of a roller conveyor in which multiple parameters can change. One of these parameters is the position of motorized rollers. On all the other positions in the conveyor a different non-motorized roller should be placed. I've created a component pattern and placed a 'normal roller' at every position. I've used an iLogic rule to suppress all the positions where a motorized roller was already automatically placed. In the iAssembly this works perfectly fine, when I switch to another component of the iAssembly this automatically triggers the rule and updates the position.

However when I create a different assembly in which I'd like to use different roller conveyors from this iAssembly, the position of where the 'normal roller' should be suppressed is based on the last opened component of the iAssembly and not triggered per individual component of the iAssembly.

How can I trigger the iRule per individual component of the iAssembly, such that this problem does not occur?

I've attached a screenshot of the issue to further show the problem, unfortunately I'm not allowed to share any code or models. 

Explanation of the screenshot:

In the screenshot the roller conveyor on the right is the one that was opened last. The red colored rollers are the motorized ones and thus the other rollers at these positions are supressed. In the left roller conveyor you can see motorized rollers indicated by the coller blue. The locations of the missing rollers in this conveyor correspond with the location of the conveyor on the right.

[A.Acheson]

Hi @jvankooij 

The minute I see iAssembly and iLogic the immediate question is are using iLogic to carry out work in the factory file or just simply to switch the iassembly members? The latter is the only way iLogic can work external to the factory. You can temporarily use it to set up your factory members internally but you must remove it after as it cannot work in derived files. 

You will need to share non confidential code with either a dumb assembly or screenshots of the same to get your point across as to the desired workflow.