Jump to content

Recommended Posts

Posted

We have a 2000 Suburban 1500 4x4 that my wife inherited from her mother. We've been fixing all the little things here and there, but we're having an issue with the battery draining. If it sits for more than a day the battery goes dead. We've replaced the battery a couple of times in the last 2-3 years. I've used a multimeter and pulled fuses one at a time, but don't see a constant draw. I've disconnected the VCR and power inverter. It has an aftermarket radio, and I've pulled that fuse. Still no luck. One strange thing I've noticed is that it won't run with the battery charger connected. It will start, but dies as soon as I release the key. As soon as I disconnect the charger after charging it, it starts fine. I'm stumped. Is it possible there is an issue with the alternator and/or voltage regulator? Is there something else I may have missed?

  • 1 year later...
Posted

An update on this. The issue still exists. Alternator tested fine at AutoZone and we've gone through a few batteries, so neither is the issue. It's not a constant or predictable drain. I've let it sit 2-3 weeks and it started fine. Last week I drove it around for a few hours after the battery was fully charged, and the next morning it was dead. 

One odd thing I've noticed. When charging or jumping the battery, it will start and then die if the external power source is connected. I have to charge the battery, disconnect the charger, and then start it. I've never seen that before. I've put a volt meter inline on the positive side and have never seen any abnormal draw. I've randomly pulled fuses but haven't seen any significant or unexpected change in draw. I've pulled fuses and let it sit overnight and still came out to a dead battery. 

I've been to a couple of shops and they can't figure it out. 

This vehicle has sentimental value to my wife so we will never get rid of it. If necessary, I'll start replacing electronics one at a time, and the wiring harness if it comes down to it. But I sure don't want to go down that road if I don't have to. 

  • 1 month later...
Posted

FINAL UPDATE: I bought an Optima Yellow top battery. At over $300, I'll admit it was reluctantly. I started it to make sure all connections were good and shut it off. The Suburban sat untouched for 9 days and it fired right up. I let it run a while to warm up and turned it off. 

It has now sat untouched for over two weeks. This morning it's 42 degrees in SE Texas. The Suburban fired right up with no hesitation. 

I've installed multiple new batteries in it the last several years since we've had this parasitic drain, multiple brands. I have read about the electronics drain on batteries from this model. I don't know if the quality of batteries has declined, or if the Yellow Top is just able to mask or compensate for the issue, but it is fixed enough for me. We'll see how the Optima does over time, but I'm happy. 

Posted

I’ve had two vehicles of different brands drain batteries after two weeks not being driven. Three when the battery was new. The only common theme was aftermarket alarms. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...