External interfaces of the product

1. User interfaces
   This section must describe how the product communicates with the users. In applications using graphical user interfaces, the subdivision should be oriented to the visible elements.
   When describing the user interfaces, it is advisable to subdivide the description into a general part, complete with details of the general setup of the user interface (e.g. "Subdivision into menu/screen/status bar," "How are Help Pages constructed?", "Use of OK/Cancel buttons" etc.), and into specific descriptions dealing with the individual parts of the user interface (e.g. entry masks, menus, etc.).
   This section should not describe how the user interface is implemented internally. Any specifications on the part of the client regarding the libraries which are to be used or "GUI Builder" should be described below in section 4.
   This section can also contain references to prototypes or feasibility studies (increasingly, user interfaces are not being defined "on paper").
   • Examples of aspects which need to be described:
     • Input data
     • Dialog, user prompting
     • Commands, control parameters
     • Menus
     • Entry masks
     • Graphics
     • Output data
     • Logs, lists
     • Operating messages
     • Error responses
     • Help texts
     • Control elements (arrangement, function)
     • Displays and signaling (arrangement, function)
   • Refer also to comments on GUI in MeetingDec142011
2. Accelerator interface
   1. A LabVIEW interface is available. Refer to Subversion repository.
   2. Default value for the virtual accelerator ID is read from configuration file.
   3. Virtual accelerator ID can be changed at runtime.
3. Serial line devices
   1. COM-Server of Wiesemann & Theis.
      • This device is a gateway to make serial line interfaces available on the ethernet.
      • RS232/485 communication parameters can be set individually for each COM port.
      • COM ports can be accessed via TCP/IP socket connections, with port ids 800n, n€{0,1,2,3}
   2. TPG300, Balzers/Pfeiffer, is connected to a port of a COM-Server of Wiesemann & Theis.
      1. This device uses an ASCII protocol for communication.
      2. Datenformat: Refer to its programmer manual.
      3. Programmschnittstelle: A LabVIEW instrument driver library is available.
      4. Datenraten: 9600 Baud
      5. Relais output are available to indicate vacuum status to be used as interlock.
   3. MKS647, MKS, is connected to a port of a COM-Server of Wiesemann & Theis.
      1. This device uses an ASCII protocol for communication.
      2. Datenformat: Refer to its programmer manual.
      3. Programmschnittstelle: A LabVIEW instrument driver library is available.
      4. Datenraten: 9600 Baud
      5. Relais output are available to indicate vacuum status to be used as interlock.
   4. PR4000, MKS, is connected to a port of a COM-Server of Wiesemann & Theis.
      1. This device uses an ASCII protocol for communication.
      2. Datenformat: Refer to its programmer manual.
      3. Programmschnittstelle: A LabVIEW instrument driver library is available.
      4. Datenraten: 9600 Baud
   5. Pyrometer IPE 140
      1. Connected to a COM port of a PC.
         A vendor program is used to access the device for configuration and monitoring parallel to TCS.
         1. This device uses an ASCII protocol for communication.
         2. Datenformat: Refer to its programmer manual.
         3. Programmschnittstelle: A LabVIEW instrument driver library is not available.
         4. Datenraten: 9600 Baud
      2. Connected via 4-20mA current loop to a separate display. This box also generates interlock signals in case exceeding temperature limits, that are set manually.
      3. Connected via 4-20mA current loop to NI-RIO. This option is used for the TCS.
   6. COMPACT detector
      1. This device uses an ASCII protocol for communication.
      2. Datenformat: Refer to its programmer manual.
      3. Programmschnittstelle: A LabVIEW application is available.
      4. Datenraten: ?
4. MIL-Bus devices
   1. MIL-Bus interface card
      1. A DLL-driver for communication with the MIL-Bus interface card is available.
   2. Magnet Control
      1. This device uses the MIL-Bus DLL-driver.
      2. Datenformat: Refer to its programmer manual.
      3. Programmschnittstelle: A LabVIEW application is available.
      4. Datenraten: ?
      5. TTL output is available to indicate vacuum status to be used as interlock.
      6. A independent hall probe send values of the magnetic field. Its converted by an U/F generator.
5. Hardware signals are listed in a separate Excel-Sheet, TCS_HW_Signals.xls, attached to this document.