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: | AreaDetector 2-5, NDPluginDriver |
From: | "Madden, Timothy J." <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Tue, 22 May 2018 15:48:59 +0000 |
Dear Tech Talkers (or Mark):
I am rather stuck in writing a plugin for AD, even though I have done about 20 of these. I am inheriting from NDPluginDriver, and the plugin never responds to NDArrays from the driver. The driver is working OK, as other plugins can get arrays from them.
I call start() in the plugin constructor to start the plugin threads etc.
The IOC console gives on startup:
2018/05/22 10:35:24.570 NDPluginDriver::start timeout waiting for plugin thread start event
So it looks like the plugin is never starting up. Why would this happen? How to debug it? Very strange. Never seen this one before. I have been hacking on this for awhile.
Is there a way to ask a driver how may plugins are waiting for NDArrays? Or to list listening plugins with something like asynReport?
I stepped through the code with debugger, and I don't think my plugin is in the list of pClients the driver uses to pass arrays.
Also, I have seen other plugins like the FFT plugin, that do not call start(), but I assume they work. Am I supposed to call start? I have another plugin that only works if I call start.
Frustrated, Tim Madden
|