Jump to content

Recommended Posts

Posted

Anyone had these updates to their trucks? I had my oil changed today and they updated both modules. What ever was done to the ECM/tcm seems to have made my shifting a little strange.

Posted

Sorry silver spaceship my frustration got the better of me this time. I'll keep everyone posted though in the days to come. I also searched my vin# and came up with no recalls for mine but the dealer did I guess.

  • 2 weeks later...
Posted

Harder shifts that aren't welcomed.... Noticed on 1-2 shift and 2-3 shift.

I had mine done also and feel the same thing. Did yours get better? Mine seems a little better but not like it used to be. My truck also goes into 4 cylinder mode more........
Posted

My shifting is back to how it was before, my mileage dropped about 1.8 mpg but now, a tank 1/2 later it looks like its close to be back, fingers crossed. To me I don't feel the transition from 4 to 8 and vise versa isn't as smooth as before. Sometimes it will show v8,v4 and back to v8 all in a split second, never seen that before.

Posted

Good to hear that your shifting is back to where it was before. Mine jumps in and out of V4 and V8 A LOT more!! Kicks into V4 and lugs the truck into low rpms and then downshifts to get going again. Hopefully the tranny gets back to normal and gets rid of this.

Posted

Aren't firm shifts a GOOD thing??

 

Just curious if you guys are expecting a soft shift that you don't even feel, or if it's gone from a nice, firm shift, to something that's simply way too harsh?

Posted

Cap'n Pete.. My '14 shifted smoothly when I got it.. After the update it would hit hard from 2nd to 3rd.. A very noticeable difference. After driving it for a few more days it is better as its only noticeable when the trans temp is still cold and goes away once it reaches about 100 degrees.

Posted

Yeah mine was rough till i got on it hard 1 time passing someone.. Now its butter.

I had this done yesterday. BCM was already updated, just had the AFM updated. I had read this thread prior to taking it in and when the truck was complete, I took it on the Interstate immediately. 1/4 Mile on ramp, I got on her pretty good, once on the highway, I did a few pedal to the floor blasts and all is well.

 

Mike

  • Like 1

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   5 Members, 0 Anonymous, 1,931 Guests (See full list)

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