by
Hollow » Sun Sep 24, 2017 5:41 pm
some more questions to check and answer:
- is it a new phenomenon or did it occure before?
- is it reproducible or was it just once?
- how is the system configuration?
All Waters modules connectec by Ethernet or some analog Inject start cables?
- did every module got the start command correctly?
- did you changed the Empower system by taking offline/online in <configure system>?
If it was only once: such thing just may happen. Maybe you'll never find the cause...
As for the last point:
We had some issues when changing from/to certain Empower systems with "taking offline/online" without rebooting the PC (Emp workstation; all Waters Module, Ethernet).
In such situations, some detectors didn't get the start signal, so there were no data from that detectors and also the run did finish in Empower but won't go to next injection (like Empower waits for an stop form the detector, while the detector still waits for the start...).
What helps then, is to change the system with offline/online, then exit Empower and reboot Workstation, login to Empower and it works...
If it's not only this "change system" issue, maybe the trigger is the same: some of the modules didn't get the start signal and therefore doesn't send a Stop, so Empower won't proceed to next injection. Check if all modules are started correctly and the data are collected by Empower.