PDA

View Full Version : QUICK!!! Tried Auto VE tuning and now I have a problem



12sec.5.3
November 27th, 2009, 09:40 AM
Done everything step by step as the tutorial's instructions say and after updating the calibration differences from alternate to primary tune my VE table is completely blank. No numbers or anything just white cells. Cranked it up and it will not stay running bc it is so lean. Sounds like a top fuel car though... hehee. Please help. Only thing I could think of that was wrong was something when building and applying the filter bc the tutorial did not give a thorough explanation on it.

GAMEOVER
November 27th, 2009, 09:45 AM
Post up your tune file...

mr.prick
November 27th, 2009, 09:47 AM
You copy primary VE to the back up VE.
If you can, upgrade the OS to something w/o a back up VE table.

12sec.5.3
November 27th, 2009, 10:10 AM
I might have done something wrong so I redone it. My VE table looks to be wayyy off with crazy high spikes in it so take a look.

12sec.5.3
November 27th, 2009, 10:16 AM
Also, After I load my new tune do I replug my maf? I tried and it still doesn't want to run. Maybe the maf has to be calibrated now too?

mr.prick
November 27th, 2009, 10:44 AM
Dude that VE table is fktup. :eek:

12sec.5.3
November 27th, 2009, 11:03 AM
lol. yes i know. If i send you my log could you help figure this out?

mr.prick
November 27th, 2009, 11:19 AM
There is something wrong with the data that was applied to the VE table
or/and the way it was applied.
Post the log that resulted in the tune posted above and
what data and how it was applied.
FYI
you have LTFTs/Closed Loop enabled,
therefore the AutoVE process is moot.

12sec.5.3
November 27th, 2009, 11:30 AM
This is the log

mr.prick
November 27th, 2009, 11:41 AM
Your WBO2 is not configured right, EXT.AD voltage is low.
This is giving you incorrect AFR/BEN data.
Check the fuel settings and voltage output in Logworks.
A free air calibration would be a good idea too just to make sure that is not the cause.

12sec.5.3
November 27th, 2009, 11:45 AM
"Check the fuel settings and voltage output in Logworks"? Not sure wt that is. Sorry I just connected the wb the other day and wasn't exactly sure wt I was doing so it prob isn't right.

mr.prick
November 27th, 2009, 12:09 PM
Innovate Motorsports Support (http://www.innovatemotorsports.com/support.php)
Throw away this log and revert to the last tune that worked for you.
Get the WBO2 configured and start over.

12sec.5.3
November 27th, 2009, 12:13 PM
Which manual do I need to download?

GAMEOVER
November 27th, 2009, 12:16 PM
I think you need to start all over...:)

12sec.5.3
November 27th, 2009, 12:25 PM
Yea I know..I'm sooo lost right now. This is pretty frustrating

mr.prick
November 27th, 2009, 12:47 PM
Which manual do I need to download?

LOL
which WBO2 do you have?
The log showed the LM-1 so I assumed that is what you are using.

12sec.5.3
November 27th, 2009, 01:00 PM
Nope. I'm using an AEM but there's no PID for it

