I have purchased recently OBD2 scan tool(Autel MaxiScan MS300) which supports ISO9141. My car (Mitsubishi Lancer GLX 1.3 1999) seems like ODB2 compatible using ISO9141-2 protocol for communication (checked here). I plug the tool, it initialized, I turn the key to "OK" position (the one which is indicated in the manual), the tool goes through different protocols and at the end reports that it is unable to communicate with my car. I have searched for solution, some people told that it is possible to be that some of the fuses is burnt, I have checked today all the fuses, cleaned contacts, still without luck. Are there any other issues which might be causing the problem in communication of the tool and the car?

Thanks a lot!

  • Could anyone point me also which tags I should add? I do not have enough reputation to add ODB2.. – Serhiy Jul 25 '15 at 12:33
  • It might help if you added the brand/model of the scan tool you are trying to use. – Pᴀᴜʟsᴛᴇʀ2 Jul 25 '15 at 16:35
  • added the name of the tool to the post Autel MaxiScan MS300 – Serhiy Jul 25 '15 at 20:36
  • I don't know why it wouldn't be working. The ISO 9141-2 is the Chrysler protocol, but I believe the 1999 Mitsu was when Chrysler and they were still in bed together. I read on Amazon that someone described initialization of the tool as: Plug in; self power on; turn ignition to on; press enter to start the tool registration. I would bet that is what you are doing, but thought I'd throw it out there. – Pᴀᴜʟsᴛᴇʀ2 Jul 26 '15 at 0:22
  • I will have to try on another vehicle, which is also OBD2 compatible (though it only will be possible in few weeks). Going to report the findings.. – Serhiy Jul 27 '15 at 9:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.