Using iLogic to drive assembly subcomponents

[joerog]

Hello

I am trying to create a top level assembly whose parameters are used to drive the design of its subcomponents (that in turn drive some of the features on the top level). The attached picture will show how I am linking/driving the parameters.

Because you are unable to link a parameter directly to a part from an assembly that contains said part due to cyclical errors I need to use iLogic to change the parameters of the subcomponent. I then, in turn have resulting reference parameters from the subcomponent fed back into the top level assembly which are then fed into iLogic for the purposes of switching some features on/off or adjusting the item count of some component patterns. My ultimate goal in this design is to have an assembly where I can change 1 or 2 parameters at the top level, save the change, and have all iLogic rules at all levels execute without the need to open up any subcomponents whatsoever. Instead I am finding myself having to do just that, defeating the purposes of linking parameters

Due to NDA, if needed, I will create a more dumbed down version of my assembly in question if that will help anyone help figure out the best way to accomplish this

Thanks in advance!

[joerog]

Hello

I am trying to create a top level assembly whose parameters are used to drive the design of its subcomponents (that in turn drive some of the features on the top level). The attached picture will show how I am linking/driving the parameters.

Because you are unable to link a parameter directly to a part from an assembly that contains said part due to cyclical errors I need to use iLogic to change the parameters of the subcomponent. I then, in turn have resulting reference parameters from the subcomponent fed back into the top level assembly which are then fed into iLogic for the purposes of switching some features on/off or adjusting the item count of some component patterns. My ultimate goal in this design is to have an assembly where I can change 1 or 2 parameters at the top level, save the change, and have all iLogic rules at all levels execute without the need to open up any subcomponents whatsoever. Instead I am finding myself having to do just that, defeating the purposes of linking parameters

Due to NDA, if needed, I will create a more dumbed down version of my assembly in question if that will help anyone help figure out the best way to accomplish this

Thanks in advance!

[Sergio.D.Suárez]

Good morning, if possible, attach a simplified model (which does not represent anything real, only schematic) and specify the operation you need to perform, I am sure it can be achieved. What is the function that gives you the most headaches? run the rules on each subcomponent? Greetings

[Sergio.D.Suárez]

Good morning, if possible, attach a simplified model (which does not represent anything real, only schematic) and specify the operation you need to perform, I am sure it can be achieved. What is the function that gives you the most headaches? run the rules on each subcomponent? Greetings

[FINET_Laurent · Accepted solution]

Hi,

I'm not sure about this work flow.. It looks over complicated to me & Chances are if you can't do it mannualy you won't be abble to do it with iLogic in my opinion.

Here is how I'dd do it instead :

(All this takes places in the top assembly )

Hope this helps,

Regards,

FINET L.

[FINET_Laurent · Accepted solution]

Hi,

I'm not sure about this work flow.. It looks over complicated to me & Chances are if you can't do it mannualy you won't be abble to do it with iLogic in my opinion.

Here is how I'dd do it instead :

(All this takes places in the top assembly )

Hope this helps,

Regards,

FINET L.

[joerog]

Thank you Sergio! It will take me a couple of hours but I will get you a simplified assembly with the code fully intact. I appreciate you help!

Joel

[joerog]

Thank you Sergio! It will take me a couple of hours but I will get you a simplified assembly with the code fully intact. I appreciate you help!

Joel

[joerog]

Thank you Finet! I think you might be right on this. It might be much better to kill the parameter feedback into the top level assembly. This would mean that I will just need to focus on getting the subcomponent iLogic to run on it's own. As soon as I finish making the simplified model per Sergio's request please feel free to download and troubleshoot/tweak.

Joel

[joerog]

Thank you Finet! I think you might be right on this. It might be much better to kill the parameter feedback into the top level assembly. This would mean that I will just need to focus on getting the subcomponent iLogic to run on it's own. As soon as I finish making the simplified model per Sergio's request please feel free to download and troubleshoot/tweak.

Joel

[joerog]

See the attached for the simplified assembly.

[joerog]

See the attached for the simplified assembly.

[joerog · Accepted solution]

I was able to reach out to support at my company regarding this issue. Looks like Finet is correct. There doesn't seem to be any (apparent) way to trigger the iLogic in the subcomponents to run from the top. So I am controlling all of the conditional features from the top level iLogic. I also ditched calling the reference parameter from the subcomponent and instead calculated at the top level.

Thanks so much!

Joel

[joerog · Accepted solution]

I was able to reach out to support at my company regarding this issue. Looks like Finet is correct. There doesn't seem to be any (apparent) way to trigger the iLogic in the subcomponents to run from the top. So I am controlling all of the conditional features from the top level iLogic. I also ditched calling the reference parameter from the subcomponent and instead calculated at the top level.

Thanks so much!

Joel