areaDetector/ADEiger

Pump & Probe mode crashes FileWriter

Opened this issue · 2 comments

MarkRivers commented

If the FileWriter is enabled when a frame is collected with TriggerMode=External Gate and ExternalGateMode=Pump & Probe then the FileWriter on the DCU appears to die. Even using a Web interface returns error 404, page not found.

MarkRivers commented

The only way I have found to recover from this is to use the Web interface to Applications/Detector/Restart, I cannot even use Web page System/Initialize Detector, because that produces an error saying Initialize failed.

MarkRivers commented

I tested this as follows:

  • Restarted the detector application on the DCU and initialized the detector
  • Configured the detector with nimages=1, nexpi=1000, trigger_mode=extg, extg_mode=pump_and_probe. Verified with curl:
>curl http://164.54.160.41/detector/api/1.8.0/config/trigger_mode
{"access_mode":"rw","allowed_values":["exte","extg","exts","inte","ints"],"value":"extg","value_type":"string"}

>curl http://164.54.160.41/detector/api/1.8.0/config/extg_mode
{"access_mode":"rw","allowed_values":["hdr","pump_and_probe"],"value":"pump_and_probe","value_type":"string"}

>curl http://164.54.160.41/detector/api/1.8.0/config/nimages
{"access_mode":"rw","max":2000000000,"min":1,"value":1,"value_type":"uint"}

>curl http://164.54.160.41/detector/api/1.8.0/config/nexpi
{"access_mode":"rw","value":1000,"value_type":"uint"}
  • Verified that the filewriter was enabled and ready with curl
>curl http://164.54.160.41/filewriter/api/1.8.0/status/state
{"access_mode":"r","allowed_values":["disabled","ready","acquire","error"],"value":"ready","value_type":"string"}
  • Started acquisition and sent 2000 external pulses, at 1 kHz, 100 microsecond pulse width. The DCU sent the data over the stream interface as expected after 2 seconds.
  • Tried to read the state of the filewriter interface with curl
>curl http://164.54.160.41/filewriter/api/1.8.0/status/state

>curl http://164.54.160.41/filewriter/api/1.8.0/status/state

>
  • There was no response.
  • Tried to open a Web browser to the filewriter to read the state:
This 164.54.160.41 page can’t be found
No webpage was found for the web address: http://164.54.160.41/filewriter/api/1.8.0/status/state