So remove it?

 

I'm not even completely sure when its used. The program only goes there if a bit flag is set and that bit flag code is really tough to track.

 

can you post the table? I can then set the values the higher and see if that stops the stutter, what conditions are required to set the bit?

Andy

 

That will need to wait until tomorrow I'm just too tired right now

 

no probs I've made a few changes that I want to try with the current setup anyway and will let you know how it goes

 

Hmm how odd your rom uses a 3d table with rpm and load instead of just load....

It seems to be kinda like a Maf Comp in the ways its used so it definitely directly effects fuel. There is the same bit test that allows it to be used or not so there is probably some code that is setting that bit as my guess causing the hiccup.

The RPM thing i'm not too sure if thats the right scaling.

XML to try:
<table name="3d Comp" address="6071" type="3D" level="1" scaling="Percent (128)">
<table name="Load" address="66f2" type="X Axis" elements="14" scaling="Load"/>
<table name="RPM" address="7adc" type="Y Axis" elements="8" scaling="RPM"/>
</table>

<table name="3d Comp Min RPM" address="1718" type="1D" level="1" scaling="RPMStatLimit"/>


Edit:
So this is the warmup enrichment table apparently should be easy to figure out if the lower right hand side keeps getting used or not.

 

I was just going over old threads on this table actually. Do you see in the code when exactly this table is used, or a control table based on coolant temp?

 

There is a bitflag when it seems to be used a tst for 0x2h which unfortunately is used in hundreds of places so its going to be really hard for me to figure out exactly what te condition is when its used.

There is also a sort of minimum RPM associated with it. I could probably could track down the bit flag assuming it doesn't rely on other bit flags cause then its just going to get messy to track.

 

Interestingly enough I found something in the evo 8 where the MAF Hz completely reset to zero probably for a second or two before the code is cleared.

So there are probably two ways of dealing with this assuming its the problem. First is to ensure that the bitflag is never set which is more complicated or just ignore it altogether and hope that this simple workaround Fixes it.

9417:
<table name="Maf Reset Disable (stock 0xA021) -> 0x9 (nop)" address="11258" type="1D" level="1" scaling="Hex16"/>

9653:
<table name="Maf Reset Disable (stock 0xA021) -> 0x9 (nop)" address="11174" type="1D" level="1" scaling="Hex16"/>

 

Ill let you know tomarro

 

Ill try to get it loaded before u leave work today and let you know

 

Ok I got the patch added and I only felt the car cut out once during city driving. I will be driving the freeway tomorrow and will report back my findings.

 

Same place in the 2-3k rpm range?

It would help to know what sort of load is on the car when this happens.

 

yeah it was right around 2k. Ill be able to tell you better tomorrow when Im on the freeway. Ill try to get a log of it if it happens again.

 

I'll keep looking for things to tweak. Maybe I'll disable this bit flag setting next which seems to be some sort of error flag like for the maf. We'll figure it out at some point haha