Inventor API and iLogic Tips & Tricks | Autodesk Virtual Academy

[@WillEhrendreich]

Woot! You guys rock! Thanks for the great content always! I love the automation and API stuff!

[@KETIVTechnologies]

Thanks Will! Make sure you are subscribed at ketiv.com/ava to get weekly emails updating you with each week's topic!

[@johnstondesign3687]

Great video .... I'm definitely going to try some of these rules in my models.

[@KETIVTechnologies]

That's great to hear! Be sure to subscribe at ketiv.com/ava to be notified of all our future topics ahead of time!

[@fjnagle2nd]

I would be really interested in an explanation of the syntax for the API. The VB stuff is pretty east to figure out. The API syntax not so much.

[@KETIVTechnologies]

Thanks for reaching out Frank. You can learn more about the API syntax via Autodesk's dedicated api API Documentation here: help.autodesk.com/view/INVNTOR/2020/ENU/?guid=GUID-5901102A-F148-4CD4-AF50-26E2AFDEE6A7 Best,

[@GIFD]

I usually have an assembly with a skeleton and parts derived from the skeleton. In the skeleton I have equations that are used to calculate a number of bolt holes based on the length. The parts are derived from the skeleton and get the length and hole quantity parameters this way. I then need to bring back that number of holes from the skeleton to the assembly level so I can assemble the bolts. I saw that I can use the LINK in fx to get the number of holes from the part up to the assembly, but I am pretty sure it will break when copying design in Vault. Should I instead have all my parameters and equations at the assembly level and pass the parameters down with the method in this video? I also want to use a form at the assembly level. What's the point of having a skeleton part then?

[@xSebbz]

Awesome video´s you guys are making! I understand a bit more little by little. I´m working on a school project myself and I´ve spent countless hours (days) trying get a good understanding of the Inventor API and the coding for it so I can automate drawings and reduce repetitive tasks. I think I´ve spent so much time on it the last couple of weeks watching and reading content that I'm a bit overwhelmed and I've lost clue of where to start. Do I need to know about the API, coding or iLogic. Maybe I need to focus on the basics of .NET or using C# or just coding overall or do I just start tingling around in Inventor?!?! As you can see, overwhelmed by content. Maybe you guys can give me a clue.

[@KETIVTechnologies]

Check out our new Automation Tool Kit which will hopefully help with your school project! ketiv.com/automation-diy-kit/

[@Anirudh989]

Is there an advantage to setup automatic dimensions through inventor API and attributes when compared to an approach where you manually dimension a template and simply replace model reference in the drawing? I currently have a simple flanged pipe assembly that I have set up for automation via iLogic and API. When I run the create drawing rule it opens up a drawing that I had previously set up to use as a reference and then it simply replaces the model in that drawing with the one that was just created. I'm wondering if using attributes and API to create dimensions from scratch would offer anything that the other method doesn't.

[@KETIVTechnologies]

Thanks for reaching out Anirudh, Unfortunately, it's hard to evaluate any reliability issues with your approach without first seeing your work first hand. Your issues (if any) may even be solvable without strict API. Best,

[@vinamragehlot572]

I'm working on a project that'd require me to have 1000s of CADs with small variations, have them saved in separate folders, with a snapshot in ISO view. The part then will be simulated and stresses need to be evaluated, along with transforming each CAD into a point cloud(separate python libraries for that). Would, in theory, this can be done through VB in inventor? I have average programming skill, but would love to know if it's possible in theory or not, before I go neck deep into it.

[@KETIVTechnologies]

Good question, you might want to check the Autodesk VB forum which is monitored by Autodesk. forums.autodesk.com/t5/vba/bd-p/33 KETIV | Nicole Morris

[@KETIVTechnologies]

Without knowing more about the variations that are required it's hard to say yes. In theory that's probably the best way to go. KETIV | Matt Bussey

[@vinamragehlot572]

@@KETIVTechnologies Variation would be as simple as placement of a feature(Rib/hole) with respect to faces/plane, or thickness of the overall part.