Experimental Physics and Industrial Control System
|
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]]
Sent: Tuesday, October 24, 2017 2:34 PM
To: Mark Rivers
Cc: EPICS mailing list
Subject: Re: Problems getting PI motors working
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!
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?
|
- References:
- Problems getting PI motors working Eric Norum
- RE: Problems getting PI motors working Mark Rivers
- Re: Problems getting PI motors working Eric Norum
- Navigate by Date:
- Prev:
Re: Problems getting PI motors working Eric Norum
- Next:
Re: Online EPICS training Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
Re: Problems getting PI motors working Eric Norum
- Next:
standard motion connections and pinouts Ernesto Paiser
- 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
|
ANJ, 21 Dec 2017 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|