Jump to content

2017 Silverado Low Power, Remote Start not Working, Check Engine light One, where do I start?


jim larson

Recommended Posts

Posted

Well last night I went to remote start engine after a wrestling meet, 40 degrees outside, It did not work, I put the key in and it started; but ran poorly, low power light came on in instrument panel, car was barely running, Check engine light was on. Also the light for spinning tires came on.  Well I made it home, tansmission shift points seemed changed, cruise did not work, low power all the way home. Check engine light stayed on as well as the squigle tire light.  

 

When home I turn car off and waited 5 minuets.  Car started with key,  Check engine light was on all, other lights normal, all else seemed normal, car ran fine, transmission shifted OK, cruise worked.  This morning went to start car with remote,  it did not work, locked car seemed to operator normal, push remote start on fob and lights can on and stayed on with no start of car engaged.  Put key in ignition and car started.  Ran as normal with Check Engine light on.    About 20,000 miles. 

 

I was planning to make a 2000 mile trip starting at 6 am tomorrow morning.  Do I have to take it a dealer first.   I would have no problem driving  my 1966 chevelle as I know how to fix any problems with that engine; but this 2017 silverado 5.3 is a puzzle to me.   Please help if you can.

Posted

If the SES light is on, auto start is disabled by the ECM.
You're under warranty..
Get it to the dealer.
It's just a guessing game otherwise.

Sent from my SM-G965U using Tapatalk

Posted

I had a 17 cc z71 5.3 and had an almost indentical problem and it would go to the dealership and then come back and a few days later it would happen again.  It turned out the active grill shutters were binding.  If the temp dropped overnight they would get stuck and every problem you had I had.  It took that long because it was getting down into the 40s and night and by mid morning the temp was already in the mid 60s

Posted

At 20,000 miles call your dealer and tell them to have the loaner waiting. it's their problem to fix while under warranty, not yours.

 

Last Sunday, 243 miles, 65 degrees I had a no start with mine. No prior warning or check engine light. Truck powered up, all lights in the dash working, but when key was turned to start position all went blank. Battery hot, both keys, and remote start all failed to start the truck. On Star sent me a P129D code and a wrecker. Dealership owner offered to meet me there with a loaner but I waited until Monday.

 

Truck cranked up at dealership Monday morning as hasn't missed a lick since. They kept it for a week and didn't find anything wrong.

 

Isn't technology wonderful ???

  • 1 year later...
Posted

Just bought a used 2019 Silverado three weeks ago, tried starting it with remote start this morning and it tried but wasn’t successful, went to manually start it and it started but now the check engine light came on ugh what a bummer only three weeks out with it with 10k miles come on...has anyone else had this issue? 

Archived

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

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...