The DTC Disable thread (P1235, P1241, P1238, etc)
Got Tephra mods working awesome (thank you Tephra). Now the only DTC I'm getting is P0011 which is intake camshaft too far advanced. I don't have any sites that get more than 15 degrees advanced so I suspect maybe the JUN 272's are just too big and the ECU thinks something is wrong. Tephra any way you can look into this one? Would love to have the CEL off. Anyone else with man size cams have this issue?
Got Tephra mods working awesome (thank you Tephra). Now the only DTC I'm getting is P0011 which is intake camshaft too far advanced. I don't have any sites that get more than 15 degrees advanced so I suspect maybe the JUN 272's are just too big and the ECU thinks something is wrong. Tephra any way you can look into this one? Would love to have the CEL off. Anyone else with man size cams have this issue?
We've had a couple locals with that code on stock cams and stock ROM and it went away once the sensor was swapped for a known good one.
- Bryan
Install is perfect and car running strong! I do see that the car is very sensitive with the cam advance. I had to even out the advance under vacuum as any major changes would cause major changes in airflow. Same goes for the exhaust MIVEC. Idle is stable but very rough sounding even at 970 RPM idle speed. I suspect the JUN 272's are a bit bigger than other advertised 272 camshafts out there.
Last edited by Guru; Aug 14, 2010 at 08:39 AM.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
it shouldn't matter how big your cam is
a degree is a degree
either bad sensor, or your MIVEC is lagging behind target too much... ie bad oil control valve...
a degree is a degree

either bad sensor, or your MIVEC is lagging behind target too much... ie bad oil control valve...
I'll check sensor but I'm leaning towards the control valve. It did want to come apart when I removed head and I thought I fixed it but perhaps I need a new one. Thank you everyone!
Last edited by Guru; Aug 14, 2010 at 08:39 AM.
i have done the CEL disable on an MR and there seems to be a problem -
Was driving my friends SST Evo X and it was a total joy.. but he was complaining about a few problems that he was having... the most interesting and confusing one being this -
When cruising lets say at about 40-50 miles in 5th gear and you need to make a 90 degree turn, as we turn, the car downshifts to 3rd gear and when we step back on the throttle, there is NO response.. we tap it like 5-6 times and its just dead! The car is running but there is ZERO throttle response... this was really confusing! Any Ideas?
Gunzo Replied -
So whats the solution here?
Was driving my friends SST Evo X and it was a total joy.. but he was complaining about a few problems that he was having... the most interesting and confusing one being this -
When cruising lets say at about 40-50 miles in 5th gear and you need to make a 90 degree turn, as we turn, the car downshifts to 3rd gear and when we step back on the throttle, there is NO response.. we tap it like 5-6 times and its just dead! The car is running but there is ZERO throttle response... this was really confusing! Any Ideas?
Gunzo Replied -
So whats the solution here?
Has the P0140 disable been found for 2008 USDM yet?
I tried this and it no worky.
<table name="DTC P0139/P0140 Disable 0x1 -> 0x0" category="Misc" address="503b2" type="1D" scaling="Hex8"/>
I dropped this into my evo10base, and so far it at least looks right for every rom I've opened that uses it (5269:5305), or at least the numbers match. I will test it on my MR hopefully this weekend, but it looks right.
question, so i've put all this patches and other fixes into my 5268 roms because i own a GSR, but a guy wanted me to turn off a couple of DTCs in his MR 5269 and when i pulled up his map on ECUflash i saw that it still pulled up those same tables. but the thing is, i haven't put anything in my 5269 xml file. as a matter of fact, when i open the 5269 xmls they're very "bare bones" if you will. so anyways, i tried to put all on FFFF and what not and most of the address are the same, not realizing that some aren't, i still put the fix and it bricked his ecu. so we benched it and now i'm dong research on it. The code he keeps getting is P1235 and it throws him into limp mode, kinda weird. he's got FP green, dw1000s on e85, and mx1 cams. anyways that's besides the point. my question is, do the 5269 roms inherit from the 5268? if so, do i just need to add the 5269 fixes into the 5269 xml and label the tables "MR" or something so i know the difference? i just don't get why it still pulled those tables when it was a different rom.
Yes it does inherit the 5268 xml and that is why it showed up in the 5269. You can just enter the specific address for 5269 within ECUFlash. Open a 5269 ROM in ECUFlash and click (highlight) the specific item you want to edit. Right click and select edit map. Map sure you are on the 5269 tab and just enter the correct address for 5269. This basically will enter a new line in the 5269 xml and it will not use the inherited 5268 address.
question, so i've put all this patches and other fixes into my 5268 roms because i own a GSR, but a guy wanted me to turn off a couple of DTCs in his MR 5269 and when i pulled up his map on ECUflash i saw that it still pulled up those same tables. but the thing is, i haven't put anything in my 5269 xml file. as a matter of fact, when i open the 5269 xmls they're very "bare bones" if you will. so anyways, i tried to put all on FFFF and what not and most of the address are the same, not realizing that some aren't, i still put the fix and it bricked his ecu. so we benched it and now i'm dong research on it. The code he keeps getting is P1235 and it throws him into limp mode, kinda weird. he's got FP green, dw1000s on e85, and mx1 cams. anyways that's besides the point. my question is, do the 5269 roms inherit from the 5268? if so, do i just need to add the 5269 fixes into the 5269 xml and label the tables "MR" or something so i know the difference? i just don't get why it still pulled those tables when it was a different rom.




