Markus Zolliker
97034fb998
A proxy module is a module with a known structure, but accessed over a SECoP connection. For the configuration, a Frappy module class has to be given. The proxy class is created from this, but does not inherit from it. However, the class of the returned object will be subclass of the SECoP base classes (Readable, Drivable etc.). A possible extension might be, that instead of the Frappy class, the JSON module description can be given, as a separate file or directly in the config file. Or we might offer a tool to convert the JSON description to a python class. Change-Id: I9212d9f3fe82ec56dfc08611d0e1efc0b0112271 Reviewed-on: https://forge.frm2.tum.de/review/c/sine2020/secop/playground/+/22386 Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de> Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
23 lines
394 B
INI
23 lines
394 B
INI
[node filtered.PPMS.psi.ch]
|
|
description = filtered PPMS at PSI
|
|
|
|
[interface tcp]
|
|
type = tcp
|
|
bindto = 0.0.0.0
|
|
bindport = 5002
|
|
|
|
[module secnode]
|
|
class = secop.SecNode
|
|
description = a SEC node
|
|
uri = tcp://localhost:5000
|
|
|
|
[module mf]
|
|
class = secop.Proxy
|
|
remote_class = secop_psi.ppms.Field
|
|
description = magnetic field
|
|
iodev = secnode
|
|
value.min = -0.1
|
|
value.max = 0.1
|
|
target.min = -8
|
|
target.max = 8
|