I was messing around and it seems to me that you can use a diacom file in VE master and it will still work. It does change parameters in the specified .bin file. Anyone have experience with that? I was also wondering what kind of driving should be on the logged file that VEMaster looks at to change the .bin file? Idleing, cruise, what happens if you hit PE? How high of rpm should you have VEMaster tune for? Any help or experiences would be helpful.

 

VE Master is used to tune from idle to no more than 3500 RPM. The intent is that when a cam is change of course the VE characturistics of the engine is change considerably. A larger cam will reduce VE in the lower idle and cruise RPM while at higher RPMs the cam will increase VE. There is no sense in trying to use VE Master to tune WOT or PE mode, as it looks at the constantly changing trims to do its work. So during datalogging sessions just run the car in the desired RPM ranges that you want VE Master to iterate changes to.

I usually datalog for 10 minutes at 2000 RPM then 10 minutes at 2500 RPM and 5 minutes at 3000 RPM. Then let VE Master do a iteration on the BIN, then test drive and datalog again to see where the fuel trims come in. Then repeat the process as again if necessary. It isn't necessary to get the trims right on at 128 because for one thing you probably never will. It won't even be perfect on a stock engine with a stock calibration. The whole idea is to get as close as you can. I usually try to have the trims around 125-126 that way its a tad on the rich side which is better than a tad on the lean side.

If necessary, once you get the cruise iterations done, datalog a idle session for about 10 minutes then let VE Master iterate a change for the idle RPM range to get the idle fuel trims closer.

VE Master does work from data recordings with Diacom as well as DataMaster.

 

Thats exaclty what I needed Tom, thanx. I have been waiting to buy a datamaster cable to make logs, but hadn't gotten around to it. Now that I know that I can use Diacom, I will do it as soon as the weather clears. This weather isn't very good for road tuning.

Remember I told you that my throttle wasn't opening 100%, the ASR is the culprit. The spring in there doesn't hold all the "cams" tight enough. It is like it is limiting the throttle whenever I give it 100% throttle, except the motor driven gear isn't even moving. I'm testing when the engine isn't running. I haven't fixed it yet, but I may need you to help me with some parts. Talk at ya later.

 

Sounds good let me know if I can help you get parts. Enjoying the snowy weather we are having? Skiing has been superb on Mt Hood :)

 

Tom - VEmaster dosent seem to do anything below 1200rpm for me... is it supposed to? I ended up adjusting those VE tables myself using export to excel function in datamaster, the avg. function in excel and some mathmatics.. it ended up working great.. Also, what do you recommend for tuning WOT... Lastly when at WOT I;ve heard conflicting reports about what fuel table the computer uses.. does it use the VE vs. MAP vs. RPM or does it use the PE table.. which I think is like RPM vs. TPS vs. MAP

 

For tuning WOT there are two tables within TC. They are:

"% Change to AFR vs coolant temperature at WOT"

"% Change to AFR vs RPM at WOT"

Of the two I work with the change vs RPM table first. If I need more fuel then I play with the change vs coolant temp table. Normally I only change a couple entries there where the engine would most likely be temperature wise.

When tuning your WOT tables it is best to get a wide band system connected to the engine to datalog the event. That way you can see where your AFR is across the RPM range so that you can see exactly where you are rich or lean. Some people and even a lot of pro tuners still use datalogged O2 sensor voltage to tune with. While it does work it is a little risky. Using the stock sensors and if you do I tune so that the O2 voltage is at the 850 to 900 mV range. At that voltage level I feel pretty safe that I have enough fuel in the engine. It will be on the rich side but I don't know by how much, that is why I recommend a wide band system.

VE master should work at the RPM of which you tell it to iterate a change. Doing it with Excel is another way to do it as well. Either way is effective another, is the use of Craig Moates VE Phd program which is Excel based. It is a little more work but very effective as well.

 

Tom.. my Def file ECM_DA2 doesnt have those tables... I do have:

"PE % change to F/A ratio vs. coolant temp"
and
"PE % change to F/A ratio vs. RPM"

that must be the one right? Then this table tells it at what TPS postion at what RPM to go use those tables over the base fuel map
"TPS threshold vs. RPM for power enrichment"


do I have that right?

*edit*

BTW: I'm at about 925 02 mV at WOT


[Modified by BluByU, 6:36 AM 1/8/2004]

 

Those are the tables! You can also change when the ecm goes into PE. I don't understand wich table it uses when in PE. Does it use both? Are the percentages added together?

I noticed that using VEMaster changes my VE trim all the way down to 400 rpm.

 

Tjwong .. the numbers in those two tables you mentioned are just percentages. Do I correctly assume that you simply lower the percentage to lean it out and increase to richen it? Or is that going to do the opposite and increasing the percent will raise the ratio of fuel to air.. in effect leaning it, and lowering will richen it?

Thanks! :cheers:

 

In the forementioned tables you can either richen or lean out the WOT fuel by making the number smaller or bigger. You can even put in negative numbers. Most people just play with the RPM table, and if more or less fuel is needed then they can adjust the temp table. But note in the temp table you would only be adjusting in the normal operating temperature regions. Most people of sounds mind won't be attempting WOT runs with a cold engine. :)

 

I created a program for use with Ease that does something similar to VEMaster but I have used it for all RPMs (Non-WOT, NON-PE)

I was able to get my fuel very close within 4 burns. Having something to do all the calculating for you is great.

The program I made does require ou to manually copy the Orignial MAP tables out of and the New tables back into the BIN. But it is easy compare to all the calculating

 

Would you like to share? :D

 

I will once I buld it into an .EXE i will. right now I am still working some of the bugs out and need to add a few more hooks in order to make it less for the user to do.

Right now I have to use Excel to remove all the OPEN loop data then I manually sort it for RPM and kPA.