ODB Port with no pwer | Ford Explorer Forums

  • Register Today It's free!

ODB Port with no pwer

2016FordJerry

New Member
Joined
August 9, 2020
Messages
5
Reaction score
0
City, State
Miami Lakes, FL
Year, Model & Trim Level
2016 Ford Explorer XLT
Hi, I have a 2016 Ford Explorer XLT and I just took it to the dealership for a recall for the Torque converter (20B27) and they are advising me that the ODB port won't communicate. They wanted to charge $165.00 to investigate plus parts plus any additional labor.

After doing some research I understand that most likely it is a fuse, usually teamed up with a lighter or other.
Does anyone know which fuse it is?
Additionally I dont have any accessories or other functionalities not working, so this seems like I may be chasing down the wrong bunny hole.

Any help is greatly appreciated.
 



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!
.





There are 2 fuses shown in the Owner's Manual for 'Smart data link' which may be the OBD port. Have you checked them? Fuses 13 and 15 in the cabin fuse panel.

Peter
 






Not cool that the dealer didn't check the fuse. Takes 5 minutes..... Just had this issue in my Sienna and fixed it. Ck your manual per Peter. Should fix.it.
 






I had a 16 Explorer that wouldn't communicate either through the obd port but everything worked fine. Ended up the GWM/Gateway Module which is what the OBD port is actually, had poor solder joints for the pins in the OBD connectors. I had to reflow the solder joints and never had a problem again.
 






There are 2 fuses shown in the Owner's Manual for 'Smart data link' which may be the OBD port. Have you checked them? Fuses 13 and 15 in the cabin fuse panel.

Peter
Ok so I checked the fuses and both were good. I plugged the fuse back in and checked it with my BT OBD and it worked! THank you for the feedback. Dont know why it didnt respond but apparently it needed a reboot.
 






Back
Top