![]() ![]() If that gets deleted, your Techstream won’t be able to connect. I had to add it to my exceptions list to make sure it remained intact. There is something about the MVCI Driver files that my anti virus doesn’t like. I fixed it and was then able to connect to the car. I double checked my folder names, and sure enough I had a typo in one of my folder names. Then all of a sudden the sensor would go on and after maybe 50 miles of driving it would turn off. ![]() I did recently change my tire and everything was fine for about a week. I looked at the registry info and saw it was all there, but I also noticed that the file locations were called out there as well. My main reason for getting the MVCI cable was to see which one of my TPMS was causing the TPMS light to stay on. ![]() I was getting a connection error message within Techstream. I was having the same problems others had noted. Not sure if capitalization matters or not, but to be safe I’d even make sure that is followed. Go to first unread post Techstream 14.10.033, Windows 7 圆4, clone J2534 and unable to connect to VIM error. Make sure that the directories you create are in EXACTLY the same location specified in the instructions, and with the exact same spelling and wording as listed. The information that is copied to the registry gives very specific locations for the Xhorse drivers. For those of you who have commented on successfully seeing the connector work via the firmware update tool, but not able to connect using the Techstream software, I think I know why. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |