My computer went crazy today
#1
My computer went crazy today
Truck was running fine. I dropped off a return at the Home Depot PRO desk (truck off). Started the truck and moved to PRO parking and parked nose-to-nose with some kind of older RAM with a chrome bumper (did not touch front ends).
Did some shopping, got back in the truck, started it and:
Computer restarts.
Message flashes: adaptive cruise not available
Message box: check manual (ok)
Message flashes: pre-collission not available
Message box: check manual (ok)
Computer restarts.
Message flashes: hill start assist not available
Message box: check manual (ok)
Check engine light on.
I wondered if it had to do with parking so close to the RAM? So I drove it to an empty space, shut it down, waited a moment, started it back up -- same thing.
So I drove it to the ford dealer (5 minutes away). Shut down / restarted for service writer -- no messages -- just check engine light.
He tells me it's an all day thing, and they are booked up. Make an appointment.
I figured forget that, I'll just clear it myself and see what happens.
Using Torque Pro, I pull the codes and all I get is this:
P2610 - Powertrain
M/PCM Internal Engine Off Timer Performance Fault
So I clear the codes, the check engine light turns off. I shut it down, restart it, and it seems fine. I drove it about 5 miles and it's parked now.
The only other 'variable' I know of is I was trying to set up the DPF monitors in Torque Pro and couldn't get them working -- right before I went in to Home Depot. But I'm 99.999% sure I didn't write anything to the truck.
So I don't know if it's parking close to a metal bumper, messing around with Torque Pro, or something else. Scratching my head, but happy with no error codes at the moment...
Did some shopping, got back in the truck, started it and:
Computer restarts.
Message flashes: adaptive cruise not available
Message box: check manual (ok)
Message flashes: pre-collission not available
Message box: check manual (ok)
Computer restarts.
Message flashes: hill start assist not available
Message box: check manual (ok)
Check engine light on.
I wondered if it had to do with parking so close to the RAM? So I drove it to an empty space, shut it down, waited a moment, started it back up -- same thing.
So I drove it to the ford dealer (5 minutes away). Shut down / restarted for service writer -- no messages -- just check engine light.
He tells me it's an all day thing, and they are booked up. Make an appointment.
I figured forget that, I'll just clear it myself and see what happens.
Using Torque Pro, I pull the codes and all I get is this:
P2610 - Powertrain
M/PCM Internal Engine Off Timer Performance Fault
So I clear the codes, the check engine light turns off. I shut it down, restart it, and it seems fine. I drove it about 5 miles and it's parked now.
The only other 'variable' I know of is I was trying to set up the DPF monitors in Torque Pro and couldn't get them working -- right before I went in to Home Depot. But I'm 99.999% sure I didn't write anything to the truck.
So I don't know if it's parking close to a metal bumper, messing around with Torque Pro, or something else. Scratching my head, but happy with no error codes at the moment...
#2
So I've made two trips since. Everything is fine. My best guess is:
1. Starting the truck with the sensor that's inches from a large metal surface scrambles the computer's eggs.
2. I kept turning it on and off trying to see if it would clear. I suspect that caused the P2610 fault (which if I understand correctly means it can't determine how long it's been running) -- due to more brain scrambling from the on/off/on/off/on stuff.
I'll report back if there are other issues. Meanwhile I'd love to hear from anyone who gets any similar symptoms and especially if they were up against a big sheet of metal when it happened.
1. Starting the truck with the sensor that's inches from a large metal surface scrambles the computer's eggs.
2. I kept turning it on and off trying to see if it would clear. I suspect that caused the P2610 fault (which if I understand correctly means it can't determine how long it's been running) -- due to more brain scrambling from the on/off/on/off/on stuff.
I'll report back if there are other issues. Meanwhile I'd love to hear from anyone who gets any similar symptoms and especially if they were up against a big sheet of metal when it happened.
#3
Join Date: Apr 2004
Location: North of Salt Lake City
Posts: 5,159
Likes: 0
Received 26 Likes
on
24 Posts
This isn't exactly the same thing but I noticed on my 2011 that if Torque Pro was running the truck would sometimes randomly throw an error code. I attributed it to a bandwidth issue of the truck's computer or OBDII port. I read once that by simply listening to too many PIDs can actually interrupt internal communications. This is only a theory on my part supported by a post somewhere else.
It's more likely that on startup the related module glitched and didn't communicate properly therefore throwing a code. I think this is something that we are only seeing the beginning of. Truck glitches and the fix is to reboot.
It's more likely that on startup the related module glitched and didn't communicate properly therefore throwing a code. I think this is something that we are only seeing the beginning of. Truck glitches and the fix is to reboot.
#4
So I've made two trips since. Everything is fine. My best guess is:
1. Starting the truck with the sensor that's inches from a large metal surface scrambles the computer's eggs.
2. I kept turning it on and off trying to see if it would clear. I suspect that caused the P2610 fault (which if I understand correctly means it can't determine how long it's been running) -- due to more brain scrambling from the on/off/on/off/on stuff.
I'll report back if there are other issues. Meanwhile I'd love to hear from anyone who gets any similar symptoms and especially if they were up against a big sheet of metal when it happened.
1. Starting the truck with the sensor that's inches from a large metal surface scrambles the computer's eggs.
2. I kept turning it on and off trying to see if it would clear. I suspect that caused the P2610 fault (which if I understand correctly means it can't determine how long it's been running) -- due to more brain scrambling from the on/off/on/off/on stuff.
I'll report back if there are other issues. Meanwhile I'd love to hear from anyone who gets any similar symptoms and especially if they were up against a big sheet of metal when it happened.
#5
#6
I removed the dongle, restarted the truck, zero issues.
Thanks for this!
#7
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post