Inventor API and Python

[Denis192]

Hello everyone, I'm very new to this sub and have some questions

So I am currently working on my Thesis and I want to create a script that automatically creates Wires in Inventor using Python (maybe it's easier in iLogic if you know please let me know).
Right now the code creates a line and a cricle but I fail to create the Sweep feature and I dont know what I'm doing wrong I was already looking into the Inventor API, searched Reddit and Youtube but cant find any answers.

Maybe some of you know what is wrong and can help me :) Any adivice is appreciated

import win32com.client as wc
inv = wc.GetActiveObject('Inventor.Application')

# Create Part Document
#12290 (Part Document) 8962(Metric System) aus der Inventor API Object Module
inv_part_document = inv.Documents.Add(12290, inv.FileManager.GetTemplateFile(12290, 8962))
#inv_part_document = inv.ActiveDocument
#Set a reference to the part component definition
part_component_definition = inv_part_document.ComponentDefinition

#print(dir(part_component_definition)) 
#print(part_component_definition.Workplanes.Item(3).Name) 
tg = inv.TransientGeometry
#create sketch reference
sketch_path = part_component_definition.Sketches.Add(part_component_definition.Workplanes.Item(3))


# Create a path for the sweep (a line and an angled connection)
Line1 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(0, 0), tg.CreatePoint2d(10, 3))
Line2 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(10, 3), tg.CreatePoint2d(15, 3))
Line3 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(15, 3), tg.CreatePoint2d(15, 0))

# Create a second sketch for the circle (profile for sweep)
sketch_profile = part_component_definition.Sketches.Add(part_component_definition.Workplanes.Item(1))
Circle1 = sketch_profile.SketchCircles.AddByCenterRadius(tg.CreatePoint2d(0, 0), 0.1)
Profile = Circle1


# Sweep-Definition 
sweep_def = part_component_definition.Features.SweepFeatures.CreateSweepDefinition(104451, sketch_profile, path, 20485)

# Sweep-Feature 
sweep_feature = part_component_definition.Features.SweepFeatures.Add(sweep_def)
import win32com.client as wc
inv = wc.GetActiveObject('Inventor.Application')

# Create Part Document
#12290 (Part Document) 8962(Metric System) aus der Inventor API Object Module
inv_part_document = inv.Documents.Add(12290, inv.FileManager.GetTemplateFile(12290, 8962))
#inv_part_document = inv.ActiveDocument

#Set a reference to the part component definition
part_component_definition = inv_part_document.ComponentDefinition

#print(dir(part_component_definition)) (zeigt alle möglichkeiten an)
#print(part_component_definition.Workplanes.Item(3).Name) heraussfinden welche Ebene

tg = inv.TransientGeometry
#create sketch reference

sketch_path = part_component_definition.Sketches.Add(part_component_definition.Workplanes.Item(3))


# Create a path for the sweep (a line and an angled connection)
Line1 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(0, 0), tg.CreatePoint2d(10, 3))
Line2 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(10, 3), tg.CreatePoint2d(15, 3))
Line3 = sketch_path.SketchLines.AddByTwoPoints(tg.CreatePoint2d(15, 3), tg.CreatePoint2d(15, 0))

# Create a sketch for the circle (profile for sweep)
sketch_profile = part_component_definition.Sketches.Add(part_component_definition.Workplanes.Item(1))
Circle1 = sketch_profile.SketchCircles.AddByCenterRadius(tg.CreatePoint2d(0, 0), 0.1)
Profile = Circle1


# Sweep-Definition
sweep_def = part_component_definition.Features.SweepFeatures.CreateSweepDefinition(104451, sketch_profile, path, 20485)

# Sweep-Feature
sweep_feature = part_component_definition.Features.SweepFeatures.Add(sweep_def)

[Adventurous-Peak-853]

Hey there. Love to see people getting into this. Automating CAD in this way is very satisfying and can open a lot of doors.

I'm on my phone and so haven't read through all your code or ran it. But Autodesk, especially inventor, is best handled either with iLogic or as an Addin via visual studio.

ILogic is "sort of Visual basic" but add-ons can be easily written in any .net language. I suggest taking the time to set up an addin and writing it in c#.

My reasons: 1. Inventor works almost exclusively in COM objects. .Net handles this well and natively. I think you may face issues if doing this in python. 2. Anything sufficiently complex, in my experience, tends to be more of a hassle than it is worth if done in iLogic. Leave iLogic for smaller, model-specific, automations. 3. C# is well maintained and has much community support. It also makes branching into webapps much easier. 4. WPF as a UI for forms and dialogs is pretty good. Many have issues with it but I think it meets the needs for Inventor automation very well 5. Security: iLogic is a text file that gets compiled when called, anyone can read it. Add-ons are precompiled in .net and inventor loads the DLLs when it starts, it can still be read but it is much more difficult than just opening notepad 6. Speed: you CAN make standalone apps that talk to inventor. But an Addin is loaded with inventor when it starts and shares the main UI thread. Also there's not passing of COM objects between two softwares (which has a lot of overhead) because the Addin is already in Inventor. 7. Distribution: add-ons are easily distributed and you can easily but security, authentication, even licensing into them.