Jump to content

dexos oil

Jworks
 Share

Recommended Posts

Jworks Enthusiast

Jworks

Posted
  • Author
Posted
On 9/11/2022 at 11:22 AM, pokismoki said:

what was the engine temp, oil viscosity and engine loading at when the gauge read 20psi?

 

i know the computer controls the variable oil pump, but super thin worn out oil might also cause  a low reading.  then there is the two different oil filters GM offers that fit our trucks, one is low pressure , and the other is a higher  pressure bypass. you need the correct filter to jive with this computer controled oil system

Pokismoki, engine temp was warmed up...210 degrees.  The oil I was using was dealer furnished GM Dexos (Dexos1 I think).  Engine was at idle.

Jworks Enthusiast

Jworks

Posted
  • Author
Posted
On 9/12/2022 at 9:35 AM, diyer2 said:

How often have you changed the oil or your average mileage when changed?

diyer 2, I change the oil when the computer gets down to 20-25% remaining.  Thats around 5-6000 miles.

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted
9 hours ago, Jworks said:

GrumpyBear, earlier today I posted a question earlier about Dexos and I had forgotten I posted this post a year ago.  So.....got a question for you.  You mentioned M1 makes the dexos oil for GM.  I didn't know that.  But you also said " that doesn't mean its equal to M1 oil.  Understand that.  Since I'm letting an independent mechanic do my next oil change I'm considering going with M1.....or Castrol synthetic.  Two questions:  (1) With 157k miles on a 2011 5.3 would you stick with Dexos, or would one of those two full synthetic oils be fine if they are not Dexos1?  (2) How do you feel about Castrol synthetic?.

 

First, they both are Dexos1Gen3. Here's a list: dexos®1 Gen 3 | GM (gmdexos.com) You will find both your choices on this list for that spec. 

 

Dexos1 Gen 3 is Here | Chevron Lubricants (US) Some commentary on the topic. 

 

To your question about what I would do. Hum.... well, I ignored the entire DEXOS drama and used a boutique oil. Red Line HP on 5K OCI's and Purolator ONE filters for the majority of miles in my personal truck which now has 176K on the clock and from the moment I bought it with 1,300 miles on her and a full warranty in play. It looked like this around 165K:

 

image.thumb.jpeg.a5892e80aa9ca969595c572462de83b5.jpeg

 

If you can pull your cover and it looks like this, then keep doing what you are doing. 

 

If it looks like this or worse, ask again. 

 

image.png.cd347625d8e25b361dd557377776afae.png

 

 

 

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

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