| 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: | RE: Problems getting PI motors working |
| From: | Mark Rivers <[email protected]> |
| To: | 'Eric Norum' <[email protected]> |
| Cc: | EPICS mailing list <[email protected]> |
| Date: | Tue, 24 Oct 2017 19:50:39 +0000 |
|
You are definitely not the first person to make this mistake, which I why I recognized it right away. We should probably print a better error message from devMotorAsyn than just reporting that the int32 interface is not found, providing
more of a hint as to what is probably wrong. Mark From: Eric Norum [mailto:[email protected]]
Is my face ever red. Yes, I had the wrong ASYN port name in the database. I was referring to the TCP port not the motor port. All working now. Sorry for the interruption!
On Oct 24, 2017, at 10:52 AM, Mark Rivers <[email protected]> wrote: That error about the int32 interface not being found is familiar. It is usually a problem with the database file, where the wrong asyn port name is used in the motor record INP link. It should be the port for the asynMotorController driver,
i.e. PIE873_1 or PIE873_1 in your case. But perhaps instead you have used the name of the underlying TCP port, i.e. pie873A or pie873B in your case? Mark -- |