Yes it was meant to refer to the Front Cylinder, not the rear

 

I can appreciate the forum let me talk in circles trying to learn. The bottom line is probably me and the way I am riding to collect the data. I am going to raise my hit count I had been using 30 and concentrate on quality. I will continue with my current tune and I will start one over with my original fuel moto map. I am not having any issues per se with the map I manually adjusted VEs on bike to me seems to run pretty good honestly its the best I have had the bike running since I put the cams in but my data logs are saying that the VEs are not leveled out. I get myself confused when a cell seems level then moves a lot.

 

Has this been done with my Fuel Moto map or is this something I need to do?

 

Let me tell you what I have been doing this week....I have a four gauge screen set up for Lambda (AFR), MAP, CLI and AFF. For the CLI and AFF, you can select either front or back cylinder. I reset the trim tables when I load the tune. I run through all of the RPM and MAP possibilities. You will see the CLI table starting to stabilize at 100 +/- 2-3 percent. The AFF table show a number that will turn out to be the amount of change that will be made in each cell. I do not do a data log until the CLI stabilizes around 100. I think you get a cleaner data log if you do not start to track the data until the trim tables get all of the adjustments in place with your new tune.

I am postulating that when the CLI and AFF tables both run 100 +/- 2-3, your VE tables are close.

Just curious if anyone else has tried this and I am wondering if this makes sense to others on the board...

 

Lion,

Very similiar to what I propose to do. Run data logs and make adjustments. then test ride with CLI showing for front and rear cylinders. When amount of change in the CLI is less than 5 percent....bingo...tune is done.

 

I have the VE tables dialed in. What is a good AFR setup for SE204 cams?

 

I think that what I am doing is a little different. I am checking the VE table with the AFF Gauge. I think that if the AFF table is near 100 percent, the VE table is correct. From what I have seen, the CLI table will track towards 100 percent as the trim table adjusts the VE tables via the O2 sensors. I will not do a log run until the CLI is at or near 100 percent.

 

I'm a little confused on this point. Wont changing the bias tables to 700 increase the afr?

Thanks to everyone for all the great information being shared.

 

Yes, but not much. The O2mv scale is not linear, as seen in the attached graph. The chart gives a range of values showing Lambda, AFR, and O2mv--but not all of these are usable. I've heard 450 should be the minimum (14.68) and 780 the max (14.43). My stock '07 CLB table shows 500-600 in the cruise range, which is between 14.6 and 14.7. I'm not sure why you can't set O2mv higher, but it may be because of a lack of accuracy above a certain point. Note that in the graph the line begins to shift radically to the left in about the area we normally think of as the max.

 

We generally set it at 700mv, and 770mv is about as high as we like to see Bias voltage, this is near the limit where the O2 sensors can still accurately control the mixture. Above 800mv and the system does not know the difference between 14:1 and 12:1 AFR as you are outside of the working range of the sensors.