How to Upload a Setpoint File in Chromperfect (All Digital Instruments)
- Chromperfect
- 2 days ago
- 3 min read
Topic Classification: Data Acquisition – Digital (All Digital Drivers)
This article applies to all digital instruments supported by Chromperfect, including:
Native Chromperfect digital drivers (.M68, .M78, etc.)
ICF (RC.NET) digital drivers (.MIC)
This article does not apply to analog (Tigre) acquisition systems.
Video Reference
The full upload workflow is demonstrated in this video example using an Agilent 7890.
Although the instrument shown is a 7890, the process applies to all digital instruments supported by Chromperfect.
Why Setpoint Files Must Be Uploaded
A setpoint file defines the operating conditions the instrument will use during acquisition.
For most digital instruments, a setpoint file cannot be created directly in the File Editor.
This is because modern instruments may have:
Different hardware configurations
Different installed modules
Different detector setups
Different firmware revisions
Before Chromperfect can reliably control an instrument, it must first read the instrument’s configuration directly.
This is accomplished by uploading the initial setpoint file from the instrument.
Once that first file has been uploaded, it becomes the template for creating additional setpoint files.
Important Exception: HP 5890
The HP 5890 is a legacy instrument with a simpler internal architecture compared to later digital models.
Because of this simplified design, Chromperfect can create M58 setpoint files directly within the File Editor without first uploading from the instrument.
However, aside from this difference in file creation, the operational use of setpoint files for the HP 5890 within Chromperfect is identical to all other instruments:
The setpoint file is referenced in the method.
It is downloaded to the instrument before acquisition.
It defines run conditions.
The workflow described below applies to all other digital instruments.
Step-by-Step: Upload setpoint file in Chromperfect
The overall process is consistent across different makes and models.
The file extension will differ depending on the driver architecture:
.M68, .M78, etc. → Native digital drivers
.MIC → ICF (RC.NET) digital drivers
The workflow remains the same.
1. Ensure Instrument Status Is Ready
After configuring a new instrument, its status may appear as:
Awaiting Download
Before uploading a setpoint file, change the status to:
Ready
Important: Use a method that does not have a setpoint file attached when changing status from “Awaiting Download.” Otherwise, an error may occur.
2. Open Instrument Control
Click the Control icon for the instrument.
Enable Show Special Features.
This opens the instrument-specific dialogue.
3. Select the Upload Tab
Within the Special Features dialogue:
Select the Upload tab.
This is where the initial setpoint file is created.
4. Enter a File Name
Use the Browse button to select a directory and enter a file name.
Chromperfect will automatically apply the correct file extension based on the instrument type.
Examples:
7890 (native) → .M78
ICF instrument → .MIC
5. Click Upload
When you click Upload:
Chromperfect reads the current instrument parameters.
A setpoint file is created in the selected directory.
The file reflects the instrument’s current configuration.
This file becomes your master setpoint file.
Editing and Creating Additional Setpoint Files
After uploading the first setpoint file:
Open the File Editor.
Open the uploaded setpoint file.
Make changes as required.
Use Save As to create additional setpoint files.
Multiple setpoint files per instrument are normal and expected.
It is not recommended to share setpoint files between instruments, even if they are the same model. Hardware configuration may differ.
Referencing a Setpoint File in a Method
To apply a setpoint file:
Open the Method Editor.
Go to the Acquisition tab.
Select the appropriate instrument type.
Choose the setpoint file from the directory.
Save the method.
Each time this method is used for acquisition, Chromperfect will download the referenced setpoint file before collecting data.
Common Questions
Why is the “New Setpoint File” option greyed out?
For most digital instruments, setpoint files must first be uploaded from the instrument. Direct creation in the editor is not supported.
The HP 5890 is the only exception.
Does this process differ between native and ICF instruments?
No. The upload workflow is the same.
The only difference is the file extension:
Native digital drivers → .Mxx formats
ICF drivers → .MIC
Do I need a new setpoint file for each method?
Not necessarily.
You may reuse a setpoint file across multiple methods if the run conditions are identical.
However, creating separate files for different operating conditions is common practice.
Summary
All digital instruments use setpoint files.
Most instruments require the first setpoint file to be uploaded from the instrument.
The HP 5890 is the only instrument where setpoint files can be created directly.
The file extension reflects the driver architecture.
Operational use of setpoint files is consistent across instruments.
Comments