02 F150 odometer reads dashes and won't start
#1
02 F150 odometer reads dashes and won't start
Hello all,
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
#3
Hello all,
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
#4
Talked to the mechanic a little bit more about the problem. He is getting a good power source to his computer scanners. It seems he was having trouble communicating with the PATS module and the PCM. They tried reflashing several times and the PCM still didn't seem to work very well. However, he was able to communicate with other modules easily (ABS etc) . After the PCM reflash, I believe he was able to get some random error codes regarding problems with the vehicle speed sensor, auto delay circuit, and airbag/seat belt warning but it still wasn't working like it should. They are suggesting a remanufactured computer that runs about $400. I'm supposed to let them know today if I want to go this route because it would take 3-4 days to get it in? He really seems to think it's the computer and he tells me he checked everything else thoroughly so I don't know what else to do.
Any thoughts??
Any thoughts??
#5
My 2002 F150 5.4L Supercrew is doing the same thing. However, it only does it when the engine is hot. I'm getting the same dashes on the odometer with the ignition switch in the "run" position. If I let it cool for 30 minutes it will start up and the odometer will show the mileage instead of the dashes.
The only mod's on the engine are a K&N Air Filter assembly and a G-Force Performance Chip. I am suspecting that the performance chip has caused a problem with the PCM. I'll check the fuses as suggested above but I will probably have to let the dealer look at it.
The only mod's on the engine are a K&N Air Filter assembly and a G-Force Performance Chip. I am suspecting that the performance chip has caused a problem with the PCM. I'll check the fuses as suggested above but I will probably have to let the dealer look at it.
#6
Join Date: Jun 2002
Location: Under the flightpath of old ORD 22R
Posts: 10,511
Likes: 0
Received 7 Likes
on
7 Posts
...<snip>...
The only mod's on the engine are a K&N Air Filter assembly and a G-Force Performance Chip. I am suspecting that the performance chip has caused a problem with the PCM. I'll check the fuses as suggested above but I will probably have to let the dealer look at it.
The only mod's on the engine are a K&N Air Filter assembly and a G-Force Performance Chip. I am suspecting that the performance chip has caused a problem with the PCM. I'll check the fuses as suggested above but I will probably have to let the dealer look at it.
#7
Join Date: Oct 2002
Location: St. Louis (Out in the woods)
Posts: 7,247
Likes: 0
Received 104 Likes
on
97 Posts
The following users liked this post:
Trending Topics
#8
Thanks again, TG
#9
I have a 2011 F150, and I'm wiring in a bunch of switched and wiring right now. I think I shorted something, as my interior lights went off, and then the truck wouldn't start. I got the 'dashes-of-death', and 4 warnings from the productivity screen (oil temp, tire pressure, etc).
I checked EVERY...SINGLE...FUSE in both fuse boxes (there is a TON of fuses in these things), and not one was gone, also troubleshot all the wiring and stuff.
It was 11PM, I have to work tomorrow, not going to lie, I was feeling pretty ****ty.
I read your post, and even though I've never had a failed relay in my life, I decided to trudge back out to the garage and try it. I pulled the relay, shorted the socket, and HOLY HELL away it went.
You are pretty much my hero right now. Thanks SO much.
The following users liked this post:
#10
I know this post is fairly old but I am having the same issue. I have a 2002 Ford F150 4.6L. Truck was working fine, now it cranks but wont start. Through some internet research I was able to retrieve the two HEC diag DTC codes:
d262 - missing SCP message
9600 - PATS ignition key transponder signal is not received
I tried all three keys I have to the truck none of them work, also tried disconnecting the battery and letting is set (I let it set overnight) then reconnecting it, I even tried talking to a JustAnswer.com mechanic and he indicated that he thought I needed to replace the Instrument Cluster. That seems a bit over the top but I just wanted to see what the community thinks before sending this thing to the dealer.
Changing out the PCM Power Relays seems a lot easier and cheaper then replacing the Instrument Cluster.
d262 - missing SCP message
9600 - PATS ignition key transponder signal is not received
I tried all three keys I have to the truck none of them work, also tried disconnecting the battery and letting is set (I let it set overnight) then reconnecting it, I even tried talking to a JustAnswer.com mechanic and he indicated that he thought I needed to replace the Instrument Cluster. That seems a bit over the top but I just wanted to see what the community thinks before sending this thing to the dealer.
Changing out the PCM Power Relays seems a lot easier and cheaper then replacing the Instrument Cluster.
#11
We not sure if it was just corroded contacts or not but I swapped the PCM Power Relay from my 2001 Ford Expedition and my truck started right up. Then I put the PCM Power Relay from the truck into the Expedition and it started up as well. Not sure what the hell happened, but everything is working as it was now.
Thank you Jesus!
Thank you Jesus!
#12
Fix
Hello all,
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
Pulled into a restaurant Friday night and when I came out 30 minutes later I could not get the truck started. It seemed to crank fine but I noticed when I turned the key to "RUN", the odometer displayed dashes "---------". Battery seems to be good as it seems to crank fine. Towed it down to my mechanic and yesterday he tried reading any codes that might have registered but he said that the reader would not communicate with the computer (pcm?) I've been doing some research and it seems there are some varying solutions like fuel pump relays, ecm relays, bad instrument cluster and so forth. My concern is that the computer took a dump because it can't communicate. On researching the other fixes, it seems like maybe they were at least able to communicate with the computer. Is there anything that would cause the computer to not communicate with the scanner and not be the computer itself? Thanks!!
#13