How to loose 200kgs?....

[Dylan]

I use the monitor window too. No spreadsheets or histograms. TPS MAP and RPM in the top window.
Target AFR and actual wideband and calc ve in the bottom. Only make changes once it's warm then once the VE is right tune the charge temp to get consistency.

[Holden202T]

I setup this dash screen to use for dyno tuning, just get it to a load point, watch the wideband and target till they match, also the calc VE is in there so you can compare it to the current load point.

i've also setup in the key shortcuts A and Z as increment and decrement so then can just locate the mouse over the update button, then go up and down and then mouse click to sent it, works pretty well.... and then use the arrow keys to move around the table.

also the alarm settings in the ADX are worth using, i set the coolant to go orange at 105 and red at 107 or something like that, so if you see it flash red you can easily pull out of it.... you can do similar with wideband, if its red you want to put out of a power run etc.

[antus]

Maybe we should have called "Calculated VE" "Estimated VE" instead... probably a better representation of how it should be used.

[Dylan]

I use calc ve as a guide too but it's pretty good. Especilly whe the ve is already close. When it's early on or the ve is choppy it csn be misleading.

[Holden202T]

yeah its a bit of a hard one, theoretically its calculating the new VE from the old one along with target and wideband AFR's so it technically is named right, i guess just as long as people know its just calculating a new figure for you from the data you give it then its ok

[Gareth]

Im glad that calcVE stuff has been pointed out, I assumed it was a wonder tool that did it all buy itself, thanks for explaining that guys, makes perfect sense

[Jayme]

yeah nothing wrong with the calcVE itself... its all about how you use it, for example if you flit through a VE cell briefly during Decel, the wideband reading is going to be waaaaaaay off reality.. and so will the calcVE reading. if you use that log in a histogram then copy the calcVE histogram over your VE table, then that cell will by a big incorrect spike. thats why I tend to use the monitor window, you can exclude the cells that are bullshitting to you.

[Dylan]

Look for steady tps readings and map and rpm.

[Holden202T]

yeah calce ve is definately good for a long log say driving to work one day, just hit record and drive, then after the drive you can use calc ve numbers with average or something like that and that will help filter out alot of the lean spikes you might see, but always use your head, after putting calc ve data into the ve table view the ve table in graph and look for bit spikes in an otherwise smooth area, if its brought back up to fit in its most likely going to be right, and if its too rich at least its not going to hurt the motor!

[Dylan]

I recently brought a monitor to run off my laptop. Best thing I ever done.
Have the logs playing on my laptop and the 3D graph of the VE table on the second 22" monitor.
Makes it a lot easier.