Re: IOC Severity Report

[Matt Rippa <mrippa@gemini.edu>]

Thanks all for the ideas. I had a few minutes during today's

telescope testing. I ran dbcar(0,1)  and see the first argument

should be the record name --at least in our version. So

dbcar(*,1) looks very useful here. We'll try again during

tomorrow's testing.

Back in the lab on a test system, I ran Andrew's suggestion:

> dbl "ai", "SEVR STAT"
gis1:CA_CLNT_CNT, "NO_ALARM", "NO_ALARM"

...snip...

gis1:tsrs:crword202:word, "INVALID", "UDF"
lis1:in:plcHb, "INVALID", "READ"
lis1:seq:word178, "INVALID", "UDF"

Then I checked some of these.

> dbpr lis1:seq:word178 10
ACKS: NO_ALARM      ACKT: YES           ADEL: 0             ALST: 0              
AOFF: 0             ASG:                ASLO: 1             ASP: 0x0             
BKPT: 00            DESC: analog input record               DISA: 0              
DISP: 0             DISS: NO_ALARM      DISV: 1             DPVT: 0x634494       
DSET: 0x1cd728      DTYP: AB DF1 serial EGU: volts          EGUF: 0              
EGUL: 0             EOFF: 0             ESLO: 0             EVNT: 0              
FLNK:DB_LINK lis1:seq:calc1word178.VAL  HHSV: NO_ALARM      HIGH: 0              
HIHI: 0             HOPR: 0             HSV: NO_ALARM       HYST: 0              
INIT: 1             INP:INST_IO @/dev/ttyS1 40 178          LALM: 0              
LBRK: 0             LCNT: 0             LINR: NO CONVERSION LLSV: NO_ALARM       
LOLO: 0             LOPR: 0             LOW: 0              LSET: 0x63fef8       
LSV: NO_ALARM       MDEL: 0              
MLIS: 00 00 00 00 00 00 00 00 00 00 00 00                   MLOK: 00 5a a6 80    
MLST: 0             NAME: lis1:seq:word178                  NSEV: NO_ALARM       
NSTA: NO_ALARM      ORAW: 0             PACT: 0             PBRK: 0x0            
PHAS: 0             PINI: NO            PPN: 0x0            PPNR: 0x0            
PREC: 0             PRIO: LOW           PROC: 0             PUTF: 0              
RDES: 0x2d65d0      ROFF: 0             RPRO: 0             RSET: 0x1cde68       
RVAL: 0             SCAN: I/O Intr      SDIS:CONSTANT 0.000000000000000e+00      
SEVR: INVALID       SIML:DB_LINK lis1:simStatus NPP NMS     SIMM: NO             
SIMS: NO_ALARM      SIOL:DB_LINK lis1:sim:word178 NPP NMS   SMOO: 0              
SPVT: 0x66a590      STAT: UDF           SVAL: 0             TIME: <undefined>    
TPRO: 0             TSE: 0              TSEL:CONSTANT       UDF: 1               
VAL: 0              

This may be related to being in the lab. I'm not yet sure what's causing STAT: UDF.

And the follow one maybe because the PLC is no longer connected. At least it has

processed, looking at the TIME field.

> dbpr lis1:in:plcHb 10
ACKS: INVALID       ACKT: YES           ADEL: 0             ALST: 0              
AOFF: 0             ASG:                ASLO: 1             ASP: 0x0             
BKPT: 00            DESC: analog input record               DISA: 0              
DISP: 0             DISS: NO_ALARM      DISV: 1             DPVT: 0x63446c       
DSET: 0x1cd728      DTYP: AB DF1 serial EGU: volts          EGUF: 0              
EGUL: 0             EOFF: 0             ESLO: 0             EVNT: 0              
FLNK:CONSTANT 0     HHSV: NO_ALARM      HIGH: 0             HIHI: 0              
HOPR: 0             HSV: NO_ALARM       HYST: 0             INIT: 0              
INP:INST_IO @/dev/ttyS1 40 88           LALM: 0             LBRK: 0              
LCNT: 0             LINR: NO CONVERSION LLSV: NO_ALARM      LOLO: 0              
LOPR: 0             LOW: 0              LSET: 0x63fee8      LSV: NO_ALARM        
MDEL: 0             MLIS: 00 00 00 00 00 00 00 00 00 00 00 00                    
MLOK: 00 5a a6 60   MLST: 0             NAME: lis1:in:plcHb NSEV: NO_ALARM       
NSTA: NO_ALARM      ORAW: 0             PACT: 0             PBRK: 0x0            
PHAS: 0             PINI: YES           PPN: 0x0            PPNR: 0x0            
PREC: 0             PRIO: LOW           PROC: 0             PUTF: 0              
RDES: 0x2d65d0      ROFF: 0             RPRO: 0             RSET: 0x1cde68       
RVAL: 0             SCAN: I/O Intr      SDIS:CONSTANT 0.000000000000000e+00      
SEVR: INVALID       SIML:CONSTANT 0.000000000000000e+00     SIMM: NO             
SIMS: NO_ALARM      SIOL:CONSTANT 0.000000000000000e+00     SMOO: 0              
SPVT: 0x66a498      STAT: READ          SVAL: 0              
TIME: 2017-06-13 18:50:46.112607023     TPRO: 0             TSE: 0               
TSEL:CONSTANT       UDF: 1              VAL: 0              

Thanks again,

-Matt

On Tue, Jun 13, 2017 at 7:06 AM, Andrew Johnson <anj@aps.anl.gov> wrote:

While you can't do the filtering inside the IOC, if you don't mind using
an external tool to do that you can use the 'dbl' command to display all
your records (or all those of a specific record type) along with a
selection of their field values, so the command
  dbl "ai", "SEVR STAT"
will print the record name and SEVR and STAT field values for all ai
records in the IOC. Use "" or "*" to request all record types. I would
redirect the output of this command to a file and grep through that file
at my leisure:
  dbl "*", "SEVR STAT" > all-serv-stat.txt

I think this might even have worked with 3.13, but I'm not certain about
that (the "*" might not).

- Andrew

On 06/12/2017 03:46 PM, Matt Rippa wrote:
> We have some IOC's on 3.14.12.4 with several thousand records.
> Is there an easy way to get a severity report for any record where
>
> SEVR!=NO_ALARM ?
>
> I ask, because we're moving these systems from 3.13.x. We notice some
> non-existing input records now cause SEVR=INVALID and record processing
> is halted. This is a great new feature, btw.
>
> Thank you,
> -Matt

--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon