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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Using asynDriver outside of an EPICS IOC |
From: | Mark Rivers <[email protected]> |
To: | "'Emmanuel Mayssat'" <[email protected]>, Jimmy Johnson <[email protected]>, EPICS mailing list <[email protected]> |
Date: | Mon, 26 Jan 2015 22:48:53 +0000 |
> Or are you saying that asyn can be used to interface with hardware in any other control system? The main motivation for using asyn in another control system would be to take advantage of drivers that have been written using asyn. This includes areaDetector and supports for lots of
other hardware. As Andrew said, both the asyn core (asynManager) and the existing asyn drivers use libCom for mutexes, queues, etc. The alternative would be boost or something similar, but libCom is very
portable (does boost run on vxWorks and RTEMS?) and it is what the existing asyn code uses. Mark
From: Emmanuel Mayssat [mailto:[email protected]]
Mark, From:
[email protected] Has anyone used the asynDriver framework outside of an EPICS IOC and if so would you be willing to share your experience? Thanks Jimmy Johnson |