Experimental Physics and
Industrial Control System

Zimoch Dirk via Tech-talk <tech-talk at aps.anl.gov> · Thu, 16 Nov 2023 08:04:44 +0000

Hi Andrew,

That is interesting. I have never seen this behavior and would like to reproduce
it. But for that, I need to understand exactly what happens.

StreamDevice claiming something "unexpected" happens of course means that I
never expected it to happen and thus I have no idea how to force this behavior.
Thus, the more precisely you can tell me what exactly your instrument does, the
higher the chance I can fix it.

Does the instrument shutdown its socket? Or does it simply switch off its
network interface? Or is it for example a firewall that interrupts the
connection? Can you get the same behavior switching off your instrument or
pulling the network cable? Anything I can try without having access to your
instruments?

Dirk

On Wed, 2023-11-15 at 19:24 +0000, Wang, Andrew via Tech-talk wrote:
> 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
>  

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System