Great help. The only annoying thing is needing to open the BoxParameters part to change the parameters. If you could somehow link it so you can change them from within the assembly it would be nice. I did find that you can put the BoxParameters part into the assembly, and just set its BOM to Reference, and you can edit it to change the parameters, saving you having to open it every time.
Nice video, i liked it. I would like to ask, that is there a solution if i want to change the paramateres of a part from the assembly? i mean it takes much time to open a part all the times i want to change something, but the part would drive the assembly.
A very common approach is I create the driving parameters in the assembly. Then you can use iLogic to push those values into the required parts. So the assembly drives the part, as opposed to the other way around. Below is a link to one of my videos that shows how to push parameter values into files from the assembly. ruclips.net/video/2rr_hdambEw/видео.html. I hope this helps. If you have any other questions, please let me know.
Hi I'm trying to link parameters between 2 i parts with 5 variants each, So what I want to do is that the parameters of the part A variant 1 matches with the parameters of the part B variant 1 and so on. In order to when I change the parameters of the part A also change on the part B. What I did was to link the values in the excel table of each part but Inventor did´t respond after that. Is there other way to do it? Thanks.
I think a better way to do this is to use iLogic to trigger the change in Part A, then switch to Part B based on Part A's change. You can create a parameter, or parameters, that help you identify Part A. This command is a template for searching the iPart. i = iPart.FindRow("iComponentName:1", i = iPart.FindRow("iComponentName:1", "columnName", "
Sam, you can occasionally get Inventor to do that, however, most of the time Inventor will complain about a cyclical link. For some reason, it doesn't like having the file that has the parameters link as the assembly or one of the components. If you would prefer to have the box parameters be part of either of the components or the assembly, you can write an iLogic rule that passes parameters between files. It does work better to put them in the assembly and have the rule pass the values down to the components.
Steve Olson Right, the same problem that would want you to have a separate ipt in the first place I suppose. I do use the Ilogic Rule, I was just investigating other methods that could be more easily understood by Eng co op students that haven’t been introduced to Ilogic. However, it remains the most reliable method of creating Ilogic assemblies that I have seen. Excel table linkage seems alright too, but somehow less elegant still.
@@Jyuicycuhhh Yeah, there are so many ways to build a little intelligence into models. I find it frustrating that linking the parameters between components in the same assembly doesn't work. It seems like it should, but I guess there are ways it could cause trouble so it is prevented. I am glad you are aware of iLogic. It is probably the best way, but since coding is involved, it is a little intimidating to some.
Congratulations!
Full explained!
Great help. The only annoying thing is needing to open the BoxParameters part to change the parameters. If you could somehow link it so you can change them from within the assembly it would be nice. I did find that you can put the BoxParameters part into the assembly, and just set its BOM to Reference, and you can edit it to change the parameters, saving you having to open it every time.
halo sir
i'm from indonesian
thank you for this video's
verry inspiration
Yes, very helpful. Thank you!
God Bless You
Thank you, this video really helped!!
Thank you very much. I am glad that you found my video helpful.
I am glad to hear that you found my video helpful. Thanks.
Nice video, i liked it. I would like to ask, that is there a solution if i want to change the paramateres of a part from the assembly? i mean it takes much time to open a part all the times i want to change something, but the part would drive the assembly.
A very common approach is I create the driving parameters in the assembly. Then you can use iLogic to push those values into the required parts. So the assembly drives the part, as opposed to the other way around. Below is a link to one of my videos that shows how to push parameter values into files from the assembly. ruclips.net/video/2rr_hdambEw/видео.html.
I hope this helps. If you have any other questions, please let me know.
Hi I'm trying to link parameters between 2 i parts with 5 variants each, So what I want to do is that the parameters of the part A variant 1 matches with the parameters of the part B variant 1 and so on. In order to when I change the parameters of the part A also change on the part B. What I did was to link the values in the excel table of each part but Inventor did´t respond after that. Is there other way to do it? Thanks.
I think a better way to do this is to use iLogic to trigger the change in Part A, then switch to Part B based on Part A's change. You can create a parameter, or parameters, that help you identify Part A. This command is a template for searching the iPart.
i = iPart.FindRow("iComponentName:1", i = iPart.FindRow("iComponentName:1", "columnName", "
@@3DSteve52 thanks for the answer i´ll try it.
@@dieteras9372 No problem. If you run into issues, please let me know.
Can the "Box Parameters" ipt equivelent exist inside the assembly of interest?
Sam, you can occasionally get Inventor to do that, however, most of the time Inventor will complain about a cyclical link. For some reason, it doesn't like having the file that has the parameters link as the assembly or one of the components. If you would prefer to have the box parameters be part of either of the components or the assembly, you can write an iLogic rule that passes parameters between files. It does work better to put them in the assembly and have the rule pass the values down to the components.
Steve Olson Right, the same problem that would want you to have a separate ipt in the first place I suppose. I do use the Ilogic Rule, I was just investigating other methods that could be more easily understood by Eng co op students that haven’t been introduced to Ilogic. However, it remains the most reliable method of creating Ilogic assemblies that I have seen. Excel table linkage seems alright too, but somehow less elegant still.
@@Jyuicycuhhh Yeah, there are so many ways to build a little intelligence into models. I find it frustrating that linking the parameters between components in the same assembly doesn't work. It seems like it should, but I guess there are ways it could cause trouble so it is prevented. I am glad you are aware of iLogic. It is probably the best way, but since coding is involved, it is a little intimidating to some.
It is disarming how complicated inventor is. you can do the same thing in liteally 5 seconds and in a beteer way