Jump to content

Plowing with a '13 2500HD 6.0L electrical charging

stallion81
 Share

Recommended Posts

casey.mikl Enthusiast

casey.mikl

Posted
Posted

Upgrading the alternator to battery as well as ground strap wouldn’t hurt, bigger wire = more current. It will make a slight difference, hence why car audio guys upgrade them all the time to thicker wires. I have the wiring to do it all in mine, just don’t really feel like tearing into it. If anything, maybe hook the plow wiring to the second battery, and let it draw from that instead of the main battery.


Sent from my iPhone using Tapatalk

aseibel Senior Enthusiast

aseibel

Posted
Posted
On 12/17/2017 at 4:44 AM, stallion81 said:

1) Alternator charge wire. Mine is probably 6 gauge. Go to a high quality 4?

 

3) Plow supply leads. These were obviously hooked to the main as I only had 1 battery on install. Should I attempt to move those to the 2nd battery? I'm unsure I have the length in the harness, but it would be easy to find out. Would it make a difference since the batteries are in parallel anyway?

Thanks for your time. 

1) I don't know that this wire really limits the output amperage. It can't hurt to make it bigger, but i question whether it actually changes anything.

 

3) don't waste your time moving the plow power cables. since your battery terminals are directly connected already- it makes absolutely no difference which end the plow is connected to. Your two batteries now operate as one battery with double the amp-hours.

sdeeter19555 Senior Enthusiast

sdeeter19555

Posted
Posted

Upgrading the alternator wire can improve performance, but it think that 175a fuse is probably more restrictive than the wire from the alternator.

I upgraded the wire on my last Dodge Cummins (160A alt), it was impressive the difference. The alternator could "catch up" much faster, voltage would come back to normal after a hard draw in 1/3 less time. That was the only place I didn't use regular automotive wiring, I used high strand count stereo power wire for that five foot run. I rarely use the winch on this truck and have two batteries, so I've never bothered to upgrade this Silverado.

Steve
2012 2500hd 6.0l

  • 3 years later...
john neu New Member

john neu

Posted
Posted

My 2013 chevy silverado 2500hd came from the factory with the plow prep package and I know this because I purchased it used and the window sticker came with the truck but there is no second battery and no wiring why is this thanks John.

davester Senior Enthusiast

davester

Posted
Posted

maybe you got the wrong build sheet (not for your truck), or the vin has been swapped to another vehicle (ie, stolen or rebuilt vehicle)?

jhplak325 Enthusiast

jhplak325

Posted
Posted
On 5/30/2021 at 11:05 PM, john neu said:

My 2013 chevy silverado 2500hd came from the factory with the plow prep package and I know this because I purchased it used and the window sticker came with the truck but there is no second battery and no wiring why is this thanks John.

Dual batteries on a gas engine is not part of the plow prep package. 

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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...