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 2021 2022 <2023> 2024 2025 | 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 2021 2022 <2023> 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | More precise timing for record processing |
From: | "Sobhani, Alex via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 29 May 2023 01:35:27 +0000 |
The SCAN field lets you choose from .1, .2, .5, 1, 2, 5, or 10 seconds. In cases where this is not enough, is there a simple way to make a record process at other intervals such as 2.7 seconds or 5.4 seconds, specified at runtime? I know
you can add options for more periods of the SCAN field by editing dbd files, but you cannot change your mind at runtime. I envision something like this: record(timer, “BL0:mytimer”){ field(PERI, 2.7) field(FLNK, “BL0:mytrigger”) } And then subfields to enable/disable it. Does anything like this exist? I would imagine that something like this would be very generally useful. Alex |