Jump to content

2018 SLT Intermittent remote start issue

RPOD71
 Share

Recommended Posts

RPOD71 Enthusiast

RPOD71

Posted
Posted (edited)

Back in July, I traded in my 14 Silverado for an 18 SLT premium plus.  Been more than happy with the upgrade.

 

Since it's cold, I've been using the remote start when needed.  Noticed the issue a while back when I tried using the fob walking to my truck after work.  Lights flashed and nothing.  I dismissed it at that time.  Worked via fob or app for a while and then it didn't again.  So I took it to the dealer.  They couldn't replicate it but did do an update that addressed the crank position sensor.

 

A week or so of starts remotely worked, then it didn't again.  Most recent failure was this morning.  If it fails via the app it gives error 220_99.  If I try again with the app it is 220_12.  The 220_12 (I think) is the same you get if you remote started twice and tried a 3rd time without using the key.

 

One recent failure via the fob (after the dealer), I was in my garage and I heard it.  It sounded like you just bumped the ignition.  This will be new info when I go back to the dealer, but I'm wondering if someone else had this issue? 

 

 

Screenshot_20181209-073147.jpg

Screenshot_20181209-073156.jpg

Edited by RPOD71
JimCost2014 Senior Enthusiast

JimCost2014

Posted
Posted
1 hour ago, RPOD71 said:

Back in July, I traded in my 14 Silverado for an 18 SLT premium plus.  Been more than happy with the upgrade.

 

Since it's cold, I've been using the remote start when needed.  Noticed the issue a while back when I tried using the fob walking to my truck after work.  Lights flashed and nothing.  I dismissed it at that time.  Worked via fob or app for a while and then it didn't again.  So I took it to the dealer.  They couldn't replicate it but did do an update that addressed the crank position sensor.

 

A week or so of starts remotely worked, then it didn't again.  Most recent failure was this morning.  If it fails via the app it gives error 220_99.  If I try again with the app it is 220_12.  The 220_12 (I think) is the same you get if you remote started twice and tried a 3rd time without using the key.

 

One recent failure via the fob (after the dealer), I was in my garage and I heard it.  It sounded like you just bumped the ignition.  This will be new info when I go back to the dealer, but I'm wondering if someone else had this issue? 

 

 

Screenshot_20181209-073147.jpg

Screenshot_20181209-073156.jpg

I would think you are throwing a code. Remote start will not work, when there is something not right. That is how I found out the CEL would be on in my 16, no remote start, and the CEL would be on shortly.

RPOD71 Enthusiast

RPOD71

Posted
  • Author
Posted

No CEL, no code.  The dealer plugged into OBD upon arrival and me explaining the problem.  Said no code for anything.

 

When I scheduled the appt, I asked if a failure to start remotely would leave a code, they said only if the CEL is on.

1SLOW1500 Senior Enthusiast

1SLOW1500

Posted
Posted
3 hours ago, RPOD71 said:

No CEL, no code.  The dealer plugged into OBD upon arrival and me explaining the problem.  Said no code for anything.

 

When I scheduled the appt, I asked if a failure to start remotely would leave a code, they said only if the CEL is on.

Lies all dirty lies. There is always a history log that will pull with codes. I still have temp, history, permanent, and even status codes. In fact I had two pages of them with NO sel  light on dash. Mine are everything from a unplugged sensor to fuses blown/removed, fuel trims, baro, map,cats/o2s, speakers and sensor voltage out of range.  

First I would load test the battery. It is usually free then I would sit in car and remote start it. Then I would go threw the sensors that stop remote starting. Like hood switch. 

RPOD71 Enthusiast

RPOD71

Posted
  • Author
Posted

I've read that elsewhere on here that it will store the info without cel.  How do you tell the service advisors that you know it does when they and the mechanic tell you otherwise, and they are the "experts"?

 

 

neokonig Enthusiast

neokonig

Posted
Posted (edited)

I seem to remember an old thread on here, I think it was that you have to manually start it every nth time (not sure what number n equals). As in, you can't remote app start it a bunch of times in a row without a few manual ignition cycles. Was some software limitation they implemented.  This might be different, as I thought the key fob counted as a manual start, but something to consider. 

Edited by neokonig
  • 2 weeks later...
RPOD71 Enthusiast

RPOD71

Posted
  • Author
Posted
On 12/10/2018 at 9:19 AM, neokonig said:

 

So I took it in and again..  nothing.  I left it overnight so it sits for 12+ hours, in the cold, like it does for me at home or at work.

 

They said they can't fix something they can't replicate, started numerous times for them.   No codes, no history (because no CEL).

 

Frustrating.  

 

Going to pick it up and ask to see what was done other than starting it remotely.  Would like to see my battery listed as something checked as well as whatever switches would keep it from starting.

14cris Enthusiast

14cris

Posted
Posted

Mine did this too, the other day to be exact
It was the post on the battery had the slightest of build up on them


Sent from my iPhone using Tapatalk

RPOD71 Enthusiast

RPOD71

Posted
  • Author
Posted

They claimed the load tested the battery and checked all components related to the remote start.  I don't believe they did.  The invoice just stated they hooked up the tech2 and tried to recreate the problem, found no codes, etc.  I would think it would have the other stuff listed to keep from chasing their tails for the next time I brought it in.

 

I'll check the battery myself, but if it happens again, I'm going to a different dealer.  They claim my OnStar error codes are "probably" from a bad signal from the satellite.  They can't even give me an exact reason for the codes.

2017Darkness Enthusiast

2017Darkness

Posted
Posted

Stop using the app and use the key fob only... I have had 2 of these trucks with the app capability and get random remote start failures from time to time.

  • 2 months later...
MoonJuice New Member

MoonJuice

Posted
Posted

Bump

Having same issue, only 300 miles on truck and a week old (bought new last week, 2018 left over).
Does it randomly with remote start (witnessed it walking towards the truck) and when using the key.

 

Anyone find a solution?

  • 5 months later...
Alamo New Member

Alamo

Posted
Posted

My 2018 GMC DENALI 

intermittently starts via the remote using my key fob.  If I start it via my key in the ignition and then immediately try to remote start it soon after it starts once or twice and then nothing other than my lights blink once.  It seems like this issue began right after I had opened my hood to check fluid levels.  The hood is shut completely and I have no codes or service indicator.  Also it's not in the valet mode.  I call my dealer and they said they never heard of this happening.

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

  • 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   2 Members, 0 Anonymous, 2,875 Guests (See full list)

  • Latest Articles

  • Posts

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...