Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

Not to derail things but this is very similar to the issue I'm having. Caps, rotors, wires, Cats, NSS, all replaced. I keep getting EZL code 8. I've swapped LH modules and didnt' help things. I finally have all the parts to do the trans overload switch change and will try to do it soon but I'm calibrating my expectations that this will be a cure all. In particular, your comment about intermittency resonates strongly - on my car, after a cold start I usually have no issue with WOT upshifts, either from start or from a highway pull. But after some time driving (20 mins?) flooring it on the highway results in hesitation, both in 3rd and in 4th, especially in the 4k-5.5k RPM range. I also recently got the cold start upshift delay (code 26).The first few times I stood on it on the highway it downshifted and took off just fine. No problems. Once I had a wide open stretch I stood on it again and let it pull up to about 100. Right at 100 it upshifted to 4th (I think it was 4th anyway) and it started to surge again. From that point on, the issue was back. It's weird. It's almost like it detects something it doesn't like, and then it goes into a failsafe mode. Maybe that's how it's designed. Maybe I'm reading too much into it.
Anywho, it's strange that the car didn't do this with the used switch I had installed, and in fact didn't do this with the brand new switch until a few pulls after I did the diff swap. I think I'll try my other 4.2 EZL and see if that makes a difference. If not maybe I'll go back to the used switch I'd been running and see if that does anything.
Sounds super similar for sure. I still haven't solved it on mine. Once I get the ABS sorted I'll probably try swapping sensors again to see if I can get any different results. Definitely feel free to post here or message me directly if you want to discuss further. I'd love to figure this one out.Not to derail things but this is very similar to the issue I'm having. Caps, rotors, wires, Cats, NSS, all replaced. I keep getting EZL code 8. I've swapped LH modules and didnt' help things. I finally have all the parts to do the trans overload switch change and will try to do it soon but I'm calibrating my expectations that this will be a cure all. In particular, your comment about intermittency resonates strongly - on my car, after a cold start I usually have no issue with WOT upshifts, either from start or from a highway pull. But after some time driving (20 mins?) flooring it on the highway results in hesitation, both in 3rd and in 4th, especially in the 4k-5.5k RPM range. I also recently got the cold start upshift delay (code 26).
Will be positing my progress here on this, fingers crossed we can solve.
I did. The issue remained. In my case the EZL I swapped in was from a 95, which is somehow different from the 92 EZL I should have, but the same issue was there in either case.Have you tried swapping the EZL? Isn't that the 'brain' that could be impacting this?
Yeah, it's just 2 wires. It would be easy to connect two wires to the switch temporarily, but connecting to the EZL would be more difficult. One of those two wires just goes to ground, so that's easy, but the other one joins up with several other wires inside a harness that goes to one of the larger connectors on the EZL. It would not be easy to connect that wire to the EZL without cutting into that harness and connector.It's just a two wire circuit, right? Can you run new wires on a piggyback to rule that out, and potentially pin direcly to the switch?
Wiring seems kinda unlikely to be so consistently inconcsistent. Maybe it's something internal to the trans, when it heats up to a certain point? I may need to call Mark at Sun Valley for an issue on another car and will pick his brain on this one.

That's a good idea.Might be worth getting a cheapy hand oscillisope off amazon. Would allow for more precise visuals of the signals coming from each of the sensors. I think they are fairly affordable these days.

