Bronco Forum - Full Size Ford Bronco Forum banner

1 - 9 of 9 Posts

·
Registered
Joined
·
76 Posts
Discussion Starter #1
Ever since I replaced my 302 my check engine light has been on since the first fire up. I pulled the codes and am getting a P0414 and P0417, secondary air intake system shorts in the A and B circuits. My question is where the wires for this would be located, and is it related to that black cylindrical check valve at the back of the block? What are the consequences of not addressing this? I am not an expert on all of this, I just know enough to be dangerous :doh:
 

·
Super Moderator
Joined
·
25,823 Posts
yo,
I had to re-boot twice because of Comcast..so, here is a quickie in case I get trashed again
What are the consequences of not addressing this?
Your Emission Controls will be in an open loop procedure, the extra unburnt gasoline will usually cause your exhaust to smell rich,

Overview & Diagram; "...Secondary Air Injection system consists of a belt-driven Air Pump, single or dual AIR Diverter (AIRD) valve(s), an AIR Bypass (AIRB) valve, and AIR Bypass solenoids, air silencer/filter, Powertrain Control Module and connecting wires and vacuum hoses. The Belt-Driven Secondary Air Injection system provides either upstream/bypass air or upstream/downstream/bypass air. The number of these system configurations vary significantly with AIR Bypass (AIRB) and AIR Diverter (AIRD) valve combinations (Figure 179). 2. The PCM provides one or more signals that enable one or more AIR Bypass solenoids. 3. The AIR Bypass solenoids control one or more AIR Bypass valves and/or AIR Bypass Diverter Valves in order to route secondary air depending upon the specific configuration. 4. The belt-driven Air Pump is operational any time the engine is running..." "...The 2ndry air system is known to fail in a wide variety of ways. The check valves that prevent hot exhaust from entering the rubber hoses age, rust, leak, & crack open melting the plastic TAB & TAD valves, creating exhaust leaks that can damage other components, raising exhaust oxygen levels (setting lean codes or rich adaptive limit codes), and making rattling noises. The hard steel tubing between the exhaust & the check valve can rust or crack (especially the infamous "crossover tube" on the backs of V8 heads). The vacuum controls leak (including the coffee can reservoir on the R wheelwell) (Miesk5 NOTE, this is the Vacuum Reservoir (VRESER), it stores excess vacuum to prevent rapid fluctuations and sudden drops in a vacuum signal, such as during acceleration) get misrouted during other repairs, or the diaphragms rupture. The electronics that control the vacuum controls can fail electrically or mechanically, or the wires can be damaged. But all of these failures are either A) relatively cheap & easy to repair, or B) cheap & easy to prevent with normal inspection & maintenance..."
read more & see diagram(s)
Source: by Steve83 (Steve, That dirty old truck) at SuperMotors.net


Read more about it and the Thermactor Air Bypass (TAB) Solenoid (AIRB) / Thermactor Air Diverter (TAD) Solenoid (AIRD) and their assoc. valves in my site @ http://www.broncolinks.com/index.php?index=416
DIAGNOSTIC TROUBLE CODES (DTCS) P0413, 0414, 0416 AND 0417: CHECK VOLTAGE OF VPWR CIRCUIT

AIRB/AIRD circuits shorted to power.
AIRB/AIRD circuits open or shorted to ground.
AIRB/AIRD resistance out of range.
Damaged Powertrain Control Module (PCM).
DTCs P0413, 0414, 0416 and 0417 indicate that voltage output for Secondary Air Injection solenoid(s) did not change when activated.

Possible causes:

Disconnect AIRB/AIRD solenoid connector.
Key on, engine off.
Measure voltage between VPWR circuit and battery ground of one solenoid, then repeat for the other solenoid.
Is each voltage greater than 10.5 volts? Yes No
GO to HM76 . SERVICE open harness circuit. RECONNECT both solenoids. RERUN Quick Test.

