PITZ Laser Beam Line Control

Back to Index

LBL Server configuration

As soon as the LBL server has been startet and before it can communicate with any client it should be configured. A number of files from the working directory is read in with the intention to submit almost all relevant parameters via those files so that a wide range of changes is possible without modification of the LBL server code.

The configuration consists of three main parts:

  • Configuration of the TINE system itself (cf. TINE configuration files) . Some of the files of this part, however, have direct connection with the LBL server and hence are checked by the LBL server.
  • Configuration of the LBL server itself with respect to the hardware in use (cf. Axis configuration files).
  • Restoring of the actual positions (cf. Beam status file). 
    The positioning hardware used in the Laser Beam Line is of incremental type, i.e. there is no way to find out the actual position of a device from the hardware, for example after a power cut or simply after re-boot. For some other numbers the same is valid. To overcome this difficulty, a special file holds at any moment the actual positioning counts and some other parameters for all devices in the system. The name of this file is fixed in the LBL server code to be beamStatus.dat, the path to it is given in the Status directory file.

All configuration files are text files and can be easyly edited to adopt them to the particular needs. This, of course, opens the same time the possibility to introduce any number of errors. So, all files having direct connection with the LBL server are checked from different points of view to find possible errors and to inform the user.

Any error observed in a configuration file is regarded as FATAL, all further action is stopped. The error should be corrected and the LBL server re-started (CPU re-booted)! 

The communication with the user goes via PITZ GUI which can display only one error at a time. So, if there is more than one error in the configuration files, the above action should be repeated several times.

A list of error messages with some additional explanations is included in the documentation.  

Back to Index

 

Last update by R. Leiste on 16.12.2003 (leiste@ifh.de)