Why is "controller stop automation request" terminating my runs?

I have seen this error occur when a module is turned on and connected via CAN cable, but not in the configuration in OpenLAB ChemStation (and I believe would hold true for MassHunter as well). If that "extra" module is Not Ready, it will stop the running of an analysis. All of the configured modules may be Ready, but this "unknown" Not Ready signal is what stops the run from beginning. Because the module is not in the configuration, OpenLAB ChemStation is not recording anything useful from the "ghost" module. So be sure to turn off any module not in your configuration. Explained another way, be sure that your instrument configuration accurately reflects what is turned on and connected.

This was found by checking in Lab Advisor and noticing an extra module there not found in the Configuration.

I have seen this error occur when a module is turned on and connected via CAN cable, but not in the configuration in OpenLAB ChemStation (and I believe would hold true for MassHunter as well). If that "extra" module is Not Ready, it will stop the running of an analysis. All of the configured modules may be Ready, but this "unknown" Not Ready signal is what stops the run from beginning. Because the module is not in the configuration, OpenLAB ChemStation is not recording anything useful from the "ghost" module. So be sure to turn off any module not in your configuration. Explained another way, be sure that your instrument configuration accurately reflects what is turned on and connected.

This was found by checking in Lab Advisor and noticing an extra module there not found in the Configuration.