1.1 Understanding Chromperfect Architecture: The Service vs. The Client
- Chromperfect
- Apr 8
- 3 min read
This article is an in-depth analysis of a single video within the Chromperfect Beginner Training Series. Specifically, we are looking at Module 1.1: Service vs. Client Explained from Section 1: System Foundations.
In the world of chromatography data systems (CDS), software stability is the difference between a successful overnight sequence and a week of lost laboratory time. This module solves the most common "pain point" for new users: the confusion over whether closing a window stops an active run. By decoupling the user interface from the engine, Chromperfect ensures that your data remains safe, even if your desktop environment does not.
Why Watch? The visual demonstration in this module allows you to see the real-time interaction between The Service vs. The Client . reinforcing how to manually restart the engine should communication ever be interrupted.
The Quick Answer
Chromperfect operates using a two-part architecture: the Service (the background engine that talks to the instrument) and the Client (the interface you use to enter names and view plots). Because they are separate, you can close the user interface without stopping your data acquisition.
What is Chromperfect?
At its core, Chromperfect is a comprehensive chromatography data system designed to manage instrument communication, data acquisition, processing, and reporting within a controlled environment. To maintain this control, the system divides its workload into two primary components.
The Chromperfect Service: The Silent Engine
The CP Service is the background engine of the system. It runs at the operating system level as a Windows Service and is the only component that directly maintains active run control.
Autonomy: It typically starts automatically with Windows and operates independently of the user interface.
Responsibility: It handles all instrument communication and writes acquired data directly to the disk as RAW files.
Manual Control: If the service is stopped, it can be restarted via the Windows "Services" applet.
Critical Dependency: The Service must be running for the Client to operate; if it is offline, the Client will prompt you to start it manually.
The Chromperfect Client: Your Interface
The CP Client is the Windows application you interact with. It is accessed via the Chromperfect main menu by clicking "Run".
Interface Elements: It features a "Status" tab and a "Selection" tab, distinguished by different background colors.
User Tasks: This is where you select methods, enter sample names, and view real-time chromatogram plots.
Indirect Control: Crucially, the Client does not directly control instrument hardware. It acts as a messenger, passing your instructions and methods to the Service.
Comparison: Service vs. Client
Feature | Chromperfect Service (Engine) | Chromperfect Client (UI) |
Visibility | Runs in the background | Visible Windows application |
Hardware Link | Directly communicates with instruments | No direct hardware control |
Data Handling | Writes RAW data to disk | Displays plots and enters file names |
Closing the App | Continues running if Client is closed | Can be closed without stopping a run |
Why This Separation Matters
The primary reason for this architecture is stability. By separating the user interface from the acquisition engine, Chromperfect ensures that an issue with the UI—or a user accidentally closing a window—does not terminate a sensitive analysis.
Pro-Tip: This architecture also allows for Distributed Acquisition. A single Client on your PC can connect to multiple Services across a network, giving you visibility of instruments located in different labs or even different sites.
The Workflow Blueprint
The direction of control always follows this specific path:
Client to Service: You send the method and instructions.
Service to Instrument: The engine starts the hardware.
Instrument to Service: Raw data flows back to the engine.
Service to Data Storage: Data is written safely to the disk.
The Road Ahead: The Full Training Series
Understanding this foundation is the first step in the System Foundations section. To become fully operational, you will progress through the following five sections:
Foundations: Architecture and instrument status.
Files & Methods: Managing Raw vs. Bound data and method control.
Data Processing: Working in the Analyze program and integration.
Reporting: Generating and exporting results.
Automation: Sequences, batch processing, and security.
Next Step: Move to Module 1.2: Understanding Instrument Status States to learn how the Service communicates the real-time readiness of your hardware.
People Also Ask (FAQ)
Does closing Chromperfect stop my sample run? No. Closing the "Client" (the user interface) does not stop the "Service" (the engine). The Service will continue to manage the acquisition and save data in the background.
What should I do if the Client says "Service Not Running"? You must start the CP Ack Service manually. Open the Windows search bar, type "Services," find the Chromperfect Service, and click "Start".
Where is my data actually saved during a run? The Service writes data directly to the disk as RAW files during acquisition. These can be processed into BND (Bound) files later, which we cover in Section 2.
Comments