Like many seasoned auto technicians, I’ve relied on Snap-on diagnostic scan tools for years. Starting with a Solus Pro around 2000, these tools have generally been dependable for diagnosing vehicle issues. However, recently my Solus Pro (7.2) has been increasingly encountering “no communication” errors across various car brands, including BMW E36, Renault models from 2004 onwards, and Mercedes E-Class vehicles.
Initially, occasional communication failures were dismissed as anomalies. But lately, it feels like almost every other car I connect to presents this problem. Thinking a software upgrade might resolve the issue, I attempted to update to the latest version (10.2, on a demo unit), but the problem persists, particularly with newer Renaults and other makes. I’ve even ruled out issues with my leads and keys.
This has led me to question the value of upgrading my current Snap-on tool. I’m now considering investing in a secondary scan tool, possibly a Launch. Interestingly, a budget-friendly Sealey OBD scan tool I purchased for £50 successfully communicates with all the vehicles that the Solus fails to connect with, confirming the issue isn’t vehicle-related.
Has anyone else experienced similar communication problems with their Snap-on diagnostic scan tools? Are there any settings adjustments that could resolve this? Any insights or advice would be greatly appreciated, as troubleshooting these communication issues is becoming increasingly time-consuming and frustrating.
