No comms with EZL module?

[darek_u]

I have just did a trial start of the engine after rear diff swap and fuel pumps overhaul. Engine started and run fine, maybe it shaked a bit more than normal - I didn't run it for a long time so maybe a bit of the moisture build up under the caps. I don't worry about it now anyway. I wanted to check and clear all the codes before taking the car off the QJ and rolling it out of the garage.

All went fine except for EZL. I can't get any response from this module. I double checked all the connections - all good. Is it normal? Shouldn't it blink once if AOK, just like the rest of the them?

Other modules don't report lack of communications with 3/1 so I assume it is alive, the engine run fine ('ish), without EZL working it won't run at all I think. What should I think about it? Just leave it as is and move on or start to worry?

 

[Jlaa]

I have just did a trial start of the engine after rear diff swap and fuel pumps overhaul. Engine started and run fine, maybe it shaked a bit more than normal - I didnt run it for a long time so maybe a bit of the moisture build up under the caps. I dont worry about it now anyway. I wanted to check and clear all the codes before taking the car off the QJ and rolling it out of the garage. All went fine except for EZL. I cant get any response from this module. I double checked all the connections - all good. Is it normal? Shouldnt it blink once if AOK, just like the rest of the them? Other modules dont report lack of communications with 3/1 so I assume it is alive, the engine run fine (ish), without EZL working it wont run at all I think. What should I think about it? Just leave it as is and move on or start to worry?

I have found communication w the EZL module with SDS and Chinese sourced C4 to be somewhat flaky. 80% I can communicate with the EZL and 20% It doesn’t communicate. This has happened on both my car and @dionphaneuf ’s car. Sometimes I just reboot the SDS and reseat the silver connector and try again and it works …. And the likelihood that it works improves if the engine is not running.

I don’t know if this issue I see is electronic noise related, C4 related, or if my experience helps you at all, but maybe it provides clues? FWIW I have noted that when I cannot talk to the EZL, I cannot talk to the DM either. This occurs with my China sourced 38 pin cable that has all the pins. Anyways I recently sourced an MB OE 38pin cable and haven’t seen this issue yet with the MB OE cable, but I have only used this cable once.

 

[gerryvz]

Were you using the Chinese clone of the Star C3/SDS, or an ordinary blink code reader?

If using the Chinese STAR C3, it is well documented on the forum that the cables are defective (don't contain all of the necessary pins) and do not communicate with all of the car's systems. Replacement cables that do have all of the communication pins are available.

 

[darek_u]

Gents I have simple blink tester. I'm using a set of known good cables and splitter box. I've never had a problem communicating with EZL - I used to have a permanent code coming from overload protection switch that I replaced a month ago with new OE. In fact my intention was to clear this code but now there is nothing - not a single blink...

 

[gsxr]

If the blink tester won't communicate, verify there is continuity between pin #17 at the 38-pin diagnostic port, and the EZL. Possibly to coupling A, pin 7? (Not sure, never checked this.) FSM details here.

The modules communicate with each other via CAN bus and yes, the engine would not start or run if the EZL was dead.

 

[darek_u]

I need to check it out today.

 

[darek_u]

Dave you should be officially called a Genius
Indeed there was no continuity between pin 7 and the diagnostic socket. Culprit - pin 17 moved back in the socket, it just slided off the locking device. All is back to normal now, all codes deleted. Thanks again!

 

[gerryvz]