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  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Show alarms, events and measurements from DSP in CS-Studio and generate files with this data
From: Mark Rivers <[email protected]>
To: Carlos Gómez Martinez <[email protected]>, "[email protected]" <[email protected]>
Date: Fri, 11 Mar 2016 12:34:20 +0000
Hi Carlos,

I don't use alarms a lot, but here is one example that uses alarms on the mca record.  When the value of the deadtime is above 70 there is a HIHI alarm, which has severity MAJOR, above 40 is HIGH alarm which has severity MINOR, etc.

https://github.com/epics-modules/mca/blob/master/mcaApp/Db/mca.db

These alarm values are used to set the color of a bar graph shown under the label DeadTime on this plot

https://github.com/epics-modules/mca/blob/master/documentation/mca.png

Here is another example with some bi records that set the severity (ZSV, OSV) to MINOR or MAJOR to indicate status or problems.

https://github.com/areaDetector/ADCore/blob/master/ADApp/Db/NDFile.template

Those are used on this screen to set the colors of fields such as those labeled Enable, Exists, Write status, etc. on this screen:

https://github.com/areaDetector/ADCore/blob/master/documentation/NDFileJPEG.png

In your case how is the PLC sending the alarm status back to EPICS?  Via a bit in a Modbus register?  If so then you can set the ZSV and OSV of the bi record for that bit to the appropriate value (NO_ALARM, MINOR, MAJOR, etc.).  That alarm status can then be used in your CSS display to indicate a problem with colors or change the visibility of some part of the display.

Mark


________________________________
From: [email protected] [[email protected]] on behalf of Carlos Gómez Martinez [[email protected]]
Sent: Friday, March 11, 2016 3:29 AM
To: [email protected]
Subject: Show alarms, events and measurements from DSP in CS-Studio and generate files with this data

Hi ,

I am Carlos from Spain and I am developing an HMI, it consists of:
A DSP sends measurements, alarms and events through modbus addresses, these data are converted to EPICS and displayed on screen with CSS. The "brain" of the project is the DSP, ie, alarms are not made by epics, alarms are generated by the DSP and the cs-studio is only displayed if there is failure, if there is no fault, measures etc .. I would know how these failures can be collected, events and actions and how I can build a table in CS-Studio where these data to be displayed and also to generate a file with this data.

Thanks,

Carlos


References:
Show alarms, events and measurements from DSP in CS-Studio and generate files with this data Carlos Gómez Martinez

Navigate by Date:
Prev: Show alarms, events and measurements from DSP in CS-Studio and generate files with this data Carlos Gómez Martinez
Next: Re: mrfioc2 error at uTCA platform Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Show alarms, events and measurements from DSP in CS-Studio and generate files with this data Carlos Gómez Martinez
Next: Re: Show alarms, events and measurements from DSP in CS-Studio and generate files with this data Kasemir, Kay
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·