| 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: | RE: preventing changing an EPICS motor's commanded position |
| From: | "Goetze, Kurt via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "Gregory, Ray" <gregoryrd at ornl.gov> |
| Cc: | Tech-talk <tech-talk at aps.anl.gov> |
| Date: | Tue, 3 Oct 2023 18:19:42 +0000 |
|
Hi Ray, “motor.db” loads a bo record, “$(P)$(M)_able”, that the motor record’s SDIS field points to. We use this to enable/disable the motor record. When disabled, writes to the motor record’s .VAL field are not allowed. Kurt From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of
Matt Newville via Tech-talk Ray, Perhaps what you're looking for is simply to set the Motor Record low and high limits to the drive value you want to maintain. You could also set the SPMG field to 0 or 'Stop'. That would allow someone to change the VAL field (which is what you said you wanted to not allow), but it will prevent the Motor from actually
moving until SMPG is changed back to 2 or 'Go'. Both of these use the exposed interface to the Motor Record, so in principle can be changed at any time. But they are also not uncommon things to do for motors that you want to not accidentally move. On Tue, Oct 3, 2023 at 8:17 AM Kevin Peterson via Tech-talk <tech-talk at aps.anl.gov> wrote:
-- --Matt Newville <newville at
cars.uchicago.edu> 630-327-7411 |