You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to implement dead time correction to our 7-element SDD connected to an Xspress3. We do it by getting
data = dev.command_inout("ReadScalers",[LastFrameNo, ChannelNo]) #dev is proxy to xspress3 device
that returns a length-11 array per channel (detector element). One element of that array is used as a multiplicative corrector and two more are just stored in the Sardana output.
This works but it is slow. Every invocation requires ~10 ms per channel, which accumulates to a long delay and makes our fly energy scans really slow.
Q1. Is it possible to read all channels by one command?
Q2. Is possible to have a buffered readout, similar to our ROI controller that uses limaccd?
The solutions might already be present in the newer versions (?); currently we have
lima-xspress3-1.4.0, lima-core-1.7.2, tangods-limaccds-1.5.3, xspress3-sdk-2.0.0
Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
We are trying to implement dead time correction to our 7-element SDD connected to an Xspress3. We do it by getting
data = dev.command_inout("ReadScalers",[LastFrameNo, ChannelNo]) #dev is proxy to xspress3 device
that returns a length-11 array per channel (detector element). One element of that array is used as a multiplicative corrector and two more are just stored in the Sardana output.
This works but it is slow. Every invocation requires ~10 ms per channel, which accumulates to a long delay and makes our fly energy scans really slow.
Q1. Is it possible to read all channels by one command?
Q2. Is possible to have a buffered readout, similar to our ROI controller that uses limaccd?
The solutions might already be present in the newer versions (?); currently we have
lima-xspress3-1.4.0, lima-core-1.7.2, tangods-limaccds-1.5.3, xspress3-sdk-2.0.0
Thank you!
The text was updated successfully, but these errors were encountered: