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  2020  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: NDPluginPva - PV not appearing on network
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: "'Warrick, Edmund (DLSLtd, RAL, LSCI)'" <edmund.warrick at diamond.ac.uk>
Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
Date: Tue, 14 Sep 2021 16:35:21 +0000

Hi Ed,

 

I have not heard about a similar problem before.

 

Have you tried a more recent version of base, which would be a later version of pvAccess?  Are the other IOC that work OK using the same version of base and ADCore?

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Warrick, Edmund (DLSLtd, RAL, LSCI) via Tech-talk
Sent: Tuesday, September 14, 2021 11:04 AM
To: tech-talk at aps.anl.gov
Subject: NDPluginPva - PV not appearing on network

 

Hi,

 

I’m trying to use the NDPluginPva plugin from ADCore to support a live viewer application for one of our beamline detectors. On one of my detectors, I seem to see the EPICS v4 PV consistently fail to appear on the network.

 

Using ADCore 3-8, PVAccess 7-0-0, on RHEL7.9

 

Relevant parts of my ioc startup script:

 

# NDPvaConfigure(portName, queueSize, blockingCallbacks, NDArrayPort, NDArrayAddr, pvName, maxBuffers, maxMemory, priority, stackSize)

NDPvaConfigure("EXCBR.pva", 16, 0, "EXCBR.CAM", 0, BL14I-EA-EXCBR-02:PVA:ARRAY, 0, 0, 0, 0)

startPVAServer

 

No error messages produced, and no alarm state shown by any of the v3 PVs in the plugin – but a pvget to the PV returned by PvName_RBV consistently times out. pvlist shows the detector server as hosting a pvaserver instance, but pvlist <host ip>:<port> to list the hosted PVs also times out.

 

I suspect some sort of race condition – by stripping back the IOC, removing everything but the PVA plugin and a simdetector instance, I can get it to successfully start serving the PV on startup some of the time, although sometimes it still fails to appear. When using the full detector driver IOC, it always fails.

 

Other ADCore IOCs on the same network using NDPluginPva respond to pvget requests as expected, and running up one of these IOCs temporarily on the same detector server also results in its PVA PV appearing.

 

I’d appreciate any assistance you can suggest with debugging this. I’m happy to provide any further diagnostic information that may help.

 

Thanks,

 

Ed Warrick

Senior Software Systems Engineer

Diamond Light Source

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 


References:
NDPluginPva - PV not appearing on network Warrick, Edmund (DLSLtd, RAL, LSCI) via Tech-talk

Navigate by Date:
Prev: NDPluginPva - PV not appearing on network Warrick, Edmund (DLSLtd, RAL, LSCI) via Tech-talk
Next: Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Kuldeep Joshi 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  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: NDPluginPva - PV not appearing on network Warrick, Edmund (DLSLtd, RAL, LSCI) via Tech-talk
Next: socketcan driver and the tudsocketcan 曹彪 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  2020  <20212022  2023  2024 
ANJ, 16 Sep 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·