- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
@Anonymous wrote:
I think this is a misunderstanding going both ways. I do not want to use iLogic to modify or generate the tables. I want to use it to include or exclude all of the hardware and simple parts that go with a specific table configuration but are not in the table. iLogic has an enable feature to it, so I am not understanding why this will not work. Because when you place the iAssembly member into another assembly it will not reflect the iLogic exclusions, you would have to place the iAssembly member, then run the iLogic rule... and because it would better practice to just use one or the other.
Having the ".Excluded = True" as part of iLogic leads me to believe that iLogic can control weather a part is included or excluded in an assembly, Yes it can do this same as a table entry would do, no it will not be the same result, as you've noticed it will not modify the table to reflect the the suppression state when you use iLogic to suppress this is a potential problem and creates two places to touble shoot issues rather than just one, iAssemblies without having to use a table entry for that item using the iLogic to perform these tasks automatically. I'm suggesting you use one or the other, missing the two in the way that you are attempting has no benefits as far as I can tell
Component.InventorComponent("RING TERMINAL .25 12-10GA RING TERMINAL .25 12-10GA-Silver:3").Excluded = True
This brings back my question of how assemblies with 100's of configurations should be handled. The Boss doesn't want to hear that it will take a month to update all of the models and prints configuring a large iAssembly as you describe should not take that long, a few days to setup and test, and then making modifications should only take minutes to add a freaking decal to all of machines. Just for clarification the Decal command is not supported in assemblies, but if you mean a part file representing a decal then this can be included/excluded as well... you might know this already but just in case not I thought it should be mentioned There has to be a more efficient way to do this. How does everyone else deal with this? Creating container subassemblies to hold hardware, etc. and using Excel to copy-fill and or Copy/paste in the table to quickly configure it is the way many would do this for large assemblie - OR - using ilogic to configure the assembly would be the way many others would do this, mixing the two is likely a rocky road
I want ONLY these options in my final iAssembly table to choose from:
Transformer (1-10)
Bridge (1-2)
Output Style (1-4)
UI Style (1-3)
If you decide to use iAssemblies then make those items Keys, and have your hardware subassemblies turn off the rest per your table configurations
Based on what options I select in the table, I want the associated pieces to "know" if they belong in that configuration or not. Is that not what iLogic was designed for? Not really, iLogic can do many things one of which is suppressing components, as I've mentioned there are functions in iLogic that relate to iAssemblies, these can control the which member (aka row) of the iAssembly is used when you run a rule, but it relies on the table to be configured a head of time....
Could you mix the two in the way that you are wanting to do?.... I guess maybe it could work....to me it would make a mess, and result in two places to have mistakes and conflicting information.
I see no reason to mix the two, choose the one that you think will work best, but I'd work through a "proof of concept" taking it all the way from setup to use in design, to see what limitations or problems you encounter before spending time configuring the entire thing.
if you do decide to use iLogic please post your code and programming questions on the Inventor Customization forum rather than this general Inventor forum:
http://forums.autodesk.com/t5/Autodesk-Inventor-Customization/bd-p/120
I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com