When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Most on here use scangauge2, or equiv. Hard to pin it down with questionable ect and no eot. Everything is based on ford sensor values for coolant and oil temps.
Most on here use scangauge2, or equiv. Hard to pin it down with questionable ect and no eot. Everything is based on ford sensor values for coolant and oil temps.
Yea i understand. Im gonna work on this some more. Any Livelink experts feel free to chime in.
The numbers i have been basing this thread on were from digital gauge, quadzilla commander. This evening i ran the ect with SCT livelink and was getting an ect of 196*f, while my gauge was reading 205*f. Livelink is new to me and im unable to figure out the readings for eot.
This weekend when i heard my fan kick on it wasnt loud like many have describe on this forum, it was barely noticeable. With the readings i got tonight, im really confused and dont know what to believe.
Is the commander connected to it's own sensor? Otherwise your ECU is agreeing with it (it controls the fan) and not Livelink (which I am not familiar with)...
Yea I've read over your thread, that sucks, I'm hoping for a lesser problem. Do you know what diagnostics they ran that lead them to think cracked head gasket?
Head Gasket test was to drive the truck while checking cooling system pressure. It shot up IMMEDIATELY when the tech stepped on the go pedal.
The cracked head thing is a 'probable' - the tech said he smelled diesel in the coolant.
Is the commander connected to it's own sensor? Otherwise your ECU is agreeing with it (it controls the fan) and not Livelink (which I am not familiar with)...
The ecu uses the ect sensor for the vehicles ect values right? The ecu doesn't gather that info another way does it?
This morning on way to work my gauge was reading 205* and livelink showed a max of 192*. Livelink monitors the ecu through the odb ii port, so i would think it is accurate. My gauge is wire tapped into the ect sensor (I'll check tap).
I was thinking bad ect sensor, but that sensor is where the ecu gets that data also right? So livelink should read the same as gauge.
I don't know if just tapping into a sensor can cause an issue, but others here with more experience said that is a big No-No. Both have to convert an electric signal (volts I assume) to a numeric value. Could be different calc's...
But yes, the ODBII is the same as what the ECU is using, in fact IRRC the number is coming from the ECU...
So i went and paid 40$ for a diagnostic. They were getting ect temps 10* lower than what my gauge is reading. Their reading was the same add my livelink reading. So currently my gauge its reading 202° ect, but my livelink reads 193°. So my gauge is reading inaccurately. But thus still doesn't explain why my fan came on slightly thus weekend.
[QUOTE=emmagator;13183328 But thus still doesn't explain why my fan came on slightly thus weekend.[/QUOTE]
The oil temp also factors into the fan speed. So if you can't read the engine oil temp with the odb reader you have you are stuck. Also be aware the engine will defuel if oil temp gets too high.
So i went and paid 40$ for a diagnostic. They were getting ect temps 10* lower than what my gauge is reading. Their reading was the same add my livelink reading. So currently my gauge its reading 202° ect, but my livelink reads 193°. So my gauge is reading inaccurately. But thus still doesn't explain why my fan came on slightly thus weekend.
The fan does come on every once in a while and that is normal, but it isn't an on/off thing the fan is variable speed and sometimes you won't even notice it. You shouldn't have any spliced wires to OEM sensors.
Do you have a Droid phone by any chance? or an Iphone, or either one in a pad device? It's not much to get the app that would give you a whole new view into what is going on under the hood. I'm becoming less and less of a Scangauge promoter -- it's just what was 1st available to do this sort of thing and is really basic and hard to set-up. If you have an Android phone go out and buy Torque pro for $4.95 and a bluetooth ODBII connector (ELM 327 v1.5 or higher) for maybe $12 and get the Ford specific PIDs that come free with Torque. Or if you have an Iphone or tablet get DashBoss and it's data gateway ($150ish). Fan speed is just one of many things you can just select to monitor in real time; or if you wish put to a log file for analysis later, and it is JUST a pick and click operation with cool gauges to choose from...
Best money I've spent very little of almost ever....
The fan does come on every once in a while and that is normal, but it isn't an on/off thing the fan is variable speed and sometimes you won't even notice it. You shouldn't have any spliced wires to OEM sensors.
Do you have a Droid phone by any chance? If you have an Android phone go out and buy Torque pro for $4.95 and a bluetooth ODBII connector (ELM 327 v1.5 or higher) for maybe $12 and get the Ford specific PIDs that come free with Torque. Or if you have an Iphone or tablet get DashBoss and it's data gateway ($150ish). Fan speed is just one of many things you can just select to monitor in real time; or if you wish put to a log file for analysis later, and it is JUST a pick and click operation with cool gauges to choose from...
Best money I've spent very little of almost ever....
Yes i have a droid, ill check into that. I didnt know the fan was variable. From what ive read, some guys say it sounds like a jet taking off when the fan comes. It being variable makes sense, i was possibly hyper aware of it because the ect values my gauge was giving me so maybe i noticed the fan a little more. But when it came on it wasnt loud at all, barely noticeable over engine noise with radio off.
Im going to continue to investigate this situation and get my gauge figured out. Its not actually a splice, if that matters, but a wire jumper. It clips onto the ect sensor wire poking through making contact with wire.
. Its not actually a splice, if that matters, but a wire jumper. It clips onto the ect sensor wire poking through making contact with wire.
quote]
The Fact remains the SAME
You or Someone spliced into the circut One Way or Another this Adds Extra wire to the Circut and also Adds More Electrical Resistence with the Added wire
The PCM Uses Electrical voltage to sent too and from each sensor The return Voltage will be the sensor operating value
The More wire the return signal has to go threw the more resistence you have and the Bigger the voltage drop will be
Odds are Both Gauges are reading wrong The Gauge reading off the OBDII Port is likely the closest but could be Off some
Alsp the fan is always turning.
Typically 300-600 rpm always.
800-900 sometimes when up to temp and a/c is on. Really need sg2 or odb2 reader otherwise you are either worrying about everything or unaware of what -may - actually be wrong.
The ecu uses the ect sensor for the vehicles ect values right? The ecu doesn't gather that info another way does it?
This morning on way to work my gauge was reading 205* and livelink showed a max of 192*. Livelink monitors the ecu through the odb ii port, so i would think it is accurate. My gauge is wire tapped into the ect sensor (I'll check tap).
I was thinking bad ect sensor, but that sensor is where the ecu gets that data also right? So livelink should read the same as gauge.
The readings are less than 7% different. I'll bet that's well within the advertised accuracy of the gauge.
If you used a blue "snap tap" to connect the wire you may want to replace it. Those things are terrible. Guaranteed to be a problem sometime in the future.
There's no such thing as too big a wire. The gauge can add load (amperage) to the circuit reducing the voltage back to the PCM and cause it to read wrong, but because it is parallel it doesn't add resistance. If the gauge were wired in series it would(could) add resistance.