Jump to content

Recommended Posts

Posted

Im blown away with how many service reps  / dealers dont have a clue about greasing the front end zerk fittings on the 2500 HDs. Thank goodness the dealers 1 "Diesel guy" knew . Why is this? Id imagine most folks dont know so they dont ask for it etc? 

Posted
1 hour ago, SpaceCoastTony said:

Im blown away with how many service reps  / dealers dont have a clue about greasing the front end zerk fittings on the 2500 HDs. Thank goodness the dealers 1 "Diesel guy" knew . Why is this? Id imagine most folks dont know so they dont ask for it etc? 

 

 

99% of the rest of the GM lineup doesn't use them anymore, so the lube techs are often blind to them.  The 1500's haven't had fittings since 2019.  The 2007-2018 1500s they only used fittings on the outer tie rod ends and everything else was sealed. 

 

Other HD trucks on the market (Ram and Ford) don't have any to begin with either, so nothing to grease on those.  GM is the only 3/4 and 1 ton truck left with grease fittings on front suspension components.  

 

 

  • Like 1
Posted
Quote

yea , I understand that but the 2500/3500 still have them and i just felt more than 1 person at a dealership should know this...  at least the service rep had a good attitude about it and said he learned something new . Hes been there 5 years tho.. 

 

  • Like 1
Posted
On 12/23/2025 at 5:57 PM, SpaceCoastTony said:

 

 

I haven't been bringing my chev 3500 to the dealer or anywhere else for that matter for service since I prefer to do my own oil changes and greasing so I know its been done and I know what oil actually went into the engine etc and that no one had "checked" my air filter for example and loosened the intake duct hose clamp off or stripped out the screws that hold the cover on into the plastic housing below, or installed the filter sloppily and is now allowing dirt to pass by the filter for example ( l live on a gravel road in a rural farming area ... I farm after all ). I just don't trust some of the staff that work those bottom of the barrel positions in the lube bay. 

 

Service reps are typically not mechanics and they are reading what is in front of them on their computer, I am sure some have quite a bit of knowledge but there would be enough of them that certainly wouldn't have a clue. So then it comes down to the person in the lube bay and how the shop itself views the whole thing, do they credit the lube tech for doing a grease job on an HD truck vs a 1500 that has no zerk fittings .. good question. Certainly not every truck owner would even know if their own truck had grease zerks or not because many people do not work at all on their own vehicles and rely on a shop to do it for them and hoping they are doing a proper job of it. I've certainly heard the comment before from GM HD owners clued into the fact that the dealer was not greasing their truck during an oil change and so had asked why not ... the answer in one instance was and of course that would be from a service advisor was "oh that's not part of the oil change package". 

 

So the long and short is one has to know for one thing that those zerks exist and then each time one would bring it in if it was a GM dealer or some other shop, to specify and have them put that in writing in their system that the customer wants all steering/suspension grease points greased. Then look after the fact to see if anything was done, which goes full circle to why I skip all that crap and just do it myself or as long as I am able to anyway.  

  • 4 months later...
Posted

Serviced my 2024 over the weekend and I hit the grease zerks with a couple pumps each. I try to do them every 10,000-15,000 miles. usually every other oil change.

 

Made a quick video pointing them out for anyone interested. Hope it helps. 

 

 

  • Like 2
  • Thanks 1

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...