Accelerating ANYCAD Importing with Inventor (DELETE OTHER POST)

[janelson33]

Please delete the other post, I did not realize that it was still in the IT account.

Hello,

We receive these ANYCAD format files (STEP, IGS, X_T, etc.) and I have been thinking that I can automate my clicks.

I think VBA editor or Macros (based on what they can do in MS Office products) are the go-to instead of iLogic since I am looking to record clicks (if even possible). Most of these are assemblies that I would be working with, so the example I show will be what I am doing for IAM files.

Regardless, the flow is like this for solid body component files:

->Import as Inventor file (IAM)

->Ground all components

->Open component and navigate to Document Properties

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

For surface model parts, the flow is like this:

->Import as Inventor file (IAM)

->Ground all components

->Open component and perform Surface Repair when required

->Navigate to Document Properties

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

I imagine that one of Inventor's features should allow this to happen. Conversely, if this is not really possible, it would seem like I would need to create iLogic or VBA for those singular aspects outlined above, and just run those individually?

[janelson33]

Please delete the other post, I did not realize that it was still in the IT account.

Hello,

We receive these ANYCAD format files (STEP, IGS, X_T, etc.) and I have been thinking that I can automate my clicks.

I think VBA editor or Macros (based on what they can do in MS Office products) are the go-to instead of iLogic since I am looking to record clicks (if even possible). Most of these are assemblies that I would be working with, so the example I show will be what I am doing for IAM files.

Regardless, the flow is like this for solid body component files:

->Import as Inventor file (IAM)

->Ground all components

->Open component and navigate to Document Properties

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

For surface model parts, the flow is like this:

->Import as Inventor file (IAM)

->Ground all components

->Open component and perform Surface Repair when required

->Navigate to Document Properties

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

I imagine that one of Inventor's features should allow this to happen. Conversely, if this is not really possible, it would seem like I would need to create iLogic or VBA for those singular aspects outlined above, and just run those individually?

[Frederick_Law]

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

All of those are set in ipt, iam template files: Standard.ipt, Standard.iam

[Frederick_Law]

->Set Linear Units as desired

->Set Angular Units as desired

->Set Linear Precision as desired under Modelling Dimension Display Category

->Set Angular Precision as desired under Modelling Dimension Display Category

->Toggle dimension view to Display precise value under Modelling Dimension Display Category

All of those are set in ipt, iam template files: Standard.ipt, Standard.iam

[janelson33]

I know. That has nothing to do with what I'm asking however. Autodesk does a middle-tier job at marketing exactly what tasks, schedules and operations things like iLogic and VBA can do. Everything is geared at people who are making slight variations of the same part, DWG import or rules about what to do with certain parts when in assemblies.

I am an ME, therefore know essentially jack-diddly about coding, but I am curious as to whether I could create something valuable for the company. Hopefully this Screencast helps everyone understand the clicks (process) I am trying to capture and execute.

https://knowledge.autodesk.com/community/screencast/95b80b1b-0524-4584-89dd-28f05294daed

[janelson33]

I know. That has nothing to do with what I'm asking however. Autodesk does a middle-tier job at marketing exactly what tasks, schedules and operations things like iLogic and VBA can do. Everything is geared at people who are making slight variations of the same part, DWG import or rules about what to do with certain parts when in assemblies.

I am an ME, therefore know essentially jack-diddly about coding, but I am curious as to whether I could create something valuable for the company. Hopefully this Screencast helps everyone understand the clicks (process) I am trying to capture and execute.

https://knowledge.autodesk.com/community/screencast/95b80b1b-0524-4584-89dd-28f05294daed

[Frederick_Law]

VBA, macro, ilogic, addin don't do "click".

So you can't write code to move muse, select menu and click.

It can't capture user input and make a program.

They use internal commands.

The developer need to find out which command got executed.

So developer need to go through API help and see what commands are available.

