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: "Heesterman, Peter J" <Peter.Heesterman@ukaea.uk>
To: "'Bruno Martins'" <brunoseivam@gmail.com>
Cc: "Lange Ralph \(Ralph.Lange@iter.org\)" <Ralph.Lange@iter.org>, "rivers@cars.uchcago.edu" <rivers@cars.uchcago.edu>, "EPICS Tech-Talk \(tech-talk@aps.anl.gov\)" <tech-talk@aps.anl.gov>
Date: Mon, 20 Mar 2017 14:22:58 +0000

Hi Bruno, Mark, Ralph (not to mention Mark Engbretson and Hugh Slepicka),

 

Thank you for your excellent responses.

 

Under my (3) and (4), I have reverted the misunderstanding, and have been able to get it to work (at least, to the same extent as before).

 

I had experimented rather extensively with the names used, but the nature of the PV save/restore process means that a couple of re-starts are required, before erroneous usage is cleared.

This doesn’t too easily lend itself to trial’n’error experimentation...

 

I have also been able to get the simulation detector to work (at least, to the same extent as before).

 

I confirm that I have EPICS_CA_MAX_ARRAY_BYTES set to a large value (100000000, this is possibly overkill).

I also confirm that I have enabled array call-backs.

 

I confirm that I am able to caget the array 13URL1:image1:ArrayData, but the array is so big it is rather difficult to see what (non-zero) data it contains.

 

I also checked these values:

            13URL1:image1:MinCallbackTime.  It has the value 0 (I assume this is the default).

            13URL1:cam1:ArrayCallbacks. It has the value Enable.

 

The ImageJ plugin shows green, and no errors are being logged.

Nonetheless, no picture is displayed...

 

Many thanks,

 

Peter.

 

 

 

From: Bruno Martins [mailto:brunoseivam@gmail.com]
Sent: 18 March 2017 16:21
To: Heesterman, Peter J <Peter.Heesterman@ukaea.uk>
Cc: EPICS Tech-Talk (tech-talk@aps.anl.gov) <tech-talk@aps.anl.gov>
Subject: Re: AreaDetector / ADURL queries

 

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
References:
AreaDetector / ADURL queries Heesterman, Peter J
Re: AreaDetector / ADURL queries Bruno Martins

Navigate by Date:
Prev: Re: Multi-monitor for CSS opi palak shimpee
Next: Re: new MVME5500, device "gei0" not found Dirk Zimoch
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 Mark Rivers
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 ·