Jump to content

2015 Silverado Won't Start!

enroberts

By enroberts
in Troubleshooting & Recalls

 Share

Recommended Posts

enroberts Enthusiast

enroberts

Posted
  • Author
Posted
2 hours ago, tbarn said:

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

Proper scan?  You mean like BCM and ECM scan?  My ECM isn't doing much of anything because nothing can connect to it. 

  • Replies 33
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

tbarn
tbarn

Not really wasting time. You have to get to the bottom of the issue. Is the doctor wasting time diagnosing? This thing ain't no 78 Cheyene. They are complicated.

enroberts
enroberts

For those interested, my ECM failed. Replaced it at the dealer today and had it reprogrammed. Back in business!   Sounds like an expensive trip to the dealer for them to waste a bunch of t

Posted Images

SS502 Senior Enthusiast

SS502

Posted
Posted
5 minutes ago, enroberts said:

No, factory gauges. 

The two on the left are factory? Not familiar with them...

60924485-3A0F-4BE2-8B1A-09B9790E84C4.jpeg

enroberts Enthusiast

enroberts

Posted
  • Author
Posted
Just now, SS502 said:

The two on the left are factory? Not familiar with them...

60924485-3A0F-4BE2-8B1A-09B9790E84C4.jpeg

Oh, sorry, those are definitely not factory lol. I actually removed them today. 

enroberts Enthusiast

enroberts

Posted
  • Author
Posted

I just ordered a new starter, positive battery cable, and negative battery cable. Amazon will have it to me by Wednesday. I'll throw it all on and see what happens. If still no start, I'll put it on my trailer and tow it to the dealer for a scan and see if they have an issue connecting to the ECM too. As of now, I'm leaning towards a failed ECM. 

tbarn Senior Enthusiast

tbarn

Posted
Posted

Proper scan with proper equipment like GM's GDS2 and an MDI . Or other high end scanner.

tbarn Senior Enthusiast

tbarn

Posted
Posted (edited)

You have to know which modules are communicating and which are not. Then check power and ground at them. Then if they have power and ground you next check the networks. It's a process and can be fairly quick or  take a long time. Clearly, if the PCM does not have power or ground, you don't need to check the onstar module. One tip, check between the battery and right front fender for rodent damage. It's a common place for them to chew wiring. One more thing, any module on the high speed circuit can take the whole circuit down. The Onstar module is a common module to do just that. You can't just unplug a module to test. You have to jump the network circuits.

Edited by tbarn
enroberts Enthusiast

enroberts

Posted
  • Author
Posted
13 minutes ago, tbarn said:

Proper scan with proper equipment like GM's GDS2 and an MDI . Or other high end scanner.

Makes sense. If the cables/starter don't resolve it, that will be my next step at the dealer. 

enroberts Enthusiast

enroberts

Posted
  • Author
Posted
3 minutes ago, tbarn said:

You have to know which modules are communicating and which are not. Then check power and ground at them. Then if they have power and ground you next check the networks. It's a process and can be fairly quick or  take a long time. Clearly, if the PCM does not have power or ground, you don't need to check the onstar module. One tip, check between the battery and right front fender for rodent damage. It's a common place for them to chew wiring. One more thing, any module on the high speed circuit can take the whole circuit down. The Onstar module is a common module to do just that. You can't just unplug a module to test. You have to jump the network circuits.

Sounds like an expensive trip to the dealer for them to waste a bunch of time combing through module after module. 

tbarn Senior Enthusiast

tbarn

Posted
Posted

Not really wasting time. You have to get to the bottom of the issue. Is the doctor wasting time diagnosing? This thing ain't no 78 Cheyene. They are complicated.

  • Like 1
Supreme Pizza Senior Enthusiast

Supreme Pizza

Posted
Posted (edited)
59 minutes ago, enroberts said:

I just ordered a new starter,

 

It is possible for the starter to cause electrical problems, but I think it would probably have to short out internally, combined with a simultaneous solenoid failure resulting in a "stuck on" position. This would kill you battery pretty quickly. If you want eliminate the starter as a possible cause, you could disconnect the wires from the starter, and turn the ignition on. If everything works perfectly on the dash, reconnect the starter and check the dash again. You can also bench test the starter by using a car battery and jumper cables. Or you can test the stater in the vehicle by crossing the terminals with a screw driver.  

Edited by starman8tdc
  • 2 weeks later...
enroberts Enthusiast

enroberts

Posted
  • Author
Posted

For those interested, my ECM failed. Replaced it at the dealer today and had it reprogrammed. Back in business!

 

On 12/15/2018 at 10:51 PM, tbarn said:

You have to know which modules are communicating and which are not. Then check power and ground at them. Then if they have power and ground you next check the networks. It's a process and can be fairly quick or  take a long time. Clearly, if the PCM does not have power or ground, you don't need to check the onstar module. One tip, check between the battery and right front fender for rodent damage. It's a common place for them to chew wiring. One more thing, any module on the high speed circuit can take the whole circuit down. The Onstar module is a common module to do just that. You can't just unplug a module to test. You have to jump the network circuits.

Sounds like an expensive trip to the dealer for them to waste a bunch of time combing through module after module. 

  • Like 1
Hillwood Enthusiast

Hillwood

Posted
Posted

I glad you got your truck fixed...
Happy New year.

Sent from my SM-G965U using Tapatalk

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

    • 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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...