I just upgraded from my MT2500 to a used Solus with 9.2 software. I hooked it to a 2008 F250 6.4 diesel, a 2008 Ford Escape 3.0, and a 2007 Dodge Caliber 2.0. With both of the Fords, it communicated intermittantly and would pull codes and initiate self tests at times, but at other times it would lose communications. When it lost comm, the cable was not disturbed and the dlc connection was tight and straight without being disturbed. This was with the K17 key on both Fords. I swapped the cable and the obd2 block with my MT2500 which I know works with no change. I dont have any other keys to swap though. The Dodge Caliber using the K25 key would not auto id or communicate at all. Also, using the K20 key and global obd2 had the same result--sometimes it would communicate fine and other times it would not at all. Even when it communicates fine, if I go into data (on either of the Fords) I will get a data stream for about 30 seconds to 1 minute and then it will lose communications. Im a little frustrated with this--has anyone else experienced this? I hooked it to my 96 F150 5.0 with the K2a key(non CAN) and it worked flawlessly. Any ideas? Thanks in advance for any help you might have for me.
Solus loss of communication
Collapse
Comment