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  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: How to be warned when a record processing is ignored because already busy (PACT=1)
From: haquin <[email protected]>
To: [email protected]
Date: Tue, 30 Sep 2008 09:51:57 +0200
Hi all,

Here is what I do:
a Calcout record output its value into the VAL field of a Waveform record (using a Process Passive link triggering the processing of the Waveform).
Then the Waveform record performs a Modbus/TCP write access with Asyn/Modbus device support.


My problem is the following:
Sometime though the last value is in the VAL field of the Waveform record it is not written via Modbus.
I have already investigated on the Asyn/Modbus side, but it turns out that when the problem occurs Asyn/Modbus is not even called.


It seems that the problem occurs when the Calcout record requests the Waveform record for a new Modbus write access but the Waveform record is still busy with the previous one...
Can someone explain me how to be warned or informed when the processing request of a record is ignored because it is still busy (PACT=1).


I tried setting field TPROC=1 to check if the Waveform trace is missing when the problem occur,
but this is intrusive and the problem is then not reproducible...


thanks.

begin:vcard
fn:Christophe Haquin
n:Haquin;Christophe
email;internet:[email protected]
tel;work:02 31 45 46 61
x-mozilla-html:FALSE
version:2.1
end:vcard


Replies:
Re: How to be warned when a record processing is ignored because already busy (PACT=1) Tim Mooney
Re: How to be warned when a record processing is ignored because already busy (PACT=1) Ben Franksen

Navigate by Date:
Prev: An error when building EPICS base R3.14.9 on Solaris 8 Evgeniy Tikhomolov
Next: Question about a tutorial wiritten by Norum Silver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: An error when building EPICS base R3.14.9 on Solaris 8 Andrew Johnson
Next: Re: How to be warned when a record processing is ignored because already busy (PACT=1) Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·