Issue #44 describes the X stage becoming unreferenced when the software starts. As a consequence of this, the z motion to the start position of the stack never happens. I suspect what happens is the software first tries to go to the correct X/Y position, this fails, and it never proceeds to moving to the correct initial Z position. Despite this failure to move to the correct position, the acquisition still begins taking slices from whatever is the current Z position. Therefore there does not seem to be a final check to ensure that the stages are at the correct position before the acquisition of the stack begins.
I confirm that with the X stage referenced and working properly, the Z stage behaves as expected and stacks are taken from the correct position.
nvladimus
commented
1 year ago
Issue #44 describes the X stage becoming unreferenced when the software starts. As a consequence of this, the z motion to the start position of the stack never happens. I suspect what happens is the software first tries to go to the correct X/Y position, this fails, and it never proceeds to moving to the correct initial Z position. Despite this failure to move to the correct position, the acquisition still begins taking slices from whatever is the current Z position. Therefore there does not seem to be a final check to ensure that the stages are at the correct position before the acquisition of the stack begins.
I confirm that with the X stage referenced and working properly, the Z stage behaves as expected and stacks are taken from the correct position.