PEPII RF Controls

 

Controls Meeting Minutes

Tuesday, December 10, 2002
Notes by:  Kristi L. Luchini
In attendence: S. Allison, C. Chestnut, S. Clark, K. Luchini, J. Rock, N. Spencer, M. Zelazny

Agenda

  1. PEPII RF SCP Configs
  2. Restoring an RF station to initial state after a SCP config has been loaded
  3. Gotchas

Actions To be Taken

  1. PEPII RF HER AND PEII RF LER SCP Config Files.

    2. Obsolete the existing VMS PEPII-HER and PEPII-LER SCP Config files. These files are not complete, and there is no need to restore all HER and/or all LER stations. The expert operator (R.Akre,M.Browne,D.Teytelman) only has the need to restore individual RF stations. All individual PEPII RF station config files will be updated to match the list of channels by the IOC save/restore system (ie ChannelWatcher pvlist input files).
     
  2. PEPII RF HER AND PEII RF LER SCP Config buttons.

    3. Modify the PEPII RF SCP Config buttons so that a button macro is executed that will force each of the individual RF Station Config buttons to be pressed for the desired ring.
     
  3. Saving PEPII RF SCP Config files.

    4. All PEPII RF SCP Configs saved will continue to be saved to the scratch disk. However, the saved configs will remain be moved to the physics disk after 30 days. If a users needs to restore an rf station config file older than 30 days, they will need to contact a ESD Software person for assistance so that the file can be retrieved can copied to the appropriate VMS directory and.
     
  4. Updating PEPII RF SCP Config files.

    5. The VMS SCP Config files will be updated to contain the complete list of PV's found in the ChannelWatcheer save files used on Unix. This task will require that  the existing PEPII RF ChannelWatcher PV list template files and scripts to create a SCP config files that will be loaded from VMS. This will require that the scripts listed below, be modified so that they will produce a VMS SCP config file in the proper format,  in addition to creating the ChannelWatcher PV list input file used on Unix. The task to modify the unix script that will generate the VMS SCP config files  requires 2-8 work.  The SCP configs will be saved in the Unix code version control system (CVS).  At the time when a new version of a SCP config file placed into CVS the email facility of CVS will be used to send email to the necessary ESD software people (E.Miller,N.Spencer,K.Underwood)  who need to know this information.  The new SCP config files will also need to be shipped from Unix to VMS. The mechanism used to grap Unix db reports (K.Brobeck,J.Rock) may be able to be used.
     
      Template Files: 
      Please noote that the savedataALARM file is no longer used.
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/template/2CV
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/template/4CV
       
      ChannelWatcher Script:
      The following scripts are used to generate channel watcher pvlist input files below.
      /afs/slac/g/cd/soft/ref/app/channelWatcher/script/p2rf2cv_cw_build
      /afs/slac/g/cd/soft/ref/app/channelWatcher/script/p2rf4cv_cw_build
      /afs/slac/g/cd/soft/ref/app/channelWatcher/script/cw_build

      Channel Watcher pvlist input files:
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/LR43
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/LR44
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/LR45
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR21
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR23
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR25
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR26
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR81
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR83
      /afs/slac/g/cd/soft/ref/app/channelWatcher/pvlist/HR85

      SCP Config Files Format:
      See Nancy Spencer for more information.
      Example)
       !
       !===========================================================================
       !
       ! Abs:  PEPII RF High Energy Ring (HER) Station 8-3 Parameters
       !
       ! Name: RFHR8-3TEMP.CNF
       !
       ! Auth: 04-May-2001, Stephanie Allison
       !
       !--------------------------------------------------------------------------
       !
       ! Mod:
       !
       !==========================================================================
       !
       ! Station Gap Voltage, Drive Power, Klystron Power Setpoints
       !
       % DEFI /CNFD="HR83:STN:VOLT:CTRL"
       % DEFI /CNFD="HR83:KLYSDRIVFRWD:POWER:SAT"
       % DEFI /CNFD="HR83:KLYSDRIVFRWD:POWER:ON"
       % DEFI /CNFD="HR83:KLYSDRIVFRWD:POWER:HIGH"
       % DEFI /CNFD="HR83:KLYSOUTFRWD:POWER:NORM"
       % DEFI /CNFD="HR83:KLYSOUTFRWD:POWER:HIGH"
      !
      !==========================================================================

      The SCP Config files are located in the following directories with the following naming convension.

      $255$DUA3:[COMMON.CONFIG.RFLR4-3]RFLR4-3TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFLR4-4]RFLR4-4TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFLR4-5]RFLR4-5TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR2-1]RFHR2-1TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR2-3]RFHR2-3TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR2-5]RFHR2-5TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR2-6]RFHR2-6TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR8-1]RFHR2-1TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR8-3]RFHR8-3TEMP.CNF
      $255$DUA3:[COMMON.CONFIG.RFHR8-5]RFHR8-5TEMP.CNF

      SCP Config Data Files:
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFLR4-3]RFLR4-3$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFLR4-4]RFLR4-4$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFLR4-5]RFLR4-5$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR2-1]RFHR2-1$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR2-3]RFHR2-3$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR2-5]RFHR2-5$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR2-6]RFHR2-6$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR8-1]RFHR8-1$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR8-3]RFHR8-3$<version>.CNF
       $255$DUA3:[PROD_SYS.CONFIG_SCRATCH.RFHR8-5]RFHR8-5$<version>.CNF
       

  5. Station Initialization after a SCP Config has been restored:

    6. The current problem with SCP configs regarding EPICS applications is that the ioc is that although parameters (PV's) are restored to known value, action is required by the users to force that restored information to be used. Therefore, a Matlab program will be written to force an RF station to initialize after a SCP Config has been restored. The initialization of an RF station entails a series of EPICS display button pushes.  This can be accomplished by issuing a series of  EPICS channel access puts (caputs)  in  the proper order. Delays will need to be used after some caputs to wait for completion of  the action.  Although this task could also be done from a script, you will need a separate script for each stations with makes maintenance more difficult and the chance of a typo greater.  f caputs for each RF stations, a matlab program will be used to issue the caputs, using the stations id and number of cavities as the input parameters. The RF engineers and physists already maintain a list of matlab programs for pepii rf. Some of these matlab programs already do a subset of what is necessary for this task, so the developer of this matlab program may find it useful to cut and past from the existing matlab files.  This task will be done by the RF Hardware group.
     
  6. New Button Added to Displays for RF Station Init:

    7. A new button for initializing an rf station after a SCP Config has been restore will be added to the PEPII SCP Config panels.
    This button will initiate cmdSrv to execute the Matlab (rf_stn_init.m) program listed above to be executed with the proper input arguments.  A similar button will be placed on the PEPII RF Matlab display. Warning text will be placed on both of these displays to let the operator know that an expert should be performing this function.
     
  7. Gotchas

    8. The Dan VanOlst program on VMS that saves the SCP Configs has a limitation that needs to be fixed.  The limitation is related to the DBalloc() function used (65535) . If the number of channels in the SCP Config input file channels exceeds a certain number then the DBalloc() function fails. This limitation has already been reached with the NLCTA SCP Config files. However, since NLCTA is not currently using these configs this limitation has not been resolved yet. However, it is anticipated that the extension of the individual PEPII RF SCP Config files this limitation will be reached and the problem resolved at that time.

    When the SCP Config files are completed the will contain calibration data specific to a module. Therefore, an expert is required to restore an RF Station Config in order to know the ramification of such an action.  Please remember that if a module has been replaced, and that modules uses calibration data, if a config is restored to that station, you will see unexpected results. A change in module requires different calibration data. Warnings will be placed on the PEPII RF SCP config panel to warn the operator before restoring configs.
     

  8. Remaining Questions:

    9. Will partial configs be needed? No