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: | Altering motor resolution via MRES field |
From: | "Marco A. Barra Montevechi Filho via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Cc: | SOL <sol at lnls.br> |
Date: | Thu, 10 Nov 2022 12:51:58 +0000 |
Hello all,
We are using a micosIOC (https://github.com/epics-motor/motorMicos.git) to control an UPR-160 motor: https://www.pi-usa.us/fileadmin/user_upload/pi_us/files/product_datasheets/Air_Bearing_Rotation_Stages_UPR-Air_Family.pdf According to the motor technical data, its resolution can go down to 0.00004 degrees. The current IOC has a motor with .MRES=0.04 deg, so we cant make movements smaller than this. When i caput MRES to 0.004, i can caput .VAL from 0.1 to 0.105, for example, and the motor will move. However, although the .RBV shows the movement incrementing 0.005 degrees, the actual observed movement is of 0.05 degrees. In other words: changing the motor MRES to ten times lower makes the motor move ten times more than what is commanded. We (me and Augusto Horita) also tried using the SMChydraChangeResolution("Hydra1", 1, 0.004) function and leaving MRES as 0.004 in substitutions, but the same behavior was found. Am i doing something wrong? Thanks for any help, Marco Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente. Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately. |