HM76 MEASURE AIRB/AIRD SOLENOID RESISTANCE
Key off.
Disconnect both AIRB/AIRD solenoid connectors and measure both solenoid resistances.
Is each resistance between 50 and 100 ohms? Yes No
GO to HM77 . REPLACE AIRB/AIRD solenoid assembly. RECONNECT both solenoids. RERUN Quick Test.


HM77 CHECK CIRCUIT CONTINUITY
Key off.
Disconnect Powertrain Control Module (PCM). Inspect for damaged or pushed out pins, corrosion, loose wires, etc. Service as necessary.
Install breakout box, leave PCM disconnected.
Measure resistance between AIRB circuit at breakout box and AIRB circuit at vehicle harness connector.
Measure resistance between AIRD circuit at the breakout box and AIRD circuit at vehicle harness connector.
Is each resistance less than 5.0 ohms? Yes No
GO to HM78 . SERVICE open harness circuit. REMOVE breakout box. RECONNECT PCM and both solenoids. RERUN Quick Test.


HM78 CHECK FOR SHORT TO GROUND
Key off.
Breakout box installed, PCM disconnected.
Disconnect Scan Tool.
Disconnect both AIRB/AIRD solenoids.
Measure resistance between AIRB circuit at the breakout box and Test Pins 51, 91 and 103. Measure resistance between AIRD circuit at the breakout box and Test Pins 51, 91 and 103 at the breakout box.
Is each resistance greater than 10,000 ohms? Yes No
GO to HM79 . SERVICE short to ground. REMOVE breakout box. RECONNECT PCM and AIRB/AIRD solenoids. RERUN Quick Test.


HM79 CHECK FOR SHORT TO POWER
Key off.
Breakout box installed, PCM disconnected.
Both AIRB/AIRD solenoids disconnected.
Measure resistance between AIRB circuit at the breakout box and Test Pins 71 and 97. Measure resistance between AIRD circuit at the breakout box and Test Pins 71 and 97 at the breakout box.
Is each resistance greater than 10,000 ohms? Yes No
REPLACE PCM. REMOVE breakout box. RECONNECT both solenoids. RERUN Quick Test. SERVICE short to power. REMOVE breakout box. RECONNECT PCM and AIRB/AIRD solenoids. RERUN Quick Test. If DTC is present, REPLACE PCM.

------------
... that black cylindrical check valve at the back of the block? ...
That is prob the Vapor Management Valve in the Evaporative System ; it is located on passenger side firewall, high in our 96 5.0L

Depiction w/Port Identification; miesk5 note the Vapor Management Valve (EVAP SYS) miesk5 note; for OBD II, The vapor management valve (VMV) replaces the canister purge valve used in EEC IV
Source: by Steve83 (Steve, That dirty old truck) at SuperMotors.net

 

·
Registered
Joined
·
76 Posts
Discussion Starter #3
Alrighty I will go over it to see. Thank you! What issues are you having with Comcast? I worked for them for 9 years so I can help you with that
 

·
Registered
Joined
·
76 Posts
Discussion Starter #4
------------
... that black cylindrical check valve at the back of the block? ...
That is prob the Vapor Management Valve in the Evaporative System ; it is located on passenger side firewall, high in our 96 5.0L
Nah I am stupid, I see what I was referring to is the bypass/diverter valve.
 

·
Super Moderator
Joined
·
25,823 Posts
yo!
I have to see if I have the pin-outs for all above later...For pin-point test/ pin-outs, etc, Suggest you buy a Ford Bronco Electrical and Vacuum Troubleshooting Manual (EVTM), Powertrain Controls and Emission Diagnosis Manual (PCED) CD or DVD from Steve83, E bay
Best ~$7.00 to $10.00 you'll ever spend on the Bronco repairs.



I'll let you know another day about All the cable issues here in da woods. Basically, a neighbor has a CC truck at his home about 3 times a month; prob a relative, maybe something other than...
We have had an improvement since last CC teckkie came over and found that the pref tech installed the PC cable so it ran thru a CC amplifier; after that was re-routed direct to the PC, speed has increased, but it still slows dn to a crawl; like dial-up speeds in 1996
The ICSI Netalyzr
Summary of Noteworthy Events –
Major Abnormalities
Your DNS resolver returns results even when no such server exists
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
We received unexpected and possibly dangerous results when looking up important names


