Jump to content

GREAT news! DFM disable coming soon


Recommended Posts

Posted
6 minutes ago, Mudcon said:

True only time will tell really.  The anwser was going to DFM and dropping different cyl at different times and down to 1 at times.  Over all to me it is the same thing it what it will do over time but just might take alittle longer.  But time will really tell.  I just like the smoothness of the 10 speed transmission so I hope it is something that will get sorted out to not affect the trans shifting. 

My assumption is that with DFM it is constantly changing all the time, so it's never a pattern of the same cylinders shutting down for any length of time, so a lot of the lubrication and lifter issues may be alleviated...

  • Replies 242
  • Created
  • Last Reply
Posted
Just now, bshort said:

Any of the beta testers do some serious towing yet?  

Not serious towing but I've had over 1000 pounds in the bed twice and had no issues 

Posted
Just now, bshort said:

Any of the beta testers do some serious towing yet?  

I am not sure the exact weight you would consider serious towing but I have towed many times with the beta unit up to 6000 lbs. I honestly can't say I feel much difference towing when pulling. When towing and cruising the DFM may kick in without the range but I can not say 100%. I have not had issues either way. 

Posted
2 hours ago, Bob Ross said:

I am not sure the exact weight you would consider serious towing but I have towed many times with the beta unit up to 6000 lbs. I honestly can't say I feel much difference towing when pulling. When towing and cruising the DFM may kick in without the range but I can not say 100%. I have not had issues either way. 

I primarily tow and the DFM will kick in during lower throttle inputs.  

Posted
6 hours ago, Mudcon said:

Has any of the testers noticed the trans shifting different on the 10 speed trans with the range hooked up?

I notice it seems to shift different as well on my 10 spd.  Much closer to sport mode is the best way I know to describe it.  It also does a slight surge if you are cruising at very low speed on fairly flat road (i.e. in a neighborhood) between 1000-1300 rpm.

Posted

I've noticed that surge too. back and forth and back and forth between 1100 and 1300 rpm like Rob said when trying to maintain a cruise speed around 35mph

Posted
1 hour ago, Robwcormack said:

I notice it seems to shift different as well on my 10 spd.  Much closer to sport mode is the best way I know to describe it.  It also does a slight surge if you are cruising at very low speed on fairly flat road (i.e. in a neighborhood) between 1000-1300 rpm.

I have noticed that too.

Posted

I've towed but not 8000 pound loads. It tows well, and having had lifter issues with an earlier GMC I really like that it keeps the DFM from kicking in when I'm towing (or any time for that matter).

 

I've been seeing the slight surge that some of you are seeing, and will be doing some additional testing for Range.

Posted
7 hours ago, RaStahmann said:

I've towed but not 8000 pound loads. It tows well, and having had lifter issues with an earlier GMC I really like that it keeps the DFM from kicking in when I'm towing (or any time for that matter).

 

I've been seeing the slight surge that some of you are seeing, and will be doing some additional testing for Range.

correct me if I'm wrong but does the dfm and auto stop/start are disabled when the 4 or 7 pin trailer plug has something plugged into it?

Posted
2 hours ago, snork said:

correct me if I'm wrong but does the dfm and auto stop/start are disabled when the 4 or 7 pin trailer plug has something plugged into it?

I think someone here posted that they experienced that, however I have never confirmed that myself. @bshort posted above that when towing they experience the DFM kicking in during low throttle inputs.

Posted
10 hours ago, RaStahmann said:

I think someone here posted that they experienced that, however I have never confirmed that myself. @bshort posted above that when towing they experience the DFM kicking in during low throttle inputs.

I have the GM performance exhaust and can hear DFM kick in when pulling the travel trailer out of the neighborhood.  I want to say that it even kicked in with M9.  

Posted

I had a 2015 with the 5.3 and the Range was a game changer, the AFM was horrible and caused throttle lag and surging, I hated the truck because of it. The Range improved my driving experience and got me an extra 1 MPG. My wife also has a 2018 Buick Regal TourX with Auto Stop that cant be disabled and we hate that feature but love the car. Luckily Range makes a product for that and now we have Auto Stop disabled in the Buick.

 

I just a got new 2020 Sierra with the 5.3 with DFM and I have to say I can't notice it engaging at all, it works just like it should. Not sure I would spend the money on a Range for this truck since the system actually works well, and the Auto Stop is easy to disengage. But I'll probably end up buying it anyway just to try.

Posted
14 hours ago, No Coast Rider said:

I had a 2015 with the 5.3 and the Range was a game changer, the AFM was horrible and caused throttle lag and surging, I hated the truck because of it. The Range improved my driving experience and got me an extra 1 MPG. My wife also has a 2018 Buick Regal TourX with Auto Stop that cant be disabled and we hate that feature but love the car. Luckily Range makes a product for that and now we have Auto Stop disabled in the Buick.

 

I just a got new 2020 Sierra with the 5.3 with DFM and I have to say I can't notice it engaging at all, it works just like it should. Not sure I would spend the money on a Range for this truck since the system actually works well, and the Auto Stop is easy to disengage. But I'll probably end up buying it anyway just to try.

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

Archived

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

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