QMAPP-mq / qudi

A modular laboratory experiment management suite.
GNU General Public License v3.0
4 stars 0 forks source link

ntmdt stage xy movement generates MANY warnings #39

Closed mvbnano closed 6 years ago

mvbnano commented 6 years ago

What is affected by this bug?

There are constant warnings displayed each time a movement is made. The warning (see details below) is concerning the z movement of the stage.

When does this occur?

When a xy scan is launched in the confocal, the following warning it constantly displayed:

warning Cannot make the movement of the z axissince the boarder [1e-07,6e-06] would be crossed! Ignore command!

The range [1e-07,6e-06] is the constraints on the z axis.

Where on the platform does it happen?

The error message is being generated inside the hardware module ntmdt_piezo_stage.py.

Expected behavior (i.e. solution)

It should behave as expected.

Other Comments

It does not appear that this is impacting the movement of the x and y axes. You can see below that come count date is still being collected.

Screenshot

image

image

mvbnano commented 6 years ago

The probable cause of this appears to be because the confocal thinks that is is at z = 20um.

image

I am not sure why this is happening. I have ensured that the constraints, for the z axis, in the configuration are set correctly.

The confocal scan can still be run in the xy plane, I will just not move it in z.

mvbnano commented 6 years ago

The stage can successfully scan a single line. However, the below error prevents it scanner the next line.

image

mvbnano commented 6 years ago

Turning it on and off again fixed the single line scan error (I think):

image

latchr commented 6 years ago

The 20 um z position could be due to restored StatusVariables. I would suggest that you clear the app_status directories in the location of your config file. Do this on both the vm and the "master" machine just in case.

You will know if it worked, because when you load the confocal GUI it should show only 0-6um in the z range, and probably put the crosshair at 3um by default (midrange).

mvbnano commented 6 years ago

Thanks @latchr , unfortunately this did not do the trick. Odd behaviour.

mvbnano commented 6 years ago

Fixed in commit 96feb8404f4ddd6ff9e2110cbc0b39078478256c