Can the stealer tell if you've used a programmer?
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
Now that I've officially embarrassed myself with regards to my competence in matters of CS programmers, I'd like to thank everybody for answering my noobie questions!
On a side note (and off topic) I just thought I'd mention that my trail graps performed exceedingly well in the ice and snow at highway speeds and crawling through snow banks. Highly reccomended!!
Technical Article Contributor
Joined: Apr 2009
Posts: 10,697
Likes: 14
From: In the fast lane from LA to Tokyo...
What's the other mountains like?
Just messing wicha....
Global Moderator &
Senior Member
Senior Member
Joined: Mar 2005
Posts: 26,080
Likes: 85
From: Burleson/Athens/Brownsboro, TX
There's some wannabes in a few of the other states. 
__________________
Jim
Jim
Global Moderator &
Senior Member
Senior Member
Joined: Aug 2007
Posts: 7,890
Likes: 61
From: Among javelinas and scorpions in Zoniestan
Like those little "bumps" back East.
Interesting, though. I've taken my truck, pulling a trailer up over 11,000+ foot passes in Colorado and more recently up over the Tioga Pass in the Sierras (still pulling the trailer) and have not had any problems at all. It wasn't in the winter though. I wonder if the cold, dry, "thin" air fools the system at altitude, or, exceeds the limits of the closed loop feedback system to compensate?
Your description of the meaning of the code though, John, could simply mean there's a problem with the O2 sensor. If the system sees a high voltage on that sensor, I think it causes the malfunction code. I can't tell from your post - were you still in the mountains when the light came on?
As has been suggested (by you), I'd try clearing the code(s) and see if it/they return. I think once the malfunction code is set, it stays until it is cleared, even if the problem goes away.
- Jack
Interesting, though. I've taken my truck, pulling a trailer up over 11,000+ foot passes in Colorado and more recently up over the Tioga Pass in the Sierras (still pulling the trailer) and have not had any problems at all. It wasn't in the winter though. I wonder if the cold, dry, "thin" air fools the system at altitude, or, exceeds the limits of the closed loop feedback system to compensate?
Your description of the meaning of the code though, John, could simply mean there's a problem with the O2 sensor. If the system sees a high voltage on that sensor, I think it causes the malfunction code. I can't tell from your post - were you still in the mountains when the light came on?
As has been suggested (by you), I'd try clearing the code(s) and see if it/they return. I think once the malfunction code is set, it stays until it is cleared, even if the problem goes away.
- Jack
Last edited by JackandJanet; Feb 2, 2011 at 07:16 PM.
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
So I cleared the codes and loaded up my canned economy 87 tune. It ran fine all afternoon but P2270 just popped up again.
Anyhow I've returned it back to stock, again, and I'll see if the code comes back.
My appointment is for tomorrow morning at the dealer so I think I might just have to take it in.
I'm hoping it's something minor like the O2 sensors and not an issue with the tune
EDIT: I've found a resource that suggests that this code will be thrown when the PCM fails to recieve info from an O2 sensor over a calibrated amount of time.
It listed possible causes as pinched/crossed wiring, exhaust leaks, loose/broken sensor.
Looks like it shouldn't be a big deal (knock on wood)
Anyhow I've returned it back to stock, again, and I'll see if the code comes back.
My appointment is for tomorrow morning at the dealer so I think I might just have to take it in.
I'm hoping it's something minor like the O2 sensors and not an issue with the tune
EDIT: I've found a resource that suggests that this code will be thrown when the PCM fails to recieve info from an O2 sensor over a calibrated amount of time.
It listed possible causes as pinched/crossed wiring, exhaust leaks, loose/broken sensor.
Looks like it shouldn't be a big deal (knock on wood)
Last edited by johnjohnson78; Feb 2, 2011 at 09:50 PM.
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
Like those little "bumps" back East.
Interesting, though. I've taken my truck, pulling a trailer up over 11,000+ foot passes in Colorado and more recently up over the Tioga Pass in the Sierras (still pulling the trailer) and have not had any problems at all. It wasn't in the winter though. I wonder if the cold, dry, "thin" air fools the system at altitude, or, exceeds the limits of the closed loop feedback system to compensate?
Your description of the meaning of the code though, John, could simply mean there's a problem with the O2 sensor. If the system sees a high voltage on that sensor, I think it causes the malfunction code. I can't tell from your post - were you still in the mountains when the light came on?
As has been suggested (by you), I'd try clearing the code(s) and see if it/they return. I think once the malfunction code is set, it stays until it is cleared, even if the problem goes away.
- Jack
Interesting, though. I've taken my truck, pulling a trailer up over 11,000+ foot passes in Colorado and more recently up over the Tioga Pass in the Sierras (still pulling the trailer) and have not had any problems at all. It wasn't in the winter though. I wonder if the cold, dry, "thin" air fools the system at altitude, or, exceeds the limits of the closed loop feedback system to compensate?
Your description of the meaning of the code though, John, could simply mean there's a problem with the O2 sensor. If the system sees a high voltage on that sensor, I think it causes the malfunction code. I can't tell from your post - were you still in the mountains when the light came on?
As has been suggested (by you), I'd try clearing the code(s) and see if it/they return. I think once the malfunction code is set, it stays until it is cleared, even if the problem goes away.
- Jack
To be honest, I didn't actually notice the code until the next morning when it was really cold out.
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
So just got some crappy news from my service advisor.
The tech said he got some code that he's never seen before and suspects it might have something to do with someone trying to change a setting for tire size, which I did do within the options menu in the edge months ago. Sounds like they don't really know what's going on and I don't think I'm going to fill them in.
They say Ford won't be covering any of the work/diagnosis under warranty.
This totally stinks. In all my research I never read about a CS causing various trouble code problems that the dealer would use against me.
Any suggestions as to what I should do at this point?
I'm now hesitant to reprogram my vehicle once they do sort this out as I have to assume it will just happen again.
UPDATE: What they're telling me is that the PCM has been corrupted and they're going to reformat the entire thing which shouldn't be a big deal other than a couple hours of labor that I'll have to take care of. This will be almost the cost of a new programmer.
Has anybody experienced anything like this with the edge CS? Do I have any reason to believe my PHP tune (once I get it) will be any less likely to cause these sort of problems?
Has anyone had any similar experience?
The tech said he got some code that he's never seen before and suspects it might have something to do with someone trying to change a setting for tire size, which I did do within the options menu in the edge months ago. Sounds like they don't really know what's going on and I don't think I'm going to fill them in.
They say Ford won't be covering any of the work/diagnosis under warranty.
This totally stinks. In all my research I never read about a CS causing various trouble code problems that the dealer would use against me.
Any suggestions as to what I should do at this point?
I'm now hesitant to reprogram my vehicle once they do sort this out as I have to assume it will just happen again.
UPDATE: What they're telling me is that the PCM has been corrupted and they're going to reformat the entire thing which shouldn't be a big deal other than a couple hours of labor that I'll have to take care of. This will be almost the cost of a new programmer.
Has anybody experienced anything like this with the edge CS? Do I have any reason to believe my PHP tune (once I get it) will be any less likely to cause these sort of problems?
Has anyone had any similar experience?
Last edited by johnjohnson78; Feb 3, 2011 at 02:23 PM.
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
I assume you mean from the dealer?
On all my reading on the forums I haven't read about a CS corrupting the PCM. Anyone heard of this?
I don't really know what else to do other than let them reformat the PCM as I certainly don't have the expertise to do anything other than clear trouble codes that keep popping up.
Any insight from those who are more experienced with programmers would be greatly appreciated.
On all my reading on the forums I haven't read about a CS corrupting the PCM. Anyone heard of this?
I don't really know what else to do other than let them reformat the PCM as I certainly don't have the expertise to do anything other than clear trouble codes that keep popping up.
Any insight from those who are more experienced with programmers would be greatly appreciated.
Thread Starter
|
Senior Member
Joined: Sep 2010
Posts: 148
Likes: 0
It also threw a P0605, which is what I think confused them.
The tech said it was some code he's never seen before
Senior Member
Joined: Feb 2004
Posts: 10,390
Likes: 10
Wow. It's well-published info: http://www.aboutautomobile.com/Equip...ol+Module+(PCM)
BTW - on tire size - if a non-standard size is detected (curious that they'd look for that), it's another flag, as only IDS should be changing TS, and only for very select sizes. If it's not a standard IDS-supplied size, it can be assumed it was put there by other means (user flash). All flash acitivity by Ford dealers is logged in IDS.
MGD
Senior Member
Joined: Jan 2009
Posts: 10,731
Likes: 47
From: Concord, NC