Address-based Tests +
NAT detection (?): No NAT Detected
DNS-based host information (?): OK

Your global IP address is xxxxxxxxxxxx and matches your local one. You are not behind a NAT.
Reachability Tests –
TCP connectivity (?): NoteDirect TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.

Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.

TCP ports are not renumbered by the network.
DNS-based host information (?): OK
You are not a Tor exit node for HTTP traffic. You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should only be sending authenticated email, email through the ISP's mail server, or using webmail. The SORBS DUHL believes you are using a dynamically assigned IP address.
NAT detection (?): No NAT Detected DNS-based host information (?): OK
Reachability Tests –
TCP connectivity (?): NoteDirect TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.

This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
Miesk5 NOTE; we had an X 10 Sec cam once and it's Motion Sensor went nutz and it took pics every sec and e mailed them to us. So CC shut our e mail down. We del the auto e mail X 10 feature and contacted CC; they said they would take us off the X list... forget what it was titled... But...


The applet received the following reply instead of our expected header:
"220 AVG ESMTP Proxy Server 9.0.782/9.0.829 [271.1.1/2932] " Direct TCP access to remote DNS servers (port 53) is allowed. Direct TCP access to remote HTTP servers (port 80) is allowed. Direct TCP connections to remote POP3 servers (port 110) succeed, but do not receive the expected content.

The applet received the following reply instead of our expected header:
"-ERR AVG POP3 Proxy Server: Cannot connect to the mail server! " Direct TCP access to remote RPC servers (port 135) is blocked.

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed. Direct TCP access to remote SNMP servers (port 161) is allowed. Direct TCP access to remote HTTPS servers (port 443) is allowed. Direct TCP access to remote SMB servers (port 445) is blocked.

This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed. Direct TCP access to remote secure IMAP servers (port 585) is allowed. Direct TCP access to remote authenticated SMTP servers (port 587) is allowed. Direct TCP access to remote IMAP/SSL servers (port 993) is allowed. Direct TCP access to remote POP/SSL servers (port 995) is allowed. Direct TCP access to remote OpenVPN servers (port 1194) is allowed. Direct TCP access to remote PPTP Control servers (port 1723) is allowed. Direct TCP access to remote SIP servers (port 5060) is allowed. Direct TCP access to remote BitTorrent servers (port 6881) is allowed. Direct TCP access to remote TOR servers (port 9001) is allowed. UDP connectivity (?): OKBasic UDP access is available.

The applet was able to send fragmented UDP traffic.


The applet was able to receive fragmented UDP traffic.
Direct UDP access to remote DNS servers (port 53) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote MSSQL servers (port 1434) is allowed. Path MTU (?): OKThe path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1500 bytes.


TCP connectivity (?): Note UDP connectivity (?): OK Path MTU (?): OK
Network Access Link Properties +
Network latency measurements (?): Latency: 17ms Loss: 0.0%The round-trip time (RTT) between your computer and our server is 17 msec, which is good. We recorded no packet loss between your system and our server. TCP connection setup latency (?): 20ms
The time it takes your computer to set up a TCP connection with our server is 20 msec, which is good. Network background health measurement (?): no transient outages
During most of Netalyzr's execution, the applet continuously measures the state of the network in the background, looking for short outages. During testing, the applet observed no such outages. Network bandwidth measurements (?): Upload 7.9 Mbit/sec, Download 14 Mbit/sec
Your Uplink: We measured your uplink's sending bandwidth at 7.9 Mbit/sec. This level of bandwidth works well for many users.
Your Downlink: We measured your downlink's receiving bandwidth at 14 Mbit/sec. This level of bandwidth works well for many users. Network buffer measurements (?): Uplink 229 ms, Downlink 150 ms
We estimate your uplink as having 230 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic. We estimate your downlink as having 150 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

