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

Subject: RE: Building motor6-3 record
From: "Mark Rivers" <[email protected]>
To: "David Morris" <[email protected]>, <[email protected]>
Date: Thu, 3 Apr 2008 17:37:17 -0500
David,

I am not familiar with the Galil driver, but here is something to be
aware of.

The are 2 different uses of asyn in the "motor" module.

1) As the low-level interface between the motor record drivers and
serial or TCP/IP devices.  This use is quite old, and is used by many
"non-asyn" device drivers.

2) As a medium level interface between motor record device support and
new drivers.  This is a relatively new development, with an asyn device
support and driver support that are both device-independent.  This is
probably what you meant by "asyn drivers".

So it is possible that you are building the motor module with drivers
that are not in category 2, but still needs asyn because they are in
category 1.

Mark

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of David Morris
> Sent: Thursday, April 03, 2008 4:08 PM
> To: [email protected]
> Subject: Building motor6-3 record
> 
> Hello all
>   We are trying valiantly but unsuccessfully to build the 
> motor record 
> 6-3 to incorporate the Galil motor driver from ALS (a non-asyn device 
> driver). In trying to build the NoAsyn example of the motor 
> record, we 
> are constantly encountering the requirement to have asyn. We have not 
> yet tried this on a clean install of base, but suspect there 
> may be some 
> debris from our asyn build (used for another project) leaking 
> over into 
> the motor record build. Has anyone experienced this, and 
> found a solution?
> 
> Thanks in advance.
> 


References:
Building motor6-3 record David Morris

Navigate by Date:
Prev: genSub and capture monitor event Emmanuel Mayssat
Next: Re: genSub and capture monitor event Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Building motor6-3 record David Morris
Next: Re: Building motor6-3 record Ron Sluiter
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·