Jump to content

Low Oil in Diesel Engine 6.6L

AK_ Maverick-X3
 Share

Recommended Posts

AK_ Maverick-X3 Enthusiast

AK_ Maverick-X3

Posted
Posted

Okay feeling really stupid right now, but I'm all sure we have made some kind a mistake that we should have know better. My tail is between my legs!

 

Recently changed my oil on 2016 Chevy 2500 3/4 ton. This was my second oil change since owning the truck (bought used) 5000 miles ago, now at 52,700 miles.

I changed the oil 2 weeks ago and is wasn't driven for week.

I drove approximately 100 miles and the low oil was prompted by the computer on the truck. I immediately pull off the road and check to see if the drain plug or oil filter was loose and leaking oil. No visible oil leak. I popped the hood and found there was no oil on the dip stick.

I just had just left Costco, which was in eye sight. I when back in and bought another case (6 quarts) of 5-30W. The truck took 2 1/2 quarts  of oil. I could swear that I checked the oil stick when I had originally changed oil and thought it had enough oil. I can't remember placing 10qt of oil when changing it.

Note: I have own trucks for 38 years and have always changed my own oil in the trucks. This is the first diesel truck I own and will not forget 10 Quarts the next time.

 

Questions:

Did I do any damage to the engine?

Why did the computer take so long to notice that it was low on oil?

Is there anything else I need to know?

Please do not shame to bad, feel like crap already.

 

Thank you in advance for taking the time to read my post.

Scott

 

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

It'll be fine. You'd need to have less oil than that to start starving the oil pump of oil and damaging parts. Figure if anything there is probably 3 quarts of oil in that size engine going through the pump, oil passages, lifters, pushrods, valvetrain and running back into the pan at all times.

 

There must have been just enough oil in the pan that so that is was staying exactly at the low level sensor and must have just dropped below it enough times to trigger the sensor. Perhaps once the oil was nice and hot the level could drop quicker as the oil thins out.

Duramaxsky Enthusiast

Duramaxsky

Posted
Posted

You didn't hurt it at all. The add oil mark on the dipstick is 2 quarts low. The only way you could have hurt it is if you ran it at very high RPMS cold. Then the oil pump could move it faster than it could flow back. Even then it may not have been a problem. Don't waste time worrying about it.

 

Sent from my SM-A505U using Tapatalk

 

 

 

 

Duramaxsky Enthusiast

Duramaxsky

Posted
Posted

When you say low oil light was it low oil or low pressure?

Sent from my SM-T510 using Tapatalk

Duramaxsky Enthusiast

Duramaxsky

Posted
Posted

Then you didn't hurt it. Low oil pressure would be a different story.

Sent from my SM-T510 using Tapatalk

newdude Senior Enthusiast

newdude

Posted
Posted
On 12/2/2020 at 11:06 AM, AK_ Maverick-X3 said:

I live in Alaska with colder temperature.

 

5w30 is not approved weight for the 6.6 Duramax.  0w40, 5w40 and 15w40.  GM shows 5w40 for cold weather but you can probably go down to 0w40.  

Duramaxsky Enthusiast

Duramaxsky

Posted
Posted
Should the current oil in truck be changed out, or change out at the next oil change?
Oil for gas engines is different than oil for diesel engines. If it is gas engine oil then i would get it out of there. Plus the reason the high number is 40 is even in cold weather the turbo gets hot. So I would just to be safe.

Sent from my SM-T510 using Tapatalk

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   5 Members, 0 Anonymous, 1,931 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...