Network latency measurements (?): Latency: 17ms Loss: 0.0% TCP connection setup latency (?): 20ms Network background health measurement (?): no transient outages Network bandwidth measurements (?): Upload 7.9 Mbit/sec, Download 14 Mbit/sec Network buffer measurements (?): Uplink 229 ms, Downlink 150 ms
HTTP Tests +
Address-based HTTP proxy detection (?): OKThere is no explicit sign of HTTP proxy use based on IP address. Header-based HTTP proxy detection (?): OKNo HTTP header or content changes hint at the presence of a proxy. HTTP proxy detection via malformed requests (?): OK
Deliberately malformed HTTP requests arrive at our server unchanged. Thus, the proxies along your path are able to transparently forward invalid HTTP traffic.
File type-based filtering (?): OK
We did not detect file-content filtering. HTTP caching behavior (?): OK
There is no suggestion that a transparent HTTP cache exists in your network. JavaScript-based tests (?): OK
The applet was not run from within a frame. Your web browser reports the following cookies for our web page:
netAlizEd = BaR (set by our server)
netalyzrStatus = running (set by our server)
Your web browser was unable to fetch an image using IPv6.
Address-based HTTP proxy detection (?): OK Header-based HTTP proxy detection (?): OK HTTP proxy detection via malformed requests (?): OK Filetype-based filtering (?): OK HTTP caching behavior (?): OK JavaScript-based tests (?): OK
DNS Tests –
Restricted domain DNS lookup (?): OK
We are able to successfully lookup a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.
Unrestricted domain DNS lookup (?): OK
We are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server. Direct EDNS support (?): OK
EDNS-enabled requests for small responses are answered successfully. EDNS-enabled requests for medium-sized responses are answered successfully. EDNS-enabled requests for large responses are answered successfully.
DNS resolver address (?): OK
The IP address of your ISP's DNS Resolver is 68.87.64.147, which resolves to phil-nrcns01.ndceast.pa.bo.comcast.net. Additional name servers observed for your host: 68.87.64.148 DNS resolver properties (?): Lookup latency: 110msYour ISP's DNS resolver requires 110 msec to conduct an external lookup. It takes 93 msec for your ISP's DNS resolver to lookup a name on our server. Your resolver correctly uses TCP requests when necessary. Your resolver is using QTYPE=A for default queries. Your resolver is not automatically performing IPv6 queries. Your DNS resolver does not use EDNS. Your DNS resolver can successfully accept large responses. Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner. No transport issues were discovered which could affect the deployment of DNSSEC DNS glue policy (?): OKYour ISP's DNS resolver does not accept generic additional (glue) records — good.
Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers. Your ISP's DNS resolver does not follow CNAMEs. DNS resolver port randomization (?): OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.


DNS lookups of popular domains (?): Warning
1 popular name has a moderate anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server, although we expected to find a name. This is most likely due to a slow responding DNS server. If you rerun Netalyzr and see this condition remain, it could be due to a misconfiguration on the part of the domain owner or your DNS server could be misconfigured or enabling a Man-in-the-Middle attack.

