Background:
I'm building a product configurator with iLogic. We have a base model that we Copy Design in the Vault for each new product, and then configure it through iLogic.
In the product, I have one component that is accepting ~10 parameters (dimensions of different plates, enable/disable different features, etc). Additionally the component derives features from other parts of the product, meaning the component will be unique for each product. For example; the overall length of the component, and distance between certain features will always be unique for each product, but common for each instance of the component in one product.
Problem:
If I only had a single instance of the component, it would be easy to modify it through iLogic from the top level assembly. The issue is that there can be 2-10 instances of this component in each product, AND they should all be possible to configure independently (using the ~10 parameters per instance of the component).
Possible solution:
A simple way to solve it would be to copy the component part to 10 different files manually (and then configure and enable/disable the different instances through iLogic). The issue is that when we need to change the base model of the component, we will need to overwrite the other 9 duplicates manually, which can get tricky.
I'm considering automating that process through iLogic, but that would get messy and tricky due to Vault integration.
Question:
Is there a better approach for this type of problem?
Solved! Go to Solution.
Solved by Sergio.D.Suárez. Go to Solution.
Hi, I think the focus of your problem should be with ipart.
The advantage of ipart over ilogic is at this point you just described.
If you model with ipart you can specify different configurations in each multiple instance of the same part in the assembly.
On the other hand, if your configuration is by ilogic, you must create as you explain files with different names and one for each configuration you need.
I think you should differentiate each particular use of your part, both of ilogic and its multiple advantages as with ipart
Grettings!
Sergio Daniel Suarez
Mechanical Designer
| Upwork Profile | LinkedIn
Hello @Anonymous !
Great to see you here on Inventor Forum.
Did you find a solution? Let us know by clicking the green 'Accept the solution' button below the post
Находите сообщения полезными? Поставьте "НРАВИТСЯ" этим сообщениям! | Do you find the posts helpful? "LIKE" these posts!
На ваш вопрос успешно ответили? Нажмите кнопку "УТВЕРДИТЬ РЕШЕНИЕ" | Have your question been answered successfully? Click "ACCEPT SOLUTION" button.
Hi Sergio. Thanks for your reply!
I've considered iParts., and they would be perfect for this purpose, IF it was possible to modify the iPart table externally (either directly through iLogic, or through an external Excel file updated through iLogic).
The issue is, some of the input parameters should be automated and decided by rules, I don't want want the user to enter them manually. (To avoid mistakes and to make it easier for the user, but also because all other input is handled through iLogic, so it makes for a simpler workflow)
This works:
Dim i = iPart.CurrentRowValue("FL_Width")
But there seems to be no way to this:
iPart.CurrentRowValue("FL_Width") = 500
Cont. regarding iParts:
I could create Numeric Inventor Parameters for each dimension on every iPart row I would like to modify (Height_1, Height_2 ... Height_10, Width_1, Width_2 ... Width_10, etc) and reference them in the iParts table, that actually works!
But the iParts table doesn't let me reference Text parameters for "Suppress"/"Compute", to allow me to suppress features. If there is some way to get that working, that would be a good enough solution for me.
I kept searching, and found out that it is possible!
Can't find what you're looking for? Ask the community or share your knowledge.