Re: Strange problem with areaDetector driver

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Jörn,


> I ran into a severe problem in the image readout handler.

> When calling doCallbackGenericPointer() the IOC creates every time a couple of  new threads and consumes lot of CPU power ( 300% on a quad core).


First a few questions:


Is this Linux or Windows?


What frame rate are you using?


What plugins are running?


Is the CS-Studio GUI on the same machine as the IOC or a different machine?


The first thing to establish is whether the problem is the areaDetector IOC or the CS-Studio client.  I suggest you do the following:


-  Disable all plugins except NDPluginStdArrays for testing.


- Exit CS-Studio so there is no display client running.  What is the CPU load under those conditions?


- Try the ImageJ viewer instead of CS-Studio for testing.  Does that also have the problem?


Mark





________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Jörn Dreyer via Tech-talk <tech-talk at aps.anl.gov>
Sent: Wednesday, May 27, 2020 7:03 AM
To: tech-talk at aps.anl.gov
Subject: Strange problem with areaDetector driver

Hello,

currently I have a very strange problem in a code I'm developing to read out
cameras from ZWO. I ran into a severe problem in the image readout handler.
When calling doCallbackGenericPointer() the IOC creates every time a couple of
new threads and consumes lot of CPU power ( 300% on a quad core). So after a
very short time the system becomes unresponsive and has to be switched off.
The image is 3520*4656 bytes in size and is in monochrome mode, so UInt8 as
data type.

In a GUI (CS-Studio) that is displaying the image data as Intensity graph I
observe a "disconnect" state for every cycle of the image, once the NDStdArray
has been enabled. In between it shows "No data".

Has anybody seen such behavior before? Any ideas welcome how to search for the
reason of this.

Regards,

Jörn Dreyer