iLogic, iParts & Part Files

[llorden4]

I'm attempting to expand my abilities with iLogic and I've found a number of tutorials & threads on using iLogic with iPart tables but all of them appear to work at the assembly level.  I'm wanting to develop & manage tables at the Part level and I'm not finding a lot of help at this level.  I've experimented a bit but haven't had any success in being able to retrieve any data, much less modify it.  The iPart family wants the "PartName:1" which (I believe) is only found within assembly files, so I have not been able to access any data from the iPart table from within the .ipt file, even by omitting that feature in the iLogic line.

The usual question is what am I trying to do?  In this instance, I have parent part that will have a small range of variables and I'd like the iPart table to help me manage these vs relying on the user/drafter as the variations can create a rather lengthy table and requiring a VERY keen eye for comparison.  Variations include thickness of material, size of hole, length of part, width of part, etc.  I can use these variations to drive a part numbering system but I also have to develop a second numbering system that simplifies it to basically the next available number in sequence (a dumb number) that is short (for the monkies we dangle banana's in front of) to identify the physical part vs a mark on the drawing.

There's a few things I'm trying to accomplish for the drafter...

1) Search the table to determine the number of line entries to determine the next available number available

2) Search the table to determine if the current features (or smart part numbers) all match, if so then activate (or notify user of) that iPart

3) Edit the "Member" name on new parts to add to iPart list

4) Read "Member" name to copy to iProperties("Project","Part Number") field

5) Not cause a paradox

Anyone know of a good tutorial or example problem they'd be willing to share?  Thanks in advance!

[HermJan.Otterman]

can you share your part? with the code you made so far?

[llorden4]

I'm currently setup to manage 9 "Parent" [TS01 through TS09] categories (via iLogic rules) but can accommodate many more.  I've geared up to "simplify" the interface with these part files to a single parent and simply warn the user if the parameters exceed the range of the parent values and direct them to the correct parent part file to use.  I am hoping to be able to manage all categories with a single file if I can succeed with this quest.

[HermJan.Otterman]

I'm sorry, I don't get what you want.

the question is also if an iPart is the solution to your questions...

normally you use the iparts in an assembly, but you don't do that?

note that the in the childparts there are NO iLogic rules..

[llorden4]

I fall into that niche' where I (we) am both designer & manufacturer and I need control from both the part level and the assembly level, and you're quite correct that I might be attacking this problem from the wrong angle.

Basically, I design parts that will eventually be used in assemblies so I need an "ever growing" library of parts that will have a Part Drawing produced in the format of a generic shape with a table of all current members in order to produce the correct part from an assembly drawing that will call out the Member/Part number to identify to the fabrication crews which member out of the list they need to produce.  We may also instruct the production crews to build a frequently used item for stocking purposes.  There are also times when we need crews producing the part before we complete the entire project and this provides us the means to manage that information between departments.  This isn't a norm for many manufacturer's so it's not uncommon that this process is foreign to most.

But yes, at some point we do attach the part to something.  I want to provide some control features to prevent duplicate entries across a series of features and if I manage different parents in one file then I'm also managing a single "master" file and not several similar files.

[MechMachineMan]

Pro-Tip: Get familiar with Autodesk's Documentation on the software that they provide (in both online and offline form).

Your answer to your questions can be found through this link, some reading, some application and possibly some trial and error.

http://help.autodesk.com/view/INVNTOR/2018/ENU/?guid=GUID-FE230CC1-D9A7-4050-9018-2BBE35941067