(It is possible to simulate mouse and keyboard input but it doesn't use Inventor API)

(Software company use that to do automated testing on their software)

With that said, lots of thing can be done without programming.

BTW I'm ME also.

[Frederick_Law]

VBA, macro, ilogic, addin don't do "click".

So you can't write code to move muse, select menu and click.

It can't capture user input and make a program.

They use internal commands.

The developer need to find out which command got executed.

So developer need to go through API help and see what commands are available.

(It is possible to simulate mouse and keyboard input but it doesn't use Inventor API)

(Software company use that to do automated testing on their software)

With that said, lots of thing can be done without programming.

BTW I'm ME also.

[janelson33]

I thought it would be unlikely to be able to record the clicks, but I wanted to make sure since Macros/VBScript essentially work like that in Excel and I wanted to clear that up a bit (I'll do my more research there).

It does seem like I would at least be able to create and run a code/program/trigger for VBA once I write it however. From my reading and watching, when it is internal to Inventor most of the times iLogic seems to be the winner. When I need to go in between Autodesk or VBA programs, I should stay in VBA. VBA is going to me more reliable, and I can check the code in a compiler too, so it seems more advantageous all around if you don't care about the calling of a special face/feature/parameter or whatever.

Now I just have to write the code/rule/script/trigger for each different task. There would be a Trigger I click that executes an iLogic/VBA code to change the units from mm to in, and so-on-and-so-forth. Looks like it's time to get back to YouTube and the small help Autodesk does provide so I can get this rolling.

Thinking about it now, the task scheduler might be great for getting all ANYCAD files imported and converted to Inventor world, then I'll spend less time with that and can just run my codes on the files themselves to change their dimensions and precision.

[janelson33]

I thought it would be unlikely to be able to record the clicks, but I wanted to make sure since Macros/VBScript essentially work like that in Excel and I wanted to clear that up a bit (I'll do my more research there).

It does seem like I would at least be able to create and run a code/program/trigger for VBA once I write it however. From my reading and watching, when it is internal to Inventor most of the times iLogic seems to be the winner. When I need to go in between Autodesk or VBA programs, I should stay in VBA. VBA is going to me more reliable, and I can check the code in a compiler too, so it seems more advantageous all around if you don't care about the calling of a special face/feature/parameter or whatever.

Now I just have to write the code/rule/script/trigger for each different task. There would be a Trigger I click that executes an iLogic/VBA code to change the units from mm to in, and so-on-and-so-forth. Looks like it's time to get back to YouTube and the small help Autodesk does provide so I can get this rolling.

Thinking about it now, the task scheduler might be great for getting all ANYCAD files imported and converted to Inventor world, then I'll spend less time with that and can just run my codes on the files themselves to change their dimensions and precision.

[Frederick_Law]

You can program import all files from a folder.

Don't know if you can program repair.

Changing precision etc can be don't before saving the file.

Did you import a STEP file?

Usually STEP import pretty good and should give you mostly solid instead of surfaces.

[Frederick_Law]

You can program import all files from a folder.

Don't know if you can program repair.

Changing precision etc can be don't before saving the file.

Did you import a STEP file?

Usually STEP import pretty good and should give you mostly solid instead of surfaces.

[Frederick_Law]

There are 3 way to program for Inventor: Macro (VBA), iLogic and Addin.

Macro and iLogic are build in with Inventor.

Addin require Visual Studio.

I started with VBA Macro and moved to Addin with VB.Net.

Planning to move to C#.

Didn't do much with iLogic.

Technically VBA is dead.  Don't know how long it'll be around.

[Frederick_Law]

There are 3 way to program for Inventor: Macro (VBA), iLogic and Addin.

Macro and iLogic are build in with Inventor.

Addin require Visual Studio.

I started with VBA Macro and moved to Addin with VB.Net.

Planning to move to C#.

Didn't do much with iLogic.

Technically VBA is dead.  Don't know how long it'll be around.