differences ilogic modules, iassembly and ipart

[INVENTORMUSTDIE]

hi, I can't quite understand the deference with predictions and defects between ilogic, iassembly and iparts modules. I have a set to add parammetrized sub-axis to be modified as I want. what would be the best way to proceed? And why?
Thank you

 

[mihele]

iassembly and iparts are the same excise thing that with iassembly you can insert as many iassembly and iparts as you want.
ilogic is programming with the sql language a set or an iparts deciding what to do as a color change or decide whether to replace a piece or other, in short, program a set of commands.

 

[INVENTORMUSTDIE]

thanks for the answer, but I wanted to know if I make parametric models to insert them in turn into other axiemes, is it better to use the method of modules made with ilogic or use the method of the various measures that are compiled by making an iassembly? and I wanted to know advantages and disadvantages between one and the other method.
Thank you

 

[Catafratto]

iassembly and iparts are the same excise thing that with iassembly you can insert as many iassembly and iparts as you want.
ilogic is programming with the sql language a set or an iparts deciding what to do as a color change or decide whether to replace a piece or other, in short, program a set of commands.

I'd say a little confusing.
starting from ilogic:
- programming language is a basic dialect, not sql;
- can handle parts (not only iparts) and assemblies;
- allows to manage a little all aspects of modeling; removal/habilitation of processing, choice of material, reading and changing parameters values (for example, from the main aid to parts and vice versa), compilation of iproperties etc. etc. you can also quickly create simple data entry masks.
pro: power and flexibility
conversely: you have to have at least the basics of the programming to be able to exploit it, but it really takes little to begin with and there are numerous "code pieces" proposed automatically. I had done only a few tests and then abandoned ilogic components because:
1) file names generated for me were not good, but this is a very subjective question.
2) It was complex to reuse existing parts.


ipart:
excellent for components easily manageable through tables, you can basically copy catalog items with their table (e.g. supports or bearings but also everything to your design), you can also put the various members on the table (including flags if you are interested). for each row of the table is created a file connected to the main ipart.

iassembly
would be the equivalent of iparts in the environment together, or a table would manage the types and quantities of the iassembly member; However I have never deepened so much because (follia of the follies) with the iassembly skips the separate management base and this for me has always constituted an insurmountable obstacle; I can try again, maybe with 2019 something changed and in case I report.
https://www.cad3d.it/forum1/threads/distinta-isassemby-problema.48589/http://help.autodesk.com/view/invntor/2017/ita/?guid=guid-6e529299-cab9-4f5c-b100-7901d877b83fwanting to restart, what I would now do is an ipart + ilogic hybrid (the iparts for the parts to always reuse, ilogic for other metal profiled components to measure); I wouldn't waste time with assembly.

If I were you, I'd try to experiment with simple iparts so much to understand them a little better, they're still useful.

 

[Catafratto]

other important thing to keep in mind is how to handle the tables, if this is an important thing in your case; with iparts is relatively easy, with iassembly should also (but the distinct! ahimè...), with ilogic you have to throw down code lines.

 

[INVENTORMUSTDIE]

Thanks for the answer!?? ? ! much clearer and direct than any other guide I read!! ?

 

[mihele]

catafract, good I have not been clear and precise, in fact it is as you say, let's say that for a year I use inventor without making any course.
I actually thought I'd create an iassembly, but I need a separate table set, so I think I can't use it, right?

 

[Catafratto]

by doing other tests (as I said I had left iassembly years ago) I suppose I had to remand part of what I wrote about iassembly: in the table the distinct seems to work normally. However I seem to remember from old posts that there were problems with the quantities in some cases, but I do not remember which (and perhaps the problem was simply solved over the years), the evidence that I have done so far seems good... I said that, they still seem a bit snout and I would still be undecided if using them... you should do some simple test iassembly and see in person if the game is worth candle.