I dont think its that complicated. Take a look at the sample data in the toolbox / green "load" button, and select o2 integrator, ve, ve new, engine speed and throttle pos graphs. Select a frame with strong fluctuation in o2 integrator and zoom in. The integrators are the small real time calculators inside delphi to figure out the best guess what ve should be any given moment. best guess. Say you have o2 integrator front 94.5% and the ve front at that rpm and tp 60, then delphi calculates the new ve at 56.5 - the formula is simply new_ve = current_ve * integrator. If you look at the o2 front voltage at that point and few samples before, it is higher than the clb indicating the cylinder is rich but the trick is that the integrators calculate the required change, real time, same as in closed loop operation. Now my strong guess is that the smart tune process only goes through every sample, organises the new ve values according to the rpm and tp and then calculates the average of "new ve"s for each cell. And that is the smart tune table. So the hard work is really done by delphi. Maybe the smart tune is a bit smarter now that it can interpolate cells it does not have samples for, but i dont think it has very much smartness in it, just averaging over a large set of samples.

Oh yes, as described somewhere earlier and just to remind, when you flash with smart tune checked, it not only sets the afr table to closed loop, it also sets the whole clb table to a fixed value (cant remeber what, maybe 700mv, you can check by reading the smarttune flash back from delphi), and retards spark.

 

We manually change the VE's. The software shows us the Air fuel line on an RPM scale, then we adjust the VE's to get the line where we want it. In my case I calibrate to 13.0 so I will sample each throttle position and record the air fuel for each then adjust the VE's untill I reach my 13.0 target.

 

thnaks...always wondered.

 

Did I understand this right? O2's are not used for VE?

 

To the poster PAUD

I don't believe it's appropriate to add your words into someone else's quote. You did it in two places to one of my postings and in a sarcastic way at that. I can't stop you from doing that. But it sure doesn't add anything.

 

Man, you need to hang around here more and grow a thicker skin. People do this all the time. He was asking specific questions about specific remarks you made and he put his words in red to distinguish from yours.

Might want to read this; https://www.hdforums.com/forum/10723929-post1775.html

 

Merlin V;

It was not sarcastic. I was serious. You proposed, (if I interpreted it right), that smart tune does NOT use o2 sensors to evaluate and create VE numbers. Is that right?
Secondly, I made my remarks in RED to distinguish from yours.
I have read all your post tying very hard to understand what you were asking and why. My comments are my conclusions to your posting.
I stand by my questions, right or wrong. <-This is how I learned to do some basic tunes. Many in here have helped and some did answer rather sarcastically. Be that as it may, I merely asked questions with NO malice in mind.

 

I read his posts as well. I think his only question was how the smart tune feature uses the downloaded data to create the new ve tables. I don't think that question is very hard to understand. Nobody has answered it, because I don't think anybody knows except the guys who wrote or own the software. And they ain't talkin. Trade secret! Anybody who uses smart tune to tune their bikes takes on faith that it's doing the right things. Theorize all you want about O2 data and whatever. But that doesn't make it so.

 

I think I just did answer that question above. Its not a big secret, there are third party apps to do that too. Anybody with programming experience can do that, the sepst log file is a huge xml data set, all you have to do is to parse that and calculate averages. Its just collecting the New VE values and averaging.

 

don't overthink it

(current VE) x (the average O2 intregrator value/100) = (new VE)
100 x 1.02 = 102
100 x 0.96 = 96
(the average O2 intregrator value/100) at the same intersection of the table (rpm & TP or map)

Go to toolbox and open the data run (any) and move the line to where there is a change to O2 int value and a suggested new VE. multiple hits in the same cell are averaged out so to be **** you would have to find them all, add em up and divide by the number to get the average used by smartune.

The O2 intregrator value is derived from the average voltage of the O2 sensors at that cell (TP or map & rpm). don't forget about interpolation. Unless you get the exact rpm (ie 3000) and exact Tp or map # (ie 30) then the smartune suggested will interpolate from the calculated point to the intersection point.