| 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: read RVB and VAL don't match when moving smarAct motors without encoders |
| From: | Kevin Peterson via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Juliane Reinhardt <jreinhardt at lbl.gov>, Mark Rivers <rivers at cars.uchicago.edu> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Thu, 12 Nov 2020 17:27:17 -0600 |
2020/11/12 15:11:03.905 192.168.168.200:5000 write 5\ :GP1\\n\ 2020/11/12 15:11:03.908 192.168.168.200:5000 read 8\ :E1,129\\n\ 2020/11/12 15:11:03.912 192.168.168.200:5000 write 5\ :GA1\\n\ 2020/11/12 15:11:03.915 192.168.168.200:5000 read 8\ :E1,129\\n\ The sensor type that is returned is 1: :GST1\\n\ 2020/11/12 15:11:03.912 192.168.168.200:5000 read 7\ :ST1,1\\n\A sensor type of 1 is a "linear positioner with nano sensor", according to the MCS RS-232 interface documentation.
I don't see any commands that would query a theoretical position of an axis that doesn't have an encoder. If SmarAct can provide that information, we can modify the driver to use it.
Kevin On 11/12/20 5:16 PM, Juliane Reinhardt wrote:
Hi Mark, does the output in the txt attachment make more sense to you? Cheers, Juliane