We’ll start this iLogic tutorial by informing you that there is no built-in cutlist functionality in Autodesk Inventor –parts lists, sure, but a parts list in most cases is about as useful as teats on a bull. I will likely go back later and split the top and create a glue-up schedule as well, but for now, an automated cutlist.
I cobbled together the technique used in this iLogic tutorial back when iLogic was a subscription bonus add-in a few years back. It uses Custom iProperties to hold WIDTH, LENGTH, and THICKNESS values on a per-part basis. These values are filled in automatically using and iLogic rule that reads parameters in the parts, and are then used at the drawing level in fields of the same name.
This tutorial builds upon the twenty three previous tutorials in the Shaker Table series. On with the Cutlist Tutorial. Begin by opening up the Designing a Shaker Table with Autodesk Inventor.iam (the assembly). From there open the layout part which should be at the top of the list in the Browser Bar. We need to know all of the parameters that describe the width, length, and thickness of the Leg A solid body so that we can bring them into the assembly. Looking at the Parameter Editor, we can see one of them, Leg_Width…


For the thickness, I went to the solids folder, expanded the Leg A solid body, then double clicked on the Leg A Ext extrusion. As you can see in the image to the right, we used the same Leg_Width parameter to get the thickness. Now all we need to know is where to find the length.
To find the length, again we use the solid body to find the info we need. Everything about the leg in question can be found by expanding the Leg A solid body and looking. In this case, we need to expand the Leg A Ext extrusion, and double click the underlying sketch, the Leg Profile A sketch. As we can see in the image to the left, the length of the leg is controlled by a formula within the d20 parameter (your number may differ –it doesn’t matter a lick). Finish the sketch, that’s all we need to know.
Now fire up the parameter Editor and find d20 (or whatever you have), and change it to Leg_Length. The only reason for doing this is for clarity sake. We will be using this parameter in formulas later, and a cryptic d20 does not convey design intent (a lot of modelers out there really suck at this, and it makes things much harder for those down the line).
With that done, we will switch back to the Designing a Shaker Table with Autodesk Inventor assembly, and double click the Leg A part in the Browser Bar to activate the part in situ. Then right click on the derived layout part within the Leg A part, and choose Edit Derived Part…

We are going to be bringing in (Linking) the two parameters we just refreshed our memory about. To do so, expand the Parameters list, then the Model Parameters list. The former d20 parameter –now named Leg_Length should be clicked to change its status to Derived. Do the same in the User Parameters list to bring in the Leg_Width parameter. Click OK to finish up.
Now would be a good time to add iProperties to your Quick Access toolbar (if not there already). We will be using iProperties quite a bit, and this will make things more convenient…

Now launch iProperties, and click on the Custom Tab. Add three Custom iProperties with the Type set at Number:
- 1. WIDTH
- 2. LENGTH
- 3. THICKNESS
They will order themselves alphabetically in the Custom iProperties window –pay the order no never mind. Click OK to add these Custom iProperties. Now for an iLogic Rule to connect the new iProperties to the parameters we linked earlier. Create a new iLogic Rule called Parts List. In the iLogic Rule Editor, go to the System Tab of the Snippets column, expand the iProperties list, and double click Custom. Hit enter and do it twice more so that you have three snippets stacked atop one another.
Here is where things suck a bit. For some reason, Autodesk neglected to add any way to access iProperties from within the iLogic Rule Editor. One way around this is to copy and paste the iProperties you will be manipulating into Notepad or another text editor –or try to remember the ones you need, and hope to get the exact spelling correct (otherwise your rule will fail). Lucky for us, we have the list above.
Change the three PropertyName place holders to the ones listed above…

…then tie them to the parameters we linked earlier by clicking on the Linked Parameters on the Model Tab to expose the two parameters, adding an equals (=) sign after each iProperty snippet, then placing the insert hash mark after the = sign and double clicking the correct parameter –except for the thickness. We know that it is the same as the width, but for illustration of a later feature, just add the number 66 (or any other number)…

Now, open your iProperties thingamajig. Switch to the Custom Tab, and there you have it…

