Jump to content

Sounds like my blinkers are on in my engine

haider320

By haider320
in Troubleshooting & Recalls

Recommended Posts

haider320 Enthusiast

haider320

Posted
Posted

230 miles on my new 18.  Just started hearing the noise yesterday.  On a cold start, it literally sounds like my blinkers are on. The sound is coming from the bottom of the engine on the drivers side.  Once the engine is warmed up, the sound goes away.

 

I cant hear the sound from inside the cab. Only reason I heard it yesterday, is because as soon as I started the truck, I got out to run back into the house.

 

Exhaust leak?  

BigBadSierra Senior Enthusiast

BigBadSierra

Posted
Posted

Direct injection.... The injectors are loud they get better when they warm up. Since they are direct injection they operate at a much higher pressure.

 

I've been hear this in my last four vehicles they all had direct injection.

 

it's normal.

 

haider320 Enthusiast

haider320

Posted
  • Author
Posted
12 minutes ago, BigBadSierra said:

Direct injection.... The injectors are loud they get better when they warm up. Since they are direct injection they operate at a much higher pressure.

 

I've been hear this in my last four vehicles they all had direct injection.

 

it's normal.

 

Thank you sir

haider320 Enthusiast

haider320

Posted
  • Author
Posted

After listening more, I don't think it's the injectors.  Listen to this clip and you can hear the blinker sound.  Goes away once the truck is warm.

 

Here is a link from YouTube. It sounds like a blinker.

Watch "2018 Chevy knock" on YouTube
https://youtu.be/dqqfRdke9Yk

mikedeezxxx Enthusiast

mikedeezxxx

Posted
Posted
After listening more, I don't think it's the injectors.  Listen to this clip and you can hear the blinker sound.  Goes away once the truck is warm.
 
Here is a link from YouTube. It sounds like a blinker.
Watch "2018 Chevy knock" on YouTube


My wife’s 2018 Durango RT makes that same noise. Only does it on cold starts. Gonna have dealer address it at first oil change coming up.


Sent from my iPhone using Tapatalk
haider320 Enthusiast

haider320

Posted
  • Author
Posted

I'm wondering if it's the heat shields around the exhaust expanding?  It's a consistent sound, like a blinker. 

haider320 Enthusiast

haider320

Posted
  • Author
Posted
34 minutes ago, paumat said:

Vacuum pump?

 

34 minutes ago, paumat said:

Vacuum pump?

As in going bad?

haider320 Enthusiast

haider320

Posted
  • Author
Posted
13 minutes ago, 300 Blackout said:

If you could record it and post a video that would help

I did.  It's the YouTube link 7-8 posts above.  

300 Blackout Enthusiast

300 Blackout

Posted
Posted

Ok, that does not sound like a relay to me. I agree that the consistency and tone are similar.

This is what the inside of your vacuum pump looks like. The center vane rotates and slides as it rotates. If for some reason this was binding or there was debris lodged somewhere within the oil grooves, it may make a consistent ticking noise similar to what you are observing. I’m not convinced this is the culprit though and need some more info.

Does the frequency of the tick increase with engine RPMs?79632f9df4031c73803fdad746560229.jpg

haider320 Enthusiast

haider320

Posted
  • Author
Posted
1 hour ago, 300 Blackout said:

Ok, that does not sound like a relay to me. I agree that the consistency and tone are similar.

This is what the inside of your vacuum pump looks like. The center vane rotates and slides as it rotates. If for some reason this was binding or there was debris lodged somewhere within the oil grooves, it may make a consistent ticking noise similar to what you are observing. I’m not convinced this is the culprit though and need some more info.

Does the frequency of the tick increase with engine RPMs?79632f9df4031c73803fdad746560229.jpg

I tried to listen to it while pressing on the accelerator.   The engine ended up drowning out the sound, so i couldn't tell if it increased with rpms.   What i dont understand, is the sound goes away once the truck is up to normal temperature. 

 

The sound seems to be coming from the drivers side, down by the exhaust.  

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      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? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      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. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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