About:
iLogic is a technology implemented in Autodesk® Inventor® software that allows designers
and engineers to introduce automation to design even when they are not experienced programmers.
They can easily build procedures, functions, rules and interfaces for them.
Previously, these activities required knowledge of the basics of VBA programming
and API software, so it was much more difficult than now. More about iLogic you can find
here.
Types of modeling:
When you build an assembly you need to consider how its elements will be created.
Of course, it is easiest to create a base model and then generate parts from
it as derived. Unfortunately, this solution rarely works due to the fact that
almost every company has a database of its standard components. Creating them
each time is not the best option. It is easy to imagine that one part will have
even a hundred equivalents. What if you need to update eg. Description in the parts
list for this item? Instead of one, we will have to correct as much as we generated.
A more difficult solution is to use a part database (Local or ContentCenter).
However, the initial hard work will be compensated at a later time. If you use the
parts database, you don't have to worry about multiple copies of the same item.
Updating a family description will take less than a few minutes - even if you have
to deal with thousands of the same.
Below are a few types of modeling. However, these are theoretical models.
Nothing stands in the way to mix them among themselves.
Derived-To-Assembly:
The main element is the base model, which contains all dimensions, dependencies,
rules, functions, and the user form. Parts of the assembly are created as derived
components of this model. Updating an assembly takes place in the base
model and then moves to the individual elements - all updates run at the same time.
Most of the modified parts are unique. It means that there is no connection to the database
of standard elements and another copy of the same machine may have the same components but as new.
Advantages:
- Assembly as one part
- Easy to edit
- All in one place
Disadvantages:
- Minimal use of standard parts
- Average performance
Note:
If you use this type of solution, you should remember to create a base model as multi-solid.
It allows you to avoid many unnecessary complications and protects individual parts by
interacting with each other.
One-solid part:
Multi-solid part:
Local-To-Assembly:
All dependencies, rules, functions and user form are in the main assembly.
However, the rules can also be in individual parts - it depends on the user.
Replacement of parts occurs through the built-in iLogic function "Replace"
and items are taken from local or network folders using the file path.
Advantages:
- Use of standard parts
- High performance
Disadvantages:
- Missing file to replace causes an error
- Creating Arrays with file paths
ContentCenter-To-Assembly:
Model similar to LTA. The difference between them is that this time the replacement
of parts occurs with the ContentCenter database. Thanks to that, you can easily use
common elements, such as plates, flat bars, pipes and more. The problem of this solution is performance
because the tables in the database are large (the rule searches all rows starting from the first).
You can solve it by dividing one family of elements into several smaller ones.
After that you can refer only to this with the appropriate scope. The efficiency increases several times.
The rule for replacing parts from ContentCenter, you can find
here.
Advantages:
- Use of standard parts
- Use of the ContentCenter
- No error when the reference file is missing but it is defined in the database
Disadvantages:
- Poor performance (however acceptable)
Comparison of models:
|
DTA |
LTA |
CTA |
| Easy to create: |
easy |
medium |
medium |
| Performance: |
medium |
fast |
slow |
| Using standard elements: |
minimum |
yes |
yes |
| Creating revision: |
easy |
medium |
medium |
| Examples of use: |
Push Grate |
Screw Conveyor |
Stoker Feeder |