96530006 Issues

[MadMsheen]

I just recently converted my ROM from the 05 USDM 96940011 to the 05 EDM 96530006. I'm going to list some issues, and hope some people have gone through them already with possible fixes.

1. During normal driving I get the p0505 CEL. I got this the first time I took her out after flashing the ROM. I've done the SAS adjustment with actuator activated. Actuated at 800 RPM, with regular idle at 1000 RPM; any higher and I'm looking at a 1100 RPM non-actuated. When actuated it is on the edge of lumpy. This morning, the 2nd time I've taken her out, got the code again. I know some people have eliminated the p0505 code after raising the actuated RPM adjustment, but I can't go any higher without compromising my non-actuated RPM.

2. Larger timing fluctuations while in neutral; mostly 3-4 degrees lower than normal. Not sure why this is happening vs the 96940011 ROM.

3. Slower to recover from RPM drop off when coming to a complete stop or lifting. On the 96940011 ROM, my rpms might drop to about 850 RPM whenever I put my clutch in long enough for my car to go into open loop, but it recovered fairly quickly. Now, it seems to take two to three times as long to recover whether in gear or out. Granted the recovery is smoother, now, it still takes some time. It also reflects in the length of time it takes my AFR to get to O2.

4. Got fuel cut at 260 load approximately 20 psi. That one caught me by surprise. Thought my lean spool disable wasn't working. Checked my logs, and it's fuel cut. I'll have to check my boost parameters, but I'm pretty sure I ported all settings over.

Other than that, so far so good. Any help would be appreciated.

I know we've got a Tuner Tech Talk social group, but I wanted to put this out here for everyone to see, since some of our local tuners might be quiet DIY guys. It's easier to discover ninja talent if we put it out here in the open. :)

[MadMsheen]

I might have found the issue with #4.

The table for Boost Cut Load on 96940011 is set to 319 for RPM Ranges from 3000-7000. On 96530006 there is a table defined as Boost Limit which came default as 230. I did not adjust that table. I've changed the values to 319. I'm hoping they're the same table.

Fuel cut = not fun.

[Zac 9-7-1]

So the 319, and the 230 are referenced to load? Or a different measurment for boost?

[MadMsheen]

So the 319, and the 230 are referenced to load? Or a different measurment for boost?

The scaling is listed as LoadBoost, so I believe it is. There is a setting for Boost Cut Delay Timer, which I had set to 1 second. My car didn't cut fuel until after it peaked at 295 load and dropped to 256 load. But 1 second after hitting 230 load it started its boost cut timer from LogEntryTime 37:43.2 for 230 load and fuel cut at LogEntryTime 37:44.2 on the dot. I think that was definitely my problem.

I'm going to leave my Boost Cut Delay to 1000 ms, to make sure the values I've changed in the Boost Limit table is actually what fixed the problem, if it is truly resolved.

While meth injected on the s256 I was hitting in upwards of 376 load with the values still set to 319, and did not hit fuel cut; strange indeed. I think the 319 might be interpolated as maximum/unlimited by the ECU, since that is the maximum value that can be entered in the table.

[Zac 9-7-1]

I see now. makes a certian understanding. I am still trying to learn these things.

So in your log it shows your boost cut delay 1 sec before fuel cut? thats neat stuff.

[Testudo]

I have a feeling 1,2 and 3 are related. Even though you don't like the lumpy idle, try raising the idle up some. What is your idle timing set at? 7* or 8*?

[MadMsheen]

I see now. makes a certian understanding. I am still trying to learn these things.

This is my primary reason for posting this thread out in the open.


So in your log it shows your boost cut delay 1 sec before fuel cut? thats neat stuff.

The log actually shows the BoostLoad value of 230 exactly 1 second, which is my Boost Cut Delay value, before fuel cut aka boost cut.

Since Load didn't drop below the BoostLoad maximum of 230 before the 1 second Boost Cut Delay timer expired the ECU cut fuel. Usually my pulls don't drop below 230 load for approximately 2 seconds in 2nd gear.

[MadMsheen]

I have a feeling 1,2 and 3 are related. Even though you don't like the lumpy idle, try raising the idle up some. What is your idle timing set at? 7* or 8*?

13* with 1000 RPM standard

I wonder if my idle timing is too high for this ROM. I'll try dropping it.

[Testudo]

Just adjust the BISS screw and call it a day. ;)

[MadMsheen]

Just adjust the BISS screw and call it a day. ;)

Well, George, I might just have to do that. I'm scrutinizing my logs more, and it seems the car is actually running much better. I use the 13* of timing with more fuel at idle on cold startup to keep my neighbors at bay. This creates a smoother idle with less noise.

