Hi,
On 11/08/2011 06:14 AM, Nico Stuurman wrote:
>> * Since there is no Stop(), it seems to me that there is no way to
>> cancel the calibration routine, right ?
>
> Correct.
>
>> However, at the moment I'm still unable to call SetOrigin() as in the
>> micro-manager GUI there seems to be no button for that.
>> The SetOrigin() button in the "XY List" seems to be for the XYStage only.
>>
>> * So how can I call SetOrigin() on a ZStage from the micro-manager GUI ?
>
> Even worse, it seems that there is no API call in the Core that calls the ZStage SetOrigin function.
> I just added that function. It should appear in the next nightly
build. Once that is in, you can type the following in the Script Editor:
>
> mmc.setOrigin("ZStage");
>
> (replace "ZStage" with the name of your ZStage), and your adapter's SetOrigin function should be called.
> You can have this happen on Startup by saving a file containing your
BeanShell code named "MMStartup.bsh" in the Micro-Manager directory.
thank you.
Maybe it would be an option to support XYZ coordinates in the "XY List"
dialog ?
This way not only the position of the sample could be stored, but also
the focus position.
Likewise the calibration support for XY stages would be available for Z
stages as well.
Of course there needs to be an option to allow disabling of that
functionality, considering that the possible Z positions change with
each lens.
It also makes me think if my understanding of how ZStages work in
micro-manager is correct.
Assuming that there are physical focusing stages that do not report
their absolute position after powering up, absolute positioning is in
general only possible after the stage was calibrated.
Otherwise the stage would simply not know its absolute position.
This would however also mean that at the moment in micro-manager only
relative stage positioning is possible for Z stages that can not report
their absolute position without prior calibration, right ?
So in the best case the stage would consider its power-up position as
origin. In the worst case the stage reports an arbitrary (uninitialized)
position value and any non-relative positioning command could cause the
stage to travel until it reaches an end of the axis.
If the lens hits the sample during that process, it could potentially
lead to damage.
IMHO only using relative positioning would work as well, but considering
the high price of a lens, I would like to be able to use movement limits.
This way one could define absolute focusing limits (i.e. through the
device properties).
For instance if one would like micro-manager to take a number of
pictures automatically, one could initially define lens limits (e.g. by
positioning the lens very close to the sample and defining this position
as limit).
Then, during automatic imaging, autofocus could only move as close to
the sample as defined by the limit.
This way it would be ensured that the lens can never touch the sample.
Is a functionality like this currently supported by micro-manager ?
IMHO setting limits is also possible with relative positioning, but the
limit would have to be set each time after power-up.
regards,
Stefan
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Locked
