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  2016  2017  2018  2019  2020  <20212022  2023  2024  2025  2026  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  <20212022  2023  2024  2025  2026 
<== Date ==> <== Thread ==>

Subject: Re: [EXTERNAL] calcout record processing
From: "Hu, Yong via Tech-talk" <[email protected]>
To: "Johnson, Andrew N." <[email protected]>, "Rivers, Mark L." <[email protected]>
Cc: EPICS tech-talk <[email protected]>
Date: Thu, 6 May 2021 19:03:31 +0000
I just did a quick test. Randall's problem is repeatable. If a record (e.g. testAsyn) has DTYP "asynInt32" but no field(INP, "@..."), its FLNKed record will not be processed after a put to testAsyn.  However, the value of  testAsyn is changed although its alarm severity is INVALID.

[yhu@sps-diaglabs-dev-ibm example]$ caput testAsyn 1
Old : testAsyn                       0
New : testAsyn                       1
[yhu@sps-diaglabs-dev-ibm example]$ caget -a testAsyn
testAsyn                       <undefined> 1 UDF INVALID

And I get a waring message related to devAsynInt32 after iocInit. Probably Randall did not pay enough attention to that kind of warning. 

Starting iocInit
############################################################################
## EPICS R7.0.5
## Rev. R7.0.5-dirty
############################################################################
testAsyn devAsynInt32::initCommon  invalid INST_IO Must be asynMask(<port> <addr> <mask> <timeout>)userParams

BTW, "PP" is not needed in the field FLNK. This seems more straightforward to me: field(FLNK, "$(P):fsCalc")

Cheers,
-- Yong 


On 5/6/21, 2:38 PM, "Tech-talk on behalf of Johnson, Andrew N. via Tech-talk" <[email protected] on behalf of [email protected]> wrote:


    > On May 6, 2021, at 1:05 PM, Mark Rivers via Tech-talk <[email protected]> wrote:
    > 
    >> But fsControl is also SCAN=Passive in the example. For the FLNK or the INP CP to work, something must trigger fsControl to process.
    > 
    > Randall's original message said:
    > 
    >> If I put to fsControl, it sets but nothing happens.
    > 
    > So my understanding is that he was doing a caput to fsControl, but the FLNK was not processing fsCalc, as it should have.

    That would make sense given that DTYP was set; the asynInt32 device support will have disabled the record (leaving PACT as 1) when it didn’t see an address in the INP field. In that state a put to the ai record will not cause it to be processed.

    - Andrew


    > ________________________________
    > From: Hartman, Steven <[email protected]>
    > Sent: Thursday, May 6, 2021 12:57 PM
    > To: Mark Rivers
    > Cc: Arnold, Ned D.; Randall Cayford; [email protected]
    > Subject: Re: [EXTERNAL] calcout record processing
    > 
    > 
    > 
    > On May 6, 2021, at 1:52 PM, Mark Rivers via Tech-talk <[email protected]<mailto:[email protected]>> wrote:
    > 
    > He did FLNK from fsControl to fsCalc.  If that FLNK is not actually processing fsCalc than I think it may be because of the DTYP/INP mismatch.
    > 
    > 
    > But fsControl is also SCAN=Passive in the example. For the FLNK or the INP CP to work, something must trigger fsControl to process.
    > 
    > --
    > Steven Hartman
    > [email protected]<mailto:[email protected]>
    > 
    > 
    > 

    -- 
    Complexity comes for free, simplicity you have to work for.



References:
calcout record processing Randall Cayford via Tech-talk
Re: calcout record processing Arnold, Ned D. via Tech-talk
RE: calcout record processing Mark Rivers via Tech-talk
Re: [EXTERNAL] calcout record processing Hartman, Steven via Tech-talk
Re: [EXTERNAL] calcout record processing Mark Rivers via Tech-talk
Re: [EXTERNAL] calcout record processing Johnson, Andrew N. via Tech-talk

Navigate by Date:
Prev: Re: [EXTERNAL] calcout record processing Johnson, Andrew N. via Tech-talk
Next: Building areaDetector on Windows with MSYS2 and MINGW64 Smith, William via Tech-talk
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  <20212022  2023  2024  2025  2026 
Navigate by Thread:
Prev: Re: [EXTERNAL] calcout record processing Johnson, Andrew N. via Tech-talk
Next: Building areaDetector on Windows with MSYS2 and MINGW64 Smith, William via Tech-talk
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  <20212022  2023  2024  2025  2026 
ANJ, 19 Mar 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·