Hi:
> I'm working with CODAC 2.1.0 framework (the ITER framework which include
> EPICS 3.14.12 and CSS 2.4.0). I would like to have in the Message History of
> CSS a message for any change value for all binary input PV.
> My question is how to configure the EPICS alarm's field (ZSV, OSV, COSV,...)
> of my binary input PV to get this behavior?
> I try several configurations but all were unsuccessful.
Why not simply archive your binary input PVs?
All changes are then stored.
The message log is not a value log.
It's a log for application messages (warnings, errors)
or alarm system traffic.
You __could__ add all your binary input PVs to the alarm handler,
configure them to generate alarms on change-of-state,
and log the alarm traffic to the message log.
But I doubt that all your binary input state changes are useful alarms
where each one requires an operator to inspect the alarm, do something about it,
acknowledge it, ...
-Kay
- References:
- Logging change of state for binary input in Message History of CSS ZYCHLA Emmanuel
- Navigate by Date:
- Prev:
RE: windows-x64 problem Mark Rivers
- Next:
RE: windows-x64 problem Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Logging change of state for binary input in Message History of CSS ZYCHLA Emmanuel
- Next:
Master index couldn't point to the data files Mi Qingru
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|