2.6 How to Run a Real Chromatographic Acquisition in Chromperfect

This article is an in-depth analysis of a single video within the Chromperfect Beginner Training Series. Specifically, we are looking at Chapter 2.6: Running a Real Chromatographic Acquisition from Section 2: Files and Method Fundamentals.

The Chromperfect training ecosystem is designed to take users from system basics to advanced automation through five core sections:

1. System Foundations (Architecture and Status States)

2. Files and Method Fundamentals (Method vs. Solution files, Raw vs. Bound Data)

3. Working With Data (The Analyze program, Integration, and Calibration)

4. Reporting (Templates, Formatting, and Output)

5. System-Level Features and Automation (Sequences and Access Control)

This chapter serves as the capstone for Section 2, transitioning from theoretical method configuration to active data collection. It addresses the common challenge of moving beyond a "test" environment to ensure your chromatographic data is captured accurately and stored securely.

https://www.youtube.com/watch?v=AnysaYlViHk

While this guide provides the technical steps, watching the visual demonstration in the playlist is essential to see the real-time interaction between the Acquisition Client and the instrument hardware.

Key Takeaways: Real Chromatographic Acquisition

• Critical Settings: Only three parameters—Sampling Rate, Run Time, and Detector Source—can cause a run to fail if set incorrectly.

• Method vs. Solution: Both configurations yield identical results; the choice depends solely on your laboratory's preferred workflow.

• File Integrity: Always enable the creation of Bound (BND) files to ensure all processing and calibration data remains tethered to the raw signal.

• Verification: Successful acquisition is confirmed by the status changing to "Ready" and the creation of both RAW and BND files in the designated directory.

  
  

Which Method Settings Affect Data Integrity?

Most settings in a Chromperfect method control how data is displayed or processed after the fact. However, the Acquisition Parameters block contains three "critical path" settings. If these are incorrect, the data cannot be salvaged, and the sample must be rerun.

Run Time: This must be long enough to allow all peaks of interest to elute from the column. In our demonstration, we adjust this to 10 minutes to ensure a complete profile.

Data Samples Per Second: Also known as the sampling rate. This must be high enough to provide 10 to 20 data points across your narrowest peaks. For many standard applications, 5 points per second is an ideal starting point.

Acquire From Channel: You must specify the correct detector source (e.g., Channel A). If the software listens to the wrong channel, no chromatography will be recorded.

Method Files vs. Solution Files: Which Should You Use?

One of the most frequent points of confusion for new users is the difference between a Method file (.MET) and a Solution file (.SOL). The functional outcome for the instrument is identical, but the file structure differs.

Feature	Method File (.MET)	Solution File (.SOL)
Structure	External; references other files	Internal; contains all sections
Supporting Files	Requires separate Setpoint (.M78) or Calibration files	Sections are embedded within the single file
Flexibility	Easier to share one calibration across many methods	Best for "locked" or self-contained workflows
Acquisition	Interpreted identically by the Service	Interpreted identically by the Service

Pro-Tip: Remember that you cannot use both at the same time. Choose the model that fits your lab's SOP and stick with it for consistency.

Why Should You Always Create Bound Files?

In the Processing tab of your method, the option to create a Bound (BND) file is selected by default. You should never disable this. While a RAW file contains the unprocessed detector signal, the BND file acts as a container that holds the raw data, the integration results, and the calibration information together. Using BND files ensures that if you move a file to another computer, all the work you did to integrate and identify peaks goes with it.

How Do I Start and Verify an Acquisition?

Once your method or solution is configured and saved with a meaningful name, you move to the Acquisition Client.

1. Download: Select your instrument and download the file. If using digital control, confirm the instrument acknowledges the download.

2. Start: You can trigger the run by right-clicking the instrument row, using the "TV Remote" icon, or simply by injecting a sample if your hardware is configured for auto-start.

3. Monitor: Watch the real-time plot. The run time counter will increase, and the signal should appear.

4. Verify: Once the status returns to "Ready," check your data directory. You should see two new files: a .RAW and a .BND.

   
   

People Also Ask

Why are my peaks not being named in the Analyze program?

In this stage of the training, no peaks are named because a calibration file has not yet been assigned. This is intentional. Acquisition captures the signal; identification and quantitation are covered in Section 3.

Can I change my sampling rate after the run is finished?

No. The sampling rate is a hardware instruction that determines how many times per second the system reads the detector. Once the run is over, the data density is fixed.

What happens if I forget to include a Setpoint file?

A Setpoint file is optional for the software to run, but essential for instrument control (e.g., setting temperatures or flows). If omitted, the instrument will simply run at its current physical state rather than a programmed state.

Where can I find my data files?

Files are stored in the directory defined by the instrument's data settings. You can verify this location within the Acquisition Client to ensure your RAW and BND files are being saved to the correct server or local folder.