1996 OBDII CONNECTS GOES THROUGH PROTOCALL BUT TIMES OUT

Clones · Dec 8, 2018

I have a basic code reader that has a check engine light. It runs like it has a misfire on a cylinder I wanted to check the codes and see what was going on. But when I connect my scanner it goes through the process of checking all the ports. But then claims it timed out once it completed all the ports. Any suggestions?

lawsoncl · Dec 8, 2018

Clones said:
I have a basic code reader that has a check engine light. It runs like it has a misfire on a cylinder I wanted to check the codes and see what was going on. But when I connect my scanner it goes through the process of checking all the ports. But then claims it timed out once it completed all the ports. Any suggestions?

Key needs to be in run position but engine not started. Worst case, you can do the key-on-off trick and count the blinking light.
http://www.answers.com/Q/How_do_you_manually_retrieve_fault_codes_on_a_1996_Jeep_Cherokee

Clones · Dec 8, 2018

I did read about the blink code I thought that was obd1 only? I'll try it and yes I've tested with key on

craiso · Dec 9, 2018

My 1996 has the OBDII connector, but it is not functional. The key-dance is how you retrieve the codes.

1996 OBDII CONNECTS GOES THROUGH PROTOCALL BUT TIMES OUT

Clones

NAXJA Forum User

lawsoncl

NAXJA Forum User

Clones

NAXJA Forum User

craiso

NAXJA Forum User

Similar threads