Work offsets last between powercycles…
Does CM use work offset 1? Or does it just track the offset inside the software and restore it when connecting to the machine?
Tried something out.
- Set work offset 1 and 2 in gSender.
- Opened up CM. Initialize, went to an arbitraty location, zero’d all. Quit.
- Opened up gSender to view work offsets with
$#, and it looks like work offset 1 is back to 0/0/0.
So I’m guessing CM does everything internal to the software. The only way to transfer to another program would be to go to the current X/Y/Z 0, reset work offsets, and then make a note of the current position which would also translate to the machine home offset. Fire up the other program (gSender, lightburn, whatever), move to that location, and set the origin/offset/zero to that location.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.