Jump to content

Recommended Posts

Posted (edited)

Hi,

 

I am late to the party for sure. Could some one out here contact me regarding if the Black Bear tune fixed the fish bite / chuggle issues. I saw where SCUBA78 said his was fixed., but that was a while ago. I am a little fearful from other posts about the torque convertor needing to be replaced. If the torque convertor is the primary issue, then I do not want to throw 709 bucks for a tune that is faking the ECM/TCM to make me think its repaired. Then  another 75 k on the truck and the transmission goes. Please advise. PLEASE. Thx

Edited by mountaincreek
correction
Posted

I've had this issue since day one with my truck (2017 5.3L 6 speed). I had one TSB performed that slightly improved the issue (forget the TSB #, but it was software reprogramming, not the new fluid/fluid exchange TSB that's out for the 8-speeds). Otherwise have used a Range device on and off for a couple of years to help deal with the issue. No tune, although I have considered it.

 

Just after I turned 100k miles this past January, I had one day where the transmission really acted up and a check engine light came on (I think it was P0741, TCC clutch performance or stuck off). I cleared the code with a ScanGauge, but the poor shifting continued and the CEL came back on. The dealer diagnosed the issue as the torque converter. They replaced it and the check engine light has been off since. Shifting returned to "normal" along with the fish bite issue. No different than the first 100k miles. This leads me to believe the engine/transmission tuning is the issue, and it eventually causes the torque converter to fail. Not the other way around. Based on this anecdotal evidence, getting a tune early on in ownership may avoid torque converter issues down the road.

 

Hope this helps.

Posted (edited)
32 minutes ago, sonerick said:

I've had this issue since day one with my truck (2017 5.3L 6 speed). I had one TSB performed that slightly improved the issue (forget the TSB #, but it was software reprogramming, not the new fluid/fluid exchange TSB that's out for the 8-speeds). Otherwise have used a Range device on and off for a couple of years to help deal with the issue. No tune, although I have considered it.

 

Just after I turned 100k miles this past January, I had one day where the transmission really acted up and a check engine light came on (I think it was P0741, TCC clutch performance or stuck off). I cleared the code with a ScanGauge, but the poor shifting continued and the CEL came back on. The dealer diagnosed the issue as the torque converter. They replaced it and the check engine light has been off since. Shifting returned to "normal" along with the fish bite issue. No different than the first 100k miles. This leads me to believe the engine/transmission tuning is the issue, and it eventually causes the torque converter to fail. Not the other way around. Based on this anecdotal evidence, getting a tune early on in ownership may avoid torque converter issues down the road.

 

Hope this helps.

Ohh Man. Not good. So ironically, I took mine in and the issue hasn't been "replicated" at all after 500 miles of test driving it. The tech, me and the tech and just me. I am at a loss. The tech did say that he checked the codes and GM had a update and so he updated it. He updated it around the 300 mile mark of the test driving we were doing together and in part. I cant get a flipping answer from no one. I point blank asked the GM at the dealership that I am willing to pay for it if they in fact think they can "fix" it. Without it doing it for them, they cant say what it is. I tried brake torqueing it. no Dice. I feel it. Its on the fringe of doing it, but it hasnt done it really good like I have been experiencing. I have had this truck since 24k and now it has 88K. I have mentioned it several times to the dealer but its just one of those things that has to act up at the dealer. I havent the first clue as to how to capture the acting up on my own for proof. GM said that IF they could get it do do it, that GM would maybe pay for 25-50% of the bill because of the previous Hx. So after reading your post, now I am really confused. 

 

Also I might add, that I take very good care of my truck. I love it. And you might ask, why do you put up with it. Well to be honest the sporadic-ness of it has gotten less and less to where it does it nearly every long hill. I just press the pedal more and it downshifts and its gone. Sooo it has come time to trade fix tune or something

Edited by mountaincreek
Posted

Nick do you mind me asking how much the clutch and torque convertor ran you? And yes that's terrible that you still have the fish biting...........

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,903 Guests (See full list)


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