CEL Light (Cams)
CEL Light (Cams)
I have GSC 272/272 cams and there is a CEL light on because of it. However I forgot how to perma-delete the CEL for this.. Whenever I try to get the code in EvoScan, it doesn't give me anything. I have OP2.0 and it connects to the ecu just fine, but when I attempt to pull the code it will "fail to communicate with the ecu" or something like that when I select read DTC's.
I have been told that you can perma - delete this CEL in EcuFlash... but How do I do that? :P
I have been told that you can perma - delete this CEL in EcuFlash... but How do I do that? :P
Are they new gsc s2s? If so they are 274s. But if you are referring to a p001 code I know that I had this issue after installing my cams. I know some of the causes can be the cams are off a tooth the cam angle sensor could have went bad or a piece of rvt maybe clogging the oil feed line. I know my car was throwing this code for about 2 months then all of a sudden it went away and has never came back.....wiers I know lol
Are they new gsc s2s? If so they are 274s. But if you are referring to a p001 code I know that I had this issue after installing my cams. I know some of the causes can be the cams are off a tooth the cam angle sensor could have went bad or a piece of rvt maybe clogging the oil feed line. I know my car was throwing this code for about 2 months then all of a sudden it went away and has never came back.....wierd I know lol.
Trending Topics
How can you perma-delete a code that you dont know what it is? A 2003 wont have the P0011 so its not that. Do you have a code reader or can get one? Chances are this is a P0300 since its an VIII and all you need to do is set periphery 2 (FCA) to 0x0001 or if it the new style all 0's except the bottom bit.
That's the problem with evom on the phone. Can't see car specs. I was assuming this was a 9. I have and read about alot of 9s with this issue after cam install. Sorry about that lol.
Ok.. here's some info on my car.
2003 Lancer Evo 8 with quite a few mods on it. I have Tactrix with OP2.0 and the reflash cable along with evoscan and ecuflash. You can pull codes with Evoscan can you not? if so, I have been trying and have had no luck.
Also, when I used Ecuflash to read my ECU/ROM My info is this:
Make: Mitsubishi
Model: Lancer
Submodel: EVO8
Market: USDM
Trans: Manual
Year: 2005 <---- WTF?
ECU ID: (blank)
CASE ID: (blank)
Internal ID: 96940011
Flash Method: Mitsukernel
Memory Model" SH7052
Checksum Module: (blank)
Inherits: evo7base
Anyone want to shed some light on this? Quite odd ROM info. This Evo has been tuned by the previous owner. I can post up my Fuel maps if need be :P
2003 Lancer Evo 8 with quite a few mods on it. I have Tactrix with OP2.0 and the reflash cable along with evoscan and ecuflash. You can pull codes with Evoscan can you not? if so, I have been trying and have had no luck.
Also, when I used Ecuflash to read my ECU/ROM My info is this:
Make: Mitsubishi
Model: Lancer
Submodel: EVO8
Market: USDM
Trans: Manual
Year: 2005 <---- WTF?
ECU ID: (blank)
CASE ID: (blank)
Internal ID: 96940011
Flash Method: Mitsukernel
Memory Model" SH7052
Checksum Module: (blank)
Inherits: evo7base
Anyone want to shed some light on this? Quite odd ROM info. This Evo has been tuned by the previous owner. I can post up my Fuel maps if need be :P
2.0 will work., and my guess with the wrong data input...when prev owner took the car to tuner or he did it himself, he never changed the model year. No big deal, as long as the Internal ID matches your car. and if he flashed the wrong ROM file, I think your car would run like a POS. if at all
Last edited by xtruemassacre; Feb 22, 2013 at 06:24 AM.






