Experimental Physics and
Industrial Control System

We encounter misbehaviour of a CALC record in the IOC running under EPICS 3.14.9/tornado 2.2.1.
(but it works correctly under EPICS 3.14.9/tornado 2.0.2) 


Test database consists of two records - CALC and BI, see below.

No matter what value - 1 or 0 - is written by "caput" program to "myBi", "myCalc" always has VAL=1

However, with CALC field changed  to <A#0>,  myCalc.VAL field  updates correctly with changes of "myBi".

What is wrong?


Regards,

Oleg Makarov

record(calc, myCalc) {

  field(SCAN, "1 second")

  field(CALC, "A=1")

  field(INPA, "myBi")

}

record(bi, myBi) {

}

Replies:

Re: CALC record weird behaviour Dirk Zimoch

Navigate by Date:

Prev: vxWorks, IP-OCTAL-232, interrupt, and reboot John Dobbins

Next: RE: vxWorks, IP-OCTAL-232, interrupt, and reboot 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: Re: What's wrong if a PV with DISA=1 still processes? Till Straumann

Next: Re: CALC record weird behaviour Dirk Zimoch

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