Jump to content

Oil Jugs with foil Seals


Recommended Posts

Posted
3 hours ago, reardiff said:

Is it just me or does anyone just cringe each time you do an oil change and have to poke open that foil seal on the oil jug, paranoid that some small sliver will find its way into the oil.  I think I spend at least 5 minutes with a razor knife making sure it's safe before I pour it, but would really like to just twist it open and pour.  I use Mobil One so i can't speak for the other brands, but why is it that the 1 quart bottles have a plastic cap but no seal, where the 5 gallon jugs always have that darn foil seal?

 

Anyone else get worked up over this or is this OCD on my part?

 

When you pay as much as we have for these trucks and add OCD? I know the feeling but as some others have done I've always used a knife to cut or peel away all evidence of foil. In the end we don't want to be those guys screaming at the top of our lungs "Foiled again!!!"

Posted
5 hours ago, tyler.frost92 said:

Yeah, you're probably the only paranoid one.

Nope me too.  Used to bother me but now not so much

Posted
4 hours ago, Skidsareforkids said:

 


Just put some in every time you fill up the gas, then you can be sure you’ll never run out emoji869.png


Sent from my iPhone using Tapatalk Pro

 

THIS, if you have the infamous AFM oil usage problem.  However, I still change it twice a year, because the oil, even though 1/3 of it is new, gets dirty every ~4000 miles.  

Posted

I like the foil seals, to ensure nobody has messed around with the product you bought.  I just wish they would come with the little pull tabs to pull off easier, and come off in one piece instead of pieces.  As it is, I just use my pocket knife to cut the seal down the middle and then remove the 2 sides and smooth any remaining edges and pour.  I get more nervous trying to pour a 5-quart jug without sloshing oil all over.  

Posted
12 minutes ago, MaverickZ71 said:

 I get more nervous trying to pour a 5-quart jug without sloshing oil all over.  

I don't like having to hold my funnel at an angle with one hand and maneuver the full 5 qt jug with the other. There's probably an easier way to do it, or a better funnel to use, but I'm lazy and I keep using the 20 cent plastic one I got 10 years ago.

Posted

There is oil in our trucks?????? I don't DIY it these days but when I did I poked a hole with my pocket knife...

Posted

Valvoline jugs or the Napa dexos that is made by valvoline in the same place has them but guess what? They have 4 little tabs so you can grab one and whole things comes off without a hitch.

 

Sub $35 oil change when stuff is on sale.

Archived

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

  • Latest Articles

  • Posts

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