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

Subject: Re: AreaDetector / ADURL queries
From: Bruno Martins <brunoseivam@gmail.com>
To: "Heesterman, Peter J" <Peter.Heesterman@ukaea.uk>
Cc: "EPICS Tech-Talk \(tech-talk@aps.anl.gov\)" <tech-talk@aps.anl.gov>
Date: Sat, 18 Mar 2017 12:21:14 -0400
Hi Peter,

Regarding your questions

On Fri, Mar 17, 2017 at 10:13 AM, Heesterman, Peter J <Peter.Heesterman@ukaea.uk> wrote:
 
Questions:
 
1. In start_epics, I suspect that:
 
        medm -x -macro "P=13SIM1:, R=cam1:" simDetector.adl & is meant to be:
 
        medm -x -macro "P=13URL1:, R=cam1:" URLDriver.adl &
 

Yes, you are correct.
 
2. In st.cmd, in the line:
        {URLDriverConfig("$(PORT)", 0, 0)
 
    Is the brace character intended, or is a typo?
 
    I can make it work if the brace is removed.

It is a typo.
 
 
3.  In st.cmd, some lines refer to R=cam1:, whereas some lines refer to R=image1:, is this intended?
     e.g.
        dbLoadRecords("$(ADURL)/db/URLDriver.template","P=$(PREFIX),R=cam1:,PORT=$(PORT),ADDR=0,TIMEOUT=1")
     and
        dbLoadRecords("$(ADCORE)/db/NDStdArrays.template", "P=$(PREFIX),R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT),TYPE=Int8,FTVL=UCHAR,NELEMENTS=12582912")
 
     I can make it work if I change R=image1: to R=cam1:
 
4. In auto_settings.req some lines refer to R=cam1:, and some refer to R=image1:, is this intended?
 
    Again, I can make it work if I change R=image1: to R=cam1:

"cam1:" refers to PV's that control the camera itself: starting / stopping the acquisition, setting the exposure time, etc.
"image1:" PV's are for the NDStdArrays plugin, which converts the internal NDArray representation used by areaDetector into a waveform that EPICS clients can understand.
Of course, you can choose whatever prefixes you want, but those are kind of standard.

What kind of error do you get if you leave the NDStdArrays prefix as "image1:"?
 
5. The issue I haven’t been able to resolve is this (see screen shot):
 

I believe the software is correctly collecting image data frames, and the ImageJ plugin shows green with correct connection.
 
But – I don’t see any picture...
What could I be missing here?
 
As Ralph said, check that the environment variable EPICS_CA_MAX_ARRAY_BYTES is adequate. It should be larger than the largest image you intend to transfer.
You could check if caget complains if you try to read the PV 13URL1:image1:ArrayData


HTH,

Bruno

Replies:
RE: AreaDetector / ADURL queries Mark Rivers
RE: AreaDetector / ADURL queries Heesterman, Peter J
References:
AreaDetector / ADURL queries Heesterman, Peter J

Navigate by Date:
Prev: Re: AreaDetector / ADURL queries Ralph Lange
Next: RE: AreaDetector / ADURL queries Mark Rivers
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
Navigate by Thread:
Prev: Re: AreaDetector / ADURL queries Ralph Lange
Next: RE: AreaDetector / ADURL queries Mark Rivers
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
ANJ, 20 Mar 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·