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: Using Motor Record with READBACK Deadband and number of Retries. |
From: | "Rarback, Harvey M." <[email protected]> |
To: | "Williams Jr., Ernest L." <[email protected]>, Tech-talk <[email protected]> |
Date: | Thu, 15 Jul 2010 16:32:23 -0700 |
Ernest, > We are currently using "Motor Record Version 5.9" > on some of our stepper motor applications. > > We would like to use the motor software with USE READBACK enabled. > We are connecting our calibrated LVDT to the READBACK link. > > What has been your experience in using this feature of the Motor Record? At SPEAR we are using motor record 6.22. All our motors use the readback link to external encoders. Although we have had some issues with callbacks going astray with soft motors (ask Till!), the external readback links seem to work ok. > When using READBACK inlink for Motor position sensing: > (1) Selecting YES/NO does not update the motor record properly. > Should the software actually copy the contents of MOTOR.VAL to MOTOR.RBV > If READBACK is toggled back to "NO" > > If the READBACK is set to "YES" then "MOTOR.RDBL", should be copied to > MOTOR.RBV ? I believe your problem is "YES" is not equal to "Yes". It bit me too ;-) --Harvey