Jump to content

Recommended Posts

Posted

On the GM website this Program/Recall is listed as incomplete on my newly acquired 2008 Silverado. Anyone know what it is and what is involved in fixing it?

Posted (edited)

Reprograming of the ECM.

 

The customer letter:

May 2015

 

Dear General Motors Customer:

 

This notice applies to your vehicle, VIN: ______________________________________

 

This notice is sent to inform you that General Motors is conducting a voluntary emission recall that includes your 2008 Chevrolet Avalanche, Silverado, Suburban, or Tahoe, or GMC Sierra, Yukon, or Yukon XL.

 

Reason For This Recall: The design of the fuel control system did not adequately control carbon monoxide emissions under certain operating conditions.

 

What Will Be Done: Your GM dealer will reprogram the engine control module with a modified fuel control calibration. This service will be performed for you at no charge.

 

What You Should Do: Please contact your GM dealer as soon as possible to arrange a service date. Instructions for making this correction have been sent to your dealer. Please ask your dealer if you wish to know how much time will be needed to schedule, process, and repair your vehicle.

 

Edited by 15HDriver
Posted

15H driver, thank you very much. Dealer said I could wait while they do the repair.

Posted

Update: After the recall was performed the engine is running rough. I'm hoping it is just an issue with adaptions in the ECU. Anyone else experience this?

Posted

Hello Blackhawk36,

 

While I am happy to see that your were able to get your recall addressed, I’m sorry to hear that your engine is running rough after you got it performed. I would be happy to reach out to your involved dealer on your behalf to schedule an appointment for service to address your new concerns. If this is something that you would like for me to do, please send your VIN, mileage, contact information, and dealership of choice so that we can further assist.

 

Have a great day,

 

Blair E.

Chevrolet Customer Care

Posted

My sister's Cruze got a similar recall notice. I told her not to bring it in because all I could think is that they would lean it out a little or something. All I know is that it is running fine now. I figure nothing good could come from messing with it.

Posted (edited)

Update: After the recall was performed the engine is running rough. I'm hoping it is just an issue with adaptions in the ECU. Anyone else experience this?

I say it all the time.....Stay away from dealership service departments, they usually make things worse and create more problems because most have no idea what they are doing. Sorry to hear this happened to you. You should not go there without issues and leave with your truck not running properly because of those know nothing tech's!

 

Do you have any idea what they did to your truck? They need to make it right no matter what needs to be done. Sad because now your only option is to take it back in to have the clown who caused this issue fix it.

 

Good luck, hope it gets back to running normal for you.

 

 

Sent from my crappy iPhone 6

using Tapatalk

Edited by BlackZ71Silverado
  • 6 years later...
Posted
On 7/31/2015 at 9:28 AM, Blackhawk36 said:

Update: After the recall was performed the engine is running rough. I'm hoping it is just an issue with adaptions in the ECU. Anyone else experience this?

I just had my carbon monoxide emissions “fixed” as a recall and now my motor is misfiring and running like crap. I notified the dealer immediately and now they’re telling me I need to bite the bullet and buy a new motor. They said they would see if I would get approved for a certificate for 2k on a new vehicle and it has t be brand new. My truck drove fine and once I got it back it ran awful. Brought it back in and they are trying to sweep me and my truck under the rug. 

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,803 Guests (See full list)

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...