| 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: motor record: soft motor & DMOV |
| From: | "Konrad, Martin" <[email protected]> |
| To: | "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> |
| Date: | Tue, 10 Sep 2013 16:45:02 +0000 |
Hello motor record maintainers, further investigation revealed that this problem can also occur without motor record (cf. the new thread on http://www.aps.anl.gov/epics/tech-talk/2013/msg01898.php). BUT: The problem with short 1-0-1 transitions could be avoided if the record using this data is in the same lock set as the motor record. Sure I can use NPP+FLNK to connect other records to the motor record's DMOV field. But unfortunately it seems motor record does not trigger its forward link after setting DMOV to 0. This makes NPP+FLNK pretty useless for this field... Is it possible to trigger the forward link when DMOV goes to 0 without breaking hundreds of other applications? From the documentation I was expecting that DLY=1 should stretch the time of the 1-0-1 transition to 1 second. But that doesn't have any effect if the motor does not need to be moved. Is this the intended behavior (the documentation does not cover this special case)? Any suggestions how to fix my problem? Martin