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 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 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: StreamDevice/AsynIPPort question |
From: | Mark Rivers <[email protected]> |
To: | "'Michael Westfall'" <[email protected]> |
Cc: | "[email protected] Talk" <[email protected]> |
Date: | Fri, 11 Nov 2016 18:40:00 +0000 |
Is there a way to debug where it crashes when running on RTEMS? From: Michael Westfall [mailto:[email protected]]
We are using an RTEMS MVME-2700 target, with Asyn-4-29-1 and StreamDevice-2-6 On Thu, Nov 10, 2016 at 6:34 PM, Mark Rivers <[email protected]> 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:
[email protected] [mailto:[email protected]]
On Behalf Of Michael Westfall
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") 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
|