made 3 changes to ve but not much diffrence

[6speedterror]

i did 3 30 mile drives today made the changes to the ve and it did get a bit better but the wideband is still showing about -12% off. i am going by the table that says

then i multipy by % is that the right table? cuz its been changing the table by 3% but it is better that the -20% that it was when i started

[Bill@HPTuners]

are you in open loop speed density making said changes?

[S2H]

looks like mostly +/- a few now..so thats good
start using multiply by %-half

why do you have wideband in the table instead of EIO section??


easier to post the log file and the tune so we can really see whats going on

also get that table display at 24 bytes or below and you will get better resolution and probably have much better results
widebands ned higher resolution to be effective..henceforth the EIO section which logs at 40 frames per second..and right now as you sit its only going to see 5 frames per second...
it will be extremely hard to get any good results the way you have it now

[Bill@HPTuners]

why do you have wideband in the table instead of EIO section??

because he's logging through the a/c pressure sensor & using a custom pid to produce the wideband figures.

[S2H]

because he's logging through the a/c pressure sensor & using a custom pid to produce the wideband figures.

well...definately less stuff in the table is more then...you really need a higher resolution to get accurate wideband data

[6speedterror]

yep its in OLSD. here are the tune and the last log i did on the way home. what else could i manage to take off from the scanner? maybe mph and the inj pulse width, ect, iat, will be taking out the trans current gear, idle pids how do i know the resolution its logging at?

[Bill@HPTuners]

ok
a. your out of injector at wot.
b. if your not working on idle in a log you can do without the idle trims in the log
c. strongly consider on of the real time tuning custom operating systems available to you...the SD custom OS would be a great choice since it rids you of the low resolution secondary VE table while retaining full functionality of both the high & low octane tables while in SD mode...and of course giving you real time feedback.

that should get you pretty close to 24 bytes.

[6speedterror]

thanks for the help! will deffinatly consider the rtt and and some injectors, and how do you know when your out of injectors?

[EC_Tune]

When the Injector Duty Cycle goes to 100%.

[6speedterror]

would you guys say start multipy by % half now? or still do the multipy by percent

[Bill@HPTuners]

once i get under 10% i start doing multiply by 1/2

[S2H]

I usually go half once I'm down to about 5% or less on most cells