95 5.8 liter Trouble code 133

Today I did the self-test, and got the code 133. This apparently means the AIR CHARGE TEMPERATURE SENSOR signal is greater than the self-test maximum of 4.6 volts.
So I look at the photo in my Haynes manual then look at my motor. There is a threaded plug in the manifold where the one in the photo is. I looked all over that manifold and can't find something that looks like the ACTS.
Anyone know where the rascal is? Or do I even have one?
Thanks, John
PS To Lugnut - I totally understand if you're sick and tired of responding to my threads.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On Mon, 16 Jul 2007 14:07:22 -0700, john

No problem. The ACT should be either in one of the left bank intake runners near the cylinder head, in the side of the air cleaner housing or in the air intake tube. Now, are you sure about that code? The only listing I can find for 133 is high voltage for the EGR sensor which is fairly common failure and can cause some weird idle problems. The sensor is called the EVP sensor (egr valve position). I have had several that did not work correctly but none, stored a fault code because of their relativel wide range of operation. If this is the code, the EVP sensor is located on the top of the EGR valve at the right front of the engine. I'll doublecheck this code later. If it is the problem, the EGR valve may be open when it should not be causing the high idle. It does not make sense the shop did not come up with this code unless the ECM had adapted to it previously and now it is so far out of range it can no longer adapt after being reset.
Lugnut
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

As fas the code, using the self-test method as described on http://www.fordfuelinjection.com/ yeah, I'm pretty sure that's the right code. I also used their 3-digit code definitions grid. 133 is high voltage to the ACTS, according to the site.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On Mon, 16 Jul 2007 18:40:04 -0700, john

Then the code must have been 113 - not 133?
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

My mistake. The code I'm getting is 133. Repeat 133. The method I'm using gives me a single CEL pulse, followed be three more pulses. This pattern is then repeated.
Maybe I'm doing it wrong, because I can't find a description for DTC 133.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
john wrote:

I'll bet my hat you are seeing this: 1-1-1 (pass).... 1-1-1(pass)......1 (separator)........1-1-1 (pass).....1-1-1(pass) and interpreting it wrong. (This is actually a "system Pass")
The output sequence is for the KOEO Self Test is: KOEO codes repeated twice........separator code.......Continuous memory codes repeated twice.
111 is a pass code, meaning No Codes Stored. Looks like you are counting the separator as a 1, and each 111 as a 3. You're not seeing any other digit except a ONE. It's hard to show the pauses between flashes that make up other digits here, but I'll try:
111- 1....1....1 333- 1..1..1.....1..1..1.....1..1..1
Try disconnecting, say, the MAP sensor connector and running the test again. This should set a code 126 in the KOEO and possibly in Contimuous Memory, You'll see:
1....1..1....1..1..1..1..1..1.......1....1..1....1..1..1..1..1..1 (Code 126 KOEO code, repeated twice)
...........1......... (separator code between KOEO and CONT Memory tests)
1....1..1....1..1..1..1..1..1.......1....1..1....1..1..1..1..1..1 (Code 126 Continuous Memory,repeated twice) The Code 126 may not set here unless the engine is started. In that case you will get a 1..1..1....1..1..1 here (111 pass)
Whew, I sure hope that makes sense.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

Yes, Tom, you may be right. The first "1" CEL flash is very quick and fleeting, so if that is disregarded, it's code 111. I'm thinking my best chance is to have it read during a KOER. That's when I get 4 distinct CEL flashes. Apparently nothing is being stored long term.
It still starts normally, idles at about 750 rpm for about 5 secs, then off to 1500 rpm for 1 to 2 minutes now. Then back to normal until it is shut down for 15 to 30 minutes. Any ideas?
I use Google groups to post, and stuff is showing up 2 days late for some reason. This post is out of place because I can read new posts timely through another portal, but can only post on Google.
Thank you! John
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
john wrote:

That fast flicker is the "fast codes" being output. If you were using the Ford scan tool, they would show on the screen right after that pulse. Ignore it.
During the KOER test, the 4 flashes you see first is the engine ID code.( 2 for 4cyl, 3 for 6 cyl, and 4 for 8 cyl.) When you see the ID code, turn the steering wheel in both directions about 1/2 turn, step on the brake and release, and press the OD cancel switch twice. The PCM is looking for these inputs at that time. If you don't do this, it will set some codes for the PSPS, BOO, and OD cancel switches.
You may see a single flash after about 20 seconds. That's a prompt for a "dynamic response" to test the TPS. Just give a very brief full throttle application. All the way down and release. If you don't do this, a TPS code will set. It doesn't always ask for this and the flash may actually be the first part of a fault (or pass) code. If you do a dynamic response there, there's no harm done.
Oh, if the idle jumps up as you describe during the KOER test, that's the PCM heating up the O2 sensors.
I can't see your original post. Did you replace the Idle Air Control valve? Many people suggest cleaning them, but that's a real crapshoot. Even if it works at first, it usually doesn't last. You may also want to check the TPS manually with an analog meter. They can get flaky and not set a fault code. Kind of like a dirty volume control on a TV or radio that gets scratchy at the spot you usually have it set to. The TPS can get flaky at or near the idle position because that's where it gets the most wear.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

Tom, I did put a new IACV in. It had no effect, so I put the almost new one back on, and returned the new one.
Lugnut and Tom, here's where I am now. I took it to a Ford dealer today. The guy spent about 2 hours on it. I went back into the service bay with him, and he explained what he could do, testing voltage to the TPS for example, and looking for codes.
He can't find anything! He says the ECM is resetting after the idle run up, and wiping any potiential codes out. SO.........he wants me to leave it for a day or two so he can hookup a "breaker" box. He says that's the best chance to test each circuit. He will have to stop and start the motor for each circuit test (because the problem only occurs at startup). Meaning time, meaning at least $315 just for testing.
Not a great day. Not a great two weeks.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

My mistake. The code I'm getting is 133. Repeat 133. The method I'm using gives me a single CEL pulse, followed be three more pulses. This pattern is then repeated.
Maybe I'm doing it wrong, because I can't find a description for DTC 133.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

Related Threads

Motorsforum.com is a website by car enthusiasts for car enthusiasts. It is not affiliated with any of the car or spare part manufacturers or car dealers discussed here. All logos and trade names are the property of their respective owners.