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  2021  2022  <20232024  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  <20232024 
<== Date ==> <== Thread ==>

Subject: RE: StreamDevice (streamCore::readCallback called unexpectedly)
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: "Wang, Andrew" <wang126 at llnl.gov>, EPICS tech-talk <tech-talk at aps.anl.gov>
Date: Wed, 15 Nov 2023 20:30:50 +0000
  • We have them set to DHCP and a timeout of 30s meaning that the connection closes if the instrument does not receive TCP/IP commands after 30s.

 

Where have you set the 30 second timeout?  Have you set the option “disconnectOnReadTimeout” on the drvAsynIPPort?

 

Can you show the relevant lines in the startup script, and the protocol file?

 

Mark

 

 

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Wang, Andrew via Tech-talk
Sent: Wednesday, November 15, 2023 1:24 PM
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: StreamDevice (streamCore::readCallback called unexpectedly)

 

Hi all,

 

This is kind of a general question, but we have an IOC that is running 24 instruments, all of the same type. We have them set to DHCP and a timeout of 30s meaning that the connection closes if the instrument does not receive TCP/IP commands after 30s.

 

I have a fanout that processes records and fetches values from the instruments through queries defined in a protocol file. After 30s, the IOC would output a plethora of error messages from StreamDevice that all say streamCore::readCallback(rec_name) called unexpectedly. It doesn’t do that every 1 second, which is what I have the scan rate of the fanout record set to.

 

It would be great if somebody could shed some light on scenarios that could cause this error message to be generated.

 

Thank you,

Andy

 

Purple ribbon awareness

 


References:
StreamDevice (streamCore::readCallback called unexpectedly) Wang, Andrew via Tech-talk

Navigate by Date:
Prev: StreamDevice (streamCore::readCallback called unexpectedly) Wang, Andrew via Tech-talk
Next: Highland P500 support? Jeff Kirchman 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  2021  2022  <20232024 
Navigate by Thread:
Prev: StreamDevice (streamCore::readCallback called unexpectedly) Wang, Andrew via Tech-talk
Next: Re: StreamDevice (streamCore::readCallback called unexpectedly) Zimoch Dirk 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  2021  2022  <20232024 
ANJ, 16 Nov 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·