Jump to content

Recommended Posts

Posted

Hey all.  Hoping for some help!  Started my truck this morning for the first time in about a week. When I pulled out of my driveway the DIC told me to service pretty much every system in the truck (trailer brakes...no trailer attached, Stabilitrak, power steering...drive with care, 4x4, etc) and the steering wheel became ridiculously heavy with speed and tach both at 0 while moving/running.  I threw a brand new battery in it but still nothing.  The video below is AFTER the new battery was installed.   It's like the ECM isn't getting 12v or ground. The fuel gauge shows empty, which it's not, the trans isn't showing what gear it's in, and there's absolutely no cranking. All fuses are fine.

 

 

Posted

Electrical problem.

Any chance mice got to it?

Chewed wires?

 

:)

Posted

Clean and tighten battery ground at engine block.. Sounds like a low voltage concern.. clean and tighten ground wires fom battery to engine block , battery to fuse block.. don't over look any.

Sent from my SM-G965U using Tapatalk

Posted
6 minutes ago, Hillwood said:

Clean and tighten battery ground at engine block.. Sounds like a low voltage concern.. clean and tighten ground wires fom battery to engine block , battery to fuse block.. don't over look any.

Sent from my SM-G965U using Tapatalk
 

Good idea!!

Check all grounds.

:)

Posted (edited)

Hmm. That's a tough one. 

 

You could have an internal alternator fault. You might try disconnecting it, to see if that helps. 

 

To check your ground, you can take a small wire and attach it to the negative battery terminal (not the cable, but the actual terminal itself), with both cables hooked up to the battery. Then connect that small wire to the body and the engine. Then start using electrical stuff, like the starter, head lights, etc. If the small wire gets warm or hot, or the electrical components work properly, then you definitely have a ground issue. I would also grab a volt meter, and start probing stuff. If you put the negative probe on the negative battery terminal, and probe the brake light or headlights (when they are tuned on), are you getting 12+? If so, is it constant or does the voltage wander around? You might also look at any fuseable links and any main power relays. You can swap relays around to test them. 

 

Wiring is not much fun.... 

 

 

 

 

f492ab0a97de7483630f4aba5c13105b.jpg

 

 

Edited by starman8tdc
Posted

Thanks for all the quick replies!  I was just able to get my code reader to finally connect and pull codes.  The only code is U0100 which is Lost Communication With ECM/PCM "A"

Posted

U codes are communication codes... LOW VOLTAGE LOSS OF COMMUNICATION!

Sent from my SM-G965U using Tapatalk

Posted

If everything electrical looks good, I would remove the ECU and "smell it". Does it produce an odor of burnt electronics? Is it wet? Any signs of heat damage to the outer case? 

 

Also, you could clean the connections to the ECU, and maybe throw some dialectic grease at it. 

 

 

Posted (edited)

 

      I hate to say it, but you might be looking at a diagnostic shop. Running low on options. 

 

      If you go down that path, try to find one that will guarantee a diagnosis without exceeding 1 hour ($100-$150). Most won't, but some will. 

 

      Some repair shops will charge you $900 in diagnostics, and then say it needs a $1200 part. Then $2100 later, the problem is still there. Then they say: Oh, well that part needed to be replaced, but there must be another part that is bad as well. We will put our diagnostic guys back on it (after you pay this first bill). 

 

     I have seen people spend thousands on diagnostics and parts, with no remedy. 

 

     Not trying to scare you, just trying to caution you.

 

     Call 5 or 6 shops and talk to them a bit before you choose one. 

 

     If I can think of any other tests you could try, I will post it. 

 

     Good luck. 

 

 

P.S.

 

https://repairpal.com/obd-ii-code-u0100-lost-communication-with-ecm-pcm-a

 

https://www.obd-codes.com/u0100

Edited by starman8tdc
Posted

I’m pretty sure it has nothing to do with it but those gauges I saw in the video, are they newly installed? Yeah grasping at straws but as mentioned, this could get ugly.

Posted

I will guarantee you there a many more codes in the system. Need a proper scan to start with.

Posted
4 hours ago, SS502 said:

I’m pretty sure it has nothing to do with it but those gauges I saw in the video, are they newly installed? Yeah grasping at straws but as mentioned, this could get ugly.

No, factory gauges. 

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

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

  • Popular Contributors

×
×
  • Create New...