iLogic Rules - External vs. Internal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I wrote a simple iLogic rule that would write to a Custom iproperty based on the thickness of a sheetmetal part. I have this rule working like a champ and have it embedded in my part (saved locally). Now that I have it working, I decided rather than embedding it in the part, I would store it as an external rule. That way if later I run into something that I have not tested I can fix it in one place.
What I have found is that with the rule as an external rule, it does not work and I cant figure out what the trouble is.
I have attached the part (with the embedded rule) and the external rule. The two rules are identical. This rule does one thing, it writes to a custom iprop called "Gauge " depending on what it finds for the material thickness. For example, if the thickness is 0.1046in, then "Gauge" = 12. If the rule does not find a match, then "Gauge" =N/A.
1. If I use the local rule, then as soon as I change the material style, the correct value is stored in the "Gauge". I am not sure why the internal rule is ran immediately, but it is. There is no trigger set to fire this rule upon parameter change. I just thought that rules either had to be ran manually or set to fire with a trigger.
2. If I disable this local rule, and set a trigger for the External rule "Set Gauge Value_EXT" to fire on parameter change, I would expect the "Gage" value to be set to the correct value. No matter what I do here, it keeps giving me the "N/A", like it cant find a match for the thickness.
Any help would be greatly appreciated.
Thanks,
Kirk
Inventor 2018.3.4