RE: StreamDevice/AsynIPPort question

[Mark Rivers <rivers@cars.uchicago.edu>]

Is there a way to debug where it crashes when running on RTEMS?

 

From: Michael Westfall [mailto:mwestfal@gemini.edu]
Sent: Friday, November 11, 2016 12:06 PM
To: Mark Rivers
Cc: tech-talk@aps.anl.gov Talk
Subject: Re: StreamDevice/AsynIPPort question

 

We are using an RTEMS MVME-2700 target, with Asyn-4-29-1 and  StreamDevice-2-6

I think it may actually be an RTEMS BSP problem, because today I ran the same test using a Linux soft IOC, and the IOC doesn't crash when the socket isn't available like it does when running the IOC on the VME target.

 

On Thu, Nov 10, 2016 at 6:34 PM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

I run many IOCs on Linux that use StreamDevice to devices that are often disconnected for weeks, and the IOCs don’t crash.

 

What version of EPICS base, StreamDevice and  asyn are you running?

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Michael Westfall
Sent: Thursday, November 10, 2016 2:31 PM
To: tech-talk@aps.anl.gov Talk
Subject: StreamDevice/AsynIPPort question

 

We are having problems with IOC crashing when a device connected by an IP socket is unavailable.

For example, in the startup script is a line like:

drvAsynIPPortConfigure("temp", "172.16.5.218:10010")

and a StreamDevice record that uses that IP port when it calls it's protocol.

 If we unplug the ethernet cable from the device (or just power it off) the IOC crashes after a short while. No error is emitted on the console  to indicate that the connection has failed.

So, I'm wondering if there is something we need to do in setting up the AsynIPPort  or the StreamDevice protocol file in order to gracefully handle the case where the socket disappears and can't be reconnected to....

Thanks,

--

Mike Westfall

Control Systems Software Engineer

--

Mike Westfall

Control Systems Software Engineer