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: Issues in MCA module with XFlash detector |
From: | Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu>, "tech-talk at aps.anl.gov" <Tech-talk at aps.anl.gov> |
Date: | Mon, 30 Jun 2025 07:03:45 +0000 |
Hello Mark Yes, we are using the serial port to communicate with the detector. I turned on asynTrace options and I noticed that the freezing and
unresponsive buttons issues are caused due to a timeout during acquisition, this is confirmed because “timeout handler” message gets printed almost every 1 second (not all the time), and after that the temperature PV gets processed. So I switched the scan
rate on the main GUI to passive just to test and the acquisition works fine for now. Also, I noticed that the spectrum takes 1 or 2 seconds more than the real time, I looked into the MCA setup GUI and changed the “Read
spectrum every” setting to “Event”, seems a bit more responsive than before. I attached the current MCA settings screenshot. What do you think? Best Regards, Abdalla Al-Dalleh Control Engineer SESAME From: Mark Rivers <rivers at cars.uchicago.edu> Hi Abdallah, Are you communicating with the XFlash over a serial port or over their QM100 high-speed interface? If it is over a serial port then you should enable asynTrace to see the communication stream. Mark From: Abdalla Ahmad <Abdalla.Ahmad at sesame.org.jo> Hi We have the MCA module running on a Windows 10 machine to control the XFlash detector from Bruker. We started to face the following issues:
Despite what is mentioned, the IOC log shows no error messages. The Bruker software seems to acquire just fine, but not tested thoroughly. We even Installed the IOC on a different laptop and a PC and still the same behavior. Any idea on what might went wrong with the detector or IOC? Best Regards, Abdalla Al-Dalleh Control Engineer SESAME |
Attachment:
current-settings.png
Description: current-settings.png