EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  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  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: sscan question
From: Matt Newville <[email protected]>
To: l123173 <[email protected]>
Cc: tech-talk <[email protected]>
Date: Thu, 12 Apr 2018 14:00:20 -0500
Hi Li,


On Thu, Apr 12, 2018 at 8:44 AM, l123173 <[email protected]> wrote:
Hi all,
      I am using the synapps_5_8, centos 7(64) ,base 3.14.12.
      I want to use sscan module control two motors and one detector(xspress).
      The xspress worked with its own IOC. Motor was controlled with motor module in another IOC. Both the two IOC were in one PC.

Do I understand correctly that the motors are being run from a soft IOC on the same PC running the xspress3 IOC?  If that is the case, there should not be any connection issues.


     
      I got these error after I configured the sscan(Driver and trigger) and started it.
epics> Starting new scan with unexpected faze ('SCAN_PENDING')."
In the scan_more.opi, xxx:m1.SMSG was read and shows "Waiting for PV's to conect."
      Besides the error above, I have some questions.
      1. Does the trigger and drive in sscan could be in two different IOC of one PC?  Beacuse the xspress(using epics) was provided by manufacture, so I try to keep it originally?

 
We had a problem related to this with the first version of the xspress3 IOC software we got from the vendor.  I am not 100% sure what they are currently shipping, but with the initial version we got (now several years ago) there was not a single "busy record" PV that erased the spectrum, started acquisition, and waited until the acquisition was done before returning.   The sscan record needs this to operate properly, so it may still be the case that the vendor-supplied xspress3 module cannot work well with the sscan record.

You should check this.  Can you do a "caput with wait" to the "Start Acquisition" PV and have it erase the old spectra, start a new acquisition, and wait until the acquisition completes before returning? 

You might consider using the version at https://github.com/epics-modules/xspress3 which does have an EraseStart busy record that can be used with the sscan record.  This version also uses areadDetector2 and changes how MCA ROIs are defined, using the ROIStats plugin, and has some other improvements.  From recent discussions with the vendor, I know they *intend* to be using this version, but I am not certain if that is what they are shipping.  



 
      2. About the detector(xspress), the output of detector was a hdf5 file, so I could not know what the pv( xxx:scan1.D01PV ) should be.


Are you aiming to save full spectra at each point in the scan, or just integrated ROIs?  If just integrated ROIs, you should be able to use the PVs for the ROI values for the sscan detectors, and not bother with the HDF5 files at all.

If you are aiming to save the full spectra, you can set up the HDF5 plugin to save files and advance the channel.  In that case, you don't need to put anything in the sscan detector PVs, but you might want to put something like the counter (NumCaptured_RBV or UniqueID_RBV) of the HDF5 plugin as a "detector".



      3. If I would change the savefile name during the sscan, how should I do it.
      4. I think sscan 2D would be right for me, but I could not know the value of macro Q. When I set it to m1, it was confilct with motor macro, When I set it to Table1X, it was not right also.


Sorry, I'm not sure on these.  I don't really use the savefile mechanism or fancy array modes of the sscan record.
 
--Matt Newville


References:
sscan question l123173

Navigate by Date:
Prev: RE: driver support for Gamma Vacuum QPC 4 (asking for modbus records) Wallace, Alex
Next: Re: Which record is the best to use? Maren Purves
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  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: sscan question Mark Rivers
Next: RE: driver support for Gamma Vacuum QPC 4 (asking for modbus records) Wallace, Alex
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  <20182019  2020  2021  2022  2023  2024 
ANJ, 12 Apr 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·