Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
<== Date ==> <== Thread ==>

Subject: RE: Issues with latest version of base-7.0
From: Mark Rivers via Core-talk <core-talk@aps.anl.gov>
To: "'Johnson, Andrew N.'" <anj@anl.gov>, Michael Davidsaver <mdavidsaver@gmail.com>
Cc: "core-talk@aps.anl.gov" <core-talk@aps.anl.gov>
Date: Wed, 19 Dec 2018 14:21:07 +0000
Unfortunately it does not look like this issue is fixed in 7.0.2.  Whenever a busy record makes a transition from 1 to 0 this message is printed on the IOC:

Warning: '13SIM1:cam1:AcquireBusy.PUTF' found true with PACT false

It is coming from this file:
./dbDbLink.c:            errlogPrintf("Warning: '%s.PUTF' found true with PACT false\n",

This will be annoying for everyone using the busy record, which is areaDetector and lots of synApps modules.

Thanks,
Mark


-----Original Message-----
From: Johnson, Andrew N. <anj@anl.gov> 
Sent: Wednesday, November 14, 2018 9:18 PM
To: Michael Davidsaver <mdavidsaver@gmail.com>
Cc: Mark Rivers <rivers@cars.uchicago.edu>; core-talk@aps.anl.gov
Subject: Re: Issues with latest version of base-7.0

@Michael: call it experience of too many encounters with Murphy’s law...

I don’t think it’s worth using a debugger, this is probably because of the slightly unusual behavior of the busy record, which I didn’t really think about or test with this change. The synapps busy record explicitly allows the database to determine when processing is complete and hence when to fire put-completion; you should probably take a look at the busy::process() routine to understand it.

It has been suggested that we should add the busy record or something like it to base. Marty has a simple kind of busy record in the exampleCpp module.

I will look at Mark’s build issue when I get a chance, someone else here has also reported this, which is purely a warning message that I added but will probably disable for the final release.

- Andrew

--
Sent from my iPad

> On Nov 15, 2018, at 11:08 AM, Michael Davidsaver <mdavidsaver@gmail.com> wrote:
>
>> On 11/14/18 12:59 PM, Mark Rivers wrote:
>> I am having 2 issues with the version of base-7.0 that I updated today.
>>
>>
>>
>> 1)      Whenever I set a “busy” record to 0 in my drivers (e.g. areaDetector) I see this warning from modules/database/src/ioc/db/dbDbLink.c
>>
>>
>>
>> Warning: '13SIM1:cam1:AcquireBusy.PUTF' found true with PACT false
>
> Ha, now Andrew can feel smug.  I originally made this an assert().
>
> FYI. 7.0.2 has a change to the way the PUTF, PACT, and RPRO fields interact.
> The new protocol fixes an queuing issue when chaining multiple asynchronous records (via FLNK or OUT).
> This warning is flagging a state which I didn't think should ever happen.
> Though there is not any real harm if it does.
>
> Can you run in a debugger and set a break point on the errlogPrintf() in question?
> I'd like to know the exact stack trace (and thus DB link chain) involved.
>
> https://code.launchpad.net/~epics-core/epics-base/+git/prop-putf/+merge/336468
>
>
>> 2)      When I run “make” in any App/op/ that automatically converts adl files to opi, ui, etc. I get these warnings:
>>
>> corvette:modbus/modbusApp/op>make
>>
>> /corvette/usr/local/epics-devel/base-7.0.1/configure/RULES_COMMON:18: warning: overriding recipe for target `show-makefile.../../configure/CONFIG'
>
> I'll leave this one to Andrew.

Replies:
RE: Issues with latest version of base-7.0 Mark Rivers via Core-talk
References:
Issues with latest version of base-7.0 Mark Rivers
Re: Issues with latest version of base-7.0 Michael Davidsaver
Re: Issues with latest version of base-7.0 Johnson, Andrew N. via Core-talk

Navigate by Date:
Prev: We should take care of Ralph ;-) Heinz Junkes via Core-talk
Next: Re: New EPICS Releases Johnson, Andrew N. via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
Navigate by Thread:
Prev: Re: Issues with latest version of base-7.0 Marty Kraimer
Next: RE: Issues with latest version of base-7.0 Mark Rivers via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
ANJ, 20 Dec 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·