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: Canberra AIM MCA 556B |
From: | Mark Rivers <[email protected]> |
To: | "'[email protected]'" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 18 Jul 2013 16:42:10 +0000 |
Hi Peter, Thanks very much for the information. The problem the BNL people are having has been identified, but we don’t know what is causing it. When the AIM software is started on the IOC it does the following: - Starts a thread that listens for status responses from AIM modules. Those status responses are used to build a table of available AIM modules on the network. - Starts a thread that periodically sends multicast messages asking for AIM modules to send status responses. Those messages are sent every 20 seconds. - The main thread waits for the first response from any module, with a timeout of 3 seconds. At BNL the main thread is not getting any response within 3 seconds. If they increase the timeout to greater than 20 seconds it works. If they change the message rate
to every 5 seconds instead of 20 then they can decrease the timeout to 5 seconds. It appears that what is happening is that the EPICS code is missing the first response from the module, and only getting the second and subsequent responses. I assume that you have not had this problem, and the default message rate and timeout are working for you? Thanks, Mark From: [email protected] [mailto:[email protected]]
On Behalf Of [email protected] Hi Mark,
|