Jump to content

06 Duramax 6 Speed Manual Shift Not Functioning

Wesley Brown

Recommended Posts

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted

Hi speedster993,

 

I’m sorry to hear that you also have this problem with your truck. Please feel free to reach out to GM of Canada if any further assistance is needed. They can be reached at 800-263-3777 Monday through Friday from 7:30 AM until 11:30 PM and Saturday from 7:30 AM until 6:00 PM EST. Please let me know if you have any questions.

 

Kristen A.

GM Customer Care

scooby5121 Enthusiast

scooby5121

Posted
Posted

I Guarantee the Answer ...............Simple fix.

It is a broken Wire Guaranteed on the gear selector where it goes into the colum.

They Charge 50 bucks to fix it.

Dealer will want to change the shifter !!!!!!!

 

Pop off the Signal lever, with the tool . ( disconnect wire plug harness)

Pop off the front plastic cover on the steering wheel( two Pieces)

Pop off Gear Selector ( disconnect wire plug harness)

Now look at the last place the red wire is fastened to the gear shifter and where the bend in the wires are leading to the plug end. About 4-6 inches in length. At the BEND !!!! The one wire for the selection switch is broken. Look at the plastic sheething.

The sheething gets brittle over time so it breaks there. Wire in thin has a hair !!!

Scooby

scooby5121 Enthusiast

scooby5121

Posted
Posted

Was out driving with my brother the other day and I put it into the manual shift mode from park and I didn't get any response from the gear selectors. The indicator just sat on 6 and operated like it was in drive. Has anyone else experienced this or know what might be causing it. My only thought is that I've lost the electrical connection to the gear up gear down selector.

 

Anyone have any insights or personal experience with this?

Read Down on my Post !!!!

Scooby

scooby5121 Enthusiast

scooby5121

Posted
Posted

Hello everyone,

 

Just wondering if there was a fix to this problem that Wesley Brown originally posted?. My truck is having the same problem and I searched the internet, but haven't been able to come up with much.

Read my post !!! Scooby

scooby5121 Enthusiast

scooby5121

Posted
Posted

scooby5121

 

Exactly what you said, problem is fixed.... much appreciated!

 

Thank you for all the responses

I HOPE everyone out there see's the post. It is all because the wire insulation gets brittle and breaks right there...Glad you got it working again.

speedster993 New Member

speedster993

Posted
Posted

Here is a very helpful video to fix the problem. The year of your vehicle may differ, but nevertheless the procedure is almost the same for all years Chevy/GMC. I ended up going to a GM dealership and buying a new wire that already comes with the connector end. I'm the type of person that enjoys stuff like this and don't like splicing wires so I did it the long way, which is the way they do it in the video.

 

 

 

Hope this makes it easier to understand the process

newdude Senior Enthusiast

newdude

Posted
Posted

99% that the orange wrapped wire from the shifter has rubbed through and chaffed on the column. Either replace the shifter or try and repair.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...