Wednesday, September 8, 2010	Welcome Guest!   Register | Sign-in

Return to Knowledge Base

Knowledge Base Results

Category: MSD ChemStation / Macro Language

Records returned: 10

MSD ChemStation / Macro Language

1.

Where do I begin if I want to learn how to write my own macro for the GC/MS Agilent ChemStation?

Try to get hold of the Hewlett Packard manual, part number HP G1034-90034. It's a book called "Using and Writing Macros", but unfortunately it's out of print now. There's also a macro writing class offered by Agilent now, somewhere in the east coast, so check their class schedule. ChemUserWorld.com also teaches on-line classes on macro programming.

2.

What macro command shows me the variables and macros that are currently loaded into the ChemStation's memory?

The REM macro command shows you the variables and macros that are currently loaded into the ChemStation's memory. Be careful, it was designed to REMove them from memory, but you can use it to view them too.

3.

What macro command shows me the commands and functions that are currently loaded into the ChemStation's memory?

The macro command COM shows you the commands and functions that are currently loaded into the ChemStation's memory.

4.

Is the ChemStation macro language case sensitive?

No, the ChemStation macro language is not case sensitive, with rare exceptions, such as the DONTASK parameter for the "DELETE" macro command.

5.

What type of debugging tools are there for the macro language?

The best debugging tool is probably the "LOGGING" macro command. You can run it at the command line, or place it at a strategic location inside your macro. Typically, you first turn logging on to record everything that occurs to a text file. Then you turn logging off and examine the text log file for errors. An example is: LOGGING 1,"C:\temp\log.txt",1,1,1,1,1 folowed by LOGGING 0.

Another useful technique is to place "PRINT", "SLEEP", or "ALERT" commands at strategic points in your macro, especially if you have a hint where the error is occurring.

6.

How can the ChemStation macro language communicate with other Windows programs?

The ChemStation macro language communicates with other Windows programs by using a simple technique known as dynamic data exchange, or DDE. Several DDE macro commands are available. These DDE techniques were very useful before 32 bit programming became widely used, and they still work today.

7.

What type of error handling techniques are there with the macro language?

The "ON_ERROR" macro command is your best bet to use when handling errors. It will do almost whatever you code it to do when an error is encountered. For example, it can run another macro or run another macro command.

8.

What are macros, how do I make them, and what are they used for?

A macro is a list of ChemStation commands or instructions that are stored together in a text file that you most likely create with the Windows NotePad program. There are many ways to load this macro into the ChemStation memory environment so you can run or execute it. Macros are useful for automating tasks that you find yourself repeating over and over again that otherwise force you to use many mouse clicks, menu selections, and typed entries into dialog boxes. Macros are widely used to perform custom actions such as printing a unique report or interfacing with other Windows programs.

9.

Are there any variables that the ChemStation creates that I can use in my macros?

Yes, there any variables that the ChemStation creates that you can use in your macros. These are called system variables. Most of them begin with the underscore character, or "_", and are all capital letters, such as "_DATAFILE$." To see all the variables, use the "REM" command, but be careful because REM is used to temporarily REMove variables.

10.

I am looking at the variable names in the ChemStation using the REM command and see that there are many that start with the underscore ("_") character. What is the significance of the underscore in their name?

Variables that start with the underscore are referred to as system variables. They are created and modified by the ChemStation, and you can use them in your macros. In general, you can use them, but, they cannot be modified unless you use the VARLOCK macro command.