Jump to content

2021 GMC AT4 Duramax 3.0L DEF Sensor Issue

Drew Sunderland
 Share

Recommended Posts

Drew Sunderland New Member

Drew Sunderland

Posted
Posted

Hello All,

I have had my 2021 GMC AT4 Duramax 3.0L since it had 8 miles on it, I have had random issues with the DEF sensor where it has been in and out of the shop, it has 41k miles on it and now its getting irritating when the sensor goes wild and the truck thinks its out of DEF and goes into limp mode.

 

Like I have said I have had it at 1 Dealership here in OKC multiple times with this issue and they keep saying that there is nothing wrong with it, I took it to another dealership that was on my route since the truck's check engine light came on and the display said to have the DEF system serviced and that it will be in limp mode in less than 155 miles.  They stated that they found a TSB for an update that says it addresses a couple of MIL's and they said that it had some DEF sensor recalibration and heater recalibration.  I asked them for the TSB number and they gave me DOC 6126396 which I assume is TSB 22-NA-150, they charged me $250 for the updated because they stated that it would fix the issue.

 

On my drive home from the dealership the truck display started to say that the DEF miles remaining was 800 and immediately started to drop down to 777 miles.  I called the service advisor and he stated that the sensor is probably recalibrating and to bring it back next week if its still having issues.  I have never seen a sensor like this ever need to be recalibrated via the system after a couple of hours to days.  I have attached the invoice from the dealership. 

 

So far I have taken my truck into 2 different dealerships over the course of 1.5 years to address this and everyone keeps telling me its a software problem, they wont check the wiring or the sensor.  Has anyone seen this before on the sensor or know what I can do to fix this?

 

Here are the videos that I have of the displays:

 

 

 

 

 

on the Edge in the bottom left of the screen you will see DEF_LVL - SAE and you can see it go from 0 to 100% for no reason.

 

  • 1 month later...
Drew Sunderland New Member

Drew Sunderland

Posted
  • Author
Posted

After contacting GMC customer care and complaining, they had the dealership replace the whole tank.  But it is still doing the random readings like the videos above.

 

Question for anyone that has the 3.0L duramax, if you have a OBDII reader that will show live data, can you see if yours is doing what mine is in the video?  It seems to do it more when driving than sitting still.  Trying to figure out if there is a bad wire somewhere now or a grounding issue.

Drew Sunderland New Member

Drew Sunderland

Posted
  • Author
Posted

I am now wondering if the issue that I am having with the tank is actually an electrical issue, I got in the truck just now and none of the internal lights would turn on, either by pushing the light or opening the door.   I remember back a couple of months ago that my audio completely cut out, no radio, no voice, no onstar, nothing, I had to stop the truck, get out and then get back in to get audio to work again.

 

I am needing to track down this issue, I am seriously thinking its an electrical issue.

m21knight Enthusiast

m21knight

Posted
Posted

I had this issue with my 2020 LM2, took it to the dealer several times.  They performed some sort of TSB(software update I believe), that didn't seem to really do much initially.  They then read me another TSB description which basically said that there are tank level ranges that seem to have this issue and the level will fluctuate for a short period of time until the tank level moves out of that problematic range.  I didn't really think that was a good answer, but the issue seemed to correct itself after about 1,000 miles.  I'm currently at ~40k miles, but the issue started to creep up around 30k.  I would go back and press them regarding a possible software update to address the issue.

  • 1 year later...

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   3 Members, 0 Anonymous, 2,122 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...