Experimental Physics and Industrial Control System
Hi Chanaka,
I'm not questioning your choice of an scalcout record. I'm just asking what you want the record to do. For example, what alarm should result from beam_state=='At Injection' while $(DEVICE):State=='ON', and so on.
Tim Mooney ([email protected]) (630)252-5417
Software Services Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab
________________________________________
From: Chanaka De Silva [[email protected]]
Sent: Monday, March 02, 2015 1:31 PM
To: Mooney, Tim M.
Cc: [email protected]
Subject: Re: Using sCalcout record
Hi, Tim:
Thank you for the reply.
Why I decided sCalcout? I thought sCalcout is the record that can handle "String" inputs. I have used calcout record previously for such alarm variables. However I never had to handle a "String" as an input. May be I could do without sCalcout.
Thanks, Chanaka.
On Mar 2, 2015, at 2:10 PM, Mooney, Tim M. wrote:
> Hi Chanaka,
>
> I don't know what you want the scalcout record to do, but you might start with something like this:
>
> record(scalcout, "calcAlarmState") {
> field(INAA, "beam_state CP")
> field(INBB, "$(DEVICE):State CP")
> field(CALC, ("aa=='At Injection' && bb=='OFF') ? 'WARN' : 'OK'")
> field(OUT, "warning_BeamInjection PP")
> }
> record(bo, "warning_BeamInjection") {
> field(ZNAM, "OK")
> field(ONAM, "WARN"
> field(ZSV, "NO_ALARM")
> field(OSV, "MAJOR")
> }
>
> Tim Mooney ([email protected]) (630)252-5417
> Software Services Group (www.aps.anl.gov)
> Advanced Photon Source, Argonne National Lab
>
>
> ________________________________________
> From: [email protected] [[email protected]] on behalf of Chanaka De Silva [[email protected]]
> Sent: Monday, March 02, 2015 2:20 AM
> To: [email protected]
> Subject: Using sCalcout record
>
> Dear, all
>
> I am in need of developing an alarm variable using the sCalcout record.
>
> I plan to input two variables that are defined as follows.
>
> 1.
> grecord(stringout,"beam_state")
>
> 2.
> record(bi, "$(DEVICE):State")
> {
> field(DESC, "Power Supply On/Off Status")
> field(DTYP, "stream")
> field(INP, "@genesys.proto PSU-getonoff $(IP)")
> field(ZNAM, "OFF")
> field(ONAM, "ON")
> field(ZSV, "MAJOR")
> field(OSV, "NO_ALARM")
> field(PINI, "YES")
> field(FLNK, "$(DEVICE):Limits")
> }
>
> I decided to use sCalcout since both of these variables output strings.
>
> For example;
>
> The first record outputs; "At Injection"
> The second record outputs; "ON"
>
> I looked up the documentation and could not figure out what is the best approach to write a record to define an alarm variable; let's say
>
> record(scalcout, warning_BeamInjection){
> ......
> ......
> ......
> }
>
> I plan to have 1 or 0 assigned to this alarm variable, so that I can set my HIHI alarm to sit at "1".
>
> Any help is much appreciated.
>
> Thanks, Chanaka.
>
>
>
- Replies:
- Re: Using sCalcout record Chanaka De Silva
- References:
- Using sCalcout record Chanaka De Silva
- RE: Using sCalcout record Mooney, Tim M.
- Re: Using sCalcout record Chanaka De Silva
- Navigate by Date:
- Prev:
Experience with Nutaq devices Greg Tchilinguirian
- Next:
Re: Using sCalcout record Chanaka De Silva
- 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:
Re: Using sCalcout record Chanaka De Silva
- Next:
Re: Using sCalcout record Chanaka De Silva
- 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