Clarity computer requirements and compatibility

Importance of the topic

This document summarizes system and hardware requirements for Clarity chromatography data system (CDS). Clear specification of computer, operating system and peripheral compatibility is essential for reliable instrument control, data acquisition and regulatory compliance in analytical laboratories. Ensuring correct PC configuration and supported hardware keys or converters minimizes downtime, prevents data loss and simplifies validation efforts in regulated environments.

Objectives and overview of the document

The original document provides:

• Minimal and recommended computer specifications for running Clarity and Clarity Lite configurations.
• Supported Windows versions and required .NET framework versions.
• Compatibility matrix for hardware keys and communication converters (Colibrick, Zebrick, Net-PAD) across Windows releases and Clarity versions.
• Notes and practical guidance for transferring Clarity installations between PCs and for regulated installations.

Methodology and system requirements

The requirements are presented as minimal and recommended builds and as compatibility notes for various Windows releases. Key points include:

• Minimal configuration: suitable for Clarity (Lite) with a single instrument using an analog A/D converter (Colibrick). Minimal PCs can be older 32-bit systems (e.g., Pentium 4) with 2 GB RAM.
• Recommended configuration: modern 64-bit Windows (Windows 11/10/8.1/7 Pro where required), Intel i5-8250U or newer class CPU, 8 GB RAM, SSD and higher display resolution (recommended 1920x1200) for running multiple Clarity Instruments, PDA, MS extensions and Agilent ICF modules.
• Peripheral requirements: 1–3 USB ports for hardware keys and USB-based converters (Colibrick, Zebrick, MultiCOM), and a LAN port for Net-PAD or direct networked instrument communication.
• Software: Clarity requires up-to-date Windows and Microsoft .NET Framework 4.8 or higher (from Clarity version 10.0). Some external control modules may also require .NET 3.5.
• Regulated environments: Windows Pro/Professional edition is required for configuring Clarity in a regulated environment (see referenced regulatory guidance in original documentation).

Used instrumentation

The document lists supported hardware keys and communication devices and notes the Clarity version from which each device is supported. Principal items are:

• RkNDUSB hardware key and RkUSB hardware key (license dongles).
• Colibrick A/D converter (supported from Clarity 4.0).
• Zebrick converter (supported from Clarity 7.0).
• Net-PAD for networked instrument communication.

Compatibility notes: older blue-cast RkUSB keys require legacy drivers not compatible with some modern Windows security settings and therefore are not supported on Windows 10 and 11. Colibrick and Zebrick support depends on Clarity version as noted above.

Main results and discussion

Practical conclusions drawn from the compatibility and requirement information:

• Modern, 64-bit Windows systems with recent CPUs, SSDs and >=8 GB RAM are recommended to reliably run multiple instruments and extended modules; older 32-bit PCs are only suitable for minimal, single-instrument analog acquisition.
• USB ports and a LAN port are essential for dongles, converters and networked devices; plan workstation hardware accordingly.
• Using up-to-date Windows and the correct .NET framework versions is required for full Clarity functionality; some modules may need legacy .NET components.
• Legacy hardware keys can introduce compatibility and security issues; labs should migrate to supported dongles/converters and validate replacements prior to deployment.
• For regulated laboratories, Pro/Professional editions of Windows and appropriate validation procedures are required; check the vendor’s regulatory guidance for details.

Benefits and practical applications

Adhering to these requirements and compatibility notes provides several operational advantages:

• Stable instrument control and data acquisition across varied analytical workflows (HPLC/GC with PDA/MS extensions).
• Simplified validation and compliance when using recommended OS editions and documented hardware.
• Reduced risk of unexpected driver/security conflicts by avoiding obsolete hardware keys and keeping Windows/.NET current.
• Optimized performance for multi-instrument setups and processor-intensive modules (MS, PDA) with recommended hardware.

Future trends and opportunities for use

Anticipated directions and recommended actions for laboratories planning upgrades:

• Migrate to 64-bit Windows platforms and SSD-equipped workstations to support future Clarity releases and extensions.
• Replace legacy USB dongles with vendor-supported keys or network licensing solutions to avoid driver/security issues on modern OS versions.
• Monitor Clarity release notes for added support of converters and communication devices and for changes in .NET or OS requirements.
• Adopt networked instrument configurations (Net-PAD) where appropriate to centralize acquisition and simplify maintenance.

Conclusion

The Clarity system requires a range of PC configurations depending on intended use: minimal older hardware can support basic analog acquisitions, while robust, modern 64-bit PCs are recommended for full-featured multi-instrument operation. Staying current with supported hardware keys, converters and Microsoft .NET/Windows versions is critical to ensure stable operation and regulatory compliance. Plan hardware and licensing migrations proactively to avoid compatibility pitfalls when upgrading operating systems or Clarity versions.

Reference

Document identifier: Code/Version D016/EN39-20260521

Publisher: DataApex s.r.o., ISO9001 certified, Tel.: +420 251 013 400

Notes: Clarity support for specific converters and keys is version-dependent (Colibrick from 4.0, Zebrick from 7.0). Older RkUSB keys (blue casting) are not supported on Windows 10/11 due to driver/security incompatibilities. .NET Framework 4.8+ required from Clarity 10.0; some modules may require .NET 3.5.