Jump to content

Can I swap-in an 04 alternator in my 01?

elgineddie

Recommended Posts

elgineddie Enthusiast

elgineddie

Posted
Posted

Hey there team,

I have a 2001 K2500 Burban and it's had a stupid alternator whine for a long, long time and I'm ready to fix it. It happened way back when I powerwashed the engine bay, even though I used low pressure and avoided the electrical things. I've been waiting for the bearing to go out but it hasn't. I initially thought it was the power steering pump but had that replaced when the pump shaft sheered off. Whine still there. So I just bought an alternator on eBay tonight for $100 shipped. It's an OEM Delphi unit but from an 2004.

 

Anyway, back to my original question. Based on the pictures it looks like it'll bolt right up but when I checked on partsdirect.com they have different part #'s. Anyone know if it'll bolt up for certain?

For the price, I'll be willing to give it a shot and if it doesn't fit, I'll just resell it on eBay.

 

Thanks!

citydriver Enthusiast

citydriver

Posted
Posted

It should fit, as long as the clock position of the mounting lugs is correct....The different part numbers may be due to different amperage output........just a guess

Jacqson Enthusiast

Jacqson

Posted
Posted
It should fit, as long as the clock position of the mounting lugs is correct....The different part numbers may be due to different amperage output........just a guess

 

 

 

 

Yeah, I tend to agree, the type of alternator in your Sub would depend on the accessories and the engine size which could give the same looking alternator a different part number than the one you have or GM could have changed up the number from 01 to 04. If it mounts up properly then it should work for you although as citydriver said; the amperage output may be different. :crackup:

Wingnut Senior Enthusiast

Wingnut

Posted
Posted

I hate to bring this up now...But are you sure it's the alternator? The tensioner pulleys are usually the first things to go on these rigs. Both of them. Yup, there's one underneath on some of the trucks (from the crank to the AC compressor, and another tensioner pulley). That's a hard sound to directionify. Yes, that's a word. Wingnuts new word of the day. :crackup:

 

I just did the bottom one Sunday, and you have to take the top belt off to get the bottom belt off :crackup: .

 

Just thought I'd ask anyway.

elgineddie Enthusiast

elgineddie

Posted
  • Author
Posted

Thanks guys! I love this 'board!

 

I am thinking you are all right. It's 15 amps more than my 130, so that could be the part number difference. Regarding the tensioners, I already changed those, but I did so trying to chase an odd belt chip at startup! Either way it didn't effect the whine.

 

I'll keep y'all posted if the alternator doesn't fix the source of the whine. Based on my searches online, it can also possibly be the fan. (!?)

 

Later!

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   4 Members, 0 Anonymous, 2,066 Guests (See full list)

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