Jump to content

Recommended Posts

Posted

I just purchased a 2004 GMC 2500 with a 6.0. The truck has 130k miles on it. The guy I bought it from told me the alternator needed to be replaced because it had a whine that would come through the radio. He had replaced the radio because he thought it was bad...but the whine did not go away. I replaced the alternator, but had the same issue. I then took the original alternator to be bench tested, and it tested good. I put it back in, but the alternator has a whine when accelerating and it comes through the radio. 


To troubleshoot, I unplugged the wiring clip while running...and it makes zero whine under the hood. If I reconnect the the wiring, it starts making an audible whine that sounds just like the sound coming through the speakers over whatever music may be playing.

 

It is driving me crazy...has anyone else had this issue?

Posted

The problem lies with whats called a Ground loop. The radio, for lack of a better term, is using the speakers as a ground.

 Pull the radio. If you used an adapter pigtail, make sure you Solder the power and ground leads.

 Check the ground wire size, make sure its same as power. Check the ground wire ( truck off, key out) coming to the radio, to truck ground with a ohm meter. I turn on the beep on my meter, so I don't have to look at the resistance.

 Probably a NEW ground wire from the chassis of the radio, to a GOOD truck ground, ( possibly one of the 2 cigar /12 volt outlets below) will do the trick. Good luck!

Posted

Thanks for the advice! I pulled the radio and ran a new ground to the chassis, it was a 12gauge wire. 

 

Here is the odd thing, the loudest part of the whining is coming from the actual alternator. 

It completely goes away if I unplug the electrical connector while running...and instantly comes back. 

I checked all of the body grounds, as well. 

 

Its the strangest thing I've ever seen!

Posted
Quote

Here is the odd thing, the loudest part of the whining is coming from the actual alternator. 

 

Do you hear the whining under the hood at the alternator, or is only coming through the audio system?

Posted

Both. 


I can turn the radio up and hear the hum.

I can then turn the radio off,  and go pop the hood and the same noise is coming form the alternator. 
If I unplug the connector on the alternator while running, it goes quiet. 
The whining comes back when the electrical connector is plugged back in (while running).
The alternator doesnt make any bearing noise and is fully bench tested. 
It even made the noise with the new alternator. 

Posted

Adding a capacitor ( noise suppressor) is an old trick that used to work well, and may just fix this.

( credit to Pizza)

 The Body control module ( all cab functions) GROUND is UNDER the truck, on the DS, right under the DS door

on the CAB mount Extension facing the REAR of the truck. These ground wires need to be removed and cleaned well,

and frame cleaned. After put some waterproof GREASE on it..

 Did you do this ground?

  • 1 month later...

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

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