| 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 <2025> | 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 <2025> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Motor driver and lost TCP connection |
| From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Tech Talk <tech-talk at aps.anl.gov>, Torsten Bögershausen <tboegi at edom.se> |
| Date: | Fri, 24 Jan 2025 14:31:33 +0000 |
|
Hi Torsten,
You need to be specific about what you mean by "connection is lost". Does asyn really think the port is disconnected, i.e. the socket is closed? Or is it just getting timeouts, but the socket is still connected? You can use the asynReport command or the
asynRecord GUI to tell.
Does the poller ever start working again?
What caused the disconnect, a network interruption or power-cycling the controller?
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Torsten Bögershausen via Tech-talk <tech-talk at aps.anl.gov>
Sent: Friday, January 24, 2025 9:06 AM To: Tech Talk <tech-talk at aps.anl.gov> Subject: Motor driver and lost TCP connection Hej Motorist,
Working with a Newport Hexapod I realized that there is a "mismatch" between asyn and the motorDriver. When the connection is lost, it seems that a) asyn starts the autoconnect every 5 seconds. b) the poller tries to poll every 1 second (or so) However, the polling fails each time. Is there a better handling ? Someone who has written something to stop the poller ? BR /Torsten |