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: areaDetector question
From: Jörn Dreyer <j.dreyer@hzdr.de>
To: tech-talk@aps.anl.gov
Date: Wed, 18 Apr 2018 07:53:23 +0200
Hi Mark   and Hinko,

indeed that was the solution. Changing FTVL from FLOAT to DOUBLE gave methe 
correct contents caget:

caget -d 2 HIBEF:XFEL:image1:ArrayData
HIBEF:XFEL:image1:ArrayData
    Native data type: DBF_FLOAT
    Request type:     DBR_FLOAT
    Element count:    4000
    Value:            16.3838 28365 2581.61 2424.79 2361.6 2392.03 2354.58 
2429.48 2499.69 2380.32 2441.18 2366.28 2427.14 2429.48 2469.27

So now this problem is solved I can go on in designing the GUI for it.

Regards and many thanks for all the tips,

Jörn

Am Dienstag, 17. April 2018, 16:03:39 CEST schrieb Mark Rivers:
> Hi Jorn,
> 
> areaDetector definitely works with float or double arrays.
> 
> I am not sure if this is your problem, but I see an incompatibility here:
> > dbLoadRecords("$(ADCORE)/db/NDStdArrays.template", "P=$
> > (PREFIX),R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$(PORT),TYPE
> > =Float64,FTVL=FLOAT,NELEMENTS=8000")
> Note that you have told it TYPE=Float64, which selects the asynFloat64Array
> interface.  However, you told it FTVL=FLOAT, which is for 32-bit floats. 
> These fields need to be consistent, i.e. TYPE=Float64 and FTVL=DOUBLE or
> TYPE=Float32 and FTVL=FLOAT.
> 
> Mark
> 
> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov]
> On Behalf Of Jörn Dreyer Sent: Tuesday, April 17, 2018 7:24 AM
> To: EPICS Tech Talk <tech-talk@aps.anl.gov>
> Subject: areaDetector question
> 
> I'm currently developing an areaDetector module for a sensor that delivers
> its information as double values. The code is ready, but I'm somehow not
> able to setup the ioc correctly to deliver the data in the NDStdArray.
> Looking with caget at the ArrayData it shows all values as zero.
> 
> Here is what my dbLoadRecords line looks like:
> 
> dbLoadRecords("$(ADCORE)/db/NDStdArrays.template", "P=$
> (PREFIX),R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,NDARRAY_PORT=$
> (PORT),TYPE=Float64,FTVL=FLOAT,NELEMENTS=8000")
> 
> My question is, has anybody before tried to read floats? With another driver
> that reads UInt32 values, I succeeded to setup the ioc.
> 
> Regards,
> 
> Jörn Dreyer


-- 
Dr. Joern Dreyer
HIBEF DAQ + Controls
Institut für Strahlenphysik
Helmholtz-Zentrum Dresden - Rossendorf e.V
Abt. FWKX                Tel: +49 351 260 3263
                                   FAX: +49 351 260 3700
01314 Dresden        eMail: j.dreyer@hzdr.de

Helmholtz-Zentrum Dresden - Rossendorf e.V (HZDR)
Bautzner Landstraße 400, 01328 Dresden
Vorstand: Prof. Dr. Dr. h. c. Roland Sauerbrey, Dr. Ulrich Breuer
Vereinsregister: VR 1693 beim Amtsgericht Dresden



References:
areaDetector question Jörn Dreyer
RE: areaDetector question Mark Rivers

Navigate by Date:
Prev: RE: Problem with autosave module making it crash at random basis. Abdalla Ahmad
Next: CSS xy graph question Jörn Dreyer
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: RE: areaDetector question Mark Rivers
Next: Request for OSI and RTEMS citations Matt Rippa
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, 18 Apr 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·