mr.prick
November 27th, 2009, 02:06 PM
There's not?
calc_pids(AEM).txt (http://forum.efilive.com/attachment.php?attachmentid=5805&d=1259554875)

12sec.5.3
November 28th, 2009, 09:42 AM
It's not in my list of pids to select from.

12sec.5.3
November 28th, 2009, 09:54 AM
Can you send me a link to help me set this up step by step? Thanks for all your help so far! I'll get it sooner or later...ha

mr.prick
November 28th, 2009, 10:09 AM
Which AEM do you have?
Installation Instructions 30-4100.pdf (http://www.aempower.com/images/products/Installation%20Instructions%2030-4100.pdf)
The dual unit has a funky non-linear output.
Installation Instructions 30-2300 Dual Channel & 30-2301.pdf (http://www.aempower.com/images/products/Installation%20Instructions%20UEGO%20Controller.pd f)
The calc_pids.txt above should work for both models.

12sec.5.3
November 28th, 2009, 10:40 AM
I have the 30-4100. Tried using the sticky that Blacky has posted in the general scanning section but it isn't working.

joecar
November 28th, 2009, 12:01 PM
I have the 30-4100. Tried using the sticky that Blacky has posted in the general scanning section but it isn't working.What specifically isn't working...? Post some screenshots.

Do you have FlashScan V1 or V2...?

If you have V2 then use the AEM's serial output.

If you have V2 then make sure you're reading the correct AFR from your AEM 30-4100... enabled closed loop and check that the AEM reports stoichiometric AFR (same value as B3601).

How is your AEM wired up...?

Post your calc_pids.txt file.

Then make sure that you follow the AutoVE tutorial step by step... print it out and use a red sharpie to mark each step as you do it.

12sec.5.3
November 28th, 2009, 12:13 PM
I have flashscan v1. I have the white wire(0-5v output) connected to AD1(all the way to the right looking into the 3 pin plug with flashscan facing upwards)

12sec.5.3
November 29th, 2009, 05:57 AM
I got it now. Sorry guys, I guess I was going a little too much by the book and copied that calc_pid.txt to V7 not thinking I have the V7.5.
So now I have 3 new pids (Wide Band AFR 1 - AEM1), (Wide Band BEN 1 - AEM1), and (Wide Band BEN 2 - AEM2). What is BEN2 for?

mr.prick
November 29th, 2009, 06:24 AM
It is for a second sensor.
I edited the calc_pids.txt that I posted originally to show the AEM part numbers.

12sec.5.3
November 29th, 2009, 07:11 AM
Went for a test drive and done some logging but something is still wrong. After applying my info from my map to my VE it looks horrible. Something is still def wrong! Look.

mr.prick
November 29th, 2009, 09:28 AM
It looks like you are using the wrong AEM PIDs.
The Analog Output Voltage Mode needs to be P0 or P1
Page 9 of the manual (30-4100)

These settings (P1 and P0) implement a linear calibration with the most useful voltage range possible (0-5V).
The formula is based on the Calibration table of available outputs
minimum 0.00V = 10.0AFR
maximum 4.25V = 18.5AFR
(10-18.5)= 8.5
8.5/4.25= 2
(V*2)+10=AFR

12sec.5.3
November 29th, 2009, 04:39 PM
So just make sure the guage is on P0 or P1 and it should work?

mr.prick
November 29th, 2009, 05:27 PM
Set the gauge to P0 or P1 and use this.
calc_pids(AEM).txt (http://forum.efilive.com/attachment.php?attachmentid=5805&d=1259554875)

I had to fix it.
The model numbers are included in the PIDs so it's easier to select the right ones. :doh2:
The ones you want are
Wideband AFR AEM 30-4100 {CALC.AFR_AEM}
Base Efficiency Numerator - AEM 30-4100 {CALC.BEN_AEM}

12sec.5.3
November 30th, 2009, 03:01 PM
Think we got it. Doesn't this look a lil better?

12sec.5.3
November 30th, 2009, 03:09 PM
Question: Why does my torque converter lock up as soon as possible driving in SD but takes it's good ole time whenever i'm not?

mr.prick
November 30th, 2009, 03:20 PM
The BEN PID is messed up.
Are you using the PIDs in post #30?

The voltage is still low, unless AFR is actually that rich.
Is possible the gauge is set to position 3 instead of 0?
The picture in the manual shows the diagonally across from each other.
P3 shows stoich @ about 0.24V
You are using the white wire to Flashscan, right?

12sec.5.3
November 30th, 2009, 03:26 PM
Yes white wire to flashscan. I didnt check the position but it's supposed to come set at P0-P1 as default. I've been using it for about 2-3 years now and has always been pretty accurate. It is running pretty rich, wb shows 10.X-11.X the whole drive even at WOT. Should I still check it?

mr.prick
November 30th, 2009, 03:47 PM
Have you made any changes that would make AFR so rich?
The tutorial says to add 15% to the VE table,
something most people should not do IMO.

You can enable CL to see if fuel trims bring AFR down.

12sec.5.3
November 30th, 2009, 03:50 PM
Yes I did add 15%. Should I plug MAF back in or keep using SD tune and just enable CL?

mr.prick
November 30th, 2009, 03:59 PM
I would put the VE table back to where it was before the 15%,
see what that gives you.

12sec.5.3
November 30th, 2009, 04:52 PM
What would be the difference if i'd repeat the process with the newly configured VE table or go back and take away the 15% from my original? It should eventually plane out the same. Based on my original tune it seems like it's on the right track.

mr.prick
November 30th, 2009, 05:06 PM
Was AFR rich before you added the 15%?

12sec.5.3
November 30th, 2009, 05:47 PM
No it was a bit lean during normal acceleration and lean for a split second when I'd hit 100%TPS. Sometimes it would kinda backfire but under the hood and not very loud, just a lil choke, if hit it real quick. WOT was close but fluctuated quite a bit. Also in my PE table i was commanding a whole point richer than I was actually seeing on the wb.

12sec.5.3
November 30th, 2009, 05:54 PM
I noticed a LOT more throttle response in SD so hopefully it'll stay that way or I may have to start running in SD all the time. Ha

joecar
December 1st, 2009, 05:47 AM
:cheers:

Post some new logs.

12sec.5.3
December 1st, 2009, 06:01 AM
I guess I can load the new VE in and make another log still in SD?

joecar
December 1st, 2009, 06:07 AM
Yes, stay in SD for a while longer, capture more logs.

12sec.5.3
December 1st, 2009, 06:12 AM
So after I do a couple more logs and get my VE dialed in I suppose I paste that VE table to my original tune but what about PE? Where do I start to get it dialed in? Correct me if I'm wrong but since the VE will be pretty close to exact I can command the AFR I'm looking for in the PE table and should see that on my wb.... right?

joecar
December 1st, 2009, 07:56 AM
Once you get your VE table "corrected", then the measured AFR will equal the commanded AFR...

i.e. what ever PE B3618 is commanded (when PE is enabled) is what will be measured by the wideband.

For normally aspirated, try commanding AFR 12.6... then fine tune it for best ET and TS at the drag strip.

The commanded AFR will be the richest of all the active tables... B3605 (always active) or B3618 (when PE enables) or the protection tables (when protection kicks in).

12sec.5.3
December 1st, 2009, 09:20 AM
More logs:
I took the first log, loaded it up into my SD tune and went make another log. I built the second log on top of the first and after smoothing things out a bit put that VE table into my original tune file and loaded it up. It feels great right now. I haven't went to WOT yet but the throttle response is much better. I couldnt monitor any of the low rpm/map cells bc it would not idle. Not sure if thats a big deal or not but it idles great so far and I'll just have to keep driving to find new flaws to work on.

mr.prick
December 1st, 2009, 09:59 AM
It looks like the problem was indeed a high VE.

12sec.5.3
December 1st, 2009, 10:28 AM
Can't do anything in this rain but I'm on the right track now. I wish I would have tuned my VE table a long time ago! It's like a whole different truck now. Street manners and throttle response are 100% better! Can't do any WOT tuning for the PE table but I'll get to it when the rain quits.
Thank You VERY much mr.prick and joecar!!! You guys really know your shit.