Thank you for the code and input, Shawn.
Unfortunately, I've just discovered that this Visibility/BOMStructure workflow won't work for me either. When patterning a subassembly component, Inventor insists on creating the additional occurences at the "Master" View Rep regardless of the source component's view rep. They can each be manually changed back to the correct View Rep each time the pattern is altered, but this defeats the point of configuring the assembly with iLogic code.
Conversely, a custom LOD is "correctly" carried through all pattern occurences. Unfortunately, it goes a little too far and insists on needing a custom LOD at the top assembly level, even if the only component suppression is occuring at a subassembly level. With custom LOD's come a whole new set of drawing-related headaches.
It literally seems as though there is no "proper" way to use iLogic to turn off assembly components without manually correcting a myriad of problems afterwards. Are there plans to release a "Just show components the way I tell you to until I tell you otherwise" feature in IV2013?
"It literally seems as though there is no "proper" way to use iLogic to turn off assembly components without manually correcting a myriad of problems afterwards".
As previously stated i have absolutely no problems suppressing/unsuppressing assembly components with ilogic , I and my users use this functionality every day
It sounds like you are going through the same learning curve we hit about a year ago. It took some experimenting and lots of research to properly use LOD and view reps. The custom LOD is really the answer for iLogic/BOM issues.
All of our configurable models have a LOD called "iLogic" the drawings then reference that LOD for the drawing views.
Can you elaborate on the drawing issues you are experiencing?
The biggest problem with LOD's is the inability to have an assembly and it's drawing open at the same time. There seems to be a conflict between the activated custom LOD of the assembly, and the Master LOD used in the drawing's BOM. If both are open at the same time, I'll get error messages that stop me from running any iLogic code or saving whichever document was opened last (ie, the ridiculousness that is the "dirty LOD"). I can't imagine that this is a case where Inventor "works as designed", and having only one document open at a time is not a proper solution.
Additionally, the assembly will revert back to the Master LOD every time the drawing is saved. I understand that a rule can be written to force the assembly back to the iLogic LOD each time it's opened, but I also view that as a workaround, not an actual solution.
Several reps from Autodesk have stated that LOD's were never intended to support component suppression / configurations with iLogic, and I've discovered the same with regards to View Reps. Are we pushing the limits of what iLogic was intended to do, or has Autodesk failed to fully consider that these "configured" assemblies would ultimately be used in assembly drawings?
I do agree that not being able to have a assembly that uses a custom LOD and its associated drawing open at the same time. My users have become accustomed to this limitation. To cut Autodesk a little slack LOD's were around long before they aquired Ilogic , so some compatability issues are understandable, however these should be fixed.
For me ilogic "saved" inventor , previously it was very difficult to program intelligent parametrically controlled models.The benefits far outweigh the problems
Regarding the assembly reverting back to the LOD , I have never had this issue. In Tools/Application options/Assembly I set the Default level of detail to "Last Active"
That way if the assembly is saved in the custom (ilogic) LOD it will open in that LOD
I am not a fan of having a rule to force the assembly to open in a particular LOD. Sometimes it is necessary to open the assembly in the Master LOD and having a rule just complicates matters.
I do not know if you use VAULT , if you do you must open the assembly in the Master LOD to upload files
We already have our file-opening option set to "Last Active". It seems that, when populating the BOM, Inventor opens the assembly / sets it to Master LOD / saves the assembly in the background. Therefore, the assembly opens in the Master LOD when we next open it because it was technically the "Last Active" LOD.
Do you use Parts Lists in your assembly drawings? I never had a problem with undesirable asssembly LOD changes until I plopped down the parts list.
Our IT department is installing Vault in the next month or two, so I can only imagine the new list of obstacles that will present themselves. Thanks for the heads up about uploading assemblies in their Master LOD....this may be an issue for our planned workflow.
"We already have our file-opening option set to "Last Active". It seems that, when populating the BOM, Inventor opens the assembly / sets it to Master LOD / saves the assembly in the background. Therefore, the assembly opens in the Master LOD when we next open it because it was technically the "Last Active" LOD"
Never experienced this behaviour, my assemblies always open in the last active LOD
Yes i use parts lists all the time and again the LOD does not change from the last active configuration
Can you go into more detail about why you don't want to use iAssemblies? Maybe there is a different way to use them to address your needs.
I thought I read that you expect vault to be up and running in a few weeks/months. You might want to set up a test environment before you go live so you can see what effect vault will have on your automation process.
There is are a few limitations with Vault and iParts\iAssemblies:
1. you can't move the factories or childern of iParts\iAssemblies from one directory to another in Vault.
2. if you make a change to the factory, you will need to checkout, update, and checkin all of the childern of the iParts\iAssemblies
I also wonder if the improved copy-design functionality in vault will allow you to make copies of your template assembly (and all drawings, etc), run your iLogic rules against the copy, delete the extra components, and open the copied drawings with the correct quanties.
Worth setting up a Vault ADMS on your workstation for testing in my mind.
Hmm, we have several iLogic template assemblies that manipulate the configuration of designs by suppressing and unsuppressing components. Including components that may be suppressed and unsuppressed in different groups so their quantities will be different between different configuartions.
We primarily only have two issues occasionallly. If the assembly and the drawing is open at the same time occasionally there will be saving issues where the drawing is refencing the iLogic LOD but IV wants the assembly to be at master LOD to save. Not always though. Majority of the time it seems to save fine from the iLogic LOD. One thing we've discovered is that modifying the assembly while the drawing is upon is when this error mostly happens.
The other issue we occasionally have is while opening the drawing it will revert to the master LOD. But it's not to big of a deal and doesn't happen much. We are using the vault and don't seem to have to much of a problem opening files already at the iLogic LOD.
The biggest irritants with LOD seem to happen if you are editing the assembly and a drawing referencing it is open at the same time. Seems to loose which LOD is active and which one should be active.
many many worflow on here
I try many but nothing work for me
I have parameters "TR" in my master sketch "B SKETCH"
but not abble to see this parameter? or it's my rule how have a problem???
Sorry for my horrible english and thanks for your help