manufacturing extensions: what are toolpaths behavior with pay as you go?

[pmesten18]

I am curious how these new extensions will behave regarding a pay-as-you go structure.

I am happy to see steep/shallow is now an option, but I do not know how it may work if I only have periodic demand for the toolpath. here is an example:

-I buy 200$ worth of cloud credits (only needing 125, I have to buy more than required.. feels like the hotdog/bun racket)

-I program a part using the steep shallow toolpath, hole recognition, and probing inspection and make it within my 1 month period.

- I let the extension contract lapse after 1 month.

Now my question: I need to go back and make the same part 4 months later: what are my limitations without purchasing another 200$ of cloud credits?

Can I re-post my code again?

Can I go and edit the tool# that is used in the steep shallow?

Can I re-generate that code?

Can I even open the file?

Can I add other toolpaths to this file?

I can understand this contract based model for features like inspection probing, and additive manufacturing, as they seem to be fairly stand-alone functions, where you can probably use/re-make your existing work without using/owning these features.. but a toolpath could easily make it so my file would effectively be hostage to paying 200$ any time I may want to use it again in the future, unless I save my G-code.

Depending on the behavior of a file using contracted toolpaths, this could get out of hand. I won't want to use them if it will lock me out of using these files in the future. We need more information besides excited advertising about how we will be able to "leverage more technology when we need it" if it will come with a significant handcuffing when we don't own it. 

[HughesTooling]

I think the tool path will be in your setup but you'll get a message about not have a license for the feature. 

You get something similar if you enable beta mode and add a blend toolpath. Give it a try, info on enabling beta mode here. With the beta mode disabled you can't edit a blend you created before but you can post the code, don't know if this will be the same for extensions though. There's no problem adding more toolpaths or more setups.

Mark

[HughesTooling]

Attached is a test file with a step\shallow toolpath you can try.

Mark

[jeff.pek]

Mark is spot-on here. This behaves just like the different levels we've had in HSM products (and Fusion) for years:

 - You cannot edit or regenerate toolpaths that use types not available to you with your current entitlement.

So, you'll be able to post, simulate, etc., but not edit or regenerate.

Jeff