RE: dead batt causes odd problem

From: Stlaurent Mr Steven (STLAURENTS@MCTSSA.USMC.MIL)
Date: Tue Sep 03 2002 - 09:18:48 EDT


As you described, that is usually what happens when the battery dipping into
the 9.5 or 9.0 volt range.

I would opt to replace the battery if the alternator is still good. Do you
have any aftermarket items that draws heavy currents?

--------------------------------------
Steven St.Laurent
C4i System Engineer
C4i Engineering Branch, PSD, MCTSSA
MARCORSYSCOM, U.S. Marine Corps
Office (760) 725-2506 (DSN Prefix: 365)
"Never be content with somebody else definition
of you. Instead, define yourself by your own beliefs,
your own truths, your own understanding of who
you are. Never be content until you are happy with
 the unique person GOD has created you to be."

-----Original Message-----
From: Carter, Brian [mailto:brian.carter@texian.org]
Sent: Monday, September 02, 2002 9:49 PM
To: dml@dakota-truck.net
Subject: DML: dead batt causes odd problem

A week ago, my Dak ('00 QC 4x4 4.7) started acting very weird. I could
turn it over, it would catch, and then die immediately. It seemed to be
searching for idle, going to low (400 rpm) and then would die. If I gave
it a little gas it would last a few more seconds.

There was no error either. I did a tune-up about 8 weeks ago, and I
hadn't noticed any deterioration prior to this.

If I kept my foot on the pedal I could keep it alive and stabilize it at
around 1000rpm. I could redline it without a problem, so I didn't see
how it could be fuel delivery.

I figured it was something that would require a computer to figure out.
I go to Mexico all the time, so I thought I had blocked a sensor, or
fouled something that was keeping the ECM from getting the right data.
Anyway, I desperately needed the truck the next day (to go to
Monterrey), so I gave up and took it to the dealer.

They came back saying that the TB was fouled and that the battery was
weak. They did a fuel induction service (cleaned the injectors and TB),
which it probably needed; but the real problem was the battery. Even
after the fuel induction service, it still searched for idle (although
it would run) - I swapped in the new battery and voila...perfect.

The low voltage (around 9) was causing the computer to loose its memory
(the search for idle), and kept resetting the code, so no engine code
appeared. I felt real stupid, but it really didn't act like any dead
battery I ever saw.

--BTC



This archive was generated by hypermail 2b29 : Fri Jun 20 2003 - 12:05:19 EDT