Jump to content

BEST OIL AND FILTER FOR 6.2L HIGH MILES

apollo18

Recommended Posts

apollo18 Enthusiast

apollo18

Posted
Posted

hey guys! i know this has been discussed a million times, but never know what if our gm engines LOVE a specific type of oil.

So my truck is an 07 ext, on the original engine with 330,000 km's on it.

In the past it was always on Mobil 1 synthetic from the dealership, at 290k i started using amsoil for a couple changes, then royal purple for a couple, and now ive been running pennzoil ultra platinum. I heard the ultra platinum had the best protection from forums and stuff. There was some psi protection thing and Ultra Platinum had the best protection; The main problem with my engine is noisy lifters so im hoping an oil could silence that maybe, also winter is coming soon and temperatures could hit -35 celcius. I am going to be getting my oil changed soon, and i wanna try castrol edge extended performance since i havent tried it in this engine yet. With all the oils, I felt that the lifter noise was the same so maybe that will never get fixed but whatever. I guess i want the best oil for the cold winter coming up soon. Also I barely ever do any highway miles tho. its basically 90 percent driven short distances which is worse.

Also what filter do you guys recommend? Ive been running NAPA Platinum / KN oil filter / mobil 1 oil filter. I felt they all were good, but whats the best?

also should i be running a high mileage oil? or can i just run the expensive extended performance oils?

Colossus Senior Enthusiast

Colossus

Posted
Posted

Ditto on the oil analysis. As for brand, you'd probably be just fine with good ol regular full synthetic, no need to pay extra for those so called "premium" brands like Amsoil or RP. I'd do 5000 mile oil changes and use a good filter like NAPA Gold or Platinum or equivalent. Glad to hear your 6.2 has held up well thus far. Are you running 91/93 Octane fuel in it?

Black02Silverado Senior Enthusiast

Black02Silverado

Posted
Posted

What you are running or have been running is just fine. As for the noisy lifters. That just is the nature of the beast for that early year model. My 5.3 taps like a grade schooler with tap dancing shoes on for the first 20 seconds on fire up on a cold start. I have tried all the different weights that AMSOIL has and it doesn't change a thing.

 

Modern oils today are good for cold starting. If you are concerned at all just stick with a full synthetic.

 

You have tried AMSOIL in the past, did you know about their preferred customer program? It saves you 25% off the retail price. It is similar to Sam's Club where you pay $20 a year to be a member and you get all AMSOIL products at the wholesale cost. They even run promotions once in a while offering free shipping. PM me if you want more details.

apollo18 Enthusiast

apollo18

Posted
  • Author
Posted

Yeah it's been a great engine. 87 octane mostly Up until 290,000 kms. After that it's been mostly 91 octane.

 

 

And I'll look into that after I try the edge!'

 

Should I try edge high mileage or the EP?

High mileage seems like it's better for seals and stuff but EP is a higher quality oil

Archived

This topic is now archived and is closed to further replies.

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