- 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