Detailed description of the required product features

Return to Main Document: Return Top

Scope of delivery

The scope of delivery must contain a list of all deliverables (product and its subcomponents, project documentation to be supplied, user manuals, training documents, training, support in the introductory phase e.g. in the form of coaching, installation procedures, migration of data stocks, user support in the form of hotline or e-mail, etc.).

Those components which do not form part of the "product in the narrower sense" (program), e.g. user documentation, training, etc., must be described accurately in this subsection; the "product in the narrower sense" is described in detail in the following subsections.

Sequences (scenarios) of interactions with the environment

1. Interlock Subsystem
   1. Hardware
      1. Low level HW input signals are monitored and scaled.
      2. Derived information is calculated, leading to process variables.
      3. Process variables are compared to limit ranges.
      4. Interlock signals are generated if at least one limit range is exceeded.
      5. One interlock signal switches the chopper to stop beam delivery.
      6. Other interlock signals can be used by external systems.
      7. Reset interlock
      8. An audio and visual signal is generated in case of certain interlocks.
   2. Interlock Limit Configuration
      1. Default values for interlock limits are read from file at start of program.
      2. Value of interlock limits can be changed by user at runtime.
      3. User can laod and save interlock limits at runtime.
      4. Modified interlock ranges will be written to the interlock subsystem.
   3. Interlock Monitoring
      1. Display interlock status and reason of interlock and loggin in file
      2. Interlock alarm und logging
2. Macro pulse measurements
   1. Frequency
   2. Width
   3. Duty factor
   4. Update rate 1s of averaged values
3. Trafo measurements at DT2 & DT3
   1. The electrical currents must be derived from 8MHz signal in combination with range signals.
   2. The current is monitored for interlock conditions
      1. Fast IL: Current during macro pulse -> Period measurement
      2. Slow IL: Averaged pulse current, average time is one MP(<8ms). This means maximal one target segment could be damaged.
   3. The update rate for logging and on the GUI is 1s of averaged pulse current.
   4. Duty factor of MP can be used for scaling to DC current
   5. Calculate particle integral in case of measurement run.
4. Accelerator process variables
   Refer also to the device model description
   • Accelerator Device Model or
   • Equipment Model Documentation
     • U*DC* -> DCI
     • U*DT* -> DTI
     • *_P -> PLA
   1. Virtual accererator must be configured.
   2. Update rate for logging and GUI is 1s
   3. Configure Alarm limits HI & HIHI. ->Average from Acc.-Network. Spikes into FPGA
   4. List of ACC-PV's to read
      

      UX8DC2_P	positi
      UX8DC4_P	positi
      UX8DC5_P	positi
      UXIDC6_P	positi
      UT2DCX_P	positi
      UXFVV1S	positi
      UXIVV1S	positi
      UT2DCX	currinfo
      UXADT2	currinfo
      UXIDC6	currinfo
      UX8DC2	currinfo
      UX8DT3	currinfo
      UX8DC4	currinfo
      UX8DC5	currinfo

   5. Configure Alarm range for trafo current PV's, UXADT2 & UX8DT3
   6. Generate SW interlock in case of exceeding valid range of trafo currents DT2 & DT3.
   7. Some cups can be controlled.
      

      UX8DC2_P	posits
      UX8DC4_P	posits
      UX8DC5_P	posits

Here: End of discussion on 6th of February-->

1. DSSSD Detector rate
   1. Generate Interlock if averaged rate, 1s, is exceeded.
   2. Update rate for logging and GUI is 1s
   3. Configure Alarm limits HI & HIHI.
2. Rutherford detector rate
   1. Generate Interlock if averaged pulse rate is exceeded. Use individual range for each target segment.
   2. Update rate for logging and GUI is 1s
   3. Configure Alarm limits LOLO, LO, HI, HIHI.
3. Target temperature
   1. Generate Interlock if maximum is exceeded is exceeded.
   2. Update rate of latest value for logging and GUI is 1s.
   3. Configure Alarm limits HI & HIHI.
4. Vaccum System
   1. Unit for pressure is hPa.
   2. Monitor periodically status of vacuum, pressure and interlock.
   3. Configure alarm and interlock limits.
   4. Values are integrated in schematic.
5. Gas System
   1. Unit for pressure is hPa.
   2. Unit for gas flow is l/min.
   3. Monitor periodically the status
      1. Pressure
      2. Flow for each gas
      3. Interlock
   4. Configure control loop
      1. Control pressure, select master gas
      2. Control flow
         1. Separate setpoint for each gas, or
         2. Mixing ratios with toltal flow.
   5. Configure alarm
   6. Optionally: configure interlock limits.
   7. Gas selection:
      1. TASCA: He, Ar, N2, H2
      2. RTC: He, Ar, N2, O2
6. Logbook
   1. To be defined!
      1. Proposal: eLog
         • Open Source
         • LabVIEW interface library available.
   2. Log system and manual entries from distributed PCs.
7. Alarms
   1. DSC SV are used to maintain and monitor alarm limits.
   2. A few most recent alarms are displayed in the application overview panel.
   3. Distributed System Manager can be used to monitor data values and alarm status.
8. Historical trending
   1. DSC SV are used to log data into Citadel data base.
   2. Histoical Data Viewer (also available in MAX) can be used to view historical data.
9. Data-Logfile
   Interlock monitoring and measurements are performed at all times as long as the programm is active. Data becomes logged to file.
   1. Frequency = 1Hz.
   2. Log data continuously in one default file. The background logging becomes interrupted by measurements, only.
   3. Log data into measurement file on request.
10. Background data logging
    1. Particle integral values are set to zero during background logging.
    2. Default filename-prefix is defined in configuration file or can be changed at runtime.
    3. Data and time becomes appended.
    4. File is changed automatically after time or maximum file sized is exceeded.
    5. Default maximum file size is defined in configuration file.
11. Start/Stop measurement
    1. Measurement modes
       1. Manual stop
       2. Stop measurement after predefined time.
       3. Chopping mode: predefined Beam-On and Beam-Off times with sihnaling to MBS.
    2. Indicate active measurement via HW signal.
    3. Start
       1. Close chopper.
       2. Stop background data logging.
       3. Set data log filename, data, time and index becomes appended.
       4. Reset particle integrals at start.
       5. Open new data log file.
       6. Start MBS.
       7. Restart measurement.
       8. Open chopper.
    4. Automatic file change
       1. File is changed automatically after time or maximum file sized is exceeded.
       2. An index becomes appended.
    5. Stop
       1. Close chopper
       2. Close data log file.
       3. Stop MBS.
       4. Start background data logging.
       5. Restart measurement.

Return to Main Document: Return Top

-- JonPetterOmtvedt - 19 Jun 2012