EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: getAddress method behaviour
From: Mark Rivers <[email protected]>
To: "Heesterman, Peter J" <[email protected]>
Cc: "EPICS Tech-Talk \([email protected]\)" <[email protected]>
Date: Mon, 22 Dec 2014 15:20:35 +0000
I suspect you are passing the wrong pasynUser to getAddres(). Are you passing the one that was passed into writeInt32 or the pasynUserSelf? You should pass the former.

Mark

Sent from my iPhone

On Dec 22, 2014, at 9:12 AM, Heesterman, Peter J <[email protected]<mailto:[email protected]>> wrote:

Hi Mark,

I’m sorry to trouble you.

In my application I am seeking to connect multiple devices (i.e. multiple pumps, in this case).

So, for example, I have record names like:
TURBOSIM:5:WarningTemperature (5 being the last of 5 devices connected).

I had expected asynPortDriver::getAddress to emit the index of the device being addressed (0..4, in this example).

But the only address value I can detect being emitted from the method, is 0 (e.g. when called within readInt32).
I believe it is being invoked with asynUser(s) that are correctly associated with a specific device.

What could I be missing?

Many thanks,

Peter.





Replies:
RE: getAddress method behaviour Heesterman, Peter J
References:
getAddress method behaviour Heesterman, Peter J

Navigate by Date:
Prev: getAddress method behaviour Heesterman, Peter J
Next: RE: getAddress method behaviour Heesterman, Peter J
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: getAddress method behaviour Heesterman, Peter J
Next: RE: getAddress method behaviour Heesterman, Peter J
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·