Jump to content

Recommended Posts

Posted
37 minutes ago, BlaineBug said:

What day did you all experience your issues?  Recently?

Today. Vehicle updated yesterday, drove all day with no issues. Went to a friend's house, used the app to start it while talking about the truck. Drive home. Slept. And today a dash full of errors.

Posted
23 minutes ago, Hill CountryTrailBoss said:

Today. Vehicle updated yesterday, drove all day with no issues. Went to a friend's house, used the app to start it while talking about the truck. Drive home. Slept. And today a dash full of errors.

How was it updated?  TSB or recall at the dealership?

Posted

Someone was commenting on that in my separate issue's thread topic, about "OTA" over the air updates.  I was under the impression that these updates were for the infotainment apps only.  If not, why couldn't programming for recalls be done without having to come in to the dealer?

Posted
4 minutes ago, BlaineBug said:

Someone was commenting on that in my separate issue's thread topic, about "OTA" over the air updates.  I was under the impression that these updates were for the infotainment apps only.  If not, why couldn't programming for recalls be done without having to come in to the dealer?

GM requires a Battery charger on the battery while performing some recalls or TSBs to keep the charge up so most of the Control Modules require a dealer visit. The only OTA updates I have seen for the trucks is the infotainment and Onstar.

Posted (edited)
22 minutes ago, Rocz3cqg said:

GM requires a Battery charger on the battery while performing some recalls or TSBs to keep the charge up so most of the Control Modules require a dealer visit. The only OTA updates I have seen for the trucks is the infotainment and Onstar.

That's what I was thinking.  Stuff like that can download and then install later, like on a "personal computer."  Most of the engine computer updates are very, very specific in regard to what to do and what not to do.  I'd be hard pressed that they would be willing to risk it on ordinary residential wireless internet for things like that.

I wonder what the average file size is for a recall regarding some change to the engine computer programming.

Edited by BlaineBug
Posted (edited)

My truck did it last night. Started via remote start and got in and found service esc, service parking brake, and got a diagnostic email saying the exhaust system needs service. The check engine light has come on and has remained on. 1200 miles on the truck and the dealer can’t get it in for two weeks. I should add that I started it via the fob and not the app. 

Edited by BFD25
Posted

I shared the TSB from Shawn O’Leary and the Service Rep had it too. They are updating software now. This affected those of us who had recall done in Dec/Jan. 
update should fix it. 
 

I’ll do a remote start after update and let u know what happens. 
 

thank you all for your help!!!!

Posted

A quick update from me also. I bought my truck 3 weeks ago brand new. Apparently there were 4 open recalls the dealer failed to address/update software. I was able to get an appointment at a different dealer for this Friday. 

Posted
11 minutes ago, RocksRock said:

I shared the TSB from Shawn O’Leary and the Service Rep had it too. They are updating software now. This affected those of us who had recall done in Dec/Jan. 
update should fix it. 
 

I’ll do a remote start after update and let u know what happens. 
 

thank you all for your help!!!!

Does this at all relate to the Yukon/Tahoe/Suburban/Escalade crowd?

Posted (edited)
13 minutes ago, RocksRock said:

I’m not sure if it’s just a truck Silverado issue??

A couple of us are experiencing issues with 2019s.  Stabilitrac light, no power steering, most gauges inoperable, no transmission gear engagement.

Edited by BlaineBug
Posted (edited)

Update from my situation.

 

Scheduled a service appointment for 8am this morning. Pulled up at 7:55 and the service managers first question was about remote start.

 

She said there is an issue with remote start and not to use the app or the fob to remote start.

I checked the truck in, tossed my stuff into the 2019 Silverado Custom they set me up with as a loaner and headed home. 

 

About an hour later I received text alerts about the need to service the engine and transmission systems. Apparently the tech set off all sorts of shit while clearing codes and testing.

 

They found a brake system sensor that  "had gnawed wiring as if a rodent has gotten to it". Sensor won't  be available for 5-7 days.

 

So my brand new truck, with 230 miles on it will spend the next week at the shop while I drive their loaner for work. 

 

Not happy, but not quite pissed yet. At least they didn't put me in a Smurf Blue PT Cruiser like the Dodge dealership did years back. Drop off a 1 ton and leave in a go cart. 

 

Will update after I pick the truck up and speak with the manager and tech.

 

Edited by Hill CountryTrailBoss
Spelling be hard yo

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

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