Tango, Monochromator, BLEnergy

The online functions that operate the monochromator use the name mnchrmtr to refer to the monochomator server. Here is an example (/online_dir/online.xml):

<device>
 <name>mnchrmtr</name>
 <type>type_tango</type>
 <module>motor_tango</module>
 <device>p08/blenergy/exp.01</device>
 <control>tango</control>
 <hostname>haso107tk:10000</hostname>
</device>

A mnchrmtr server has to export:

Attributes
  Position
  PositionSim
  ResultSim
  UnitLimitMin
  UnitLimitMax

Commands
  Calibrate
  StopMove

There are beamlines which need several servers to control the energy, e.g. FMB-DCM, Lom, Undulator. For these cases the BLEnergy class has been implemented. It exports the above mentioned interface and it has properties (MasterDevice, SlaveDevices) which allow the specification of several servers. Each of these servers exports the same interface. Below you find an example for a property list.

Figure 62.1: Jive: BLEnergy Server Properties at P08