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: Re: Scan Time Definitions
From: Matthieu Bec <[email protected]>
To: Erik Johansson <[email protected]>
Cc: David Dudley <[email protected]>, [email protected]
Date: Mon, 11 Aug 2008 22:42:07 -0400

Hi,


I like SNL because it keeps the wake-up logic within the same process as the ioc. One option would be to couple it with pvload: you keep different (schedule) files with <record>.PROC=1 and SNL only has to run pvload at established schedule.

Matthieu

Erik Johansson wrote:
Hi Matthieu and Stephanie,

I replied separately to David, but perhaps should have cc'ed tech-talk
as well. I proposed that he could easily use event records combined with
a simple cron job to achieve what he wants. You could easily group
records with a desired scan time into a corresponding event and use a
cron job to trigger the event  via caput (or something similar).

Erik

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Matthieu Bec
Sent: Monday, August 11, 2008 3:38 PM
To: Allison, Stephanie
Cc: David Dudley; [email protected]
Subject: Re: Scan Time Definitions



As much as I would consider adding scan "60 second", and that seems human readable enough, I would ponder on SCAN="4 hours": when you get the sample would depend on iocInit time, not necessarily the intented purpose?
It sounds like a problem SNL would better address, schedule something to happen at midnight, 4 am etc.



Allison, Stephanie wrote:
Hi,

The SCAN field is an enum-type. You can alter epics-base
and extend
the range of options, but it will remain enum. Are you refering to another mechanism? 'seq' records allow specifying arbitrary delay DLY<n> when to process OUT<n> links, but that's also in seconds.
Even though SCAN is enum, the scan task finds the # of
seconds (which it uses to delay between cycles) from the menu ASCII name using strtod (see 17.3.1 of the App Dev Guide). This is unusual. It would be nicer if menuScan.dbd had 3 fields for every option - the enum value (index number), the user-friendly name, and the "raw" name which is used by the scan task. But this is a change to epics base and probably not worth the effort.
Stephanie Allison


-- Matthieu Bec Gemini Observatory Tel: +56 51 205785 c/o AURA, Casilla 603 Fax: +56 51 205650 La Serena, Chile





--
Matthieu Bec              Gemini Observatory
Tel: +56 51 205785        c/o AURA, Casilla 603
Fax: +56 51 205650        La Serena, Chile

References:
Scan Time Definitions David Dudley
Re: Scan Time Definitions Matthieu Bec
RE: Scan Time Definitions Allison, Stephanie
Re: Scan Time Definitions Matthieu Bec
RE: Scan Time Definitions Erik Johansson

Navigate by Date:
Prev: RE: Scan Time Definitions Erik Johansson
Next: Re: Scan Time Definitions Maren Purves
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: Scan Time Definitions Erik Johansson
Next: RE: Scan Time Definitions Allison, Stephanie
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 ·