HSMWorks How-To: Using templates- but not THOSE templates.

All of the Autodesk HSM products are integrated in powerful CAD environments. Let's look at how we can leverage that benefit to create cleaner workflows.

[@TMODCustoms]

I'm happy to have found your page, Thanks bud, great vid!

[@jimnnobody]

Thanks, Rob.

[@ScottMoyse]

Very cool for HSMWorks users. As you've identified not a lot of the workflow can be carried over into HSM or Fusion. Neither CAD product has the ability do the replace in the way Solidworks does, that is a neat feature I didn't know Solidworks had. I think you could get something close using workplanes in the Autodesk CAD products, but the reference rebuild wouldn't be guided. HSM and Fusion can't carry the stock over from the previous job.... still. Which really blows. And no machine configurations ruins the neat presets you had going on with the jobs. You'd have to use keywords in the setup folder name or comments or something to trigger the use of a different post somehow... actually it's probably fundamentally impossible. It just rips my undies how far behind Inventor HSM still is from HSMWorks in so many nice details. Anyway that shouldn't take away from what is a great workflow in HSMWorks.

[@rlockwood2]

Right, while fusion is #notatoy -- I still have a hard time recommending it to serious users, as while the tool path and code generation are the same, I don't think the overall package is mature enough quite yet. To be fair, most of what i'm doing here isn't a designed workflow, it's just a collection of features within Solidworks that pair together nice with the CAM environment. I sincerely hope the same can, either through creative users or implementation of features, be said of Inventor and Fusion in the near future.

[@ScottMoyse]

rob lockwood Agreed... and I get that it's not a designed workflow. But what you have demonstrated is what can be achieved when an imaginative power user puts the pieces together. It's the kind of thing I tried immediately with Inventor. But, it's missing features on the CAM side of things that make a viable workflow like this possible.

[@Max_Marz]

Oh how things change in four years... Is there a better way to do the replace operation now?

[@jdrinkh2o]

basically... always be working in assemblies bro