It is a metal body. It's only a 5 minute job to change it when the car is on the lift, so I'll definitely order one with my next parts order.If the ABS sensor has a metal body, it uses O-ring p/n 014-997-97-48, which is fairly thin. $2 MSRP, ~$1.60 or so from discount dealers. Not that you want to change it again, but next time you have a part order going in...
It does not ping when downshifting to 2nd or to 1st. The fact that it doesn't ping in 2nd probably has to do with the overload switch. I don't think it's going lean. I think the cylinder pressure is too high for the ignition advance at that moment, and the EZL is not being commanded to pull timing, so it's detonating rather than burning smoothly.Interesting hypothesis. Do you notice the same pinging in other gears/during WOT at other times?
Maybe at high speed you're getting a ton of air into the engine? But shouldn't the MAF/ETA be compensating for this?
I pulled a 2 pin male connector and a 2 pin female connector off my S500 parts car. I cut the retaining clips off the connectors, then spliced the two together and plugged the assembly between the overload switch and its harness. Then I tapped into the wire in line with the output leg of the switch, which leads to the EZL. That became my switched ground for the bulb. Then I just grabbed 12v+ off a fuse and ran that in to the other side of the bulb.Thats a really neat approach you took. How did you splice in the bulb? If its easy enough and reversible, a couple of us may be able to try it out ourselves and report back …
I don't hear pinging, and there isn't a code for it.Can you audibly hear pinging? If not, it's unlikely there is ignition retard occurring enough to feel a power loss. When retard hits the maximum (-12°) the EZL will store a code. You can view live retard values with HHT-Win on SDS, although it's tricky at WOT without a second person (don't try this at home, kiddos!)
MPH is irrelevant. The ECU's only know load and RPM's. The fact those are now at lower speeds due to 3.06 gears doesn't matter.

My transmission acts healthy. I don't know exactly when B1 engages/disengages, but I think it's plausible that it only engages in 2nd gear. If that is the case, then there is no way that the overload would ever close during a 4-3 downshift. If the EZL has no way of knowing which gear the transmission is in, then it could only judge whether the overload switch should close by looking at RPMs, engine vacuum, knock sensor output, and whatever other data it receives.Good question about the EZL and gears. I'm not sure if it "knows" what gear the transmission is in, or if it behaves the same for all upshifts (but I think it should).
The O/L switch measures B1 mvoement / pressure, correct? But does B1 engage/disengage for all upshifts?
![]()

Great research! One minor problem though. Euro models have a 2.65 differential and the identical EZL part numbers. It seems odd that only 3.06 gears would cause this problem. The trim plugs (resistors) only pull timing, for use of lower-octane fuel... I don't think any of those will help.
Next question: What specific EZL part number do you have installed? What EZL part numbers do you have as spares to experiment with?
![]()


That would most likely support the idea that my issue could be a vacuum leak. That, or there's something else involved in the EZL deciding what is 2nd gear and what is not.The 140 chassis with 4.2L engine use identical EZL part numbers as the 400E / E420, although with different chassis break points of course.
012- was used in 1992 (10:1 compression engine, early chassis, supercedes to 013-)
013- was used in 1992 (10:1 compression engine)
014- was used in 1993 (11:1 compression engine)
015- was used in 1994-95 (11:1 compression engine, with open-deck block, after chassis break point shown)
View attachment 180144
View attachment 180143

I had not seen that. That's great info, and gives me more to investigate. Thanks Dave.The info above is from the FSM, job 15-0200, section J, "Transmission Overload Protection"... PDF pages 30-31 of 32. Had you not seen that yet?
![]()
No doubt. I resisted trying this 3rd EZL for a long time because I figured it was so unlikely to be the EZL since the first two acted the same. One was original to the car. The other I got from a local junk yard. The EZL that fixed it came from my S500 parts car.Kinda nuts that two would behave the exact same way. Where did you get them? Ebay?
I don't think the gear ratio was a factor. The way the EZL works it just looks for a change in state of the overload switch from open to closed or closed to open to identify that a gear change has occurred. In my case, I believe I had two malfunctioning EZLs, both of which were unable to see the overload switch at all. That made them both go into fault mode, where they use a far more aggressive timing reduction strategy, which caused the symptom I was feeling. The manifold vacuum signal is only a factor in that the EZL needs to see vacuum below 300 millibars at 4000 RPMs or higher when the overload switch changes state in order to initiate a drop to 5 degrees BTDC for 400 ms. That's it. The gear ratio doesn't matter at all since vacuum drops way lower than 300 mb any time the car is at WOT.Poking at your original analysis, wonder what the gear ratio math works out to be for all the trans/rear diff ratios across all the models that the s500 EZL P/N was used on. Perhaps it ‘covers’ a wider range than the e420 PN?

The LH is 012-545-30-32. I believe it is original to the car. I believe the engine is also original. It's an early 4.2. It has no mounting boss on the timing cover for the later belt tensioner, so I'm sure it's a 10:1 motor.Dumb question, but what LH module part number is currently installed? Also, this is a 1992 400E 4.2L engine with 10:1 compression, correct?
Good to know. Thanks for clarifying.BTW - the EZL should not remain in a "fault" mode. It will store a code that will not go away until manually cleared, but as soon as the EZL sees data that it's happy with again, timing/retard will be normal until the next occurrence of data it isn't happy with.