Jump to content

Transmission - Shifting from D (drive) to M (manual)

channer

Recommended Posts

channer Enthusiast

channer

Posted
Posted

Does anyone know... with the truck in motion.... what gear I would be in if I shifted from Drive to Manual. I would like to be able to gear down from Drive... I don't if that is possible.

 

I know when I am stopped, if I shifted to M (manual), it automatically goes/shows M1 (first gear). If I am in motion, does would it shift to M1 or M6.

 

Its not like the old days when the dashboard shows (P - R - D - 3 - 2 - 1) on the days board :)

 

dave

DaveH71 Enthusiast

DaveH71

Posted
Posted

its will show whatever gear you are currently in. For example if the truck is in 3rd gear and you shift to M it will show 3rd gear and hold 3rd gear until you change it.

esox07 Enthusiast

esox07

Posted
Posted

This is how i believe it works. When you shift into M, it will start out in M6 or sixth gear or a lower gear if more appropriate. For instance, if you at a stop and shift into M, it will go into first gear. AS you begin to move, it will shift accordingly, basically just like regular drive and will go all the way up to sixth gear. If you are moving and shift into M, it wont necessarily change your gear and will continue to shift up and down as you change speed. Shifting into M and then hitting the +/- button will simply change the max gear that it will go to. So, say you are going 30 mph and the truck is in 3rd gear and your shifter is in "D". You won't really notice any difference when shifting into M. It will stay in 3rd gear until you change the speed or load on the transmission and it will continue to shift as needed just as before. Then say you are going 70 and are in 6th gear with "D" on the shifter and then shift into M, you still likely won't notice any difference. But if you hit the "-" button, it will force the truck down into 5th gear and prevent it from going higher but will still let it go lower. Basically the Manual mode is an upper limit in gears that the truck will go into and it is adjusted by the + and - buttons. Many times it is used in conjunction with the tow haul mode to limit the truck from going into upper gears when you as the driver know it won't be able to hold it very long anyway. That way it prevents the constant shifting that can occur when traveling with heavy loads.

I hope this helps.

Bruce

Cowpie Senior Enthusiast

Cowpie

Posted
Posted

I have regularly jumped from drive to manual and back. Whenever I have dropped from drive to manual, it generally puts the manual top gear selection at 4, 5, or 6 depending on the speed I was running. In most cases, even if I was in, say, 4th, and dropped to manual, it would most likely show M5 as the top selection on the display. Always seems to show a top selection higher than the gear I am in, up to M6 of course. Either way, it will never go to a manual mode gear lower than the one you are already in. And you can still drop or raise it as you see fit.

 

Overall, I probably spend more time in manual mode anyway. I rarely use drive. Just the old trucker in me that likes having a little control even over an automatic trans. This trans is similar to me of automated shift manual trans in commercial trucks. I can have more control over the gear selection than just the old 4 speed autos. The 6 speed with manual mode was a major selling point for me to buy. Just wish they would quickly get to 8 or 10 speeds in the near future. Now we would have a killer deal.

esox07 Enthusiast

esox07

Posted
Posted

I was listening to a commercial on tv this evening and I heard something about a 9 speed and I think it was a Jeep Cherokee or something.

scooby5121 Enthusiast

scooby5121

Posted
Posted

Esox.,

Stopped Display show 1 in Manual. Will Not go into higher Gear at all unless + is pushed. Stays in 1st Gear .

From Drive at any speed and put into Manual it Will show what gear your in at any speed. example 3rd. Will not Go higher than 3rd.

As long as you are driving in 3rd it will only down shift as speed decreases, never going into 4th.

Scooby

esox07 Enthusiast

esox07

Posted
Posted

Scooby, you are likely correct. That is how it was explained to me by the dealer when I bought the truck. But, I really haven't played with it all that much. Most I did was put it in M while towing and then hit the - button to hold it to 5 and below. I never really played with it set to the lower gears.

  • 2 weeks later...
Bad Bowtie2 Enthusiast

Bad Bowtie2

Posted
Posted

I keep my 5.3L 2013 C1500 in "M5" about 90% of the time here in town (under 50MPH).

 

Keeps that stupid "V4" mode from switching in/out too.... truck drives much better. :gmc:

  • 3 months later...

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...