Methods for electrode cleaning for Echo MS systems

Jun 3, 2025 | Blogs, Echo® MS+ system, Pharma | 0 comments

Read Time: 2 min

Depending on the samples that you are running on the system, it is possible for the Echo MS electrode to become dirty or occluded over time. Below are two different cleaning strategies that will be helpful for you to maintain your system and keep your electrodes running well.

Quick cleaning protocol

This protocol is easy to perform between running your sample plates.

From the Maintenance menu of the Echo MS direct control, select OPI Port Access then Lift to provide access to the top of the OPI port.
Disconnect electrode by loosening the finger tight red nut and pulling straight up
Place the OPI port end of the electrode into solvent. With the MS system still active, the draw created from the GS1 flow will draw solvent through the OPI into the MS source, turn Spray voltage to 0.
Wash with Milli-Q water for 1 min
Wash with 20% Acetonitrile with 0.1 M Formic Acid (0.4% FA) for 20 min
- Drawing speed is about 450 µL/min based on the consumption of 20% Acetonitrile with 0.1 M FA
Wash with Milli-Q water for 1 min
Reattach the electrode to the system and tighten the red nut finger tight.
Restart the mobile phase flow and check the Maximum Supported Flow (MSF)

Intensive cleaning protocol

This protocol is an offline protocol that can be used periodically for a more intensive wash of the electrode or to recover electrodes that are suffering from reduced flow rates.

Connect the OPI electrode to a small union (1/16 to 1/32) , IDEX Part # P-881 )

Place the electrode end of the capillary in a waste vessel capable of holding 200 mL or more
Flow at least 200 ml of 50% methanol through the electrode at a flow rate of 5 – 8 mL/min using an HPLC pump
Test on Echo MS system for droplet linearity, reproducibility, and peak shape
If storing the recovered electrode flush with 100% methanol before storing.

Some electrodes may not be able to be recovered but we have had good success with this method.

Bioanalysis across modalities: Advancing confident decisions with modern LC‑MS strategies

As therapeutic pipelines continue to diversify, bioanalysis is being asked to do more than ever before. From small molecules to complex biologics, today’s scientists must generate high‑quality, reliable data across a growing range of molecule types and workflows, often under increasing time pressure.

The rules have changed

Regulated laboratories are evolving faster than ever. New analytical modalities, higher sample throughput, increasing regulatory scrutiny, and leaner teams are reshaping how work gets done. At the same time, expectations for data integrity, standardization, and operational efficiency continue to increase complexity and/or scope. In this environment, LC-MS software is no longer simply an instrument control platform—it has become a critical part of a laboratory’s quality management system. The question is no longer whether your lab has changed, but whether your software has evolved to support the way regulated labs operate today, and if they are ready and able to meet the demands, they will face tomorrow.

The wakeup call

Analyst software has long been a trusted foundation in regulated LC-MS laboratories—and for many, it still performs reliably today. But regulated environments are evolving faster than ever. As labs transition to Windows 11, strengthen cybersecurity policies, modernize IT infrastructure, and prepare for future compliance expectations, software decisions are no longer just about what works today—they’re about managing tomorrow’s risk. Analyst will not be supported on Windows 11. While some labs may continue operating in unsupported environments temporarily, the bigger question is: when that risk becomes reality, will your lab be reacting under pressure—or executing a planned mitigation strategy with confidence?

Posted by

John Gibbons

Trained and working in Organic Synthesis I started using mass spectrometry to aid in my synthesis work. As my interest in mass spectrometry grew, I change roles several times within the pharmaceutical industry to be able to focus on its use and applications. I joined SCIEX in 2006, initially as a demo chemist, then with R&D, primarily focused on Analyst, and eventually SCIEX OS software development. More recently I switched to technical product management for Echo MS systems.

0 Comments