Jump to content

Recommended Posts

Posted

I was just thinking of doing a stock electric fan upgrade and was looking around for info... I see alot on the older body style trucks, but nothing about the 07 and up...

 

So I was looking at my relay/fuse panel under the hood and saw that the fan high and low relays are in place as well with the main relay... the 40 amp fuses are there as well. Would the fan wires be tucked away somewhere seeing that everything else is in place... Would the ECm already be programed for them as well? I am getting tired of the clutch fan being worthless at Idle... 

 

07 GMC Yukon XL 2500 

Posted

At 1st I thought you were talking about the fan for your A/C, heater and defroster but you're not.

You're talking about the engine fan. Don't assume others know what you're talking about because you do know.

When you write you need to provide all the info you can so those of us not inside your head can know what you're taking about.

For me if the fan comes on and off in accordance with the engine's needs that's fine, it ain't broke and it it ain't broke I don't fix it.

If it's not and your engine is over heating you got a problem. It's usually a tired temp sensor or it got disconnected some how, or other wiring problem.

I have seen guys run  bigger radiators thinking a cooler engine runs better; if cooler is about 200F that's fine but if you take the t stat out and put a

bigger radiator or a fan that runs all the time you may not get up to operating temp and that's no good either.

The engineers usually got the engine cooling down to what's needed plus a little to allow for blockages.

If you're not overheating I'd leave well enough alone.

Posted
7 hours ago, dna9656 said:

At 1st I thought you were talking about the fan for your A/C, heater and defroster but you're not.

You're talking about the engine fan. Don't assume others know what you're talking about because you do know.

When you write you need to provide all the info you can so those of us not inside your head can know what you're taking about.

For me if the fan comes on and off in accordance with the engine's needs that's fine, it ain't broke and it it ain't broke I don't fix it.

If it's not and your engine is over heating you got a problem. It's usually a tired temp sensor or it got disconnected some how, or other wiring problem.

I have seen guys run  bigger radiators thinking a cooler engine runs better; if cooler is about 200F that's fine but if you take the t stat out and put a

bigger radiator or a fan that runs all the time you may not get up to operating temp and that's no good either.

The engineers usually got the engine cooling down to what's needed plus a little to allow for blockages.

If you're not overheating I'd leave well enough alone.

Im Running the stock clutch fan... I have changed the fan clutch and a new thermostat... Flushed the radiator and cleaned the AC fins and the radiator fins to make sure I have good air flow

through them. If this was a post about overheating, then I would have asked... but its not, and I didnt... Truck is a Yukon xl 2500 6.0 with 4:10 gears (stock)

 

When I idle the truck with the AC on the temps start to get hot (240+ monitored by the torque pro app) then the AC starts to get warmer... this would be an AIRFLOW ISSUE hence why I would like to go with E-Fans!!!

If I idle up the truck the temps will come down... Again AIRFLOW ISSUE! 

I have 2 aftermarket trans coolers that have fans installed, 1 is a puller and the other is a pusher. This is my 2nd NBS 2500 truck and they both had the same issue. 

I use it to pull my 6k work trailer around and when the AC is on I have this issue. without the AC on the truck seems fine. (yes I have had the AC system checked, vacuumed out and refiled to 

spec) 

 

I guess I will have to figure out the fan wiring on my own. I have found some info already that will get me started. but I did find out that I will need to have the fans activated by HP tuners 

or EFI Live... The truck is almost prewired for it (the relays and fuses are there) I just need to add 6 more wires to finish it. (Fan power, Ground and ECU triggers) Then it will work like stock

with high and low functionality. This is what I have come up with so far:

 

1- Ground Input Signal from ECM for Low Speed Cooling Fan Relay Control ?
* (Factory uses Dark Green colored wire).
* Connect to (Under hood X2 Connector Pin A1).


2- Ground Input Signal from ECM for High Speed Cooling Fan Relay Control ?
* (Factory uses Dark Blue with White Stripe colored wire).
* Connect to (Under hood X2 Connector Pin B5).



3- Output to Cooling Fan Motor Supply Voltage ?
* (Factory uses Gray colored wire).
* Connect to (Under hood X1 Connector Pin C1).

4- Output to Cooling Fan Motor Supply Voltage ?
* (Factory uses Yellow colored wire).
* Connect to (Under hood X1 Connector Pin C2).

5- Output to Cooling Fan Motor Supply Voltage ?
* (Factory uses Light Blue colored wire).
* Connect to (Under hood X1 Connector Pin D1).

6- Ground ?
* (Factory uses Black colored wire).
* Connect to (Under hood X1 Connector Pin D2).

 

Anyway... thanks for your input on the basics of a cooling system but, If you have nothing to add to the OP then please do not chime in. 

Posted

GM runs a clutch fan because it pulls more air through the radiator than even my K5L 700 watt fans.  I reckon that your two transmission coolers and their fans are blocking the air flow or your clutch fan is not working properly.

 

Are the baffles around and below the radiator still in place?  If they fall away air will pass around and not through the radiator.

Posted

Trans coolers are located under the radiator, so they are not inline with the airflow, one is a derale and the other is just a bar and plate cooler I had from a supra project I didn't use...

There is no way the clutch fan pulls more at idle then the stock 2 speed E-fans... NO Way! Clutch fan is new and it is an HD one, I even changed the fan blades. Yes baffles are there and the radiator is new. I am sick of changing parts as I have an entirely new cooling system and the problem still persists. 

 

I have just about finished the wiring for the e-fans so they will work and appear like stock with the factory supplied fuses and relays. So this thread can be closed...

 

 

  • Like 1
Posted

don,t get mad, swathdiver was just pointing out things that you may have overlooked and that because of the pitch of the blades the clutch fan WILL draw more air thru the rad than the e fans, hope the efans work out for you

  • Like 1
Posted
5 hours ago, timmy1909 said:

There is no way the clutch fan pulls more at idle then the stock 2 speed E-fans... NO Way!

 

Well, that's what one of the engineers who designed the 900s told us.

 

There are two main sets of electric fans, 500 watt motors and 700 watt motors.  The 500s used a pair of 5-blade rimless blades or 5 and 7 rimmed.  The 700s used 9 and 7 blade rimmed or a pair of 5-blade rimmed.

 

Let us know what you used and how it goes when done if you will.

Posted

I have the 9 blade dual e-fans on my other truck (03 Suburban 2500) and they far out perform the clutch fan. The Fans I use are the GT fans, the LS1's are smaller. 

 

with the e-fan truck I can sit at Idle with the AC on and its still Ice cold and the temps do not rise hardly at all like the stock clutch fan. I would be over 230 sometimes reaching 240 and the AC turns to a swamp with the clutch fan truck... Let the engineer drive each on of my trucks on a hot day and see which one he prefers... The one with the E-fans is far superior... and it did not come that way. I installed them 2 years ago with a kit that I found online... and found the fans in a junk yard for $20. The fans run at 2 speeds... and with the relays that are in my 07 that came stock with the truck it will act the same. I just have to pin and add the wires to the stock fuse/ relay panel.   

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