Understanding ICF XML vs MIC Files in Chromperfect
- Chromperfect
- 2 days ago
- 5 min read
Scope of This Article — ICF Systems Only
This article applies only to Chromperfect systems using ICF (RC.net) digital communication.
It does not apply to:
Instruments using native Chromperfect digital drivers
Analog acquisition systems (e.g., Tigre interfaces)
In Chromperfect, XML configuration files are used only when an instrument is controlled through ICF. So lets explore ICF XML vs MIC files in Chromperfect...
Instruments That May Use ICF (Depending on Configuration)
The following instruments can be controlled either through ICF or through native Chromperfect drivers:
Agilent 6890
Agilent 6850
Agilent 7890
If these instruments are configured using native drivers, this article does not apply.
Instruments That Use ICF Exclusively in Chromperfect
Agilent 8890
Agilent Intuvo (and variants)
Agilent 1100 Series HPLC
Agilent 1200 Series HPLC
Shimadzu GC-2010
Shimadzu GC-2014
Shimadzu GC-2025
Shimadzu GC-2050
Scion 8500 Series
Scion 8300 Series
HTA autosamplers (ICF-controlled models)
How to Confirm You Are Using ICF
To confirm whether your instrument is configured using ICF:
Open the Chromperfect Data Acquisition Service.
Click Configuration.
Review the instrument grouping.
Instruments configured using ICF will appear grouped under:
ICF Instruments
Instruments using native drivers will appear under their instrument type (for example: 7890, Thermo, 1610, etc.).
The grouping — not the model name — determines whether ICF is being used.
If your instrument appears under the “ICF Instruments” group, this article applies.
Why This Distinction Matters - ICF XML vs MIC files in Chromperfect
When using ICF instruments, two different file types are involved:
The XML configuration file
The MIC setpoint file
They serve completely different purposes.
Confusing them can lead to incorrect troubleshooting assumptions, such as:
Attempting to modify run conditions in an XML file
Assuming a MIC file controls instrument registration
Believing XML files are required during routine acquisition
Understanding the separation between these file types eliminates that confusion.
Key Definitions
What Is ICF?
ICF (Instrument Control Framework) is a communication framework used to control compatible instruments through a standardized driver environment.
In Chromperfect, ICF is used for the instruments listed in the scope section above.
What Is RC.NET?
RC.NET is the driver layer used within the ICF framework that enables communication between Chromperfect and the instrument.
What Is an XML File (in the ICF Context)?
An XML file created by the ICF Configurator defines:
Instrument hardware configuration
Communication parameters
System-level instrument registration
It allows Chromperfect to recognize and communicate with the instrument.
It does not contain run parameters such as:
Oven temperatures
Flow rates
Detector settings
Autosampler sequences
What Is a Chromperfect Setpoint File?
A setpoint file captures the operating conditions the instrument will use during a run.
It defines what the instrument should do during acquisition.
Setpoint files are part of routine operation.
What Is an MIC File?
An MIC file is the setpoint file format used for ICF-controlled instruments.
It contains run parameters such as:
Oven programs
Flow settings
Detector configuration
Autosampler settings
The MIC file is not created during instrument registration.
It is created after the instrument is operational and is used during routine acquisition.
Note on Other Setpoint File Formats
Setpoint files exist in all digital Chromperfect systems, not only ICF.
The file extension identifies the driver architecture:
.MIC → ICF (RC.NET) digital instruments
.M68, .M78, etc. → Native Chromperfect digital drivers
All of these are operational setpoint files.
Only ICF systems use XML configuration files and the .MIC format.
If your setpoint file does not use the .MIC extension, your instrument is not operating under ICF, and XML configuration files are not involved.
The Two-Layer Model: Setup vs Operation
The simplest way to understand the difference between XML and MIC files is to separate instrument use into two phases.
Phase 1 — Instrument Registration (Configuration Layer)
This phase occurs during setup.
It involves:
Running the ICF Configurator
Creating or registering the XML file
Defining hardware and communication settings
Verifying instrument connectivity
The XML file belongs entirely to this phase.
Once the instrument is successfully communicating with Chromperfect, the XML file has fulfilled its purpose.
Most users will not need to modify it again unless:
Hardware changes
Network configuration changes
The instrument is reinstalled
The XML file is a system configuration file. It is not a daily working file.
Phase 2 — Routine Operation (Operational Layer)
This is the environment in which most users operate.
It involves:
Methods
Setpoint (MIC) files
Uploading setpoints
Data acquisition
The MIC file belongs entirely to this phase.
It is:
Referenced by a method
Used during acquisition
Modified when run conditions change
The MIC file is a working file.
It is not part of instrument registration.
One XML File vs Multiple MIC Files
For each instrument configured via ICF in Chromperfect:
There will be one XML registration file per instrument.
This file is tied to that specific instrument’s hardware and communication configuration and is never duplicated for the same instrument.
If multiple ICF instruments are configured on the same Chromperfect system, each instrument will require its own unique XML file.
Each XML file is named based on the instrument’s IP address. For example:
192.168.1.123.xml
192.168.1.131.xml
If two instruments are configured, two corresponding XML files will exist — one for each instrument.
By contrast: There may be multiple MIC setpoint files for the same instrument.
Each MIC file represents a different set of operating conditions, such as:
Different oven programs
Different detector configurations
Different methods
Different sample types
This reinforces the separation:
The XML file defines how Chromperfect communicates with a specific instrument.
The MIC file defines what that instrument does during a specific run.
Practical Implications
Understanding this separation prevents common misunderstandings:
Editing an MIC file does not change instrument registration.
Reconfiguring the XML file does not change run temperatures or flows.
Deleting or corrupting the XML file will prevent communication.
Deleting an MIC file does not unregister the instrument.
Creating a new method does not require a new XML file.
The XML file controls communication.
The MIC file controls operation.
They are not interchangeable.
Common Questions About ICF XML and MIC Files
Should I create a new XML file for each method?
No. The XML file defines instrument registration and communication. It is not related to method parameters or run conditions.
Why do I have multiple MIC files but only one XML file?
Because they serve different roles.The XML file defines how Chromperfect communicates with the instrument.MIC files define how the instrument operates during specific runs.
If I edit an MIC file, does that change instrument registration?
No. Editing an MIC file only changes operational setpoints. It does not affect hardware configuration or communication settings.
If communication fails, should I modify the MIC file?
No. Communication issues are related to configuration (XML/ICF setup), not run parameters.
Can I delete an MIC file?
Yes.Deleting an MIC file removes that specific run configuration, but it does not unregister the instrument.
Can I delete the XML file?
No, unless you intend to reconfigure the instrument. The XML file is required for communication in ICF systems.
Summary
File Type | Purpose | When Used |
XML | Instrument configuration and communication | Setup only |
MIC | Run setpoints and operating conditions | Routine acquisition |
If the instrument is already acquiring data successfully, the XML file has already done its job.
At that point, your focus shifts entirely to methods and MIC setpoint files.
For instructions on how to create or upload a setpoint (MIC) file, refer to:
How to Upload a Setpoint File in Chromperfect
Comments