Create an Inventor HSM API

[al.whatmough]

We are starting to work on delivering an API for Inventor HSM. This will be made available as a COM library, similar to Inventor’s own API. We are very interested in your feedback regarding what kinds of things you’d like to be able to do in an Inventor-based API.

Initially, we would likely support capabilities along the lines of those supported in the APIs within Fusion 360 and HSMWorks, for example:

• Access to the list of operations in a document
• Generating/regenerating toolpath data
• Checking availability of toolpath data
• Post processing
• Setting model geometry

We expect to be able to leverage an API in Inventor HSM to be able to enable interesting iLogic-based workflows. We’d love your feedback of what you’d do with such a capability.

[ArjanDijk]

I know that there is work in progress, but you still have to understand that HSM and Fusion in basis are not feature based machining solutions that are created to make a full automated system. The API work that is done, approaches this somewhat and combined with modelling power can just cut it.

I assume if there is anything worth mentioning Adesk will do that.

[dylanTEV9W]

Thanks for the correction on the current programming languages that HSM can be driven from. I don't suppose any one has any HSM sample code written in C#, VB.net or C++? If you do I would love to see it! 

[jeff.pek]

Don't know why I can't attach something here, but if you send me your e-mail, I'll send you a small example project in C#.

Jeff

[Chris.Brough]

Hello, i cant seem to find any reference to an HSM/CAM API for use within inventor CAM environment.  Has anything been released for this yet, or is this still a work in progress with Autodesk?

[jeff.pek]

Hi -

You'll find an InventorHSMAddinAPI.chm file in the Help folder, along with a InventorHSMAddinAPI.tlb in the main install folder, which represents the type library exposed by the API.

Jeff

[Chris.Brough]

@jeff.pek 

@ArjanDijk 

have you guys seen any signs that Autodesk will be opening the API to control parameters or create the operations directly?

Currently I'm accessing operation parameters read only but would love to be able to apply an operation template, then assign geometry and tool orientation using the API.  this would be a complete game changer and make it easier for me to hand off work to people with less woodworking experience.  We really struggle with the amount of manual redundant clicks, selections, number entry, etc. for very similar operations from job to job.

we unfortunately are just on the other side of the standard vs custom product line, so the hand-off to production engineers is still a bit cumbersome.

Still lightyears ahead of where we were before with exporting inventor geometry to 3rd party CAM!

[jeff.pek]

Hi Chris - 

No, I don't see that happening. We're focusing mostly on Fusion these days, in terms of moving the solution forward.

Jeff

[Chris.Brough]

That's really a shame if true.  Seems to be leaving all of the pro users in the dust.

We've put a decent amount of effort into integration with our machinery.  Much of this was based on the trend towards opening the API in 2018-19 and the AU presentation from @ArjanDijk around the same time regarding automation with Inventor CAM API.

That said, I understand the focus on F360 since thats where the masses are flocking.  Is the user base of inventor cam just not large enough to justify at least opening the API further?  One could say this would also make inventor cam much more attractive and easier to sell for the top pro customers who want the truly professional integration.  Also open the door for 3rd party CAM add-ons.

[ArjanDijk]

Hi @Chris.Brough. Cool to hear that my presentation gave you good information. In Inventor it is really easy to set up something smart with Ilogic, so in that regard it is powerfull. But we were always limited in controlling MFG. Only if all geometry was available upfront we could set up something reliable.

In F360 we have much more flexibility with pocket recognition, selectionsets and a much more extensive API. Autodesk moved away from Inventor for MFG and so did I. ATM you really need to have something really integrated and easy to machine to make Inv HSM a good businesscase. Otherwise the new functionality in Fusion wins every time.

Still, I miss the ease of programming that Ilogic offered in Fusion.....

[Chris.Brough]

Hi Arjan, I appreciate the reply.  I've been holding off on learning F360 api hoping that Inv would be further developed.  I will start diving into that now.  What resources would you recommend for getting started with the CAM api?

Is there a best practice for sharing an automation script with my team?  Such as making the script available in the assets project?  Or a folder on our shared server drive that would be set as a default script path?