pcmhacking.net

Def should not have changes of 30%, have you ever ran a standard VE table with VE learn off and logged the BLMs??

I noticed in the cal you had the MAP radius at the maximum of 4.3kPa, reduce that back to the default 2kPa and see if that helps.

its most likely the vr tune so many tables work together its not funny .ive run vr tunes on vn and vp before and they are way out hence why i use vn and vp tunes on vn and vp takes to long to make a vr tune suit vn

So may answers so quick, excellent service.

Have a question, where is "ve max value parameter" for ve learn, my xdf does not have one.

Delcowizzid, cal was based on vn values of my original factory cal which is why I find the dramatic changes so odd.

VL400, have not changed the "MAP radius at the maximum of 4.3kPa" (this is the value commented in the xdf), but will change it. Also have ran my vn cal in non ve learn in the past & don't remember getting wild blm values but will run a trial next to see what happens.

A quick question regarding idle vacuum, what is a good value for engine with 100,000km & no accessory loads ie a/c, p/s. Also value for over-run on steepist down hill would be appreciated. Trying to fine tune DFCO, have found it difficult to get map values <30kPa for down hill.

The current V104 has max and min VE for learn. The earlier versions only had min.

Thought someone might say that. Still using an earlier version believing that the basics were the same as later public releases & been too lazy to reburn VNRAM. Were there any defects with ve learn in early versions that might explain my problems.

thats the beauty of 1.02 > starting at 1.02, you can upgrade the code base via the flashtool without nvram removal you really should upgrade too, theres lots of bugfixes soem of which may fix your problems.

you should see idle vacuum of about 30-40kpa .... changing idle spark up or down can change this aswell

dfco will probably only see 20kpa if you bring the revs up high enough, ie. downshifting

Will move to latest version, did not appreciate that I would be able to flash the new code.

Regarding idle vacuum, I am running a fair bit of advance as this is supposed to help to give economical stable idle with changing load, ie a/c & p/s. Might be why my idle map values are are 30/40ish. Can get DFCO to work on big dowm hills but hard to get map below 30 at any other time & hence DFCO locked out. Making DFCO map trigger value >30kPa seems a little extreme.

Just so I do it correct, I burn v104 into the NVRAM & then I can use flashtool v18 to write my bin to the NVRAM & any future base code changes can also be flashed to the NVRAM thus eliminating burner writes.

Typo included in last post, ment to say load my cal, not bin.