Open mvbnano opened 6 years ago
Please also include example configuration - you can see an example of this in ntmdt_piezo_stage.py
on branch dev_ntmdt_stage
.
class PiezoStageNTMDT(Base, MotorInterface):
"""unstable: Matt van Breugel
This is the hardware module for communicating with NT-MDT piezo scanning stages
over USB (via the NovaSDK dll). It uses the VB script from the documentation.
Example configuration:
# ntmdt_stage:
# module.Class: 'motor.ntmdt_piezo_stage.PiezoStageNTMDT'
# scanner: 1
# constraints:
# x_range:
# min: 0e-6
# max: 100e-6
# y_range:
# min: 0e-6
# max: 100e-6
# z_range:
# min: 0e-6
# max: 6e-6
```
"""
_modclass = 'PiezoStageNTMDT'
_modtype = 'hardware'
Remember to connect _do_move_abs
as was specified in issue #16
What is affected by this bug?
Constraints management for newfocus pieze screws needs to be inline with best practice.
When does this occur?
Currently, the config is loaded and the constraints are set as class variables in
on_activate
.Where on the platform does it happen?
In
piezo_screws_newfocus.py
on branchdev_newfocus_screws
.Expected behavior (i.e. solution)
Constraints should be loaded in
get_constraints
. A dictionary is returned here, which can then be made a class variable, ie something like this:Other Comments
If required, a good example of this is in
ntmdt_piezo_stage.py
on branchdev_ntmdt_stage
.