So-far so good. The thickness is obviously jacked up, but we know that now don’t we? We need to repeat the above steps on the other three legs, except for the fake 66 value –put a different value in each of the other legs –it sucks, but we need to do it all three more times.
I’d like to say you can go ahead and do the same thing on all of the parts, but you can’t, so wait. I haven’t modeled further than what you see here, but I do know that at least one driven dimension is needed on the bracket, and we haven’t covered that
That will wrap up this iLogic Turorial. The next installment should be tomorrow. Later.
Mark
Subsribe to Post Notifications






Hi Mark. Teats on a bull lol. At the point of changing the parameter name on the leg, I'm thinking you should mention the "check export" button. Users will find the pop up screen telling them about "selecting a non-exported blah blah blah" anyway but they may not get why that is popping up. I'm still running through the tutorial and will let you know how it went. I figured a pretty cave man-ish way of doing it myself, but I figured I would wait to see what you had to say.
Hi Kent,
I didn’t even think of that. I don’t get that pop up –I have it shut off like many of the other useless pop ups. I just select them on the ‘other side’ which retroactively selects them for export back in the part. Maybe someone will comment with another take on this, but I am inclined to tell people to just shut off the message as I have done.
I’ll run some quick tests tomorrow to see if there is any utility beyond exporting to XML. I don’t think there is. Thanks for the heads up Kent, and please share your technique. I love new stuff!
Mark
The little stuff for us beginner guys may be difficult for you to see since it is probably second nature. Until you just mentioned that part about turning off the prompt, I didn't know you could do that until I expanded the dialog box. Now it's shut off. I can see how making the parts list can be an excruciatingly long and tedious process if you have a large assembly. I guess for us guys that are going to be programming just a few parts, we will be one of the lucky ones who get to do it once or twice then it's automatic from that point on.
I noticed on one of your later videos that you had a parts list with grain direction and you indicated it with z+. I hope someday you could explain your method. I too would need to know in the shop which way the grain is going, but I default myself to "length" = "with grain", but it does get confusing.
Hi Kent
I’ll have to do a new post on where to shut things off and what can be safely shut off. The draft posts just keep piling up –but that’s a good thing!
Setting up a model for automated output is a royal pain in the ass, but the end results can save enormous amounts of time. If you are a small manufacturer and are only going to make one or two of an item, you shouldn’t go through all of this. Just make a drawing and dimension it –hell, maybe even just get a dimension or two off of the screen. I just built a house that way.
The coordinate scheme was for CNC placement if I remember correctly. I’m hoping to get someone with more CNC experience to guest post soon.
Mark
I found a pretty similar way to what you just described when I was working on a separate project. I ended up tweaking the standard ipt file to include the custom iProperties (L,W,T)and used it for the file to use when making components. This way the length, width, thickness was automatically included. But I took a slightly different route after that and I'm guessing it's one of those either/or things. Both work the same way, though I didn't use any iLogic.
Did you create a template? If not, I'll do a quickie how-to tomorrow. I've had a draft half way done for damn near a year and should start pushing some of them out. Basically you go to:
C:UsersPublicDocumentsAutodeskInventor 2012Templates
Create a new folder there with whatever name you wish, and save any custom parts in that folder (or copy and paste other templates to test it out). Now go to Inventor and start a new document. Your folder will be a tab in the "New File" dialog, and parts placed in the folder are now templates that can be used throughout the program. I create these for clients, and archive them between jobs for said client. Pretty slick.
Sorry, yeah that's what I meant. I made a new ipt template using the standard ootb and saving it under a new folder name, thus making it a new tab like you said. I'm constantly tweaking and updating my own custom templates as I go. It's a PITA but life gets better as you go.
I basically end up with a similar ending to what you have but instead of using iLogic, I just open up my parameters after I double click the part in the browser. I then used the link button and selected the multi body ipt file used right before "make components". This created the ability to select the multi body part parameters from the little arrow selector in the equation part of the parameters dialog box.
Also on the last dialog box of "make components" , I messed around with the "include parameters" button which I essentially selected all of the named parameters to be placed into the single part files, which made it messy, but quick. It's a trade off if you have a great naming system that is easy to remember what the hell your parameters are referring to. If it's for a multiple user environment, probably not a good idea.
BTW, why does my assembly view and modeling view selection keep changing in the browser? It keeps changing back to assembly and I can't figure out why.