I managed to get back.to the real 0,0, but the next spindle toolpath went off course by about an inch once it started running (which is bizarre, because it is a job I have run multiple times successfully). The subsequent toolpath ran successfully…but unfortunately too late as the project was already ruined.
@GregM FWIW, Greg, I can duplicate your problem in both gSender and in Edge. If I set an offset and immediately toggle it, it is fine. As soon as I run a file, though, then toggle it, the numbers are off the map. If I disconnect from the Mill, then re-connect, all is well again.
We’ll have a fix for this in the next version. What’s likely happening is your sender is set to MM preferred units, but the file is G20 (inches) - when it sets the offset it’s setting it as 70 inches away instead of 70mm since the offset uses the current unit modal. This also maths out to the numbers you’re seeing. We’ll make sure the offset is set with the correct modal in mind.
Contradiction is fine, but this is 100% an issue with unit modal that we handle now. Modal is persistent after the toolpath is run so it doesn’t matter if a file is currently loaded or not. This is reproducible consistently manually in the console with gSender in Metric preferred units:
G21 (we’re in MM on the firmware)
Toggle Laser offset on and off - X and Y values are as expected.
Jog a little as if moved by a toolpath - toggle laser offset on and off - X and Y values are as expected.
G20 (now in inches)
Toggle laser offset on and off - offset is now (70.52, 12.89) inches away - which is (1791.2, 327.41) mm.
G21 (Back to mm)
Toggle laser offset and and off - offset will be (70.52, 12.89) from previous location as expected.
From your verification - this fixes it because the default firmware modal is G21 on connect/soft-reset.
@GregM, just an fyi, you can do your workspace layout in inches if you wish but when it comes to running your toolpaths use the mm post processor instead of inch. Vetric will do the conversion calcs for you.