| 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: maxnet encoder problem |
| From: | Kevin Peterson via Tech-talk <tech-talk at aps.anl.gov> |
| To: | 백호령 <holyeongbaeg at gmail.com>, tech-talk at aps.anl.gov |
| Date: | Mon, 27 Nov 2023 09:28:03 -0600 |
What is the init string argument to the omsMaxNetConfig call? https://github.com/epics-motor/motorOmsAsyn/blob/fa94d1dfb5051591783637e137ebb16166590f8e/iocs/omsAsynIOC/iocBoot/iocOmsAsyn/MAXnet.cmd#L25 Which axis is misbehaving? Kevin On 11/19/23 18:21, 백호령 via Tech-talk wrote:
As I result of my search, i understand that OMS's MAXv and MAXnet can be used as the motorOmsAsyn of the epics motor module. For MAXv, the encoder pulse value is read correctly, but for MAXnet, the encoder pulse value is read correctly only at the beginning and splashes ti an odd value at the second move. Is this a problem with epics code?Or should I thinj of it as a hardware problem and solve it?Thank you for your help. Baeg.