Jump to content

New 21 Silverado with 5.3 and NO DFM

Spanky06
 Share

Recommended Posts

Spanky06 New Member

Spanky06

Posted
Posted

Hello all,

    I am new to this forum, but I have been a lifelong Chevy man. I recently traded my 2015 Silverado LT Z-71 for a 2021 Silverado LTZ and I went with the 5.3 as it has been great for me since my first Silverado in 2003. My new truck did not have the DFM due to the chip shortage, the dealer took 50.00 off the sticker because of that (SMH). My question is this, could I have DFM installed once the chip shortage gets squared away, this is assuming that there is an open chip slot in the present computer of the truck?. I had AFM in the 2015 and that worked like a champ my 2015. My gas mileage was great. 23 on the highway and 18 in town. All bets were off when I was towing my Bass Boat. Thanks in advance for any information and I absolutely LOVE my new truck

2021 Silverado Crew Cab LTZ1.jpeg

  • 2 weeks later...
Ken M. Enthusiast

Ken M.

Posted
Posted

I bought the same truck and same sticker no DFM. Unless I'm mistaken I'm happy without it. It seems to cause issues even engine failure.

Spanky06 New Member

Spanky06

Posted
  • Author
Posted

Yes, I am liking mine as well, Great Truck as always, this is my 4th Silverado

GarandPappy Enthusiast

GarandPappy

Posted
Posted

My 2021 Z71 RST didn't come with it either.  All that tech involved and they took off a whoppin $50.  As I have looked at MPGs on different stickers, I haven't noticed more than 1-2 MPG difference.  I've actually averaged between 16-17 and that has been all in town for just under 600 miles.  I was actually glad it didn't come with it.  We have a 2011 Tahoe LTZ and I thought that was the most techie truck I'd ever been in.  I do have the AutoStop, and I cannot say that I am a fan of all that.  I think I might like it for more highway driving, but not the stop and go I'm in so much.  

  • 2021 with NO DFM
    • 1856010519_YouveUnsubscribed-LibertyUniversity.jpeg.7f980fc3361923efbf57d644df03bdf1.jpeg
  • 2021 with DFM
    • IMG_4341.jpeg.7ea59c480b5286771d3b8d2bc504425d.jpeg
OGreatOne Enthusiast

OGreatOne

Posted
Posted

It's interesting to look at those MPG's. I would think that the DFM would have a greater benefit at highway speeds but it looks like it has more effect in city driving.

Spanky06 New Member

Spanky06

Posted
  • Author
Posted

As for the Auto Stop, you can disable it when you start the truck to drive it (At least on mine you can), you are correct GarandPappy, it is a PITA. I am averaging about 17 mpg btw.

 

Spanky

Adamace1 Enthusiast

Adamace1

Posted
Posted

I'm curious how much of a difference it makes. 2mpg sounds about right. I use my truck 5.3 4x4 crew cab at work, some days I idle a few hours. I'm currently getting over 20 mpg over 12,000 miles. On trips I can get 22 to over 24.

 

With a base single cab 2wd ford v6 my average was never over 20. So I think something chevy does really helps with mpg. I also don't like the auto stop/start and turn it off.

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