How to enable post-run shutdown in OpenLAB CDS 2.2?

In Open LAB CDS 2.2 you have to create a Shutdown method and add in sequence no other option. In the CDS 2.3 you can load shutdown method seperately

Thank you!

...You can also set a parameter in the OpenLab control panel to switch of detector lamps after the run queue has completed all samples, since this cannot be achieved directly in a method.

Cheers

Andy

Yes You can do that but this will not shutdown the Pump and the thermostat

You're right, it only shuts down the detector.  In your answer above, you mention creating a shutdown method, which is what you would need to do, in addition to changing the Instrument Options, otherwise the detector lamp will remain on.

What I have done in OpenLab 2.2 is to create a method called shutdown, which has no flow from the pump and no temperature control on the column thermostat.  I then either add this to the end of the sample queue as a single sample (Instrument Blank as the Injection Source) or create a separate sequence with one injection using the same method to do the same thing.  I normally end up doing this as a sequence, and include a column wash or column storage method as well.  Keeping the wash/store/off methods in a separate sequence means that, when it comes to data processing, I don't have odd results with no peaks and different run times to exclude from reports!

You're right, it only shuts down the detector.  In your answer above, you mention creating a shutdown method, which is what you would need to do, in addition to changing the Instrument Options, otherwise the detector lamp will remain on.

What I have done in OpenLab 2.2 is to create a method called shutdown, which has no flow from the pump and no temperature control on the column thermostat.  I then either add this to the end of the sample queue as a single sample (Instrument Blank as the Injection Source) or create a separate sequence with one injection using the same method to do the same thing.  I normally end up doing this as a sequence, and include a column wash or column storage method as well.  Keeping the wash/store/off methods in a separate sequence means that, when it comes to data processing, I don't have odd results with no peaks and different run times to exclude from reports!