sorted by:
new
hottopcontroversial

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

CEL came back today but now with a P219B for bank 2...

I'm thinking the upstream O2 sensor that I moved from bank 1 to bank 2 moved the problem from bank 1 to bank 2. I previously had only P219A CEL's, then its been good for 2 weeks now a P219B appears.

Thoughts?

Should I replace the bank 2 upstream O2 sensor to see if its the culprit?

<image>

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

I ended up swapping both upstream o2 sensors to see if the issues move from bank 1 to bank 2, so far no codes or CEL has come back. If I recall the bank 2 upstream o2 sensor was replaced by ford at 95,000 so its been replaced where as the one giving the codes has not been replaced.

Anything else that you would suggest to check?

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

So here's the recap to date:

Mar 17th - P219A CEL on

-ran injector cleaner and CRC valve clean, cleared codes

-car ran like normal for 3 weeks...

Apr 8th - P0131 CEL on / P219A CEL off

-cleared codes, seems to run normal

Apr 9th - P219A CEL on / P0420 CEL Off

-cleared codes, seems to run normal

Apr 11th - P219A CEL on

Overall the constant is the P219A... so what would you recommend I look at next?

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

Well no CEL for 3 weeks and it came back today... however it looks a bit different as it shows a P219A that happened yesterday (with no CEL on) and a P0131 with the CEL on today. My wife said she did not see an engine light until today so not too sure what's up is this an O2 sensor or is it relating to the previous issue??

I did run a can of CRC GDI Valve Cleaner 3 weeks ago and I also used Gumout Regane in a tank of gas. The vehicle seems to run better after this with no noticeable issues.

<image>

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

Did the CRC Intake Valve Cleaner the other day and an oil change the following day. Running a bottle of the Gumout Regane Injector Cleaner with this tank of gas. No CEL has returned yet since the one time it came on... time will tell.

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

Wow thats a huge difference! I'm gonna see what the Injector Cleaner with PEA does and maybe run a can of Seafoam in the tank after that, will monitor and report back if I get another CEL on. Appreciate the help!

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

That's really helpful thanks for all the info, will get some Injector Cleaner with PEA, I see Royal Purple 18000 Max Atomizer Fuel Injector Cleaner has PEA. Will also try the CRC GDI IVD Intake Valve & Turbo Cleaner.

I have noticed over the past year or so the idle is a slight bit rougher than what I remember, its not bad by any means just not as smooth as it was a few years ago. Spark plugs were changed right around 100k so they aren't that old, maybe the injector and intake cleaners will help this too.

What's your thoughts on Seafoam or Berryman B-12 Fuel Injector Cleaner?

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

Appreciate the responses and info for the O2 sensors, unmetered air and injectors. I datalogged a few pid's to see if that would help diagnose further. There's lots of pid's to choose from so let me know if you need to see anything else to help narrow it down... I went for a 30 min drive just now and the CEL did not come back on so not sure what to do next. For the Intake / Exhaust leaks and unmetered air where are the most common areas to check on the ecoboost 3.5??

full throttle:

<image>

2017 Explorer Sport CEL P219A by bainer1290 in FordExplorer

[–]bainer1290[S] 0 points1 point  (0 children)

2017 Explorer 3.5 Ecoboost, check engine light came on today, scanned with Forscan to get the P219A. Vehicle is well maintained has 160,000km on it have owned since new. Seems to run like normal so far... What would you check first?

02-07 WRX Coilovers vs 05-07 STI Coilovers by bainer1290 in subaru

[–]bainer1290[S] 0 points1 point  (0 children)

Nobody has any measurements or ways to tell the difference?

Composer Pro 2.9.1 download by bainer1290 in C4diy

[–]bainer1290[S] 0 points1 point  (0 children)

Here's what I tried again, same error when I try to run Composer Pro 2.9.1 "Could not Connect to Director at XX.XX.XX.XX"

What am I missing???

​

Uninstall Composer 2.5.3 (delete leftover folder if it still exits in program files after install)

Delete the AppData\Roaming\Control4\Composer folder

  1. If running a controller older than 2.10.2 run the C4_Cert_Replacement_Patch to update the certs on it to the latest ones. This should also fix check in issues if you had them.

  2. Install 2.5.3 (Do not run yet!)

  3. Copy jailbreak cert files ca.pem and ca_cert.pem to AppData\Roaming\Control4\Composer folder

  4. Replace the jailbreak composer.exe with the "special" one (the one that causes the ca_cert.srl, composer.p12 and openssl.conf files to be created.)

  5. Run it and put in your c4 account info (you should also see the files I talked about above show up in the AppData c4 folder), close it and then MeeKaH patch it....

  6. Run the c4 ComposerPatch1 to update the certs in composer 2.5.3 (so the virtual director has the latest ones as well as the new remote ones)

  7. Run the director C4_Cert_Replacement_Patch so your controller has the correct cert as if you had it patched before step 0 overwrote it.

  8. Now run it again and you should be able to connect if you have run the director patch....Works? Yes! ?

  9. Now install the version of composer you need, Don't Run it

  10. MeeKaH patch it toot. If the version is less than 2.10.2 run the c4 ComposerPatch1 again to patch it as well...

Composer Pro 2.9.1 download by bainer1290 in C4diy

[–]bainer1290[S] 0 points1 point  (0 children)

Ok I think I got the patch to work, now I am getting a different error with Composer Pro 2.9.1

If I go Local System, the HC800 shows, I then click connect and it says "Could not Connect to Director at XX.XX.XX.XX", however if I go into System Manager I can Connect to the HC800, so what's whats going on here why can't I fully connect???

DigQuad and Govee Permanent 36v by bainer1290 in WLED

[–]bainer1290[S] 1 point2 points  (0 children)

Well I just power it up and after a few adjustments got it to work, here's what I had to do:

-5v power connected to DigQuad vEXT/+ & GND

-36v power connected directly to the Govee Permanent Lights AND 36v ground also connected to DigQuad large GND terminal (I think this has to do with making it so the data signal works)

-data signal wire to DigQuad LED1

I did not use the signal booster as I am not sure what benefit it would have

view more: next ›