search

xpdAcq / mission-control

Releases, Installers, Specs, and more!
0 stars 4 forks source link

detector image mode has been changed from Continous mode to Multiple mode while xrun([6],plan, robot=True) #150

Open adelezh opened 5 years ago

adelezh commented 5 years ago

detector image mode has been changed from Continuous mode to Multiple mode while we use xrun with robot= True

User used the same plan last cycle. plan was defined as 

plan =[rel_grid_scan([pe2c], diff_y, -3,3,9, diff_x,-3,3, 9, False) for i in range(1)]
plan = [subs_wrapper(p, LiveTable([diff_y, diff_x])) for p in plan]
xrun([6], plan robot=True)

we got errors and then we noticed detector Image mode was changed from Continuous mode to Multiple mode.
We changed the Image mode back to Continuous mode from CSS and do a simple xrun(0,0) , it worked fine.

we redo the 

plan =[rel_grid_scan([pe2c], diff_y, -3,3,9, diff_x,-3,3, 9, False) for i in range(1)]
plan = [subs_wrapper(p, LiveTable([diff_y, diff_x])) for p in plan]
xrun([6], plan robot=True)

Again Image mode was changed

we do simple xrun(0,0, robot=True) Again Image mode was changed

We do simple xrun(0,0), Again Image mode was changed.

we noticed there are error message from pe2 ioc. we restart pe2 ioc, it did not work, for every xrun, image mode was changed.

we restart xpdacq, it worked. we can do xrun(0,0).

Since it was very late already so we did not try xrun with robot=True again, use did their experiment by using CSS to load and unload samples.

And sorry we forgot to take screen shot for both xpdacq and ioc error messages.

CJ-Wright commented 5 years ago

Thank you very much for reporting!

sbillinge commented 5 years ago

We don't understand this behavior because xrun RE doesn't set detector mode. This needs some testing by beamline staff and/or users to try and reproduce the error before it can be trouble-shot