nonschlont

iTrader: (3)

ok, I have read the entire thread reguarding re-scaling maps for 300 load, etc. Well I have rescaled my boost tables to get better resolution w/ Boost.
Table lookes like this: Fuel map looks like this:
1500 500
2000 1000
2500 1500
2750 2000
3000 2500
3250 2750
3500 3000
3750 3500
4000 3750
4250 4000
4500 4500
5000 5000
5500 5500
6000 6000
6500 6500
7000 7000
I have noticed that logging AFR, Im getting lil dips @ inbetween rpm ranges. Example @ 4000 AFR = 11.2 and @ 4250 = 10.8AFR. I was also getting a dip @ 2750 (reason for rescale already)

My questions are... Is it a good idea to rescale the fuel map (like this), and is it ok that the rpm ranges are different? In the example above, there is a dip @ 4250, can I just change 4000 to 4250? Or should I rescale a lil differently?

Sorry if this has been asked before, I couldnt find it...

tephra

iTrader: (6)

u should be able to tune it out.

you will probably find that there is a slight delay in AFR between the map and the sensor (especially during spool)

personally I havn't (yet) needed to rescale my fuel/timing maps

I did for boost because that is very finiky + less than 2500 is pointless

nonschlont

iTrader: (3)

VGergo

iTrader: (3)

Can I start my boost table @2500RPM ? I would higher resolution in mid range.
Just write over the RPM settings like that :


2500
2750
3000
3250
3500
3750
4000
4250
4500
4750
5000
5250
5500
6000
7000

and like the same method in the fuel and ignition table if dont need the 30,50,60,80 load and anything upper 320 than I coud use that columns to have better resolution in the wot load part like 225 230 235 240 250 265 270 275 280 285 290 300 320 just need to retune the fuel and ignition table settings after it ?

jrohner

That's pretty much what I did. I really needed it every 250 rpms in certain places, but not everywhere.

Jack_of_Trades

iTrader: (17)

When RPM is lower than the lowest value in the table, the ECU uses the next known value. Same for any RPM range above the highest value in the table.

As an example, if your table was scaled from 4500-7000 RPM, anything below 4500rpm will use the value in the 4500 RPM column. Once you pass 7000 RPM the ECU will use the last known value, which is whatever is in the 7000 column. The same goes for the RPM/LOAD columns in the fuel/timing maps.

I used to run 100% WGDC before 2800 RPM and 100% WGDC after 5500rpm when I was running 29psi on the stock turbo and meth so I scaled my base WGDC table from 2800-5500 RPM in equal increments for the greatest resolution with 100% WGDC in the first and last column.

VGergo

iTrader: (3)

Jack_of_Trades,

Great infos thank you, I'm always learning here something new