Jump to content

09 Equinox - Noise Heard From Front End?

steve19

Recommended Posts

steve19 New Member

steve19

Posted
Posted

Hey everyone,

 

I recently picked up an 09 Equinox LS model and have finished the break in. I currently have 3800km on it. I have just started to hear a sound which I'd like to ask others about.

 

When I start up the vehicle after being cooled down for more than 20min, I hear a 'cling/boing' sound as I accelerate and hit 18km/h (only at 18km/h); sounds like a spring in the front end? I do not hear the sound ever again unless I cool the engine down for 20+ minutes and start it up again. Once the vehicle is warmed up and I am stopping at intersections and accelerating, I will not hear the sound at 18km/h. If I shut the vehicle off for 5 minutes, and then start it up again, I will not hear the sound; i strictly hear it only when it is cooled down for more than 20+ minutes.

 

What could it be?

 

Thanks!

  • 1 year later...
buckshot44 Enthusiast

buckshot44

Posted
Posted

I've got a 09 Equinox and also hear a sound when accelerating after it's been sitting for a while. Sounds like the same thing you're experiencing. I've never paid attention to the spead at which the sound comes on, I just know it happens every morning when I leave for work. It's like a spring release noise. I've had it into the dealership many times but they have never been able to "reproduce" the problem.

It's been happening ever since we bought it, brand new last year.

 

If you find out what it is, please share as it kind of scares me.

 

See the thread I started about it here:http://www.gm-trucks.com/forums/index.php?...&hl=equinox

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

take it in and road test with a dealer service dept staff mainly the shop foreman or service manager,

 

that goes for you to brian

  • 2 weeks later...
buckshot44 Enthusiast

buckshot44

Posted
Posted

Took it into the shop today and was able to reproduce the problem. I actually dropped it off at the shop last night so I could simulate the "cold start" that it requires. This "click" happens every morning when I leave for work, but is very hard to reproduce after driving for a while.

 

The guys at the dealership said they were able to reproduce the noise at least twice today and that makes me feel good. They are booking it in next Thursday when I can receive a courtesy car for a few days while they figure it out.

 

I'll be sure to post the results here.

  • 1 month later...
buckshot44 Enthusiast

buckshot44

Posted
Posted

Ok.. finally I have an answer about the noise. After numerous attempts, the dealership shop finally figure it out. It's the ABS Self Test that makes the "clank" noise, and it only happens after it's been sitting for a while. ABS engages at 18km/hr, so that explains why the noise only happens then and only when cold. I feel better now, knowing it's "normal", but it's still annoying. You'd think it would be a quiet self test, but it's not.

 

Hope this helps someone else wondering about their equinox mystery noise.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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