Problem - using iLogic with iParts

[anthony_hendrick]

Hi all,

I am new to both iLogic and iParts. 

I have started to use iParts to create a series of models, all controlled by shared length parameters "Dim_A" "Dim_B" & "Dim_C"

I have a small table of ipart occurences in the ipart file, each with their own specific rules created by iLogic. 

These rules are intended to control the length parameters mentioned above.

The problem I am having is that these rules once executed are controlling all iparts. I would like a certain rule to control a specific part. 

Any help would be much appreciated.

Thanks 🙂

Anthony 

[Anonymous · Accepted solution]

I would recommend sticking to one or the other, iLogic or iParts. In my experience they do not work well together. It also sounds like since you already have a rule controlling the parameters controlled by the iPart table, there is no need for the table anyway. In this case I would stick with iLogic controlling the part. The only reason I use iParts anymore is to load parts into Content Center. Hope this helps!

Edit: I guess I should also ask why you wanted to use both in the first place, in case my assumptions about your workflow arent accurate

[anthony_hendrick]

Hi Ckurre and thanks for your reply.

To give you more of an idea of what I am trying to do, I am trying to create a steel reinforcement ipart in order to create bars and bar schedules. 

I have created 4 types of bars so far, each with their own profile and sweep, which I turn on and off in the ipart list using the suppress feature depending on what bar type I want. 

I have created parameters to control the main dimensions of each bar which works quite well.

However, as each bar type has it's own manufacturing constraints which need to be adhered to, I am trying to create a rule/ rules for each bar type to ensure that the bar conforms to standards (minimum lengths, minimum radii etc.....).

I am also in the process of linking the information to a custom parts list which is to be my bar schedule.

It's going ok so far, but I need certain rules to work on specific bar types, otherwise it ruins the ipart list. 

I essentially need to add IF AND THEN statements to control the bar constraints. 

If iLogic is not the way to go, would somehow using an external excel file linked with the parameters list help?

Thanks!

Anthony 

[Anonymous · Accepted solution]

It sounds like you might be trying to do too much in a single file. I would definitely suggest doing each cross-section as a different part. As for linking an excel file for parameters, that is basically what you have in the iPart table. Between that and the parameters dialog you should have everything you need to make a robust iPart. Or maybe you go away from the iPart and have one "master" that is used each time. Use "place iLogic component" and input key parameters to create a copy of the configured part. That is an option as well.

[johnsonshiue · Accepted solution]

Hi Anthony,

I just want to bring some perspective before looking into further. iPart was designed to create reusable library components like nuts and bolts. These parts are clearly defined on the table and rarely they are changed. Based on my understanding of the issue you are seeing, it seems that you are trying to use iLogic to drive iPart (factory and member) changes. I don't believe it is a reliable workflow. First, iLogic rule can only reside in iPart factory and custom iPart member. Second, iPart members should be driven by the table. Having iLogic rule running in the factory can interfere with the update process.

I suggest you use iLogic rule to drive the regular part (not an iPart). It allows you to configure all features and parameters. You can spawn a variation by placing the iLogic part into an assembly. Or, use iLogic Design Copy to create a copy.

Many thanks!

[anthony_hendrick]

Hi all,

Many thanks for your replies. 

Yeah I think I am going a bit too far with my iparts. I am trying to do too much and integrating ilogic with iparts is certainly upsetting the the iparts a bit. 

I think I will actually create a part per bar type (U-bar, L-bar et) and steer towards an ilogic solution rather than an ipart solution. 

Thanks again for your help and advice, very much appreciated.

Anthony 🙂