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  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 
<== Date ==> <== Thread ==>

Subject: RE: sscan question
From: Mark Rivers <rivers@cars.uchicago.edu>
To: l123173 <l123173@163.com>, tech-talk <tech-talk@aps.anl.gov>
Date: Thu, 12 Apr 2018 13:58:27 +0000

Ø  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."

 

I don’t think you were reading xxx:m1.SMSG because xxx:m1 is probably a motor record which does not have an SMSG field.  Were you reading xxx:scan1.SMSG, because the sscan record does have an SMSG field?

 

You may have a firewall running which is preventing connecting to PVs.  Make sure the iptables firewall is either disabled or has holes for EPICS Channel Access.

 

If you open a terminal on the machine that is hosting the IOC with the sscan record what happens if you type

 

caget xxx:m1

 

Does it give you the value, or an error?


      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?

 

Yes, they can be in different IOCs.  They don’t have to be on the same PC, they can be on any PC that is reachable with Channel Access.


      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.

 

There are PVs for the xspress that give you the counts in an ROI, for example.  You can use these to display the counts in that ROI.  It does not matter that you are also using the HDF5 plugin.


      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.

The macro Q is only used in scanParams2D.db, which is used to create scanparm records to conveniently setup the scan.  Q refers to the name of that particular scanparm record.  You don’t this to do a 2D scan, but it is convenient.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of l123173
Sent: Thursday, April 12, 2018 8:45 AM
To: tech-talk <tech-talk@aps.anl.gov>
Subject: sscan question

 

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.
     
      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?
      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.
      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.

Regards,
Li xing

 

 


References:
sscan question l123173

Navigate by Date:
Prev: sscan question l123173
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 
Navigate by Thread:
Prev: sscan question l123173
Next: Re: sscan question Matt Newville
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 
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 ·