PDA

View Full Version : AutoVE with the RR



Whippled 496
April 19th, 2008, 12:36 PM
I am confused (Big suprise right?) So here is the deal, I am using the RR and doing the AutoVE. Things seem to be going well, when i notice that the BENs are only getting to about .96 - .97 and stopping. So i decrease the sensitivity (from 1 to 0) and it makes no difference. I manually adjust the VE table and it makes no difference, and I am like WTF? So i go into B3647 and bump my commanded AFR up by .01.....and my actual AFR goes crazy lean...to the tune of like 16.xx. I know i cant use 14.63 as the commanded AFR as it initiates the use of the O2s which is why i had 14.68 as my commanded. So i readjusted the commanded to be 14.73 and started AutoVE again and the numbers started to fall in line better but after spending a few hours AutoVE'ing already i figured i would take a break and try again later.

I noticed my wideband (LC-1) seems to really be jumping around like crazy .70 swings sometimes....this cant be helpfull for trying to AutoVE. I checked the settings and the latency was set at 1/6. The options are 1/12, 1/6, 1/3, and instant. There just seems to be a few things that are screwy here especially the way my AFR went crazy when only adjusting the commanded by +.01. I would have thought that the actual AFR would have stayed the same and only the BENs would have went rich....adjusting the commanded AFR should not have effected the actual AFR should it? I am going to post a copy of my tune again if anyone wants to look at it and see if its a setting I have missed. I am running open loop speed density.

mr.prick
April 19th, 2008, 02:47 PM
in the RTACS tab there are boxes for min/max adjustment.
these values will not be altered by BEN unless you manually
change the numbers in the boxes.(higher/lower)
3084
when you open the tune.exe the numbers in the boxes by default
are the minimum and maximum values in your VE table
and will need to be changed manually before you start or,
you can take a spot in your VE table and edit the value to a low/high
number that you are comfortable with and won`t need to change on th fly.
as you can see in my VE table i set my lowest value in a spot that
is "un-hittable" during scanning and,
my max value is 0.10 higher than my highest hit spot during scanning.
as far as your AFR changing after some adjustments that probably
should not make to much of a difference,
as IAT rises (maybe you idled or re-started after a few minutes)
this can change your BENS/AFR.
high IATs can be a pain when using the stock ECU as it tends
to throw off your logged data, so don`t worry if you are fine for awhile
then after re-starting you see high BENs/AFR,
this is why i got my RR.
and for the swinging AFR get used to it.
it will not ever be a solid value.
set your update frequency a little higher than 1, maybe 3 or 5
in the properties>Roadrunner tab.
are you using the V1 or V2?
the serial to V2 really is way better than the analog input
i don`t know if thats an option for you, but its well worth it.

hquick
April 19th, 2008, 05:24 PM
I think you have V1 right 'Whippled'?
I set my update to 1 and accuracy to 0 (so it continually updates).
I set filters to:
Exclude TPS below 0.5 (so as not to adjust idle or decel)
Exclude TPS varying by greater than 5% (to try and stop changes during transients).
Exclude KPA greater than 105.5% (so...only adjusting for Main VE)
When doing the boost VE table I change the last filter to less than 106%. Idea is to do the 105 column in the Main table and then copy paste it to the boost VE table....otherwise you'll be changing it all the time.

hquick
April 19th, 2008, 05:59 PM
Also...try commanding 14.5 instead of anything else. Anything closer seems to get rounded up or down close enough to stoich and causes the 'semi closed/open lop' condition.

Whippled 496
April 20th, 2008, 01:55 AM
Okay, thanks a bunch fella's. I am going to give it another go if the rain holds off today.

Whippled 496
April 20th, 2008, 02:17 AM
in the RTACS tab there are boxes for min/max adjustment.
these values will not be altered by BEN unless you manually
change the numbers in the boxes.(higher/lower)
3084
when you open the tune.exe the numbers in the boxes by default
are the minimum and maximum values in your VE table
and will need to be changed manually before you start or,
you can take a spot in your VE table and edit the value to a low/high
number that you are comfortable with and won`t need to change on th fly.
as you can see in my VE table i set my lowest value in a spot that
is "un-hittable" during scanning and,
my max value is 0.10 higher than my highest hit spot during scanning.


I re-read this and I am not sure if i understand what your saying 100%. The values in my RTACS tab are the lowest and highest g/cyl (values) in my VE table. I thought that those numbers represented the fact that RTACS would not adjust anything below or above those values. Keep in mind I redline at 4900 with the bigblock which is why the table drops off at 5200. Here is a shot of my VE table...

mr.prick
April 20th, 2008, 11:49 AM
the values in those boxes will not be changed by BEN.
if you are lean/rich in a spot with those same numbers
the RR will not change them.

mr.prick
April 20th, 2008, 11:55 AM
I am confused (Big suprise right?) So here is the deal, I am using the RR and doing the AutoVE. Things seem to be going well, when i notice that the BENs are only getting to about .96 - .97 and stopping. So i decrease the sensitivity (from 1 to 0) and it makes no difference. I manually adjust the VE table and it makes no difference, and I am like WTF? So i go into B3647 and bump my commanded AFR up by .01.....and my actual AFR goes crazy lean...to the tune of like 16.xx. I know i cant use 14.63 as the commanded AFR as it initiates the use of the O2s which is why i had 14.68 as my commanded. So i readjusted the commanded to be 14.73 and started AutoVE again and the numbers started to fall in line better but after spending a few hours AutoVE'ing already i figured i would take a break and try again later.

I noticed my wideband (LC-1) seems to really be jumping around like crazy .70 swings sometimes....this cant be helpfull for trying to AutoVE. I checked the settings and the latency was set at 1/6. The options are 1/12, 1/6, 1/3, and instant. There just seems to be a few things that are screwy here especially the way my AFR went crazy when only adjusting the commanded by +.01. I would have thought that the actual AFR would have stayed the same and only the BENs would have went rich....adjusting the commanded AFR should not have effected the actual AFR should it? I am going to post a copy of my tune again if anyone wants to look at it and see if its a setting I have missed. I am running open loop speed density.

you understand me 100%,
if you need less fuel than the min box you
will need to change the value in the min box,
and the same goes with the max box.
i assumed you were not updating because of this.

Whippled 496
April 20th, 2008, 01:09 PM
you understand me 100%,
if you need less fuel than the min box you
will need to change the value in the min box,
and the same goes with the max box.
i assumed you were not updating because of this.

I think it may be a combo thing going on here. One is i think my wideband is jumping around a little to much to lock in the BEN correctly. The other is i think i need to change my commanded AFR to something like 14.50 +/-. I think i am to close to a stoich number and its causing issues with AUTOVE.