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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Understanding Asyn-based motor controller driver |
From: | Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 9 Jan 2023 10:42:51 +0000 |
Hi I am trying to understand how a motor controller driver works and how the asynMotorController and Axis classes map to the EPICS motor record. For example, I am investigating this driver from ACS motion
https://github.com/epics-motor/motorAcsMotion to see if it supports some functions from the motor record that are required by our data acquisition system. Here are my questions: 1.
motor jogging: since the class does not implement the “::moveVelocity” function, does this mean that the driver does not support jogging at all? Or it does at the low-level motor record interface? 2.
VELO and ACCL fields: The class uses different variables to hold acceleration and velocity information other than the base class’s variables “motorVelocity_” and “motorAccel_”. Does this mean that VELO and ACCL
fields are useless? Same thing goes for the OFF field. In other words, if a motor driver is based on the motor record, does this guarantee that all fields are functional and working with the controller? How to verify if a certain function not implemented in the asyn classes but working and
implemented somewhere else? Best Regards, Abdalla Al-Dalleh Control Engineer SESAME (Synchrotron-light for Experimental Science and Applications in the Middle East) Fax: +96253511423 abdalla.ahmad at sesame.org.jo |