EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: back propagating error states
From: "Allison, Stephanie" <[email protected]>
To: "Leicester, PJ (Pete)" <[email protected]>, <[email protected]>
Date: Wed, 22 Apr 2009 08:29:42 -0700
Hi Pete,

> I have a problem propagating error states in my database. I have two mbbo records
> controlled through two edm buttons. These records when processed forward link to a calc
> record which calculates a value based on the two mbbo records which is then sent via
> streams and RS232 to a current amplifier (see db below). This all works fine until I get an
> RS232 communications error. Streams correctly detects the comms error and puts the
> longout record into error state (STAT TIMEOUT, SEVR INVALID). What I need to do is
> propagate this error state back to the mbbo records so that it is visible on the edm screen.
> Adding maximise severity to the existing links wont work because of the direction of the
> forward links. Clearly I can add stuff to the edm screen to display the error state of the
> longout record but this wont help with other client applications we have which talk directly
> to the mbbo PV's. I really want the mbbo records to reflect the error state of the longout
> record. Is there any way this can be achieved?
> 
> I tried linking the SDIS from the mbbo to the longout record with maximise severity set.
> This did make the mbbo reflect the longout's error state but only after being processed a
> second time so is far from ideal.

You can set the SDIS PV to "<name>.SEVR CP MS" to force processing on change of severity.  Of course, with DISV something not 0 to 3.

Stephanie Allison


References:
back propagating error states Leicester, PJ (Pete)

Navigate by Date:
Prev: Re: back propagating error states Andrew Johnson
Next: RE: back propagating error states Leicester, PJ (Pete)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: back propagating error states Andrew Johnson
Next: Re: back propagating error states (accidentally) Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·