FalconX hangs during a scan
@cyril.guilloud @matias.guijarro @papillon @claustre @sebastien.petitdemange
On @id21 we observed (Marine, Perceval) that sometime a scan with a FalconX hangs without producing an error.
This happen when for a unknown reason the FX hardware is waiting for a trigger that never happen (this can be seen in the console running the FX server).
Because of this, the scan procedure waits forever the last point of the 'fast' line.
Restarting the FX hardware (via the FX web page on server side, see @cyril.guilloud restart procedure) solves the problem.
After restarting the hardware, all is fine. So I think the config of the scan/chain in bliss is ok.
It is not a problem of acq_params (npoints/nintervals vs SYNC mode etc...)
I guess that somehow if something fails during a scan (like a timeOut on a piezo or a Ctrl-C) then the FX is left in a bad state and then next acquisitions will have this hanging problem.
So something should be done to investigate how the FX is stopped if a scan goes wrong because of any third party failure.
Maybe a restart procedure should be implemented and made available from bliss shell.
Before summer I have seen that sometime, doing a crtl-C on fast scan with the FX could leave the FX in a running state (like if ctrl-C => device.stop_acq is uneffective)