When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I've had a Check Engine Light on my 1995 7.3 F250 for quite sometime now (truck runs fine). So I bought a Samsung Galaxy E Lite tablet and a Vgate Bluetooth OBD2 scanner.
I cannot get it to read or clear the CEL from my truck. I've tried reading a bunch of threads but just haven't found a exact answer. The only thing that I can think of is my PCM might need flashed before codes can be pulled or I need a different OBD connector? But I had a shop that had a Snap-On modis ultra scanner and they were able to pull codes no problem.
To start off the pins that I have for the OBD connection under the dash are #2,4,5,10,13,16
I have to ford powerstroke PIDs uploaded on the app.
In vechicle profile I have SAE J1850-PWM type in and saved.
I am able to connect to the Bluetooth adaptor but when I have the truck running and go into adapter status the truck either shuts down or skips.
In adapter status information it shows that the connection to adapter, and connection to ECU is all good and working.
With the truck running, If I go to fault codes and try to scan, the truck will either shut off a soon as the scan starts or will skip and try to stay running but eventually shut down, and when the scan is going the Wait To Start light will go off and on.
And then after the scan is 100% complete it says there are no fault codes.
Any advice on what on try or suggestions would be greatly appreciated. I'm so tried of looking at this Yellow dash light lol.
When scanning for codes you can not have the motor running with the Torque Pro
Turn the Key to "Key on Engine Off"
Wait for the adapter to connect
Make sure the Tablet is connected to the OBD bluetooth adapter. In the bluetooth adapter settings in torque pro lets you know when u are connected to the adapter and the ECU. (sometimes I have to give the tablet "access" by allowing it to connect to the bluetooth adapter through a little drop down menu from the top of the tablet/ 32w1Mine takes a couple times of turning the key on/off)
Once connected to the adapter you can scan for fault codes. With Key on Engine Off.
I've tried the test with the truck off and the Wait To Start light goes on and off and once it finishes the scan it still reads that there are no codes.
I've tried the test with the truck off and the Wait To Start light goes on and off and once it finishes the scan it still reads that there are no codes.
do you have a chip? how do you like those u codes?
So I took my chip off of the truck, and I did the scan and I'm still not able to read the codes. But when I start the scan with the chip taken off the Wait To Start light no longer goes on and off throughout the test. Also I was having a tough time getting the OBD adaptor to connect to ECU with the programmer off. I would have to exit in and out of the app and unplug the OBD adaptor a few times before I could get it to finally connect, and then once I'd get it to connect and run the test, it would say it wasn't connected after the test. Once I was done for the night and I put the chip back on and everything back together I decided to see if the adaptor would connect and it did with no problems but still couldn't read the codes.
So when the chip is disconnected the OBD adaptor has a hard time connecting to the ECU, and once it is connected it doesn't stay connected after the test.
With the chip connected the OBD adaptor doesn't have a issue connecting to the ECU and stays connected after tests.
So does anyone have any idea why the adaptor has a hard time connecting to the ECU with the chip off? Do you guys think it might be the adaptor that's the issue? Please let me know.
I have a 1995 as well, and from what I understand the computer needs to be re flashed to be ob11 compatible. I haven't looked into how much Ford wants to do it yet.
Where would I take the ECU to have flashed? Would I need to ship it somewhere or are the local shops that are able to preform this like the dealership?
So I went through some old nots I had and last time I have a shop try to clear the codes I had I got these codes P0475 P0605
The p0475 code is understandable because I deleted the EBPV valve and all I did was disconnect the wiring.
But after doing searching on the p0605 it looks like I might have a issue directly with the ECU. I don't know much about it but could this could be reason I'm not able to read the codes with torque pro or something?
The scanner the shop was using was a Snap On Modis Ultra. Does anyone have any knowledge on the p0605 code?
If you got codes from the OBDII port, it is working. Most cheap adapters won't work with it. You have to buy one that specifically states it will work with j1850 PWM.
Most of that third world stuff is relabeled and made by the cheapest supplier anyone can find. Same label doesn't always mean same product.
The "flash at the dealer thing" applies only to the very first Powerstrokes. They had an OBDII plug under the dash and an OBDI plug by the hood hinge. Only one of them could be active at any time and the dealer had to activate the other if you wanted to change.
I have a link to some adapters that were tested but I can't find it now. I'll try to find it.
I paid a little extra and got an OBDlink MX Bluetooth. It has paid for itself, over and over. I use it for other vehicles too. They have an updated version of it now, OBDlink MX+. I wouldn't pass up a great deal on one those.
I paid a little extra and got an OBDlink MX Bluetooth. It has paid for itself, over and over. I use it for other vehicles too. They have an updated version of it now, OBDlink MX+. I wouldn't pass up a great deal on one those.
So do you think that the problem is just my Bluetooth scanner? And if so is it conformed that the OBDlink MX+ will work on a 1995 powerstroke, because the only thing that I'm not sure of is it says the adaptor will only work on 1996 and newer OBD2 vechicles and from what I've read the 1994 and 1995 powerstrokes are OBD1. I just don't want to spend $75 on it if it might not work.
So do you think that the problem is just my Bluetooth scanner? And if so is it conformed that the OBDlink MX+ will work on a 1995 powerstroke, because the only thing that I'm not sure of is it says the adaptor will only work on 1996 and newer OBD2 vechicles and from what I've read the 1994 and 1995 powerstrokes are OBD1. I just don't want to spend $75 on it if it might not work.
I believe you read correctly. Look at your build date on your door sticker. It's probably a early 95 like mine. I heard late 95 had obd11 .