hammerdown
forum member
What follows is either an amazing coincidence or something is definitely changed different... Here goes:
I just had my PATS system reprogrammed after loosing all the keys to my car and picked it up this evening to drive home.
I noticed immediately that my Aeroforce OBDII scan gauge was cycling power over and over and over again.. I had to reach down and unplug it and re-seat it to get it to come back on.
When I finally got it working again I noticed my AFR's were much leaner than I'm used to seeing even for Closed Loop/Cruising (car has a blower, CAI, larger MAF housing, blah blah blah..). My immediate concern was that having the PATS erased and reprogrammed somehow overwrote my tune back to stock.. This isn't supposed to happen, and I don't know for a fact that it did, but my suspicions were bolstered as it seemed like the speedo was reading way too fast (car also has 4:10's). So I pulled over in the nearest gas station and grabbed out my SCT handheld and flashed the tune back in. Although in retrospect, with the bigger injectors, and all the other changes, I'm not sure if the car could have even ran at all on a factory tune.. IDK maybe it would somewhat, or maybe it was all my hyperparanoia kicking in. Either way I reprogrammed it to be sure..
Pulled back out, AFR's looking good, Open Loop/Closed Loop transitions happening where they should be, speedo reading correct, life it good.
I get about a mile up the road and I get a total loss of power. Get the MIL, get the wrench light, theft light pops up, world has gone to hell in a handbasket. Push down the clutch, RPM's drop to 0, car rolls to a stop.
I use the AeroForce to pull codes:
P0607 (Indicates PCM/CPU has encountered an error)
P2707 (Electronic Throttle Control area of PCM failed self-test).
I try to start the car and it fired up normally. Thinking maybe it's just jitters from just having all this crap reprogrammed plus me re-flashing the tune. Use the AeroForce to clear the DTC's and drive on.
Get about two more miles up the road - same thing again.
Wash-rinse-repeat, and I'm off again. This time I limp it home by accelerating and stepping on the clutch and coasting, only using throttle in short bursts.
Get it in the driveway and it throws the codes again - engine dies. WTF?
Cycle the ignition key off and back on - attempt to start the car. I get a 'chick-chick-chick' sound, but not like when you have a dead battery. Much slower and much more pronounced. More like the starter is firmly engaging the flywheel at full force, but the solenoid is cycling on and off in almost a perfect twice a second rhythm. Dash gauge lights and scan gauge are cycling on and off in perfect lock step rhythm.
I turn the key off and back to run - fuel pump primes, but then I hear the rhythm again. This time it's the fuel pump priming up over and over and over just like I was cycling the key. Aeroforce Gauge is blinking on and off in rhythm.
I unplug the AeroForce from the OBDII and the cycling stops. OK, that's very strange, it's never done anything like this before.
Plug Aeroforce back in and the cycling starts up again.. It's literally as if there were a main power circuit braker and some little gremlin was sitting under the hood flipping it back and forth twice a second.
Ok, obviously something is up with either the AeroForce or the OBDII or both. Either way the two are mixing like oil and water and causing all sorts of problems. Causing DTC's and engine failure.
Leave the AeroForce unplugged and use my SCT to clear the codes and see what happens.
What happend was the car stopped acting up and ran perfectly.. I drove it to the next town over and left it idling in the driveway for nearly 30 min. No issues whatsoever (Aeroforce disconnected).
So now, the $64,000 question.. What changed between the time the car was playing nice with the AeroForce (before the PATS reprogramming) and after I picked it up when all this nonsense started?..
It could very likely be the AeroForce shorting something on the OBDII circuit and it was just destined to eventually fail, but it's also VERY suspicious that life was good before the PATS programming, and this only started since I brought the car home this evening.
Either they changed something with the way OBDII acts while they were in there and now it conflicts with the AeroForce, or it's just an INCREDIBLE coincidence that the AeroForce just up and decided to fail and start causing electrical faults after I picked up the car from the dealership.
It doesn't seem like it would be likely but I suppost it's possible I could have caused something to change too as I was mucking about with AutoEnginuity for a couple of days trying everything I could to program my own keys. Although all that really involved was my attempting to clear DTCs and (unsuccessfully) gain PATS security access.
That thread is here: http://www.s197forum.com/forum/showthread.php?t=81421
Very very strange; it's a mystery to me... Thoughts?
-HD
I just had my PATS system reprogrammed after loosing all the keys to my car and picked it up this evening to drive home.
I noticed immediately that my Aeroforce OBDII scan gauge was cycling power over and over and over again.. I had to reach down and unplug it and re-seat it to get it to come back on.
When I finally got it working again I noticed my AFR's were much leaner than I'm used to seeing even for Closed Loop/Cruising (car has a blower, CAI, larger MAF housing, blah blah blah..). My immediate concern was that having the PATS erased and reprogrammed somehow overwrote my tune back to stock.. This isn't supposed to happen, and I don't know for a fact that it did, but my suspicions were bolstered as it seemed like the speedo was reading way too fast (car also has 4:10's). So I pulled over in the nearest gas station and grabbed out my SCT handheld and flashed the tune back in. Although in retrospect, with the bigger injectors, and all the other changes, I'm not sure if the car could have even ran at all on a factory tune.. IDK maybe it would somewhat, or maybe it was all my hyperparanoia kicking in. Either way I reprogrammed it to be sure..
Pulled back out, AFR's looking good, Open Loop/Closed Loop transitions happening where they should be, speedo reading correct, life it good.
I get about a mile up the road and I get a total loss of power. Get the MIL, get the wrench light, theft light pops up, world has gone to hell in a handbasket. Push down the clutch, RPM's drop to 0, car rolls to a stop.
I use the AeroForce to pull codes:
P0607 (Indicates PCM/CPU has encountered an error)
P2707 (Electronic Throttle Control area of PCM failed self-test).
I try to start the car and it fired up normally. Thinking maybe it's just jitters from just having all this crap reprogrammed plus me re-flashing the tune. Use the AeroForce to clear the DTC's and drive on.
Get about two more miles up the road - same thing again.
Wash-rinse-repeat, and I'm off again. This time I limp it home by accelerating and stepping on the clutch and coasting, only using throttle in short bursts.
Get it in the driveway and it throws the codes again - engine dies. WTF?
Cycle the ignition key off and back on - attempt to start the car. I get a 'chick-chick-chick' sound, but not like when you have a dead battery. Much slower and much more pronounced. More like the starter is firmly engaging the flywheel at full force, but the solenoid is cycling on and off in almost a perfect twice a second rhythm. Dash gauge lights and scan gauge are cycling on and off in perfect lock step rhythm.
I turn the key off and back to run - fuel pump primes, but then I hear the rhythm again. This time it's the fuel pump priming up over and over and over just like I was cycling the key. Aeroforce Gauge is blinking on and off in rhythm.
I unplug the AeroForce from the OBDII and the cycling stops. OK, that's very strange, it's never done anything like this before.
Plug Aeroforce back in and the cycling starts up again.. It's literally as if there were a main power circuit braker and some little gremlin was sitting under the hood flipping it back and forth twice a second.
Ok, obviously something is up with either the AeroForce or the OBDII or both. Either way the two are mixing like oil and water and causing all sorts of problems. Causing DTC's and engine failure.
Leave the AeroForce unplugged and use my SCT to clear the codes and see what happens.
What happend was the car stopped acting up and ran perfectly.. I drove it to the next town over and left it idling in the driveway for nearly 30 min. No issues whatsoever (Aeroforce disconnected).
So now, the $64,000 question.. What changed between the time the car was playing nice with the AeroForce (before the PATS reprogramming) and after I picked it up when all this nonsense started?..
It could very likely be the AeroForce shorting something on the OBDII circuit and it was just destined to eventually fail, but it's also VERY suspicious that life was good before the PATS programming, and this only started since I brought the car home this evening.
Either they changed something with the way OBDII acts while they were in there and now it conflicts with the AeroForce, or it's just an INCREDIBLE coincidence that the AeroForce just up and decided to fail and start causing electrical faults after I picked up the car from the dealership.
It doesn't seem like it would be likely but I suppost it's possible I could have caused something to change too as I was mucking about with AutoEnginuity for a couple of days trying everything I could to program my own keys. Although all that really involved was my attempting to clear DTCs and (unsuccessfully) gain PATS security access.
That thread is here: http://www.s197forum.com/forum/showthread.php?t=81421
Very very strange; it's a mystery to me... Thoughts?
-HD
Last edited: