hmm, ok so i didnt touch the accel vs rpm. i started off tuning with stock MAF and i just pulled timing alot in boost i was getting -2 timing at 5 PSI and 0 knock at 14.7 AFR, so i advanced timing a bit so it wasnt so hesitant and slow, so now i have timing about 5-7 in boost and it moves ok, still MAF at stock and AFR at 14.7 gettin one count of knock at most. So i leave the timing alone. But im not getting into open loop early enough, when i give 50+ throttle open loops starts around 3200 or so, and im already in boost so its giving me knock. So i made open loop happen a little earlyer and im not getting so much, 1-2 counts. So i start adjusting MAF to make me rich and in open loop im not seeing me get any richer and im getting alot of knock, 4-8. so im thinking when i adjust my MAF sensor it just gives me knock, not sure why. ether that or im not in open loop soon enough. Im going to do a forced open loop log right now, with the MAF scalled to make me rich, so i can atleast say its not open loop thats the problem. Ill report back in a few min.

 

Ok guys check out these loggs and look through them well. So the one titled FOL_log is "forced open loop log" almost forced open loop. I set everything from 2000 RPM and higher to 10 so anything over 2000RPM was open loop as you can see in the log. The one titled "STK_log" was "stock log" and this was the first log i took after work with the timing close to zero and retarded, also stock MAF values and stock open loop values.

"FOL_LOG"- Notice at one point my knock was as high as 20 counts at a knock voltage of 0.43v at 2937 RPM at about 3 or so PSI, also note my wideband read about 11.0-12.3 AFR, timing was 5-6 advanced, MAF HZ was 512hz. It seems to me that the problem may be related to scaling the MAF sensor, as when i scale the sensor to give me rich conditions i get REDICULOUS knock.

"STK_LOG"- This log was stock MAF sensor settings, pulled timing a few degrees, pretty stock rom. Here you will notice open loop at 2,968 RPM, TPS was 39%, load was 102% AFR displayed 14.x AFR 0 knock count, timing was 0 - (-)2. So it seems thats although very underpowered at max load 130%, at 5 PSI, 3600 RPM, ARF at 14.x, timing -2, TPS 40%, the car didnt knock, if it did it was only 1 count.

So it seems to me that as soon as i adjust my MAF scaling i get crazy knock counts... Not sure what do do from this point in order to confirm this?

 

It looks like you've got it all sorts of confirmed. changed to my MAF scaling had no effect on knock....although I was rockin the base lancer rom. Now that I have the tephra rom on my car, I don't believe I will need to adjust the MAF scaling, since I pushed down on the pedal once or twice, and each time my wideband stuck right down to where it should be, with just the accel enrichment settings stock from the tephra, but using my maf scaling, size, and compensation.

I did get hella knock, at the same load/timing/tps/airflow that I didn't with my base lancer....so that's a pain in the ****, but I'll give it another look tomorrow, got to be a solution. I'm using the same knock multipliers and gains as you btw.

 

Sweet you have the tephra rom now? I didnt think i would need to adjust the stock tephra rom MAF scaling as well because i thought when roadspike worked on it, it was set up "to see boost" but touringbubble told me that its the same as the stock lancer MAF scaling just converted into HZ and GS instead of % and units like the stock lancer ROM. So im im not mistaken i think the MAF scaling is the same as a base lancer just converted, atleast for me (tephra auto rom), what are your settings with the stock tephra rom now so i can compare them to mine?

Also your saying you kept the stock lancer MAF size, scaling, and compensation and changed the accel enrich, or did you change these settings when you used the tephra rom,? sorta misunderstood ya there.

Ok so atleast i know its not just "the car" it has to do with changing something in the tephra rom. These are my MAF scalling and compensations tables, it seems im getting like a max of 8 counts of knock at times, but AFR are OK, in the 12-13 area, ill log my wideband as soon as the cable arrives, so they need more tweeking but compare them to mine:

MAF scaling:

----- HZ > 19------53.9 < G/S
-------------25----- 58.9
-------------50----- 70.2
-------------75----- 79.0
-------------101---- 84.0
-------------126---- 86.5
-------------151---- 87.8
-------------176---- 89.0
-------------201---- 90.3
-------------226---- 91.5
-------------252---- 92.8
-------------277---- 99.1
------------302---- 105.3
------------403---- 110.3
------------503---- 115.4
------------604---- 120.4
------------805---- 125.4
-----------1006--- 130.4
-----------1208--- 135.4
-----------1409--- 140.4
-----------1610--- 145.5


MAF compensation:

------HZ > 19------99 < %
-------------25----- 99
-------------50----- 100
-------------75----- 100
-------------101---- 100
-------------126---- 99
-------------151---- 99
-------------176---- 98
-------------201---- 98
-------------226---- 98
-------------252---- 98
-------------277---- 98
-------------302---- 98
-------------403---- 98
-------------503---- 100
-------------604---- 104
-------------805---- 109
------------1006--- 112
------------1208--- 116
------------1409--- 121
------------1610--- 125

 

OK, I checked your logs. When you are at 80-90 load, and at 2500-2800 rpm, are you in boost? I think you need to pull a smidge of timing there. You're seeing about an average of 3 counts at 80-90 load, so pull 1 degree in that area. Also, once that wideband gets installed, it'll be easier, I promise! If it didn't come yesterday, it wont come today I don't think since it's a holiday (a very important one at that).

Oh, and scaling wise, I'm not sure. Send me your most recent rom and XML, and I'll take a look. It's hard to compare g/s vs % or stuff like that, because some roms (xml's I mean) named a scaling 1 thing, while some name it something else. Temp is a good example, plenty of times it's C, but some of the newer Tephra's it's in F. Sometimes a unit is the same, but the description is diff....or I've seen once or twice a unit that was just flat out wrong!