Hi Dehong,
Can you send a screen shot of your main pilatusDetector OPI screen?
Does your configuration have a separate DCU server running camserver and a PPU? What computer is running the EPICS IOC?
Are you saving in TIFF or CBF format?
When the Acquire finally does toggle has the data actually been read into the ADPilatus driver? You can check by using the NDPluginStats statistics plugin to look at the data statistics.
Are there any error messages on the IOC?
If you run camonitor on the StatusMessage_RBV PV what do you see during the Acquire operation?
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Zhang, Dehong via Tech-talk
Sent: Thursday, January 6, 2022 11:06 AM
To: tech-talk at aps.anl.gov
Subject: How to reduce Pilatus IOC response time
Happy New Year Mark and other EPICS friends!
We are (still) using 3.14.12 base, and got ADPilatus from git
2-3 years ago. Every time we "Acquire", we see that the frontend
almost immediately writes the image file, but it takes over 15-20
seconds for the "Acquire" to toggle. -- We have the 1M camera.
We reduced both "AcquirePeriod" and "AcquireTime" to 0.5 seconds,
and reduced the CAMSERVER_ACQUIRE_TIMEOUT parameter
from 10 seconds to 2 seconds, but the response barely improves.
Could you please point us to how to speed up the system?
Thank you very much, best regards,