Why does useWCS default to false in the fusion post processor?

[greenleaf]

Not a complaint, but something I was wondering. It looks like the default action of the fusion post processor changed between the mach4 version and the EX version. For the EX you need to click a parameter to output the coordinate system selected into gcode, where previously you didn’t.

I was curious what the history of this was. I imagine it was to make things easier for the average user in some way, but I wasn’t sure if it was to make the gcode always just use the currently loaded coordinate system, or if there was a deeper danger in wcs that made it only suitable for advanced users.

[Eric]

@greenleaf

For the EX you need to click a parameter to output the coordinate system selected into gcode, where previously you didn’t.

This is correct we set it that way because…

@greenleaf

I imagine it was to make things easier for the average user

This is exactly why it was done. Most users just use the default G54 WCS. In some of our video guides we show how to switch that to add different fixtures.

Vectric products do not switch the WCS for you (they have no ability to do this) so when you start a job it will run on whatever the last WCS you have picked. Changing the default behavior in Fusion was done to mimic this behavior.