I believe this is a bug in the cloud.
After running each ‘motion’ file, the device resets its position to 0,0, and it lets the cloud keep track of where the head is located.
When you see “Scanning Material”, the device receives a ‘motion’ file from the cloud telling it where to move to so it can take the thickness measurement. After it is done, the cloud sends another ‘motion’ file to send it home*.
This is where the potential bug lies. The return motion sends it back to -1,1, instead of 0,0 (there is an extra “step” for each axis), but the device resets its internal position counter to 0,0 after the move.
Every scan (print) cycle results in an additional position error on both X and Y axes of .01875 mm. Doesn’t sound like much, I know. But if you never turn your unit off, it will accumulate over time.
It also could be that there is some hardware/firmware issue that I haven’t located yet that they are accounting for by adding the extra steps (I hope not).
*This is different when it sends a ‘print’ file. In this case, the device keeps track of where it is, and returns home based on its own tracking of its position.