Weird issues after cam install
Sep 29, 2013, 08:33 PM
#1
Weird issues after cam install
So I have been having a weird issues after i installed my s2. Every time I now do a pull load1byte will read up to 295.2 and then start over. This never did this before.
The car came with a JDM Head including cams when I purchased it. I have since installed Evo 8 s2 cams and trigger sensor. I am still using the 96530706 rom which I was told was a JDM rom. Did my switching to those parts cause this issue? I had no issues reading above that load number before and have no idea why it would be a problem now.
I am using a Omni4bar map sensor. I have a KPA formula in evo scan which seems to be reading correctly. My guess is the ROM is the issue but i am no ROM expert.
The car came with a JDM Head including cams when I purchased it. I have since installed Evo 8 s2 cams and trigger sensor. I am still using the 96530706 rom which I was told was a JDM rom. Did my switching to those parts cause this issue? I had no issues reading above that load number before and have no idea why it would be a problem now.
I am using a Omni4bar map sensor. I have a KPA formula in evo scan which seems to be reading correctly. My guess is the ROM is the issue but i am no ROM expert.
Sep 30, 2013, 09:02 AM
#2
So I did a little more digging. All my old pulls happened on stock 8 turbo and cams. From the looks of my logs i never saw higher then 289 in the load 1 byte column. This is on Stock MAf and Speed Density.
I have since switch to S2 Cams and put the JDM 16g Turbo back on. I left the boost controller in the same spot. The highest load I can achieve is 295.2 and then is seems to just start over. I have no issues with the load from my map sensor. This is currently on stock Maf. I am not sure if this is an issue with EvoScan or ECUFlash at this point. I have attached an illustration of what i am talking about. Any ideas on what i might be doing wrong?
I have since switch to S2 Cams and put the JDM 16g Turbo back on. I left the boost controller in the same spot. The highest load I can achieve is 295.2 and then is seems to just start over. I have no issues with the load from my map sensor. This is currently on stock Maf. I am not sure if this is an issue with EvoScan or ECUFlash at this point. I have attached an illustration of what i am talking about. Any ideas on what i might be doing wrong?
Sep 30, 2013, 03:15 PM
#4
So I did a little more digging. All my old pulls happened on stock 8 turbo and cams. From the looks of my logs i never saw higher then 289 in the load 1 byte column. This is on Stock MAf and Speed Density.
I have since switch to S2 Cams and put the JDM 16g Turbo back on. I left the boost controller in the same spot. The highest load I can achieve is 295.2 and then is seems to just start over. I have no issues with the load from my map sensor. This is currently on stock Maf. I am not sure if this is an issue with EvoScan or ECUFlash at this point. I have attached an illustration of what i am talking about. Any ideas on what i might be doing wrong?
I have since switch to S2 Cams and put the JDM 16g Turbo back on. I left the boost controller in the same spot. The highest load I can achieve is 295.2 and then is seems to just start over. I have no issues with the load from my map sensor. This is currently on stock Maf. I am not sure if this is an issue with EvoScan or ECUFlash at this point. I have attached an illustration of what i am talking about. Any ideas on what i might be doing wrong?
In your rom set your 2byte to 1byte load factor (under MISC Tephra) to 1.4, do the same in your evoscan formula for load1byte.
Enjoy the cams
Thread
Thread Starter
Forum
Replies
Last Post
Fuchsig
ECU Flash
3
Jan 11, 2015 03:20 PM