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

Subject: Re: Unpredictable behaviour with PyEpics
From: Matt Newville via Tech-talk <tech-talk at aps.anl.gov>
To: Jaroslav Adam <jaroslavadam299 at gmail.com>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 26 May 2020 10:07:44 -0500
Jaroslav, Simon, 

On Tue, May 26, 2020 at 9:14 AM Jaroslav Adam via Tech-talk <tech-talk at aps.anl.gov> wrote:
Hi Simon,

verify what PYEPICS_LIBCA is pointing to. It is the library which PyEpics
is using to make connections.

From my experience with running PyEpics inside a PythonSoftIoc, the PYEPICS_LIBCA
should point to the same channel access library as the IOC is using.

Is Simon trying to use pyepics from a Python interpreter embedded in an IOC?  I do not read that from Simon's original message.

I hope that it is obvious to anyone trying to use pyepics from a Python interpreter embedded in an IOC that this definitely requires care in loading the Channel Access library.  The process running the IOC needs to have exactly one libca (and libCom) loaded.  That will be set before the Python interpreter is started, so the pyepics library (which loads libca as late as possible) would need to point to the same one that the IOC is linked against.
 
PYEPICS_LIBCA can be used to override the default CA library used by pyepics (which is distributed with pyepics, not some "system default"). 

Just for completeness, a similar situation of potential conflict between versions of libca/libCom can arise if using pyepics with PCASpy.  I believe that PCASpy loads libca on "import pcaspy", so that pyepics should be imported *after* PCASpy and ensure that PYEPICS_LIBCA points to the same libca file.

--Matt 


Replies:
Re: Unpredictable behaviour with PyEpics Simon Rose via Tech-talk
References:
Unpredictable behaviour with PyEpics Simon Rose via Tech-talk
Re: Unpredictable behaviour with PyEpics Jaroslav Adam via Tech-talk

Navigate by Date:
Prev: Re: Unpredictable behaviour with PyEpics Jaroslav Adam via Tech-talk
Next: SoftIOC and Labview Mostafa, Jalal (IPE) via Tech-talk
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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Unpredictable behaviour with PyEpics Jaroslav Adam via Tech-talk
Next: Re: Unpredictable behaviour with PyEpics Simon Rose via Tech-talk
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  <20202021  2022  2023  2024 
ANJ, 27 May 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·