Jump to content

Whistling from Corsa at 4500-5000rpm?

Payton34

By Payton34
in Modifications & Accessories

Recommended Posts

Payton34 Enthusiast

Payton34

Posted
Posted

I had my exhaust installed for 2 weeks and I gunned it last weekend and before it shifts from 4500-5000rpm there is a loud whistle from the exhaust through each gear? I called Corsa and they said there was a issue which they redesigned the muffler but my serial# is the new design. I checked and see no leaks its a loud almost similar sound as a slipping serpentine belt.

jeffsig Enthusiast

jeffsig

Posted
Posted

I want to say I've heard this with my Borla, but it quickly went away on its own. Don't know.

TheTunaHunter Enthusiast

TheTunaHunter

Posted
Posted

My Corsa sport (dual side exit) took a couple thousand miles to break in. During that time, the tone/sound's definitely changed. Yes, I have the helicopter noise and the V4 Burble sometimes, but certainly not the "whistling" you describe. As mentioned, I would check all of your clamps, especially the first one closest to engine. Also maybe make sure you have the muffler in the correct orientation, weep hole on bottom (not sure if this could make the noise your describing)-Good luck, hope it's something quick/easy!

Payton34 Enthusiast

Payton34

Posted
  • Author
Posted

I called Corsa and they said they were aware of the whistle issue on earlier mufflers but my Serial # shows its the newer design. I sent them a video they requested just waiting to hear back. All clamps are to torque specs and no leaks muffler is installed with weak hole bottom rear of muffler.

I have to say I always loved the Corsa on my 2000 and 2005 trucks but this 2014 is much louder from in the cab. Even under normal acceleration it is very loud can't really hear the radio well. My old trucks I hardly heard it inside but it was nice and loud outside. The 2014 trucks stock are way quieter then older body style trucks so I can't understand why this system is so loud and annoying. The drone in 4cyl mode is almost unbearable.

TheTunaHunter Enthusiast

TheTunaHunter

Posted
Posted

I'd say it took a couple thousand miles for the exhaust to quiet down. I will admit, the cold start still brings a smile to my face!

Payton34 Enthusiast

Payton34

Posted
  • Author
Posted

I was told by one person the 6.2 will make the exhaust much louder than a 5.3. The sound on the inside sounds like I have a cheap glass pack exhaust not the Corsa sound I am used to. I have heard a Ford Raptor 6.2 with a Corsa on the inside and its similar to how my old truck with a 5.3 sounded inside.

Payton34 Enthusiast

Payton34

Posted
  • Author
Posted

Well Corsa called back and the engineer said there must be a design issue in the case of the muffler on the 6.2 exhaust. They are redesigning the muffler and will send me the first one when ready.

Archived

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

Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   5 Members, 0 Anonymous, 1,931 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...