Skip to content

Tango motion configuration

Jose Tiago Macara Coutinho requested to merge tango_axes_property into master

Goals:

  • No need to start jive at all to expose new motors in (new) servers.
  • Able to configure and search all info in one place

The PR proposes that the entire configuration be done in YAML (nothing in tango properties or XML). Example:

- name: th
  steps_per_unit: 1000
  backlash: 0.05
  tango_server: diffract

When configuring a new server, instead of going to jive, just start the BlissAxisManager with '-n' This will create a server if it doesn't exist. Example:

$ python BlissAxisManager.py diffract -n

And here is a script to do the migration for us: migrate.py

Not part of this PR is to improve the web interface search engine to make it easier to search for all items in a ´tango_server´ key, for example.

Merge request reports