Skip to content

Tango bliss united

Jose Tiago Macara Coutinho requested to merge tango_bliss_united into master

This is a proposal to fuse Tango servers in a common fashion. This is not a new idea. Most of the concepts are borrowed from Lima and sardana.

The ideas are:

  • Bliss servers are all of the Bliss server type
  • Bliss servers have a single Bliss manager device
  • Bliss servers can start devices of multiple types (aka tango classes) (Axis, Temperature, etc)
  • Bliss device types are discovered at startup
  • Devices are specified in a YAML session like file

This MR also proposes to:

  • refactor the BlissAxis to the new Tango style structure.

It does not introduce any incompatibility in BlissAxis but it introduces some deprecations:

  • BlissAxisManager tango class (GroupMove now implemented by Bliss device)
  • TgGevent
  • The usage of tango_server keyword in YAML configuration files

Doc with instructions on how to do configure in tango_bliss_united branch file how-to

The following snapshot shows the result of a bliss server with some mock axes configured:

bliss_tango_example

Merge request reports