Jump to content

Recommended Posts

Posted (edited)

2018 Silverado 2500 LT 1,300 miles

 

truck during the day shows volts at 12.5. I can turn on ac full blast, radio and defroster and colts stay at 12.5 all day. When driving volts stay at 12.5 when I’m rolling and foot of gas mpg gauge goes up to 99mpg then will charge at 14volts as soon as I hit the gas bolts drop to 12.5. And night when headlights turn on truck will charge at 14 volts. First two times truck was taken to dealer they said nothing is wrong now the third time they tell me that’s not normal and change alternator and never fixed the problem still in the shop. Anyone have same issues or volts stay around 13.2-14.5 volts all day and night

Edited by Leone1662
Posted

the charging cycle is temperature related . a cold battery does not charge very well, below 45 degrees mine stays at 14 when it gets to 60 it will stay just under 14 and when it get to 70 and above it will always be just above the 12 volt range. i think gm does this because the hotter the temperature the faster the chemical reaction is in the battery which makes them sulfate and boil of the chemical in the battery which shortens the life of the battery

Posted

Idk about that where I live it hasn’t been above 60 and even if it’s 50 degrees out truck sits at 12.5 volts

Posted

The system is actually designed to work like that and has been since around 2005.  Search back through these forums or just Google something like "GM charging system".  You can find very in-depth explanations of how the system works.  But under normal operation you can see anywhere between 12-14.4 Volts on the gauge.

Posted
The system is actually designed to work like that and has been since around 2005.  Search back through these forums or just Google something like "GM charging system".  You can find very in-depth explanations of how the system works.  But under normal operation you can see anywhere between 12-14.4 Volts on the gauge.
I've seen as low as 13.8vdc and as high as 15.2vdc, but never below 13.8vdc (which is the voltage of a "12 volt" lead acid battery).

That's looking at it through a stand alone monitor that is reporting the voltage the ECM/BCM is reporting. That's not a VOM...

2012 2500hd 6.0l CCSB 4wd



Posted

I was going to ask this same question today. I have a 2018 with 1500 miles and noticed the voltage guage is anywhere between 12.5 and 14v and it is constantly fluctuating. I've never seen/noticed this before in any of my other vehicles.

Posted

This was common in the Dodge Cummins-powered trucks when they started because of the cycling of the grid heaters...Dodge answered this customer complaint by make the in-dash voltage gauge read 14vdc all the time. That's right, they made the gauge useless...

Same with the oil pressure...it was a dummy gauge that read yes/no from a pressure switch (not a pressure sensor) and made up the reading based on engine rpm and temperature...what's worse is that the oil pressure gauge would read normal oil pressure for three minutes (when in reality the engine had zero oil pressure) before it would show a problem.

Essentially the Dodge dash gauges were glorified idiot lights...

Point being, I could see GM doing the same thing with too many customer complaints!

2012 2500hd 6.0l CCSB 4wd



Posted

Charging System Operation
The purpose of the charging system is to maintain the battery charge and vehicle loads. There are 6 modes of operation and they include:
Battery Sulfation Mode

Charge Mode

Fuel Economy Mode

Headlamp Mode

Start Up Mode

Voltage Reduction Mode
The engine control module (ECM) controls the generator through the generator turn on signal. It monitors the generator performance though the generator field duty cycle signal circuit. The signal is a 5-volt pulse width modulation (PWM) signal of 128 Hz with a duty cycle of 0-100 percent. Normal duty cycle is between 5-95 percent. Between 0-5 percent and 95-100 percent are for diagnostic purposes. The generator provides a feedback signal of the generator voltage output through the generator field duty cycle signal circuit to the ECM. This information is sent to the body control module (BCM). The signal is a 5-volt PWM signal of 128 Hz with a duty cycle of 0-100 percent. Normal duty cycle is between 5-99 percent. Between 0-5 percent and 100 percent are for diagnostic purposes.

 

10% duty cycle = 11V

90% duty cycle = 15.5V

 

Startup Mode should be 14.3V for 30 seconds.

Headlamp mode will be 13.9-14.5V (I've seen this delayed coming out of lower voltages).

 

 

Lower voltage means your battery doesn't need to charge. If you are constantly sitting at 14.4V+ with hours of driving your battery is probably starting to go bad.

Posted

I had a 2016 with 38,678miles and charged all day everyday around 13.2-14.5 never had a battery issue. Now this one nothing different besides it’s an 2018Lt and the other was a 2016 Wt both had one battery and 220amp alternatorthe 18 during the day it’s at 12.5 and at night is 14.5. Can’t tell me battery is always charged during the day. Truck has 1,400 miles on it

  • 5 years later...
Posted

I have a 16 sierra denali. Been chasing a battery drain for several months. I've unwired everyrhing I have added to the truck. Replaced battery and alternator couple times. No results. I noticed it was only not charging properly during day time. My alternator will fluctuate from 11.5v to 14.5v. But most often less than 12v. Covered sensor and no more issues. Now what could be shorted or causing the issue? I think it would be easier to identify if it was happening during night mode. 

 

Thanks in advance

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...