Jump to content

Recommended Posts

Posted

Hi all, my 2010 Silverado WT 4.8L with a new battery will go flat in around 4-5 days and will not start without a jump.

If I start it everyday or every other day, no issue.

When charged, the battery reads around 12.34V+/- and with engine running around 14.5-14.7V.

 I did an amperage draw with a multimeter with everything shutoff and I get a 1.4-1.5A draw.

Before I start to pull fuses one by one, is this a normal amp draw for a stripped down vehicle like my WT?

No power anything. Just the ECU.

Your thoughts.

 

 

Posted

Ok let me add this to my topic.

There is an on/off switch in my upper console that is there for a roof beacon light should I chose to utilize it.

I do have the Snow Prep Pkg.

The small amber light in the rocker switch  will go on if I press the switch.

I just noticed that it had been left on.

Would this small light be the cause for the amp drain?

It is so small, it could be un-noticed.

Posted

A vehicle equipped with RPO VYU (Snow Plow Provision Package) or TRW (Provisions For Roof Mounted Lamp) may not have the roof beacon light connected. If the customer were to inadvertently press the roof beacon switch to the on position the roof beacon indicator will illuminate on the switch. If the ignition is turned off and the beacon switch is left on a battery draw (140-180 Ma) will occur. The roof beacon switch indicator will no longer illuminate when the key is turned off however the roof beacon relay is still energized. It's suggested that the roof beacon switch be turned off before turning the ignition off to avoid a battery drain.

Please follow this diagnostic or repair process thoroughly and complete each step. If the condition exhibited is resolved without completing every step, the remaining steps do not need to be performed.

Posted
13 hours ago, tbarn said:

A vehicle equipped with RPO VYU (Snow Plow Provision Package) or TRW (Provisions For Roof Mounted Lamp) may not have the roof beacon light connected. If the customer were to inadvertently press the roof beacon switch to the on position the roof beacon indicator will illuminate on the switch. If the ignition is turned off and the beacon switch is left on a battery draw (140-180 Ma) will occur. The roof beacon switch indicator will no longer illuminate when the key is turned off however the roof beacon relay is still energized. It's suggested that the roof beacon switch be turned off before turning the ignition off to avoid a battery drain.

Please follow this diagnostic or repair process thoroughly and complete each step. If the condition exhibited is resolved without completing every step, the remaining steps do not need to be performed.

Thank you for responding.

I think I understand what you wrote.

Based on your experience, do you feel that a battery draw of 140-280 Ma is enough to drain a new battery in 4-5 days?

I can’t seem to get an answer to this.

Posted
  • The battery run down time will vary depending on the batteries reserve capacity. If the reserve capacity is higher, then the battery run down time may be longer. If the reserve capacity is lower, then the battery run down time may be shorter. The graph below indicates roughly how many days a 690 cold cranking amperage battery with a 110 min. reserve capacity starting at 80 percent state of charge will last with a constant current draw until it reaches 50 percent state of charge. Differences in battery reserve capacity and temperature will affect the results.

Current Drain

Days

25 mA

33

50 mA

16.5

75 mA

11

100 mA

8.25

250 mA

3.3

500 mA

1.65

750 mA

1

1 A

0.8

2 A

0.4

Intermittent Draws

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...