OBD II Connector issue

[POS Camaro]

So, today I take my Explorer into the dealer for emissions testing. Here in CT the deal is to plug in the OBD II port and verify no codes are tripped. Unfortuneately, when they plugged into my OBD II port, they didn't get any conectivity. They did sniff it and it passed well within specification.
I would like to know if this issue has hit anyone before and what they did to correct the problem.
Thanks for your assistance.

 

[MountaineerGreen]

Check your cigar lighter fuse- it's what powers the OBD II port.

 

[POS Camaro]

If it something that stupid, I'll beat the snot out of the dealer.

 

[POS Camaro]

The lighter works, glows cherry red. Any other ideas?

 

[MountaineerGreen]

Maybe another code reader just to see what it does?

 

[POS Camaro]

I'll give it a shot.

 

[rwenzing]

On some years/models, the Data Link Connector and the lighter share a fuse. However, the 99 Ex has a dedicated fuse for each - the DLC uses #5 (10A) in the dash fuse panel.

 

[POS Camaro]

All fuses are good. I have a cheap UIF Tech scanner. It indicates good for both my 99 Explorer and my 03 Suburban. Maybe their stuff is broken?

 

[MountaineerGreen]

They may possibly have an issue with their scanner

 

[Captinchaos]

Omg

Thanks guys, I have been trying to figure this one out for about a month now. Using my Palm Centro and a Bluetooth enabled scanner running OBD Gauge. The lighter didn't work so I thought the lighter itself was bad. Yes:, after reading this post, I immediately went out to my Explorer and checked the fuses. 2000 Ford Explorer 25 amp fuse. I knew the scanner worked, because I hooked it up to my wife’s 2001 Escort. Now I am trying to find a suitable brick wall to bang my head on…

 

[Pinout]

So, today I take my Explorer into the dealer for emissions testing. Here in CT the deal is to plug in the OBD II port and verify no codes are tripped. Unfortuneately, when they plugged into my OBD II port, they didn't get any conectivity. They did sniff it and it passed well within specification.
I would like to know if this issue has hit anyone before and what they did to correct the problem.
Thanks for your assistance.

The 1995 Explorers have the eeciv module and the engine codes are read with the under hood connector. The OBD2 connector under the steering wheel is for the abs, air bag, and gem modules. The 1996 Explorers have the eeciv module, and the engine codes along with the other systems are read with the OBD2 connector. 1995 Explorers are not OBD2 compliant because the eeciv module is not OBD2 compliant. Emission testers have to use the sniff test on 1995 Explorers.

 

[BKennedy]

11 years too late, but thanks for the post

 

[Pinout]

11 years too late, but thanks for the post

These forums still come up on Google searches for information. With the 1995's, most of the information here is misinformation. People are restoring these vintage cars, and without this vital correct information, all the 95's are going to go to the junkyard. Hopefully I can save someone else the headaches I've had trying to figure this out.

 

[gmanpaint]

These forums still come up on Google searches for information. With the 1995's, most of the information here is misinformation. People are restoring these vintage cars, and without this vital correct information, all the 95's are going to go to the junkyard. Hopefully I can save someone else the headaches I've had trying to figure this out.

What misinformation are you referring to?
Have you used the search feature here, to further your inquiry on any information you believe to be false, and has been corrected on another thread?

 

[Pinout]

What misinformation are you referring to?
Have you used the search feature here, to further your inquiry on any information you believe to be false, and has been corrected on another thread?

When I was researching my 95 explorer problems on the internet, the explorer forum threads came up quite a lot. I noticed that a number of members that were responding to questions about the 95's gave different answers to the same questions. This caused me a lot of headaches finding out which answers were correct. I wanted to find the threads with the wrong answers to the 95's, and add the correct answers to help the next person understand how to fix their vintage car.

 

[96eb96]

When I was researching my 95 explorer problems on the internet, the explorer forum threads came up quite a lot. I noticed that a number of members that were responding to questions about the 95's gave different answers to the same questions. This caused me a lot of headaches finding out which answers were correct. I wanted to find the threads with the wrong answers to the 95's, and add the correct answers to help the next person understand how to fix their vintage car.

The best scanner for a 95 would be a MT2500 Red Brick. They are still available on ebay. This can interface with the eec iv datastream, give you lots of diag info.

I guess it could be set to 97 and you could have everything including brake bleed. I was able to bleed my 96 using 97 ABS functions (for some reason 96 does not have this, you are supposed to use a tool).

 

[Pinout]

The best scanner for a 95 would be a MT2500 Red Brick. They are still available on ebay. This can interface with the eec iv datastream, give you lots of diag info.

I guess it could be set to 97 and you could have everything including brake bleed. I was able to bleed my 96 using 97 ABS functions (for some reason 96 does not have this, you are supposed to use a

The best scanner for a 95 would be a MT2500 Red Brick. They are still available on ebay. This can interface with the eec iv datastream, give you lots of diag info.

I guess it could be set to 97 and you could have everything including brake bleed. I was able to bleed my 96 using 97 ABS functions (for some reason 96 does not have this, you are supposed to use a tool).

Thank you. I did a tee splice from the Ford eeciv connector data+ (914 tan/orange) into the obd2 connector #2 spot. Then tee splice from the Ford eeciv connector data- (915 pink/light blue) into the obd2 connector #10 spot. This allowed the '95 obd2 connector to "come alive" and have the eeciv to talk to my scanner. I just haven't been able to get engine live data yet with the software in my scanner. I'll check out the MT 2500.