I'm with you on #1 and #2... Wiring isn't busted (at least near the connector it looks undamaged) and I'm already making arrangements to get another sensor.
But #3 would be the best option, for all of us. GDE? Can this be disabled in your programming? I am getting to the point where I can TELL when it is working properly... Even without my laptop connected. Now that I just recently found the power supply for the laptop, I'm going to see if that is one of the sensors that the AutoEnginuty can monitor, and actually get some data from it.
Driving home last night, just normal driving, the engine was commanded into 70mph limp mode 3 times without anything approaching a WOT or idle event. So without further investigation, I am forced to conclude that the sensor's data is being checked at more than idle events.
It would make sense if the plausibility was being checked at idle against the turbo MAP, b/c off idle, boost is changing the numbers. BUT, isn't it possible that the computer's air map includes a calculation for air volume based on the static air pressure AND the incoming air volume, that it can correlate against the boost MAP? If the math doesn't fit the range... Limp. Since I have already replaced the boost MAP with no effect, that is working properly. I haven't replaced the MAF sensor... But with it unplugged, the performance still suffers randomly. With this Mercedes MAP unplugged... Performance is markedly better, but I am limited to 40mph limp mode.
Logically, that thing has to be passing SOMETHING to the ECU during driving, which annoyed it into the 70mph limp mode last night. The unpredictability of the CRD feeling "heavy" under the same amount of throttle agrees.
Unless of course... Something ELSE that doesn't fail bad enough to throw a code has failed. It wouldn't surprise me.
