2002 Explorer Sport, Engine Won't Turn Over | Page 2 | Ford Explorer Forums

  • Register Today It's free!

2002 Explorer Sport, Engine Won't Turn Over

^ I have mixed data about that. I own the prior version but can't advise, saw contradictory info and don't know why forscan is having problems with some now.

If it weren't for your current issue then I'd put the BAFX at the top of the generics to consider.

Which do you recommend?
 



Join the Elite Explorers for $20 each year or try it out for $5 a month.

Elite Explorer members see no advertisements, no banner ads, no double underlined links,.
Add an avatar, upload photo attachments, and more!
.





^ I don't know, as I have only two, the older version of the BAFX and a cheap little generic one that won't do J1850 which Explorers used till around 2004, even though it was claimed to work with all OBD2 vehicles. I know that one works with CAN bus because it does work on my '14.

I would have recommended getting the current version of the BAFX but can't remember where I saw someone claim that Forscan won't work with it.

Okay, on the android Forescan Demo page, there are these comments:
Sam Son September 25, 2015

Did not connect Torque pro has no problem to connect to my BAFX scan adapter, but for scan does not connect. Will uninstall.

Joe Cameron February 25, 2017

As others have mentioned, will not connect to BAFX 34t5 Bluetooth OBDII Scan Tool for Android Devices, while TorqueLite has no issues. Will uninstall.

Richard G August 9, 2016

Doesn't detect BAFX Won't connect to my BAFX 34t5 DBD II

On the other hand, there are people on Forscan's forum who state that it works, and some on Amazon reviews:

http://forscan.org/forum/search.php?keywords=BAFX+34t5

https://www.amazon.com/BAFX-Product...y=recent&pageNumber=1&filterByKeyword=Forscan
 






Sounds like I'll just have to take my chances and give it a shot. lol.

I'll do that. First I'm gonna go to my ford dealership and see if they can tell me if the chip in my key is ok. My father told me today that when he was driving it several months ago that the key would be extremely hot coming out of the ignition... So maybe the chip in the key burned out? I figure it's worth looking into since I drive past the dealership every day on my way to class.
 






^ I doubt the key burned out, it's bound to be an extremely low current chip, operating by a remote magnetic field like it does, so should not be possible to heat up much. Plus that would mean it would have immediately ceased to work.

A dealership is (usually) going to want more money to check your key than it's worth. I'd just get the BAFX and see what codes it pulls first.
 






^ I doubt the key burned out, it's bound to be an extremely low current chip, operating by a remote magnetic field like it does, so should not be possible to heat up much. Plus that would mean it would have immediately ceased to work.

A dealership is (usually) going to want more money to check your key than it's worth. I'd just get the BAFX and see what codes it pulls first.

They'd charge just to check a key? That's a bit petty... lol.

I bought the BAFX and will update when I get to use it.
 






Hi everyone, I got the BAFX yesterday afternoon and ran ForScan on the Explorer today. This is what I got when checking the errors.

===OBDII DTC ===
Successful DTC reading, no error codes found

Module: On Board Diagnostic II
===END OBDII===

===PCM DTC P0232===
Code: P0232 - Fuel pump secondary circuit High

Module: Powertrain Control Module
===END PCM===

===PCM DTC P1000===
Code: P1000 - On-Board Diagnostic (OBD) Systems Readiness Test Not Complete

Module: Powertrain Control Module

Diagnostic Trouble Code details

Check of all systems is not complete since last memory clear.

--Possible Causes--
- The vehicle is new from the factory and has not yet been through a complete OBD Drive Cycle.
- The battery or PCM has been disconnected.
- An OBD monitor failure had occurred prior to completion of an OBD Drive Cycle.
- The PCM DTCs have been cleared as part of a service process.

Note: The only way P1000 can be cleared (removed) from memory is when all of the OBD monitors have been successfully completed during normal vehicle operation.

P1000 cannot be cleared from the PCM when: 1. The thermostat is stuck open and a DTC is not generated. 2. There is an open VSS circuit and a DTC is not generated. 3. If the vehicle has a Power Take Off (PTO), the circuit is shorted to VPWR or B+, or the PTO is ON during Self-test.

The purpose of the Diagnostic Trouble Code DTC P1000 is to indicate that not all of the On Board Diagnostics OBD monitors have yet been successfully completed. You may also refer to the OBD Drive Cycle defined under the Powertrain Control/Emission Diagnosis Manual-Diagnostic Methods or the Owner's Manual.

Remember: It is not necessary to remove P1000 from the Powertrain Control Module PCM by driving the vehicle.


===END PCM===

===PCM DTC B1681===
Code: B1681 - PATS transceiver fault.

Module: Powertrain Control Module

Diagnostic Trouble Code details

PATS transceiver fault.

NOTE: The PATS module functionality can be integrated into various modules. (See the Module I.D. tagged to the DTC.)

--- Possible Causes --------

Passive Anti-Theft System (PATS) Module Signal Is Not Received

No transmission is being received on the signal return line from the transceiver module.

-Suspect PATS Module



===END PCM===

===RCM DTC B1998===
Code: B1998 - Side Airbag Open Circuit (Passengers)

Module: Restraint Control Module

Diagnostic Trouble Code details

Side Airbag Open Circuit (Passengers)


===END RCM===

===GEM DTC B1818===
Code: B1818 - Rear wiper motor up relay circuit failure

Module: Generic Electronic Module

Diagnostic Trouble Code details

Rear wiper motor up relay circuit failure


===END GEM===

===GEM DTC B1398===
Code: B1398 - Left Front Power Window Relay circuit failure

Module: Generic Electronic Module

Diagnostic Trouble Code details

Left Front Power Window Relay circuit failure


===END GEM===

===GEM DTC P0500===
Code: P0500 - VSS sensor circuit fault.

Module: Generic Electronic Module

Diagnostic Trouble Code details

VSS sensor circuit fault.

Open VSS circuit.

Shorted VSS circuit.

This DTC may be caused by :

Suspect VSS.

Worn or Damaged VSS drive gear on transmission output shaft.

Suspect PCM.

Faulty or damaged instrument cluster module.


===END GEM===

===RAP DTC ===
Successful DTC reading, no error codes found

Module: Remote Anti-Theft / Personality Module
===END RAP===

===ABS DTC ===
Successful DTC reading, no error codes found

Module: Antilock braking system
===END ABS===

I bolded the PATs error code and I'm about to begin searching it on google to see what I can determine on my own while waiting for you kind people to reply. :)
 






I'd grab a multimeter and start following a flowchart like the following, regardless of it reading Jaguar at the top. Now we're getting into an area where someone with the 3rd gen Explorers might be able to directly compare with yours, which has to be at least a little different to have the starter interrupt circuit.

http://www.jagrepair.com/images/TSB/TSB2/S-Type/419Electronic Features/S419-12 Passive Anti -Theft System.pdf

If all else failed and I couldn't determine where the fault lies, I'd get a steering column (ignition lock mounted) transponder module from a junkyard and try that, as I'd assume they're interchangeable within a few models years but I don't know which ones, would try for an '02 or '03 first.

Upon researching this I also came across someone who stated that they replaced a relay and that fixed it but they dropped out of sight with no further info.
 






Whew, that's a lot of gibberish to me. I'll read through it and try to fill in the blanks with Google-Fu. Thanks much J_C
 






Featured Content

Back
Top