Like many seasoned auto repair professionals, I’ve relied on Snap-on diagnostic scan tools for years, upgrading to a Solus Pro (7.2) around 2000. Generally, it’s been a dependable piece of equipment, delivering on its promises. However, recently, I’ve encountered a frustrating increase in “no communication” errors across various vehicle makes and models, including BMW E36, Renaults (2004 onwards), and Mercedes-Benz E-Class, to name a few. While occasional communication hiccups were always expected and easily dismissed in the past, the situation has escalated significantly.
Just last month, it felt like almost every other vehicle I connected to presented a communication problem. This prompted me to consider upgrading to the latest software, hoping it would resolve these persistent issues. My dealer attempted the upgrade on my van but faced difficulties. Consequently, they provided me with a demo unit running software version 10.2, while my unit was sent away for the upgrade, which has now been three weeks. Unfortunately, even with the newer software, the communication problems persist, particularly with newer Renault models and other makes. I’ve eliminated potential issues with my leads and keys, confirming they are not the source of the problem.
Now, I’m questioning whether to proceed with the upgrade at all and instead invest in a supplementary scan tool, possibly a Launch. Interestingly, I invested £50 in a Sealey OBD scan tool and discovered that it successfully communicates with all the vehicles that the Solus fails to connect with. This comparison further reinforces that the issue isn’t vehicle-related but potentially lies within the Snap-on tool’s communication capabilities with certain models.
I’m posting this to see if other technicians are experiencing similar communication issues with their Snap-on diagnostic scan tools, specifically the Solus Pro, and if anyone knows of adjustable settings or solutions to overcome these problems. Any insights or assistance would be greatly appreciated, as I’m increasingly frustrated with the time wasted troubleshooting communication failures.
