Chemstation Concepts Explained: File Structure

(Note: This only applies to revs of chemstation after B.02.01(?) all the way up to current revs of Openlab Chemstation.)

I thought I would make a series of blog posts centered around different Chemstation topics.

This post’s topic is file structure.

A common problem that arises from not knowing the file structure of Chemstation would be the analyst makes some integration or calibration changes, and those changes are saved to the method, but they appear to be lost the next time they run their samples.  “Chemstation is not saving my changes!”, one might shout out.

Chemstation uses the standard windows file structure to organize methods and other files.  These files can be found in C:\Chem32\1(or 2, 3, or 4)\(Methods, Sequences, or Data).  The three main folders that I want to discuss are:




The Methods folder is where your methods are stored.  A method is just a collection of setpoints that will be used during the analytical run.  So things like temperature, flow, length of the run, calibration info, etc.  These all get saved into a folder, that will have a .M at the end:

Sequences are saved in the Sequences folder.  A sequence is just a collection of methods that you can organize to have Chemstation run them one after the other.  This file ends with a .S.
The Data folder is where you can find all of your data signals, reports, a copy of your method, among other things.  This folder ends with a .D.
Now that you know the main file types, let’s talk about how Chemstation processes and manipulates these files.
When you create a sequence table, you tell Chemstation what methods you would like to run.  In Sequence Parameters, you tell Chemstation where you want to store your data:
sequence parameters
In this example, I will be storing my data in Chem32\2\data\test.
Sequence Container (or result set):
If you go to View then preferences in method and run control of an online session, you can find the following window:
unique folder creation
This information only applies if you have Unique Folder Creation ON.  What this will do is create a sequence container to put in your data folder, and it will name it according to your name pattern highlighted above.
When I go to run that sequence, as soon as I push the Start Sequence button, the software make a copy of the method you have stored in the Methods folder, and puts that copy in the sequence container.  It also copies your sequence file from your sequence folder.
From this point on, any changes you make will only be applied to the copy that was placed in the sequence container, in your data folder.  And they will NOT be applied to the original method and sequence files located in the Methods and Sequences folder.  The original method is referred to as the master method, and the copy placed in your sequence container is referred to as the sequence method.
So when you are analyzing your data in chemstation, if you look at the top of the screen, chemstation will let you know if you are using the master, or the sequence method.  This is indicated by the word sequence in parenthesis:
Use sequence method
There is also a drop down highlighted above that needs to be selected as well.
So now, if I want to change my integration parameters, or my calibration, or even my report settings, when I click on save method, it will only save to the sequence method.  When I go to run a new set of samples, chemstation will use the original master method, which hasn’t been affected by any of these changes.  In order for any changes to be made to your master method, and subsequent runs in the future, you need to tell chemstation to updated the master method with your changes.  This is acheieved by simply going to the Method menu item and selecting update master method.  Now any changes that have been made WILL be applied to future runs.
Really what I wanted to do here was talk about how the chemstation file structure can dramatically affect workflow.  If the user understands sequence vs master method, this can make things much easier!
Have any comments, questions, concerns?  Please leave a comment below, would love to hear your thoughts!

Clock watchdog timeout fixed! Windows 10.

Recently,  an older PC that I use kept getting “clock_watchdog_timeout” blue screen of death,  and shutting down.  I noticed this error would happen shortly after bootup, maybe five minutes.

The blue screen of death, with sympathetic sad face.

Many fixes online like such as here, and here, mainly pointed me in the direction of drivers and software.   In my case,  the fix was hardware,  and was relatively easy. 

The fix: 

The problem was that my CPU fan built plenty of dust below the fan blades,  causing my CPU to overheat after a few minutes.   All I needed to do was clean out the dust and that problem hasn’t come back now for over a week

Side of my pc with the cover off. CPU fan is visible towards the middle.

I took the side cover off to access the fan. 

Below the fan blades is where the dust accumulated.

 In the pucture above you can see the fan.   Unfortunately, I didn’t take a picture before cleaning it so that you can see all the dust.  To clean it, I’m sure a standard air duster would work, but I didn’t have one handy.  I completely removed the fan,  there were four screws securing it to the motherboard, and used several q-tips dipped in a little bit of water.  This allowed me to gently scoop out as much dust as possible.  

After that,  I put the fan back,  and the problem was fixed!   I hope this fix may help you with your issue, please leave a question or comment below!

Blog at

Up ↑