As a lab professional, you rely on the precision and consistency of your automated liquid handlers. But what happens when you prep your deck, start your protocol, and your EVOware software suddenly claims your instrument is missing a crucial component? Recently, the SeqGen service team tackled a perplexing case that perfectly highlights why error codes don't always tell the whole story.
Quick Summary / Key Takeaways
The Tecan EVOware error EVO_EVO_022-000: Instrument has no LiHa occurs when software communication with the Liquid Handling arm is severed. While clearing driver backlogs or verifying software settings can resolve minor glitches, persistent errors accompanied by secondary Device: C5 warnings usually point to a failed Device Control Unit (CU) board requiring board replacement.
Imagine booting up your Tecan Freedom EVO, only to be blocked by a stubborn initialization error: EVO_EVO_022-000: Instrument has no LiHa.
What makes this hardware failure so frustrating is that it rarely starts with a clear warning. Because the main communication board is failing, EVOware gets completely confused and often throws cryptic, secondary errors first. For example, as shown in the screenshot below, your screen might freeze with a bizarre Error: 2, invalid command for Device: C5. It is incredibly easy to waste hours trying to fix this "C5" software error, only to realize it's just a red herring for a much larger hardware disconnection.
When your system refuses to acknowledge its own LiHa (Liquid Handling) arm, it typically halts all laboratory operations. So, where do you start?
When faced with an unresponsive LiHa and frozen EVOware screens, our engineers recommend checking a few immediate software parameters before assuming the worst:
In our recent case, the user diligently went through all these software checks. They even double-checked the physical tightening of their DiTi tips, suspecting a jammed tip motor. However, no amount of software resetting or rebooting could clear the "No LiHa" error.
Why? Because the root cause wasn't a software glitch at all.
After deep diagnostics, our field service engineers discovered that the Device CU board had failed. The broken control board was completely severing the communication pathway between the EVOware software and the physical LiHa module. The software wasn't glitching; it legitimately couldn't "see" the hardware because the bridge between them was destroyed.
While software checks are a great first step, diagnosing the true root cause of a Tecan error often requires looking beyond the screen. A failing CU board can easily masquerade as a simple configuration error, leading to hours of frustrating and fruitless troubleshooting.
Next time your Tecan instrument throws a mystery error that basic troubleshooting can't solve, don't waste your valuable time. Contact the SeqGen Service Team! Our expert engineers have the diagnostic expertise, specialized parts, and hands-on skills to uncover the root cause and get your lab back to peak performance.
SeqGen specializes in the repair, maintenance, and refurbishment of essential laboratory instruments used in DNA sequencing and genetic research. Our expertise covers a wide range of equipment, including DNA sequencers like the ABI 3730/3730XL, 3500/3500XL, SCIEX LC/MS mass spectrometers such as the SCIEX 6500+, TECAN Freedom EVO liquid handlers, real-time PCR systems, thermal cyclers, and microplate readers. With experience in both current and legacy models, SeqGen provides cost-effective solutions at significantly lower prices than leading competitors.