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  <20112012  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  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: asyn connection management with asynPortDriver
From: "Mark Rivers" <[email protected]>
To: <[email protected]>, <[email protected]>
Date: Thu, 9 Jun 2011 11:16:44 -0500
Hi Euan,
 
I am away from the lab, but I will look into this and get you an answer when I return on June 20.  It seems like the asyn record should do what you want, but maybe something is wrong.
 
Meanwhile perhaps Eric Norum can help :-)
 
Mark
 

________________________________

From: [email protected] on behalf of [email protected]
Sent: Wed 6/8/2011 8:25 PM
To: [email protected]
Subject: asyn connection management with asynPortDriver



Hi,

I would like to use the connection management features of asyn with a driver based on the asynPortDriver class. If I create the port driver class with the autoconnect flag set to true I can use the asynRecord CNCT field to connect or disconnect a device from the port. If autoconnect is set to false, then when the IOC starts up, the following messages appear:

iocRun: All initialization complete
epics> 2011/06/09 10:51:51.625 as:t:as01:drx:s1:asynRecord: queueRequest failed for special.
2011/06/09 10:51:51.625 as:t:as01:drx:s1:asynRecord: port drx1 not connected

If I try and use the CNCT field if the asyn record to connect a device then a similar message is produced:
epics> 2011/06/09 11:00:29.564 as:t:as01:drx:s1:asynRecord: exception 2
2011/06/09 11:00:39.172 as:t:as01:drx:s1:asynRecord: queueRequest failed for special.
2011/06/09 11:00:39.172 as:t:as01:drx:s1:asynRecord: port drx1 not connected

As I understand the setup, the asynPortDriver constructor will connect the port and the class methods connect() and disconnect() will connect  devices to the port. I have derived these methods in my class so that I can manage connections but without autoconnect to make the first connection these methods are not called. So even though the port is connected, without autoconnect I can't connect any devices to the port. I guess there is some setup I haven't performed. I would like advice as to how to manage the connections. I am using asyn 4.16 with EPICS 3.14.12.

cheers,

Euan.





Replies:
Re: asyn connection management with asynPortDriver Euan.Troup
References:
asyn connection management with asynPortDriver Euan.Troup

Navigate by Date:
Prev: APS Website issues Andrew Johnson
Next: Sequencer Preprocessor Build Rules Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: asyn connection management with asynPortDriver Euan.Troup
Next: Re: asyn connection management with asynPortDriver Euan.Troup
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·