Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Wed, 20 Nov 2013 22:11:42 +0000

Hi Florian,

> What puzzled me was that although I had 16bpp imagej was only displaying
> 8bpp and the values were wrapped around several times.

The problem is probably the FTVL of the waveform record you created in your startup script.  If that is created with FTVL=UCHAR then you can only get 8bpp.  You should look at the example in areaDetector/iocBoot/iocProsilica/st.cmd.  It has these lines.  You can comment out the first one and uncomment the second one to be able to use 16bpp.

# Use this line if you only want to use the Prosilica in 8-bit mode.  It uses an 8-bit waveform record
# NELEMENTS is set large enough for a 1360x1024x3 image size, which is the number of pixels in RGB images from the GC1380CH color camera. 
# Must be at least as big as the maximum size of your camera images
dbLoadRecords("$(AREA_DETECTOR)/ADApp/Db/NDStdArrays.template", "P=$(PREFIX),R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,TYPE=Int8,FTVL=UCHAR,NELEMENTS=4177920")

# Use this line if you want to use the Prosilica in 8,12 or 16-bit modes.  
# It uses an 16-bit waveform record, so it uses twice the memory and bandwidth required for only 8-bit data.
#dbLoadRecords("$(AREA_DETECTOR)/ADApp/Db/NDStdArrays.template", "P=$(PREFIX),R=image1:,PORT=Image1,ADDR=0,TIMEOUT=1,TYPE=Int16,FTVL=SHORT,NELEMENTS=4177920")

> However, I get only "20/11/13 22:28:29.77: UpdateImage got exception: pendIO timed out" errors.

That is probably because you have not defined EPICS_CA_MAX_ARRAY_BYTES on the Mac client to be big enough.

> Besides this I'm wondering how I can now include a few other plugins
> like NDStats and NDOverlay.

Again, look at /iocBoot/iocProsilica/st.cmd.  It has this line:

# Load all other plugins using commonPlugins.cmd
< ../commonPlugins.cmd

That loads examples of all the plugins, and is a configuration that is typically used.  You can of course customize it as you like.

Mark

-----Original Message-----
From: Florian Sorgenfrei [mailto:[email protected]] 
Sent: Wednesday, November 20, 2013 3:31 PM
To: [email protected]; Mark Rivers; [email protected]
Subject: Re: areaDetector for a Basler GigE camera

Hi Mark and Tom,

I tried what you suggested and after a little bit of fiddling around it
worked. I was able to see the images with the ImageJ viewer at almost
the trigger rate of 50Hz.

What puzzled me was that although I had 16bpp imagej was only displaying
8bpp and the values were wrapped around several times. Hence I tried to
use the edl screens to switch from 16bpp to 8pp and I completely messed
up the configuration of the camera. I got a lot of uknown pixel value
errors. After checking that the ioc is working fine with another camera
I tried switching of both cameras. Luckily the wrong configured one came
back in a sane state. I have no idea what went wrong, since I tried
changing the data type, the bpp, the pixel format all without any success.

The next test was now to fire up imagej on my mac (with osx 10.9). I
installed the plugin (ImageJ64 doesn't work with the plugin) and
ImageJ32 is able to load and to connect to the camera. However, I get
only "20/11/13 22:28:29.77: UpdateImage got exception: pendIO timed out"
errors.

Besides this I'm wondering how I can now include a few other plugins
like NDStats and NDOverlay.

But anyway, thanks for the fast and well directed help.

Cheers,

Flo

Am 20.11.13 09:56, schrieb [email protected]:
> Hi Florian,
>
> Once you have tried Mark's suggestions below, start the camera acquiring and check ARAVISCAM1:CAM:ArrayCounter_RBV to see if any arrays are being produced by the driver. If it doesn't increase then the problem is in the driver, otherwise the problem is in the plugin chain.
>
> As to your startup script problems, I suspect you may still be loading the AVT_Manta_1_44_4.template file in your substitution file. Have you run the aravisGigEApp/src/makeDbAndEdl.py script to make a database and screen for your particular camera? If so, then you need to point the substitution file at the database template that this script created.
>
> Thanks,
> Tom Cobb
>
>
>> -----Original Message-----
>> From: Mark Rivers [mailto:[email protected]]
>> Sent: 19 November 2013 21:29
>> To: 'Florian Sorgenfrei'; [email protected]
>> Cc: Cobb, Tom (DLSLtd,RAL,TEC)
>> Subject: RE: areaDetector for a Basler GigE camera
>>
>> Assuming the driver is actually talking to the camera and getting
>> images then there are 2 common reasons that ARAVISCAM1:ARR:ArrayData
>> would have all zeros:
>>
>> Make sure that the driver PV ArrayCallbacks is set to Enable.
>>
>> Make sure the NDStdArrays plugin has the EnableCallbacks PV set to Yes.
>>
>> These and other tips are contained in the areaDetector
>> "Troubleshooting" documentation:
>>
>> http://cars9.uchicago.edu/software/epics/areaDetectorViewers.html#Troub
>> leshooting
>>
>> I don't know why you are getting all the errors about the unknown
>> Aravis parameters, perhaps Tom Cobb who wrote the driver can help.
>>
>> Mark
>>
>>
>>
>>

--
Florian Sorgenfrei
Institute for Methods and Instrumentation for Synchrotron Radiation
Research G-ISRR
Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
Albert-Einstein-Str. 15
D-12489 Berlin
GERMANY

Tel.: +49 30 8062 12924
Fax: +49 30 8062 14987

________________________________

Helmholtz-Zentrum Berlin für Materialien und Energie GmbH

Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.

Aufsichtsrat: Vorsitzender Prof. Dr. Dr. h.c. mult. Joachim Treusch, stv. Vorsitzende Dr. Beatrix Vierkorn-Rudolph
Geschäftsführung: Prof. Dr. Anke Rita Kaysser-Pyzalla, Thomas Frederking

Sitz Berlin, AG Charlottenburg, 89 HRB 5583

Postadresse:
Hahn-Meitner-Platz 1
D-14109 Berlin

http://www.helmholtz-berlin.de

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System