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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Breakpoint tables status and usage in EPICS |
From: | Andrew Johnson <[email protected]> |
To: | Abadie Lana <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Fri, 15 Mar 2013 12:00:19 -0500 (CDT) |
Hi Lana, On Mar 15, 2013, at 6:04 AM, Abadie Lana <[email protected]> wrote:
It is apparently possible, but not an officially supported practice. I believe BESSY-2 do this, so Ralph should be able to help you with how they actually do it. The blueprint that you found was something I wrote to try and get that ability included officially, but so far it hasn't gone any further than those ideas. The complication that is hinted at in the blueprint is that the records hold a pointer to the actual breakpoint table in memory if they are using one, but there is no locking or other way to communicate with the individual record instances if the table gets modified or replaced. The built in support routines are available to any record type, but are currently only used by the ai and ao record types in Base. They could also be used by subroutine record code. That would have to be done manually (i.e. with subroutines or aSub records) at the moment unless you write your own record type to do it.
That would be an obviously useful thing to implement if someone hasn't already done it (what does the cvt record do?). -- Sent from my iPad |