-----Original Message-----
From: Allison, Stephanie 
Sent: Monday, August 19, 2002 2:44 PM
To: Rock, Judith E.; Nelson, Janice L.
Cc: Allison, Stephanie; Spencer, Nancy
Subject: RE: vac analog question


Hi Judy and Janice,

You've both sent mail about vacuum today.  It must be that time.

From Janice:

>I'm looking at the vacuum panel stuff for 8-pack.  I'm wondering how
>you're envisioning this panel.

For NLCTA, there are 3 vacuum-type displays.  
(1) tarf_vacuum1/2.dl has both the digitals from the PLC and the 
    analogs from MCC and is more a summary.  
(2) tarf_vacuum1/2_limits.dl lists just the analog vacuums 
    that need limit-checking and are checked by the sequence that turns 
    power back on after a trip (if any vacuum is in the alarm state, the 
    sequence will wait).  The limits display has columns for the user
    to enter display, error, and warning limits plus a column for the
    archive delta which is the delta on the log value.
(3) tarf_db_vacp.dl is a DB display for a single vacuum and shows
    more fields of the record plus all the related digital statuses 
    from MCC.  

For 8-Pack, I think we should have the similar information displayed 
but it makes sense to combine the first two:
(1) pack_vacuum.dl should have both the PLC digitals and MCC analogs
    listed side-by-side in 2 columns.  Add 4 more columns for the
    limits and ADEL making for 6 columns total.  If there isn't enough 
    room or if it makes sense to split the vacuum signals up somehow, 
    then make multiple displays (ie, S01A to S04D in one display, 
    S05A to S08D on a second display).  Note that the SCP has all
    vacuums on one panel.
(2) pack_db_vacp.dl is similar to tarf_db_vacp.dl.  This display
    should show the digital fault value from Cassel's PLC, the analog
    value, the HV analog value (ie, for every VPS0xy, there is
    a VPS0xyHV), and the five related MCC digitals (HV, VACUUM, HV_CTRL,
    MOD_FAIL, and SETUP).  I THINK JUDY SHOULD DO THIS DISPLAY!!

> Part of me thinks the dig stat from Cassel should be on a
> modulator panel and have a link to the vac disp from the mod panel.

I think it's best to have a linking box to the vac disp.  We can make
the box border turn red if there is a vacuum fault.

> In the scp, the analog names are asts:ta03:VPS01A, etc.  I assume this
> goes to TRS8:ASTS:VPS01A:VACM in CAS.

The PV names will be:

Digital from the PLC:   TRS8:SYS:VPS0xy:VACMSTAT
Analog  from     MCC:   TRS8:SYS:VPS0xy:VACM     (Judy will translate (see below))
Limits and ADEL:        TRS8:SYS:VPS0xy:VACM.HOPR, .HIHI, .HIGH, .ADEL
HV Analog from   MCC:   TRS8:ASTS:VPS0xyHV
Digitals from    MCC:   TRS8:VACP:xz:HV, :VACUUM, :HV_CTRL, :MOD_FAIL, :SETUP
                        where x = (1 to 8), y = (A to D), z = (1 to 4) 

From Judy:

> According to Nancy, the vacuum ASTS channels have been defined in the slcdb. 
> So....I think I need to make an EPICS db for these.  I'm not sure how to 
> connect to things in the slcdb - is it a channel access link or something 
> like that?  Where can I find some examples?

You've already defined vac_digital.template (and plc_digital.db) for Cassel's
stuff.  Now it's time to create vac_analog.template and vac_analog.db for
Nancy's stuff.  For vac_analog.db, use $TARF/slowApp/Db/rf_vacuum.db as a start.
That file has a subroutine record which does the "glitch" trapping which we'll
use as-is for 8-pack.  You'll need to make some changes:
(1) Make the name and desc look like the name and desc in plc_analog.db
    so that you can use the same macros as vac_digital.template.
(2) Change INPA so that the input comes from TA03 instead of TA01.
    Leave the "ASTS" in the INPA name (this input link will link to the
    MCC database).
I think everything else is OK.  You can test these on cdvw5 - you'll be
connecting with the MCCDEV database but that's OK for testing purposes.

Thanks!!

Steph