mlz: derive Digitaloutput from Drivable
as the underlying entangle *DigitalOutput may be BUSY and frappy.Writable disallows this. Change-Id: I6e4861c6d014f59ad4cc2355a438130173bf6569 Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/33849 Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de> Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de> Reviewed-by: Bjoern Pedersen <bjoern.pedersen@frm2.tum.de>
This commit is contained in:
parent
89df37462c
commit
2d08f25993
@ -909,7 +909,7 @@ class PartialDigitalInput(NamedDigitalInput):
|
||||
return value # mapping is done by datatype upon export()
|
||||
|
||||
|
||||
class DigitalOutput(PyTangoDevice, Writable):
|
||||
class DigitalOutput(PyTangoDevice, Drivable):
|
||||
"""A device that can set and read a digital value corresponding to a
|
||||
bitfield.
|
||||
"""
|
||||
|
Loading…
x
Reference in New Issue
Block a user