I will have to look in the log file for the offsets. But the Axes are still where they were paused. I am not entirely clear how to open the log file but will attempt to poke around and look for it when I get home this evening.
Hey B.
you can open the log file /var/log/bbctrl.log with the usual text viewers installed on all unixoid systems like less that has a search function that highlights matches like “offset”, or text editors, and of course you can search for strings with grep. The text editor nano is installed that also has a search function.
The axes moves that the g-code makes usually look this way:
I:Comm:> {"xp":20.987,"yp":10.052}
After you pressed pause on your g-code program:
I:Web:200 PUT /api/pause (192.168.***.**)
I:Comm:> {"xp":21.124,"yp":10.06,"v":0,"xx":"HOLDING","xc":71,"pr":"User pause"}
In this example, 21.124 and 10.06 are the X and Y positions after the program was paused.
Regarding the offsets, the last XYZ probing or G92 occurrence usually looks this way (these are the offsets in the offsets column then):
I:Planner:set(#58, offset_x, -15.0)
I:Planner:set(#59, offset_y, -20.0)
I:Planner:set(#60, offset_z, 15.0)
Note that /var/log/bbctrl.log is subject to logfile rotation. Should the file be empty, you find the older log under bbctrl.log.1.gz (view with zcat, uncompress with gunzip)