Skip to content

WIP: Unified tango ds key in config (after rebase )

Linus Pithan requested to merge unified_tango_ds_key2 into master

replaces !1080 (closed) after rebase of python3 to master

I tried to find a unified way how a tango device server is specified in the config and how we can access it easily in a controller. Maybe we should think about the names of tag and the new get_comm function to make sure they are not confusing and that is is consistent e.g. with the way we use lima

bliss/common/tango.py has a get_comm that uses a tango_ds tag in the yml

tango_ds:
  uri: id00/tango/dummy

with optional additional parameters

tango_ds:
  uri: id00/tango/dummy
  timeout: 3
  tango_host: lid231:20000

this change could affect the yml files of the following controllers

  • bliss/controllers/leica_microscope.py
  • bliss/controllers/lima/lima_base.py
  • bliss/controllers/md2m.py
  • bliss/controllers/motors/cs8tango.py
  • bliss/controllers/motors/esrf_undulator.py
  • bliss/controllers/motors/setpoint.py
  • bliss/controllers/motors/tangoemot.py
  • bliss/controllers/tango_attr_as_counter.py
  • bliss/controllers/tango_bpm.py
  • bliss/controllers/tango_keithley.py
  • bliss/controllers/tango_shutter.py
  • bliss/controllers/tango_tfg.py

Merge request reports