Jump to content

Recommended Posts

Posted
2 hours ago, Black02Silverado said:

Maybe, but it seems he is the only one that has backed up data to prove what he is stating. I think he is doing this more because he enjoys it and wants to get the information out to us. He's got the knowledge and access to the proper equipment and having the funds doesn't hurt.  I would love to do what he is doing and would do it if and when I hit the Powerball.  I'm not a Tribologist by any means but love to learn what I can.

 

I would bet there would be doubting people out there if a completely independent lab with high quality work and highly respected in the automotive industry, put out information like this.  The world can't be pleased, one just has to take the information that they are given, do more of their own research to find actual lab data to back up what they are trying to figure/find out.  Most don't bother, they just want to believe what they first see.  

 

I don't have the minimax but my 6.2 in my 2019 Silverado with 64k miles shows excellent UOA results with 0w-20 and for my own purposes 5w-20.  Since not much of a change using 5w. I liked the data sheet information on the SS 5w-20 and figured I would give it a try.  Still the same viscosity at 100℃.

 

In the end we all just do what makes us happy, life is too short to get upset over trivial social media.

 

On a side note, I do feel GM has dropped the ball and just cares about the bottom dollar and not quality anymore.  "Like a Rock" has been long gone.  Seems "Built Ford Tough" has as well.

I find it amusing the OP doesn’t realize this threads heading includes several engines. He should have posted in the off topic section if he wanted a more narrow focus. I really appreciate and find amusing that he actually pointed out one of my many vehicles. The Odyssey. That happens to use 0-20 oil. I love pushing his buttons. 

  • Like 1
Posted

I know it's hard for some of you to connect the dots, but there isn't a 3.0 duramax subforum, only a 2019-2026 powertrain subforum, which is where we are. You'd think the highly specific mentions and oil testing WRT the 3.0 in the first post would have been the tipoff, but I realize others need large signs posted to clue them in.

 

The oil spec for the 3.0 is unique to the 3.0. Dexos D 0w20 is not currently used in other GM diesels, and Dexos D licensed oils like ESPx2 and AcDelco's Dexos D 0w20 are different from their 0w20 counterparts like Mobil 1 0w20 AFE or Truck/SUV, or ACDelco synthetic 0w20 meeting Dexos 1 Gen 3.

 

The 0w20 for the 3.0 is different from the 0w20 you might use in a minivan, for example. I've said it 3 different ways now, but please continue to be a bored old boomer pest in these technical discussions.

 

 

Posted

What you can’t seem to understand we might be trying to keep your thread alive. Even with your condescending attitude. Just how many 3.0 mini diesel’s owners do you think are here? I have my device set for the last posts. It doesn’t take long for post to vanish. But alas I’ll just ignore you in the future. Have a nice day.

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
  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • 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...