Jump to content

Recommended Posts

Posted (edited)

Question for you guys. For the most part I'm super happy with the 1500. Love the looks , int., and such but what I'm finding is its finicky with temperature. I'm noticing if its a decent day even 32 degrees she runs good once all warmed up. We are in a big cold snap today, tonight and tomorrow if - numbers. I had taken a ride to the gym at 430 and I had no problems. My drive consists of a main road then a highway for 10 minutes then another 10 minutes on a back road. Coming home the temp is 0 degrees with a windchill of -25. I noticed it a lot on the highway but I was getting major surging. Almost like a carburetor with dirty jets. The truck would be driving and surge ,run good then surge. I know cold weather reeks havoc on everything but I figured once up to temp there would be no problem. Seems in the cold the tranny has major dead spots between shifts and the horrible surge. Has anyone else encountered this and have an answer to what may be the problem?

 

Sent from my Nexus 6P using Tapatalk

Edited by Jeff5347
Posted

Does this sound like the same behavior your truck has?:

 

http://www.gm-trucks.com/forums/topic/155198-rpms-fluctuating-when-accelerating-under-light-load/

or

http://www.gm-trucks.com/forums/topic/181145-2014-53l-6-speed-rpm-fluctuations/

 

 

A small amount of RPM fluctuation is normal. The TCC is allowed to slip a little even when locked up and causes the engine to sound like it's surging a bit.

 

 

A torque converter with an electronically controlled capacity clutch (ECCC). ECCC was developed to reduce the possibility of noise, vibration, or chuggle caused by TCC apply. In a torque converter with ECCC, the pressure plate does not always fully lock to the torque converter cover. Instead, the pressure plate maintains a small amount of slippage. In RWD 6-Speed transmissions, this slippage can range from 0-50 RPM. Full lockup (0 RPM slip) is still available on some applications. TCC may apply in 2nd, 3rd, 4th, 5th, or 6th gears. The specific TCC apply points and the amount of clutch slippage are determined by a number of operating conditions, including throttle position, vehicle speed, gear, as well as specific vehicle application. Transmission fluid temperature will also affect TCC apply points.

http://www.transtar1.com/TranstarIndustries/media/Transtar1/technical/bulletins/TLT-TC-035.pdf

Posted

From reading it sounds like that may be it. I didn't notice the needle movement like morrislee but I wasnt paying attention to it either. I drive this highway every day so I'm wondering if it is the super cold we have right now. I do 90 % of driving in the manual mode. M4 or m5 around town and when I jump on the highway upshift to m6 once I get up to 65- 70/mph. I haven't tried to see if leaving it in m5 on the highway or having the shift lever in D mode instead of M. This was at the approximate speed of 70 and I noticed it more once I had a grade to climb whether it be a slight uphill or more pronounced. I'll have to keep an eye on it and try leaving it in M5 to see if v4 or m6 is the culprit. At least this gives some info on where its coming from. Another thing and not sure if this is coincidence or a factor but I only notice this after installing my leveling kit albeit we haven't had this low of temps ( minus degrees) either.

 

Sent from my Nexus 6P using Tapatalk

Posted

From reading it sounds like that may be it. I didn't notice the needle movement like morrislee but I wasnt paying attention to it either. I drive this highway every day so I'm wondering if it is the super cold we have right now. I do 90 % of driving in the manual mode. M4 or m5 around town and when I jump on the highway upshift to m6 once I get up to 65- 70/mph. I haven't tried to see if leaving it in m5 on the highway or having the shift lever in D mode instead of M. This was at the approximate speed of 70 and I noticed it more once I had a grade to climb whether it be a slight uphill or more pronounced. I'll have to keep an eye on it and try leaving it in M5 to see if v4 or m6 is the culprit. At least this gives some info on where its coming from. Another thing and not sure if this is coincidence or a factor but I only notice this after installing my leveling kit albeit we haven't had this low of temps ( minus degrees) either.

 

Sent from my Nexus 6P using Tapatalk

 

I am starting to guess it is my air intake icing up, I cleaned and re-oiled my K&N air intake today, will see tomorrow cold morning.

Posted

Check for possible vacuum leaks while you're at it.

 

Made very sure that every hose is tight and also cleaned the throttle body.

 

Still happened this morning, so I just cleaned the MAF sensor with the CRC cleaner spray.

Posted

I had a similar issue like that I would be leaving the parking lot letting the fast idle pull the truck up to speed then add alittle light throttle then it would surge off and on some. Went to a aftermarket throttle body and haven't notice it since.

  • 4 years later...
Posted

Did anyone ever figure out what this was caused by? I have a 2015 GMC Sierra with the 5.3 doing the same thing today. 10 degrees outside. Only does it while cruising down the interstate. No codes stored or engine light. 

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
  • Latest Articles

  • Posts

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