Name IP Address Reverse Name/SOA
wireless.att.com 135.209.168.22 X
77 of 77 popular names were resolved successfully. Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups. Name IP Address Reverse Name/SOA
www.abbey.co.uk 165.160.15.20 X (pdns1.cscdns.net)
ad.doubleclick.net 64.233.169.149 yo-in-f149.1e100.net
www.alliance-leicester.co.uk 194.130.105.121 X (alice.ioko365.com)
www.amazon.com 207.171.166.252 166-252.amazon.com
www.ameritrade.com 204.58.27.113 beta-new.tdameritrade.com
www.bankofamerica.com 171.161.161.173 www.bankofamerica.com
www.bankofscotland.co.uk 195.171.171.21 X (ns0.bt.net)
www.barclays.co.uk 213.219.1.141 X (dns1.lon7.telecityredbus.net)
bit.ly 128.121.234.46 X (ns1.dn.net)
www.capitalone.com 208.80.48.112 X (chia.arin.net)
www.careerbuilder.com 208.88.80.22 X (smokey.careerbuilder.com)
www.chase.com 159.53.60.105 X (ns1.jpmorganchase.com)
chaseonline.chase.com 159.53.60.54 resources-cdc1.chase.com
www.citi.com 192.193.103.222 citibank.com
www.citibank.com 192.193.103.222 citibank.com
www.citimortgage.com 192.193.103.118 citimortgage.com
www.cnn.com 157.166.226.25 www.cnn.com
www.desjardins.com 142.195.132.100 www.desjardins.com
www.deutsche-bank.de 217.73.49.24 www.deutsche-bank.de
www.e-gold.com 209.200.169.10 unknown.prolexic.com
www.ebay.com 66.211.181.19 hp-core.ebay.com
www.etrade.com 12.153.224.22 www.etrade.com
www.f-secure.com 96.17.149.98 a96-17-149-98.d[...]echnologies.com
www.facebook.com 66.220.147.33 www-12-04-snc4.facebook.com
www.fdic.gov 192.147.69.84 www.fdic.gov
www.friendfinder.com 208.88.180.81 X (ii53-30.friendfinderinc.com)
www.google.com 72.14.204.104 iad04s01-in-f104.1e100.net
www.halifax.co.uk 212.140.245.97 www.halifax.co.uk
www.hsbc.co.uk 193.108.74.126 X (ns3.hsbc.com)
www.irs.gov 96.17.160.59 a96-17-160-59.d[...]echnologies.com
www.jpmorganchase.com 159.53.60.105 X (ns1.jpmorganchase.com)
mail.google.com 72.14.204.17 iad04s01-in-f17.1e100.net
mail.live.com 64.4.20.174 dp1.mail.live.com
mail.yahoo.com 69.147.112.160 l2.login.vip.re3.yahoo.com
www.mbna.com 209.135.59.10 X (ns1.usi.net)
www.mbna.net 209.135.59.10 X (ns1.usi.net)
www.meebo.com 208.81.191.110 X (ns1.meebo.com)
messenger.yahoo.com 68.142.230.204 myc1.msg.vip.re2.yahoo.com
www.microsoft.com 207.46.170.10 wwwtuk2vip.microsoft.com
www.nationwide.co.uk 155.131.31.82 X (ns0.nationet.net)
www.networksolutions.com 205.178.187.13 www.networksolutions.com

www.orange.fr[/url] 193.252.122.103 www.orange.fr.b2.fti.net
partner.googleadservices.com 64.233.169.164 yo-in-f164.1e100.net

www.rbs.co.uk 155.136.80.222 X (ns0-08.dns.pipex.net)
www.schwab.com 162.93.202.80 wwwschwab-vip.schwab.com
search.yahoo.com 74.6.239.185 fe.search.vip.ac2.yahoo.com
www.sears.com 96.17.201.99 a96-17-201-99.d[...]echnologies.com
www.secureworks.com 67.107.53.168 67.107.53.168.ptr.us.xo.net
smartzone.comcast.net 76.96.58.12 webmail3.westch[...]ail.comcast.net
www.smithbarney.com 192.193.20.126 X (ns.citicorp.com)
www.sterlingsavingsbank.com 12.19.55.215 sterlingsavingsbank.com
www.tdameritrade.com 204.58.27.105 beta-new.tdameritrade.com
www.ticketmaster.com 69.192.4.199 a69-192-4-199.d[...]echnologies.com
us.etrade.com 12.153.224.21 us.etrade.com

www.verisign.com 69.58.181.89 www-ilg.verisign.net


www.wamu.com 159.53.62.63 X (ns1.jpmorganchase.com)


windowsupdate.microsoft.com 207.46.18.94 X (msnhst.microsoft.com)
www.yahoo.com 67.195.160.76 ir1.fp.vip.ac4.yahoo.com

