Jump to content

Recommended Posts

Posted
On 10/15/2021 at 12:27 PM, J2Jones said:

 

I purchased the same kit from ShopChevyParts.com and took my truck to the dealer for the include reflash, showed them the paperwork and had no issues.  Walked out for free with a receipt showing the reflash had been done and a charge of zero.  Just like the the paperwork that comes with the item says it should be.  I think it's pretty clear and most dealers are just being jerks.  I will say I bought my truck from a different dealer because the sales folks were totally unreasonable.  The service folks have been fantastic despite the fact the truck was purchased elsewhere.

You got lucky,  99 percent of the dealers will charge for a flash unless the labor was paid for them to install it. 

Posted
3 hours ago, Mudcon said:

You got lucky,  99 percent of the dealers will charge for a flash unless the labor was paid for them to install it. 

Thing is, when they put that code in GM pays them.  That is the whole point in the code that comes with the CAI.  If they tell you otherwise, then time to find another dealership.

  • Like 1
Posted
20 hours ago, Black02Silverado said:

Thing is, when they put that code in GM pays them.  That is the whole point in the code that comes with the CAI.  If they tell you otherwise, then time to find another dealership.

That is wrong, GM only pays us as a dealer if we put the CAI system on that was ordered on a new car job card. Or if it was ordered from the factory with the kit. The labor op you are referring to is labeled as "Air Cleaner Kit Installation and Engine Control Module Reprogramming with SPS" with 1.0 hr of labor.  The labor op is not for just programming if you put it on yourself. 

Posted
51 minutes ago, Mudcon said:

That is wrong, GM only pays us as a dealer if we put the CAI system on that was ordered on a new car job card. Or if it was ordered from the factory with the kit. The labor op you are referring to is labeled as "Air Cleaner Kit Installation and Engine Control Module Reprogramming with SPS" with 1.0 hr of labor.  The labor op is not for just programming if you put it on yourself. 

Interesting, that means the dealer that programmed mine did not get paid. 

Posted (edited)
1 hour ago, Black02Silverado said:

Interesting, that means the dealer that programmed mine did not get paid. 

That is correct.  You will find some dealers that will do it at a courtesy but most will not.   They may give it to people at the window not to argue with a customer also but the tech will want to get paid one way or another.  We just had 2 new trucks come in for Road Atlanta and had to install exhaust and CAI on both.  The labor ops included in the packages are what we use to get paid through GM being they do not install the add on accessories at the factory even though you can order the truck with them.   Never has made sense to me with which GM pays us to install stuff that a truck was ordered with and just toss the old parts we take off.

Edited by Mudcon

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...