The RPM fluctuation on Decel Fuel Cut has actually settled down vs my 96940011 ROM. Granted it takes a little longer to reach the programmed 1000 rpm, I don't have the spike up to 1200 RPM from the 850 RPM like before.

I think this has a lot to do with the Decel Fuel Cut Ignition Retard table. On 96940011 the table adjustments had no effect. Now, with the 96530006 it's actually working, and I've adjusted for the ECU NOT to pull timing when I decel into fuel cut, which is keeping my clutch-in RPM stable.

I hate doing this, since it's not by the book, but I'm going to adjust the BISS with SAS actuated to a higher actuated RPM point and I'll adjust my requested non-actuated RPM lower so it'll actually end up at 1000 RPM.

[Testudo]

IF you set Periphery2, bit 08 (idle test) to 0 you will disable the p0505 code. One thing I have done to Evo's that have switched to the 0006 is change the standard idle tables at warm up to the values in the 0011 Rom. Another thing that might help is changing the ISCV values to those in the 88590015. If those solutions don't help you, it's time to get out of your box and mess with the BISS. :)

[MadMsheen]

Periphery2 FCA on my xml only lists P0506 and p0507 Idle Test. But I disabled them anyway; hopefully, p0505 is in there with them.

I also disabled the Periphery FAA bit 9 to turn off Warm Up Ignition Retard, since there are a few tables that seem to call up that table. I don't think i need it. But correct me if anyone has found issues with disabling the cold start ignition timing retard.

[jba3]

Setting the boost limit to 319 will disable it, which effectively disables all of the factory overboost protection. I've seen it in other tunes and it concerns me because it gives you the potential to blow your motor if your wastegate line is damaged/doesn't open or any other things that can lead to overboosting. The tuning methodologies I've read up on always recommend keeping that table enabled, and just upping the limit until you don't hit fuel cut, but leaving it active as a ceiling to protect yourself if something else goes wrong.

With the table enabled, your motor might be saved by hitting fuel cut before going way out of range. Table disabled and pushing the car when it shouldn't be ... have fun patching the hole in the block the piston leaves. ;)

I know you're much more meticulous about these things than 99% of us are, so I don't have any worries that you'd overboost and blow your motor, but for other people still new to tuning and/or monitoring.... :o

[MadMsheen]

James, that's a great idea. I'll do it. Although, my limit right now is at about 300 load. I'll set it to 300. :D

The boost should never be above 300 for more than a second anyway.

[MadMsheen]

update: Periphery2 FCA bit 8 did the trick. No more p0505.

Also, changing the values to negative for the Fuel Cut Ignition Retard map is working for keeping my timing and revs up. She's pretty smooth even when clutching in.

[fjo_newport]

One thing I've found adjusting the idle is that you need to warm the car up, then reset the ECU, then adjust the the idle using SAS. There are some learned idle variables in the ECU that can hose you. I also found that adjusting the idle a little higher than target will fix some of those issues in the original post.

[MadMsheen]

I also found that adjusting the idle a little higher than target will fix some of those issues in the original post.

I'll try again when warm. I believe I adjusted it warm the first time, but it can't hurt to do it again.

Would this work if I program the desired idle to 900 RPM, then adjust the actuated SAS so when not actuated it'll settle to 1000 RPM, thus giving my desired idle?

Update: Did a full pull today without issues. It was the BoostLoad values causing fuel cut.

[Testudo]

update: Periphery2 FCA bit 8 did the trick. No more p0505.

Excellent.

[jba3]

Update: Did a full pull today without issues. It was the BoostLoad values causing fuel cut.

Cool, let me know what else is happening with it. JBA3 motorsports with more great advice! :thumbsup:

[MadMsheen]

Still smooth as silk. I actually ported Tallen's car to the 95630006 ROM with some "minor" tweaks. Seems to be working for him so far. Next up: ECU controlled boost. :)

[JOE-EVO]

Uh huh......I bet you added to your "database" while you were at it.

[jba3]

Still smooth as silk. I actually ported Tallen's car to the 95630006 ROM with some "minor" tweaks. Seems to be working for him so far. Next up: ECU controlled boost. :)

Did you try doing it with the USDM map sensor instead of the JDM? If you did, was it just the reverse of converting the USDM to JDM?

[MadMsheen]

Did you try doing it with the USDM map sensor instead of the JDM? If you did, was it just the reverse of converting the USDM to JDM?

Matt has a JDM MAP sensor, or else I would've just given him a USDM ROM. I will be looking into getting a USDM MAP sensor version done, just to have it for my "uncool" friends. :001_tongue: