EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  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  Index 1994  1995  <19961997  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 
<== Date ==> <== Thread ==>

Subject: Re: PACT -> SDIS
From: Ian Smith <[email protected]>
To: Marty Kraimer <[email protected]>
Cc: [email protected]
Date: Wed, 14 Feb 1996 15:54:37 +0000 (GMT)
Hi, 

thanks for the reply:

On Tue, 13 Feb 1996, Marty Kraimer wrote:

> > 1: I can't monitor the PACT leg with either probe or cau etc, nothing can 
> >    connect to it, so it is impossible to verify its operation.
> > 
> 
> I think that what you mean is that db_post_event is not called for
> this field. It is possible to look at PACT with cau, probe, etc.
> The problem is that  monitors are never triggered.

I couldn't get probe to connect.  In an attempt to put a copy of the error 
message here I tried just now to connect with probe, and today it did 
connect(??).  So yes you can use probe etc to connect to the PACT field, 
but as you point out you won't see any change in value.

> I would image that what you want is to detect records that are stuck,
> i.e.PACT is true forever. 

In my particular case I'm doing something else; if you imagine a pipeline 
of records with the first one activating every 10 secs and the rest 
passive but with FLNK daisey chained.  Just occasionally a subroutine record 
half way down takes longer to process than 10 seconds, so its PACT field is 
used to stop the first record starting up again until the pipeline has 
completed.

No doubt a call back solution could implemented, but I thought it easier 
to use the PACT and SDIS fields.  It does work, I just couldn't prove it!
 
> > 2: If the record is actively processing, say every 10 seconds, then it 
> > seems to count the number of times it should have activated whilst it is 
> > disabled and then, when it is re-enabled, it seems to process n 
> > times without a 10 second wait between each. Ie, if it was disabled for 60 
> > seconds then when it is re-enabled, it processes at least twice, perhaps 
> > 6 times, instantaneously.  The record behaves itself if it is passive.
> > 
> 
>This is called "Cached Puts"
> 
Yes, that fits, the records process so fast (compaired with us humans) 
that it was difficult to tell if it was 6 times or twice.

I'm not sure what to suggest for the dillema this has exposed, but thanks 
for confirming the behaviour of the database.

cheers

Ian A Smith			Telephone: +44 (0) 131 668 8257
Royal Observatory		Fax:       +44 (0) 131 668 1130
Blackford Hill			Web:       http://www.roe.ac.uk/
Edinburgh
EH9 3HJ
UK


References:
Re: PACT -> SDIS Marty Kraimer

Navigate by Date:
Prev: Re: macro substitution Jim B. Kowalkowski
Next: Re: PACT -> SDIS Marty Kraimer
Index: 1994  1995  <19961997  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: PACT -> SDIS Marty Kraimer
Next: Re: PACT -> SDIS Marty Kraimer
Index: 1994  1995  <19961997  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·