Test Run button resets workspace to G54 about gsender HOT 6 CLOSED

GRBL check mode ($C) performs an automatic soft reset when it toggles off - that is what is resetting your workspace. This is a firmware feature and not something that can be changed by the sending software.

grbl/grbl#992

Test run runs as fast as the firmware can validate the lines since it doesn't have to wait for movement. Most users don't wouldn't want it to run slower since the entire purpose is to verify that the lines will be interpreted correctly by GRBL.

from gsender.

Thanks for the explanation. I wasn't aware grbl did all of that. Perhaps you could add a pop up window warning that workspace origin will be changed to G54 along with a checkbox to not show in the future would save someone from ruining their workpiece. I

from gsender.

I had another idea for a workaround. You could perform a $G before sending the $C to grbl and parse out and save the current workspace from the response. After the $C completes you could then output the saved G5x code that was originally set. Even if grbl fixes this in the future your code should continue to work.

from gsender.

Next release (1.1.3)should restore WCS modals after test run, similar to how Stop File restores WCS after reset 👍

from gsender.

👍 sweet.

from gsender.

@kglovern Sorry to bring this issue up again, but as long as there are no errors in the gcode file, your fix worked perfectly! However when test run detects there is an error in the gcode file, the workspace is reset to G54.
(usually this happens when a large workpieces is shifted and a line goes out of bounds.)

from gsender.