Jump to content

Recommended Posts

Posted

Hey,

 

Iv seen a bunch of posts about setting up a dual battery system and what to use, and i understand all that.

Problem is i keep seeing articles about standard relay style isolators and smart isolators (VSR) not working if you have a "smart alternator" because of the fluctuations from the alternator based on driving conditions, and therefore have to go and spend a load on a DC-DC charger. $50 vs $300

 

Anyone have any issues with their standard relay style or smart isolators on their dual battery setup?

 

Articles below,

https://www.12voltplanet.co.uk/auxiliary-battery-charging-in-vehicles-with-smart-alternators.html

https://www.redarc.com.au/faq-tech-tips/new-vehicles-technology-can-affect-dual-battery-systems-charging-performanc

Posted

Not sure many here have donethe dual battery upgrade or even have it from factory. I've been contemplating it tho.just can't see taxing the factory system.

Posted

I have dual batteries and a isolator. It is wired with a small switch and a small relay. I have it so on a normal day the factory acc wire powers it and two batteries start truck. When truck is of it is disconnected. The switch is if I try to start truck and factory battery is dead then the acc wire is dead. So small wire from the 2nd battery powers isolator and starts truck. 

I have used this one day all day. Every time I stopped the truck it wouldn't start. Push button and truck starts right up. After that day the truck charged the factory batter enough to be ok. But I said screw it and ordered a yellow top. 

Issue us the smart alternator and more importantly the bcm program only sees the factory battery till the the key is turned then it tries to play catch up. Real issue I hear most is if one battery dies it will take out the other or the alternator will be in higher amp output to play catch up. 

Posted

I had dual batteries on an old truck, that I just wired up in parallel. No real issues, but that tech was much different than the current one, so I can't give you any current info. I have not installed a second battery on my new truck as my plow doesn't strain the electrical system too much.

 

I would recommend you check out this forum for plow guys, there are several threads about installing dual batteries on there. Caution, the forum is full of a bunch of grumpy old-timers!

 

https://www.plowsite.com/forums/chevy-trucks.6/

 

Posted

I had 2 batteries left over from my old truck with a sound system so I threw it under my hood just for the hell of it. I put a 200a fuse between the positive line and ran it along the positive line that comes across the firewall at the top. For ground I ran it on the same path back to the OEM battery on the passenger side. I just had to buy the battery wedge and bolt from ebay as I have a 14 with the battery tray already installed it just doesn't come with the hold down bolt or wedge. I used 4ga OFC stranded wire, the same you would use for amplifiers. I also ran the positive wire through the OEM hall effect sensor so it didn't mess with the charging system by bypassing it. You can only fit at most a 2ga wire through the sensor with the OEM wires in there as well so be advised of that.

Archived

This topic is now archived and is closed to further replies.

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