My X5 has been in the shop for a month...

[pepe88]

My mechanic (with 30 years of German car experience) can not figure out what's going on. The truck kept going into failsafe mode but would still drive. He thought the gas pedal was bad so he put a new one in and same problem.

He has Autologic tools and has been working with them on the issue. Here are the faults:

230-E6 Pedal travel sensor, signal
231-E7 " " " , potentiometer 1, signal
232-E8 " " " , " 2, "
229-E5 Comparison, supplies, pedal-travel sensor

Also, when it's hooked up to the reader, and just the key is turned to first position (engine not running), it says the truck is at 920 RPMs.

He says something is all balled up in the brain. It's been a real PITA!

Any clues on this??

Thanks!

[killcrap]

remove the engine computer and check for water damage

[civdiv99]

Connector corrosion is my first bet. Assuming he's unplugged and inspected/cleaned any connections or grounds in this system? The one area the computer doesn't play around is in the comparisons between commanded throttle position and actual from the TPS.

System monitors driver torque request via throttle position, decides and computes among various factors and inputs within a heirarchy what torque it'll give (stab control reduction overrides driver request for more, for example). Computer then commands throttle motor based on it's decision. Multiple feedback of the throttle's actual position serves a number of purposes.

Both the driver's throttle unit and the the throttle position have redundent feedback to monitor throttle position. A disagreement is resolved by logic and the odd-man-out if you will, is ignored. This triggers your faults, but may not necessarily tell you why - but sure narrows it all down.

Why you care: if computer concludes a fault in throttle motor or position is implausible - e.g. it commands one thing but it sees a throttle position that is not plausible for conditions and commanded position, it'll go into shut down. That's one of the few areas that doesn't do limp home, since what it perceives as uncontrolled throttle position can potentially = pepe88 on the evening news. So, while most failures have a fall-back limp home table mode, uncommanded throttle position does not.

Sounds to me like you have a flakey connection forcing the computer to resolve an error but that you still have the required amount of sensor feedpack to avoid the complete "no-go." I think you will find that if the potentiometers for driver throttle and TPS under the hood read within spec for their travel, you really are down to chasing flakey connection before you cry foul on the computer itself. Garbage in = garbage out.