Proxy post-processor

[ltomuta]

I just had an idea but I doubt it is original so I hope someone can point me to an already existing implementation.

I write CAM programs intended for either a 3-axis or a 5-axis machine so using only two post-processors. But I always have to remember to switch between them based on what the current setup does/needs.

What I would like to have is a proxy post-processor that is always the current one and which, after determining if I have 5 axes features in my program or not, would call either one of the two post-processors to complete the processing.

Feasible? Does such a thing exist already?

As a bonus I would maybe customize the proxy to perform some sanity checks on the program, like looking for different tools having the same tool number.

[ltomuta]

I've been looking around into making this works and while it's not yet clear to me if this can be done I learned that at least the "identify duplicate tools" part is a non-issue since that code is already in the post-processors (at least the two HAAS ones that I'm using). However they are behind a if(false) clause and not behind a property that can be turned on/off. Why so, I have no idea. I know it is a bad ideea though, that sanity check should be always on.

[ltomuta]

So far, so good. I have the proxy post processor up and running, able to identify 5-axis work planes and launching the UMC 750 post processor in that case.

Now I have to figure out how to make sure that the post-processor launched has the correct properties as defined by the user instead of hardcoded or default ones, and I'm about done.

Minor annoyance is that a command prompt window flickers when the 2nd-phase post-processor is launched, it would be nice if I could avoid that too.

[ltomuta]

Next challenge: where are user's post-processor settings stored (looks like a .json but not in the same directory) and do they have to be set externally or is the post-processor self loading them?

[serge.quiblier]

Hello @ltomuta 

Sometimes we add code inside a post, to help the end users enhance their post using functions that need to be further refined.

For example lots of the post processors are ready for 5 axis machining.

But the machine configuration is behind an if (false) statement.

You can activate it if you wish, but you the need to complete or tune the code to suit your needs.

We don't add posts properties for everything, because people will be forgetting to "tune" the code.

So we left a template code accessible. You can change it, use it.

But it won't cause any problem to someone who would have accidently activated a property without understanding it's purpose.

Regards

[serge.quiblier]

sorry, i forgot this part:

[ltomuta]

Hi @serge.quiblier,

Looks like you still left something out. 

[serge.quiblier]

Hello @ltomuta 

Sorry i was a bit too fast, and my copy/paste didn't acted as desired.

Then clicked on the post button too fast.

For tuning the default post properties, you need to find where the json file is stored.

Some quick tests on my computer show that : a post stored locally, not in cloud or online library,

the json file is created in a sub folder from the Fusion installation.

Unfortunately this folder will be changing on each update of Fusion.

c:\users\<username>\AppData\local\Autodesk\webdeploy\production\<some_guiid_representing_Fusion_release>\Applications\CAM360\Data\Posts

The json fille will be created in this folder, with the same name as the post using a json extension instead of the cps for the post.

When you have set (changed) the default properties for the post, it will be automatically stored and loader for usage.

It will by default, only store the value altered from the default settings.

Regards

[ltomuta]

Thanks @serge.quiblier 

I've found the file as well but the settings saved there are not loaded when I launch the post-processor with a call to execute(). Only when running it from the GUI, then Fusion takes care of loading them first.

This means that I should either find a way to load them (but I did not see an API for it) or hard-code them and then pass them through execute(). The later seems doable but not elegant.

I was hoping that my own proxy should only have two properties, the names of the 3-axes and 5-axes posts respectively. Then everything would just work if said posts can be found.