turbodailydan

hey guys.


before i start here is a brief spec:

wisecos
manley tt rods
mr headgasket. arp studs
map beehives & gsc s2's
ets fmic
walbro 255
pte880
speed density
fabworx t3 manifold
bullseye borg warner s256 ett - .55 ex
boost currently set to 1.8bar

using uk fuel - 97RON


recently changed turbo setup from a holset hx35 with .63 rear end as i found it way too slow spooling on a single scroll housing so have put my trusty s256 on there. the timing map for the holset was quite aggresive to aid in spooling the thing up but Im now hitting boost a good 1k rpm sooner so alot of timing needs taking out.

Hit a 17 knock count on the 4th gear pull so ive removed 4 degrees from the 100 load onwards to start with and smoothed it out, but before i flash it back on im looking for some input on where to go with this and what required adjustments are obvious to those who map on here.

attached my rom and a log from a quick 4th gear pull (note that its not 100% WOT as it was the first road test after turbo setup change so was checking where it was hitting boost before i could edit the map) also a 3rd gear burst and 1st- 2nd i think.

thanks

domyz

iTrader: (6)

Can't open the ROM file, could you add your XML, that will simplify things.

turbodailydan

I downloaded the xml pack from the tephra v7 thread

domyz

iTrader: (6)

First of all, your logs are near useless. Uncheck everything except:

Load 1byte, RPM, LC1 wideband, timing advance, knocksum.
This will add more resolution to your logs so we can decipher what's happening more precisely (more items logged per second).


But because you hit 17 counts, I suggest you to not do another pull before we can open your ROM and have a look. I can see a 21* of advance, at 207 load/3500rpm which is very agressive.
I'm curious to see your map.

turbodailydan

I will fire up the laptop and find the xml

domyz

iTrader: (6)

I think it should be 96536706

turbodailydan

should be this one

turbodailydan

or this one.

domyz

iTrader: (6)

Many things to say about that tune.

-First, 2 byte to 1 byte load factor seems too low.. you can see load in your logs that load crosses the maximum and start back to 0.... Set it at 1.5 in ecuflash AND evoscan.

-Your timing map is really messy.

-Your tuner played with idle cells in the fuel map which indicates me that he doesn't know that they have NO effect on fueling at idle since open loop setting are stock.

--He played with Map sensor volts vs MAP kpa which mess the axis of the VE table, making it hard to tune. The more clever way would have been playing with KPA vs load.

I lowered your spool up timing in the zone where it should be and (could need more tuning from there).
Since you run good fuel, you could you run more than this, but more timing doesn't mean faster spool.


By your logs, AFR seems safe over 200 load but keep an eye on it when pushing it for the first time.

Maybe there is something else but that's all the time I have for now, good luck.

turbodailydan

Thanks mate, will flash that on and get a log to report back.

Could you explain this in more detail for me? "--He played with Map sensor volts vs MAP kpa which mess the axis of the VE table, making it hard to tune. The more clever way would have been playing with KPA vs load."

Is it worth messing with that now or just leave it alone?

domyz

iTrader: (6)

Leave SD tuning alone for now. Playing with fuel and timing maps should be enough for now.

turbodailydan

ok no probs.

what would the ill effect of this be?

-First, 2 byte to 1 byte load factor seems too low.. you can see load in your logs that load crosses the maximum and start back to 0.... Set it at 1.5 in ecuflash AND evoscan

*edit - just read its for logging resolution

turbodailydan

couple of logs taken

Not seing any knock however it doesnt feel very punchy when on boost. let me know what you think.

domyz

iTrader: (6)

First, I think you didn't change the evoscan 1byte load factor
from memory: right click / edit data items / 1 byte load / replace 1.2 by 1.5 in the formula
Also according to logs, you seem to hit 306load (max 1byte load with 1.2CF) +57load(bad reading from your log) which will most likely need a rescale because your map goes to 350.

Also I'm 100% sure it's really weak, main reason is because you are hitting negative timing values when fully spooled. AFR however does seems not too bad (a little lean at first and a little rich at higher rpm) .
Let me update this post with a little bit more agressive map, rescaled. In the future make sure you get some logs with 1byte load properly set up.

domyz

iTrader: (6)

above post updated (timing map)