Experimental Physics and
Industrial Control System

Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> · Mon, 18 May 2020 03:31:29 +0000

Hi Zhibang,

> I found that the 5 NDPluginStats showed same net value, same total value, same max value.... But I am sure the 4 ROIs were set successfully and they did not a share public zone. It seemed all 5 NDPluginStats showed the statistics of the whole image. I don't know why it happened. Also I tried NDPluginROIStat, which seemed not working either.

Please send screen shots of each of the NDPluginStats screens and each of the NDPluginROI screens.

> Another question is about an error printed after exposure. It said file exists but is more than 10 seconds old, possible clock synchronization problem.

That means that when ADPilatus tried to read the file it existed but was more than 10 seconds old.  It checks that to prevent getting old stale data.  This normally means that your file server and the computer running ADPilatus do not have their clocks synchronized.  Make sure that both machines are running NTP and that their clocks agree.

I suspect this is also the problem with your ADViewers.  ADPilatus is not successfully reading the image when it is on an NFS server, because your NFS server and the ADPilatus machine clocks are not synchronized.  You need to fix that problem, and then I suspect the other problems will go away.

Mark

________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of shenzb--- via Tech-talk <tech-talk at aps.anl.gov>
Sent: Sunday, May 17, 2020 10:06 PM
To: tech-talk
Subject: NDPluginStats show the same statistics results and ADViewer displays no image

Hello everyone,

I am using areaDetector(R3.3.1)/ADPilatus(R2.7), but there are quite a lot problems. I would like to ask for your generous help.

I found that the 5 NDPluginStats showed same net value, same total value, same max value.... But I am sure the 4 ROIs were set successfully and they did not a share public zone. It seemed all 5 NDPluginStats showed the statistics of the whole image. I don't know why it happened. Also I tried NDPluginROIStat, which seemed not working either.

Another question is about an error printed after exposure. It said file exists but is more than 10 seconds old, possible clock synchronization problem. During a scan, it went stuck when this error was thrown out; and I clicked the Stop button on pilatusDetector.adl to move it on. Might it because the detector was not ready for the next exposure? And could I write a script to automatically set $(P)$(R)Acquire "Done" while it occurs? Will there be any disastrous consequence if I do so?

Finally, it is a problem with ADViewers(R1.5). Actually I am trying to use NFS storing all datas collected by different devices. However, no image was shown by EPICS_AD_Viewer after exposure when I set the pilatus file path an NFS path. EPICS_AD_Viewer was able to detect the image pv and no error was printed in log. When the pilatus files were stored locally, everything worked well. How can I fix this problem?

Thanks in advance.

________________________________
Best regards,
--
Zhibang Shen
Institute of High Energy Physics, Chinese Academy of Sciences
19B Yuquan Road, Shijingshan District, Beijing, China
100049

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System