Jump to content

GREAT news! DFM disable coming soon

Robwcormack

Recommended Posts

Jay P Enthusiast

Jay P

Posted
Posted
12 hours ago, jail4u677 said:

You said the Auto Stop is easy to disengage.  How so?

There is a switch on the dash to shut it off. The only bad part is it resets when you shut the truck off.

 

Jay

  • Replies 242
  • Created
  • Last Reply
No Coast Rider Enthusiast

No Coast Rider

Posted
Posted
8 hours ago, jail4u677 said:

You said the Auto Stop is easy to disengage.  How so?

Push the button on the dash

jail4u677 Enthusiast

jail4u677

Posted
Posted
1 hour ago, No Coast Rider said:

Push the button on the dash

I have a 2019 AT4 and have searched the manual and my dash but I'm not sure if I'm just overlooking it.  Can you post a picture of the button you're speaking about?

Jay P Enthusiast

Jay P

Posted
Posted
12 hours ago, jail4u677 said:

You said the Auto Stop is easy to disengage.  How so?

There is a switch on the dash to shut it off. The only bad part is it resets when you shut the truck off.

 

Jay

Screen Shot 2020-04-04 at 11.51.03.png

Mudcon Enthusiast

Mudcon

Posted
Posted

Just an update, went on a nearly 700 mile trip towing and on the way up through the mountains my 10 speed was still shifting weird like it has been and I did notice the surge alot more around 35-40 mph in the mountain roads.  On the way back the surge was so bad I pulled over and turned the truck off and took the range out.  On the way home the trans shifted great and the surge of course was gone.  On the way up I got 11-12 mph and on the way back with out the range I was getting 14-15mpg.

SquireSCA Enthusiast

SquireSCA

Posted
Posted

Could the surging be due to HOW the range box works?  Does it intermittently send a throttle input signal to the ECU to make it think you are stepping on the gas to get it to go to 8 cyl mode?

Bob Ross Enthusiast

Bob Ross

Posted
Posted
2 minutes ago, SquireSCA said:

Could the surging be due to HOW the range box works?  Does it intermittently send a throttle input signal to the ECU to make it think you are stepping on the gas to get it to go to 8 cyl mode?

I have spoken to Range about this transmission surge and this is their answer. 

 

These new transmissions have an aggressive PWM (Pulse Width Modulation) torque converter that is designed so you don’t fell the firm LOCK like you used to when the Torque converter locks. It gradually locks it but when it does the truck will have a slight shudder. If it happens around 45+ MPH or so.

Robwcormack Enthusiast

Robwcormack

Posted
  • Author
Posted
8 hours ago, Bob Ross said:

I have spoken to Range about this transmission surge and this is their answer. 

 

These new transmissions have an aggressive PWM (Pulse Width Modulation) torque converter that is designed so you don’t fell the firm LOCK like you used to when the Torque converter locks. It gradually locks it but when it does the truck will have a slight shudder. If it happens around 45+ MPH or so.

Not what I'm feeling.  There's no way

Mudcon Enthusiast

Mudcon

Posted
Posted

Yea its not what I am feeling either.  As of this week they are telling me the 10 speed is the only issue they have had and they are going to release it without the listing for the 6.2 with the 10 speed and will continue to investigate it and work on it for the 6.2.

Zach-91 Enthusiast

Zach-91

Posted
Posted

Started feeling a slight surge when cruising at a steady speed between 30-40mph. Added a S&B CAI this week and not sure if it has caused this or if I can just hear it happening now because the intake is noisier. 

 

5.3l 8 speed. 

  • 2 weeks later...
chadman Enthusiast

chadman

Posted
Posted

I just ordered for my 2020 Sierra with the 5.3. Will update once I have it and give it a try.

Z45 Senior Enthusiast

Z45

Posted
Posted

Just got email, available now for $189.....

johnnypayne66 Enthusiast

johnnypayne66

Posted
Posted
On 5/3/2020 at 9:16 AM, e.texerado said:

looks like for 8 speed only?

image.thumb.png.d606abc295ee51af23e934ee493f416c.png

Oops I didn’t notice the transmission speed. I just ordered one and my transmission is the 10 speed.  Guess I will have to cancel order.  

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