Jump to content

Rebuilt the Transmission, now I'm in deep s***

rallysport096
 Share

Recommended Posts

rallysport096 Enthusiast

rallysport096

Posted
Posted (edited)

So back in March, a family friend and I rebuilt my 6L80 in my 2015 Sierra. I had taken it out, rebuilt it with him, put it back in, reprogrammed the TCM and such, truck runs great.

 

While I was without my truck, my Dad so graciously lent me his 2015 Sierra to borrow while I was working on mine. His had the same issue though (bad lockup in the tc/bad tc). Once mine was done, I decided to rebuild his. Disconnected the battery, took the trans out, overhauled it, put it back in the truck, reconnected the battery, went to reprogram the truck, and it would not show up on the reader (ACDelco Techlink with MDI). Would not populate the VIN. MDI would not read the truck.

 

Checked the program on my Sierra, the MDI and software are fine. 

 

Back to my Dad's truck, as I turned the key on when I initially plugged the MDI in, I received the following messages in the dash:

 

- Action Required: Steering Assist is Reduced Drive with Care

- Fuel Level Low (gauge shows empty, but I know I had gas when I parked it)

- Service Stabilitrak

- Service Trailer Brake System

- Automatic Light Control On (This one popped up as I am writing this post... so new?)

 

In addition:

- The PRNDM don't have a red highlight (no shift indication)

- The shifter doesn't have the safety lock engaged (where you have to press the brake to shift)

- It won't start

 

My initial worry was, "Man, I f****d up the techm somehow." But, can the techm cause all of this? 

 

The battery is a bit low (12.03V), but I've had it worse in my truck and nothing like this ever happened. Stabilitrak, for sure, but nothing else. 

 

Finally thought to connect my VerusD10 scanner, after waiting the 10 mins to start WinXP, it got through to give me the U0100 and U0101 codes.... 

 

Any ideas? Thanks!

 

Edited by rallysport096
mjm-1957 Enthusiast

mjm-1957

Posted
Posted

Make sure the connector at the transmission is fully seated and there are no bent or backed out terminals, the scanner should see the TCM at start up.If that checks out okay make sure the passthru in the case is fully seated and that the retainer is fulled locked.It should snap and click into place when fully seated.

rallysport096 Enthusiast

rallysport096

Posted
  • Author
Posted

So that was something I checked, and I can see there's no pin for #13, but it's not bent nor does it look like it broke off. I can't tell if there was even a pin to begin with. Theres a wire in the pin 13 spot on the harness. Maybe it was a clean break?

mjm-1957 Enthusiast

mjm-1957

Posted
Posted

Pin 13 is high speed communication circuit 2501. I cant figure out how to upload the schematic. If you have access to service information from GM the document ID number is 3627766. That should get you talking with the TCM again.

Spurshot Senior Enthusiast

Spurshot

Posted
Posted

I'm no techy with these devices but, I'd start with a fully charged battery. 12.03v sounds really low. 

  • Like 1
16LT4 Enthusiast

16LT4

Posted
Posted
15 hours ago, Spurshot said:

I'm no techy with these devices but, I'd start with a fully charged battery. 12.03v sounds really low. 

 

Throw in some poor grounds and a voltage drop, and that already low voltage gets even lower.  On other brands, getting in to the DME with too low a voltage (and without a charger hooked up) is a good way to brick it, though I have ZERO experience with the computers on these trucks.  Try again with a fully charged battery.

rallysport096 Enthusiast

rallysport096

Posted
  • Author
Posted

So it was pin 14, not 13. Regardless, I replaced the techm and the truck talked to the computer. Reprogrammed, went through the shifting procedures, truck drives great. 

 

So what does pin 14 do?

  • Like 2
mjm-1957 Enthusiast

mjm-1957

Posted
Posted

Pin 14 is circuit 2500 dark blue wire is high speed communication circuit, you were correct, pin 13 is blank on your model,sorry about that. If I could post the schematic you would have seen that. These old eyes aren't as sharp as they used to be. Glad ypu got it going.

  • Like 2

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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