On 01/26/2015 12:34 PM, Emmanuel Mayssat wrote:
> Are you saying that an EPICS database can be populated with data coming
> from another control system?
That is possible but not what was meant by this feature.
> Or are you saying that asyn can be used to interface with hardware in
> any other control system?
> In this latter case, why even depend on libCom from the EPICS base then?
The code in Asyn that implements EPICS device support and knows how to
talk the IOC can be disabled from the build, allowing you to build and
use Asyn within other control systems instead. You would have to write
equivalent interface code to the devEpics layer for that alternative
control system though.
Asyn makes use of libCom and the EPICS build system to provide it with
OS-independent APIs for things like threads, mutexes and semaphores,
system time, network sockets, message queues, ring buffers etc. If it
didn't rely on libCom for these it would have to implement its own
versions of most of the code in base/src/libCom/osi and some facilities
from the other libCom source directories as well.
- Andrew
--
Doctorow's Law: Anytime someone puts a lock on something you own,
against your wishes, and doesn't give you the key, they're
not doing it for your benefit.
- References:
- Using asynDriver outside of an EPICS IOC Jimmy Johnson
- RE: Using asynDriver outside of an EPICS IOC Emmanuel Mayssat
- Navigate by Date:
- Prev:
RE: Using asynDriver outside of an EPICS IOC Emmanuel Mayssat
- Next:
setting interpreter in EPICS Ana Malagon
- 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: Using asynDriver outside of an EPICS IOC Emmanuel Mayssat
- Next:
RE: Using asynDriver outside of an EPICS IOC Mark Rivers
- 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
|