Experimental Physics and Industrial Control System
|
|
Hi,
I need some advices on rules and autosave.
I configured a Linux IOC with following rules
================================================================
ASG(FAISCEAU) {
#Operation mode lock
INPA(DEFAULT:OPState)
#BEAM characteristics lock
INPB(FAISCEAU:WritePerm)
# We can always read PVs
RULE(1,READ)
# BEAM Characteristcs could be changed by everyone in maintenance mode and BEAM characteristics unlocked
RULE(1,WRITE) { CALC("A=0 && B=1") }
# BEAM Characteristcs could be changed only by operators in operation mode and BEAM characteristics unlocked
RULE(1,WRITE) {
UAG(operateurs)
CALC("A=1 && B=1")
}
}
==============================================================
DEFAULT:OPState could be 0:Maintenance 1:Operation
FAISCEAU:WritePerm could be 0:BEAMLocked 1:BEAMUnlocked
These rules work perfectly when values of DEFAULT:OPState and FAISCEAU:WritePerm are changed manually.
At starting, with autosave mechanisme, there is a mismatch between right access and lock values.
Any ideas?
Dominique.
|
- Replies:
- RE: security rules and autosave Mooney, Tim M.
- Navigate by Date:
- Prev:
RE: EPICS on VxWorks6.9 Mark Rivers
- Next:
synApps usage on 64 bit systems Henrique Dante de Almeida
- 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
2025
2026
- Navigate by Thread:
- Prev:
Does Build-AOP-RPMs" script can do most thing about epics? 梁雅翔
- Next:
RE: security rules and autosave Mooney, Tim M.
- 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
2025
2026
|
|
ANJ, 17 Dec 2015 |
·
Home
·
News
·
About
·
Talk
·
Base
·
Modules
·
Extensions
·
·
Distributions
·
Download
·
Documents
·
Links
·
Licensing
·
|