Update Config_Detector
@@ -148,7 +148,7 @@ However, detectors that provide multiple values, e.g. area detectors, tend to al
|
||||
 **Default**: empty string
|
||||
|
||||
**zmqRequester**::<BR>
|
||||
 String value that defines the ZMQ network address and port that _Pixelator_ should use to communicate measurement parameters and scheduling details with the detector. For example `"tcp://x07da-qutag-1.psi.ch:5564"`.<BR>
|
||||
 String value that defines the ZMQ network address and port that _Pixelator_ should use to communicate measurement parameters and scheduling details with the detector. For example `"tcp://x07da-qutag-1.psi.ch:5564"`. The current implementation (11.11.2022) does not actually use the requester port for anything, but a feature set similar to that of the Epics type detector is planned where communication will be performed over this ZMQ requester port.<BR>
|
||||
 **Default**: empty string
|
||||
|
||||
**getDataTimeout**::<BR>
|
||||
@@ -157,5 +157,4 @@ However, detectors that provide multiple values, e.g. area detectors, tend to al
|
||||
|
||||
**details**::<BR>
|
||||
 Integer value that defines the length of the data array (always 1D) that will be returned by the detector. Note that _Pixelator_ requires detectors to additionally return a summary of the data array as a single value per scan point.<BR>
|
||||
 **Default**: 0
|
||||
|
||||
 **Default**: 0
|
||||
Reference in New Issue
Block a user