Re: Doubts about DISS field

[Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>]

    Hi Marco,

On 6/30/22 9:19 AM, Marco A. Barra Montevechi Filho wrote:

>       
>       Thanks
>       for your reply, andrew! It did clarify some doubts.
>       
>       I did a caget into the record fields and looked at IOC
>       configuration files. Caget in .SDIS returns empty and i found no
>       evidence to believe that SDIS is being configured anywhere. DISV
>       and DISA are also not referenced anywhere, not even in the .db
>       file. Is the severity in DISS field used in any other case? Or
>       just when the record is disabled specifically by DISV, DISA and
>       SDIS fields?
>     
    There is only one place in the EPICS source code that uses the value
    in a record's DISS field, and that code is only activated when DISV
    == DISA after attempting to read the SDIS link into DISA. If this is
    what is causing the record to go into alarm state the STAT field
    will contain DISABLE_ALARM, and the record's timestamp will not be
    updated because the record has been disabled.
    
    If as you say the SDIS field is empty and the DISA and DISV fields
    contain their default values of 0 and 1 respectively, the severity
    in DISS shouldn't be affecting your records at all. I just tested
    that to confirm.
    
    There must be some other reason the records are going into INVALID
    alarm. The value in the STAT field should give an indication what
    that might be — please post the full output from running the command
> dbpr
>         "recordname", 4
>       
    on the IOC's console for one of those records if you want more
    advice.
    
    - Andrew
    
-- 
Complexity comes for free, Simplicity you have to work for.