5.2L V8 engine runs on too high RPM while 'parking' after battery was empty
Hey guys,
yesterday was on of them days, which I actually should curse - battery was completely empty. So, I reloaded the battery over night. Today morning I wasn't really impressed when the engine turns on 2.000 RPM while the shift was on 'Parking'. It's usual that the 318 V8 engine gets warmed up. But even after I've been driven 30 minutes around town and pushed him on the German highway... still the same - while the gear is on 'parking' 2.000 RPM...usually the RPM range is about 1.000 RPM or less.
Does anybody have had the same problem? Any experiences?
How can I fix this problem?! Or is it a problem?

Thanks in advance
Kowalski - 97 Dodge Dakota with 318 V8
yesterday was on of them days, which I actually should curse - battery was completely empty. So, I reloaded the battery over night. Today morning I wasn't really impressed when the engine turns on 2.000 RPM while the shift was on 'Parking'. It's usual that the 318 V8 engine gets warmed up. But even after I've been driven 30 minutes around town and pushed him on the German highway... still the same - while the gear is on 'parking' 2.000 RPM...usually the RPM range is about 1.000 RPM or less.
Does anybody have had the same problem? Any experiences?
How can I fix this problem?! Or is it a problem?

Thanks in advance
Kowalski - 97 Dodge Dakota with 318 V8
Do you have any way to read your OBD2 data? Sounds like the coolant temp sensor might not be working, causing it to stick in fast idle to warm up. I'd try unhooking the battery negative cable and stepping on the brakes (to drain residual power in the system through brake lights) and then plugging it all back in, then turning it on and see if it will warm up and get off fast idle without you touching the gas at all. Maybe the ECU just freaked out and needs to be reset.
If you've got a Palm device I'd recommend getting a pocket logger (www.pocketlogger.com) so you can read/reset CELs as well as do some data logging of the various sensors to see if anything is obviously acting up.
If you've got a Palm device I'd recommend getting a pocket logger (www.pocketlogger.com) so you can read/reset CELs as well as do some data logging of the various sensors to see if anything is obviously acting up.



problem solved