PITZ Laser Beam Line Control


Back to Index

LBL TINE configuration files

Out of the numerous TINE configuration files, in the PITZ LBL server only 4 are used which are commented upon below. The first two are used by the TINE system only and have no direct influence on the LBL server, while numbers 3 and 4 are strongly connected with it.  

  1. cshosts.csv
    Consult the TINE documentation for its meaning and usage. Leave it intact as it is. 

  2. fecid.csv
    Consult the TINE documentation for its meaning and usage. Leave it intact as it is. 

  3. exports.csv
    Consult the TINE documentation for its meaning and usage.

    It contains a list of properties which are "exported" by the server, i.e. can be accessed by a client by reading or reading/writing. Thus the server can receive commands from outside and supply various information on its own status and the status of the hardware it is controlling.

    Any change in this file normally needs appropriate changes in the server software. Without that there may be fatal error(s) at power-up/reboot or a malfunctioning of the server.

    Amongst other parameters needed for the TINE system, the file contains the so called property name and the property number. Taking into account the hardware having always two "axes" at any device, in the LBL server in connection with the PITZ GUI a few private conventions are adopted: 

    -- The full name of any property consists of two parts separated by a dot: <PRPName>.<Direction>, where <Direction> may be only HOR or VER.

    -- Any property <PRPName> must appear twice as <PRPName>.HOR and as <PRPName>.VER.

    -- All properties with full name <PRPName>.HOR have property numbers 1<=PRPNumb_H<=99.

    -- All properties with full name <PRPName>.VER have property numbers 101<=PRPNumb_V<=199

    -- For any <PRPName> the relation PRPNumb_V=PRPNumb_H+100 must be valid.

  4. <localname>dv.csv
    Consult the TINE documentation for its meaning and usage.

    The file contains a list of device names and device numbers which will then be known to the TINE system and to the LBL server.

    The string <localname> must contain exactly 6 characters and has to appear (in capital letters) also in the list of properties in exports.csv. For the LBL server this string was chosen to be stepmo. The file name is checked at power-up/reboot against a string fixed in the LBL server code, so it cannot be changed without changing the source code.

    As private convention in the context of the LBL server and the PITZ GUI it was chosen:

    - The name of any device consists of two parts separated by a dot: <DeviceType>.<TypeName>, where <DeviceType> has 6 characters and <TypeName> has 2 characters.
    - Only capital letters and numbers are allowed in <DeviceType> and <TypeName>
    - Device numbering starts from 0 and should be continuous.

    NOTE: This file offers the possibility to change the actual hardware setup without changing anything in the LBL server software. As Example 1 and 2 the two files stepmodv.csv before and after replacement of the so-called Pinhole by the mirror M5 are given below. Of course, such changes normally lead to some changes in the PITZ GUI.

    Example 1 : 2 mirrors (.M3, .M4), pinhole (.P1), pinhole 2dimens. scan (.S1), M3&M4 correlated(.34)

    MODULE_NAME,MODULE_NUMBER
    #char*16,UINT16
    MIRROR.M3,0
    MIRROR.M4,1
    PINHOL.P1,2
    PINHOL.S1,3
    MIRROR.34,4

    Example 2 : 3 mirrors (.M3, .M4,.M5), M3&M4 correlated(.34)

    MODULE_NAME,MODULE_NUMBER
    #char*16,UINT16
    MIRROR.M3,0
    MIRROR.M4,1
    MIRROR.M5,2
    MIRROR.34,3

Back to Index

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