7 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.
Name IP Address Reverse Name/SOA
www.bing.com 96.17.160.35 a96-17-160-35.d[...]echnologies.com
www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
www.postbank.de 195.50.155.73 X (ns1.arcor-ip.de)
tinyurl.com 216.218.139.86
www.torproject.org 86.59.21.36
www.trendmicro.com 69.192.9.83 a69-192-9-83.de[...]echnologies.com
2 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.
Name IP Address Reverse Name/SOA
www.bankofthewest.com 204.44.2.241 X
www.sparkasse.de 212.34.69.3 X
DNS external proxy (?): OKYour host ignores external DNS requests. DNS results wildcarding (?): Warning
Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 208.68.139.38, which does not resolve. You can inspect the resulting HTML content here.

There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.

The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.

The following lists your DNS server's behavior in more detail.

www.{random}.com is mapped to 208.68.139.38.
www.{random}.org is mapped to 208.68.139.38.
fubar.{random}.com is correctly reported as an error.
www.yahoo.cmo [sic] is mapped to 208.68.139.38.
nxdomain.{random}.netalyzr.icsi.berkeley.edu is correctly reported as an error.

Restricted domain DNS lookup (?): OK Unrestricted domain DNS lookup (?): OK Direct EDNS support (?): OK DNS resolver address (?): OK DNS resolver properties (?): Lookup latency: 110ms DNS glue policy (?): OK DNS resolver port randomization (?): OK DNS lookups of popular domains (?): Warning DNS external proxy (?): OK DNS results wildcarding (?): Warning
Host Properties +
System clock accuracy (?): OKYour computer's clock agrees with our server's clock. Browser properties (?): OKThe following parameters are sent by your web browser to all web sites you visit:
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB6.3; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Accept Language: en-us
Accept Encoding: gzip, deflate
Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Java identifies your operating system as Windows XP. Uploaded Data (?): OKThe following additional data was uploaded by the applet:
nxpage
raw_http_content

System clock accuracy (?): OK Browser properties (?): OK Uploaded Data (?): OK
=========
http://www.speedtest.net/result/853108140.png
 

·
Registered
Joined
·
76 Posts
Discussion Starter #6
Holy jumpin' all of that is greek to me right now. Been gone from them for a little over a year. I'l show it to my buddy in repair to see what's up.

The 414 and 417 codes are fixed. It helps when the fricking wires are connected to the solenoid :)Facepalm:), but now I am getting a 411 code, incorrect flow.
 

·
Super Moderator
Joined
·
25,823 Posts
yo, ok on the CC issues... Like I wrote, we had a prob with a security camera sending e mails out to us and we talked it over w/CC and they said they would take us off the "List".. but I see they never did. We also had malware on an older PC that our relative took over and used for a week; got that PC out in a hurry... loks like CC has us ont hat "other list" too.

DTC 411 indicates a dirty/ bad or connector issue w/daIdle Air Control valve (IAC). inspect it for crapola. Some can be cleaned. But our's shouldn't since the TSB says; "...Cleaning is not required on sludge tolerant throttle body designs released for 1991 and newer model years...." in Idle Air Control (IAC) Sludge; Poor Idle TSB 91-25-07 for 85-92 Bronco & F Series & many others; "...Hard cold starts, hesitation and stalls on initial start-up or during idle or decel may be caused by sludge in the throttle body and/or idle by-pass valve. Sludge deposits or oil film on the throttle body bore and plate or the idle air by-pass valve may cause one or more of the following conditions. Hard Cold Start, Stall On Initial Start-Up, Stall During Idle, Stall During Decel, Rough Idle, Rolling Idle, Hesitation During Acceleration. A new idle air by-pass service kit (F2PZ-9F939-A) is now available for service use to correct sludge contamination concerns of the throttle bore and plate only. It eliminates the need to clean the majority of past model throttle body applications. Cleaning is not required on sludge tolerant throttle body designs released for 1991 and newer model years..."

--
Thanks JK, but I am merely a conduit of info discovered or made-up by many others:thumbup
 

·
Registered
Joined
·
1,126 Posts
On my 87, there is a wire that hooks up to the neg side of the battery in addition to the main ground. Make sure this is a clean solid connection. This one little wire took me about a month to find. Basically it is a main ground for the computer. When it was not grounded 100% it threw a number of sensors off and triggered a few codes. I do no know if it helps, but if you have it, check it.
 
1 - 9 of 9 Posts
Top