Vortec Calc VET Auto Tune, Final Answer!

[EagleMark]

Ok, I am bound and determined to do this with 98-00 vortec. In other threads guys have said they did it. But I can't figure how. I've put a lot of time into it with failure. Ended up doing it the old way and spreadsheets... Have done it on other engines by working with available tutorials.

With all the excellent help here I'm sure I can come up with a Tutorial. Biggest issue right now with available tutorials is missing PIDS. Have the calc_pids.txt installed from one of the tutorials. I do have a Wide Band but would also like to do one without. So 2 tutorials, actually they could mirro what is there but work for the Vortec.

From another thread.

Not sure how guys earlier in this thread did the Auto VE or VE Calc? Done both of them on other engines, just can't validate the PIDS needed for this 98 Vortec engine? No commanded AFR or EQ Ratio? Could the Scan Tool be missing stuff?

So do I have an issue? Or where to start if these PIDS are not available in the Vortec PCM?

[EagleMark]

Trying to duplicate the Calc VE tutorial or the web version with a twist located here:
http://forum.efilive.com/showthread.php?15236-A-New-Twist-on-CALC-VE-Table-Computing-the-Entire-VE-Table&styleid=6

These are the PIDS reqired in the thread.
14347


These are what I have available showing ones that are not valid.
14346

Couple things are missing and a couple I think can be changed?

1. Retard do to Knock GM.KR to Knock Retard (Vortec) GM.KNKRET_B ? This is a suggested and not required.
2. Mass Air Flow raw Frequency MAFFREG change to Mass Air Flow raw Frequency MAFFREG2 ?
3. Dynamic Air Temp GM.DYNAIRTMP_DMA to Dynamic Air Tempreture Calc.DAT ?
4. Air Flow Grams/Cyl GM.CYLAIR_DMA to Air Mass Per Cylinder CALC.CYLAIR ?

I haven't found anything possibly suitable for:
1. Air Flow Grams/Cyl - Speed Density GM.DYNCYLAIR_DMA
2. Equivalence Ration GM.EQIVRATIO The only possible one that I thought should work does not validate, it is Commanded Equivalency Ratio SAE.LAMBDA Not sure why a SAE does not work?

[joecar]

If you can find alternate working pids then the calc pids for WO2BEN, VET and/or MAFT can be edited to achieve suitable tuning...


MAFFREQ2 can be used in place of MAFFREQ.
DAT can be estimated by using B4901 lookup or some form of IAT/ECT blending.
CYLAIR may or may not be necessary.
Some working commanded fuel pid is required (be it AFR, EQIVRATIO, LAMBDA, other).

If the pids do not validate, they are still ok as long as they log sensible values.

( this is the beauty of the EFILive scantool, it is very easy [for me, at least] to edit the calc pids )

[EagleMark]

I'd really like to tap your expertise for the calc_pids.txt file. I am comfortable with doing that type of code when the time comes. Then I would have to save original if I wanted to work on something else, correct?

But right now I've found the issue that has plagued this from the beginning. Just could not understand why EFI Live can not find a valid PID for Commanded AFR, it's the same issue in my other thread that started with the LC-1 WB.

My scan tool can find AFR, ScanXLPro can find AFR. It is GM.AFR but that does not work in EFI Live, not valid and even if you choose it data is N/A. What's worse is GM.AFR_B for the LS2 does validate and shows good data! So which one is wrong and does GM.AFR_B work correctly in LS2 ?

[joecar]

You have to rename the original file.

Also note that when editing calc_pids.txt you must ensure there are at least two blank lines at the end of file.

I think in your case the correct pid to use is GM.AFR_B, it is intended for the LS2... post some logs of this.

[EagleMark]

You have to rename the original file.That's what I have been doing, I have several now, but in the end only one can be used by the software and it must be calc_pids.txt correct?

Here is one you did AFR Calc viewing in that I added three from the Calc VE Tuning tutorial. See if I got it correct?

[EagleMark]

This started as an attempt to mirror WeathermanShawn's work. RIP! I can't compete and have much more to learn. But if you or others are willing to help, I will continue to make this work. It's just looking harder as I work out details. It may be completly differant.

If there is another route, I'm all ears... in another thread guys said they did this, I assume it was with the 98-00 Vortec as that is what the thread was titled for and section it was in. But the more I dive in the more I wonder how?

[EagleMark]

I think in your case the correct pid to use is GM.AFR_B, it is intended for the LS2... post some logs of this.I disagree, I think theres a glitch? But for now it is the route I'm going to follow because the data is accurate.

I will get some sample specific logs. Since my .tun is set Stoich 14.2 and the data says 14.2, I think a good test would be to set Stoich back to 14.7 and check data.

[slows10]

This started as an attempt to mirror WeathermanShawn's work. RIP! I can't compete and have much more to learn. But if you or others are willing to help, I will continue to make this work. It's just looking harder as I work out details. It may be completly differant.

If there is another route, I'm all ears... in another thread guys said they did this, I assume it was with the 98-00 Vortec as that is what the thread was titled for and section it was in. But the more I dive in the more I wonder how?

Can you post a link to this other thread you are describing?

[EagleMark]

http://forum.efilive.com/showthread.php?17739-AutoVE-on-our-PCMs

[joecar]

That's what I have been doing, I have several now, but in the end only one can be used by the software and it must be calc_pids.txt correct?

Here is one you did AFR Calc viewing in that I added three from the Calc VE Tuning tutorial. See if I got it correct?

Yes, correct, calc_pids.txt.

After *CLC-00-002 there is *CLC-00-00... looks like this be *CLC-00-003.

[joecar]

That's what I have been doing, I have several now, but in the end only one can be used by the software and it must be calc_pids.txt correct?

Here is one you did AFR Calc viewing in that I added three from the Calc VE Tuning tutorial. See if I got it correct?


Yes, correct, calc_pids.txt.

After *CLC-00-002 there is *CLC-00-00... looks like this be *CLC-00-003.How about this, I simplified by re-using the newer VE calculation (CLC-00-003 becomes CLC-303):

[EagleMark]

Actually it was a total mess, I was on my tuning laptop using Notepad. Never have 2 or more instances open in Notepad! I blew it. That file was all messed up as you noticed. It's still missing CLC-00-003... and look in *PRN - Parameter Reference Numbers at number 3? It's 303, shouldn't that be down lower in order?...

I use EditPad on my shop laptop. What do you use or recommend?

[ScarabEpic22]

Notepad++ is my go-to free editor for basic things like this and minor programming. Might do what you want plus has a tabbed interface. :)

[EagleMark]

Notepad++ is my go-to free editor for basic things like this and minor programming. Might do what you want plus has a tabbed interface. :)That works for free as well as my 2005 paid for version of EditPad which needed a paid for update! :thumb_yello:


How about this, I simplified by re-using the newer VE calculation (CLC-00-003 becomes CLC-303):Since *CLC-00-003 was missing in that, you replaced it with *CLC-00-303 which is what I need here I just moved it.

Is it acceptable to Comment out a entry? Look at:
*CLC-00-273
# *CLC-00-273

14356

[joecar]

Yes you can comment out like that;

it is not complete tho, you will have to provide CLC and PRN entries for CALC.B4901.

[EagleMark]

Think I got procedure right. Not sure I have all correct changes done, going to test.

Understand that I have experiance with sytax from HTML. CGI etc... and learning how/what/why these entries work.

[EagleMark]

That calc_pids file may look good but it does not work, one entry twice. Going back to start again.

[EagleMark]

You have to rename the original file.

Also note that when editing calc_pids.txt you must ensure there are at least two blank lines at the end of file.

I think in your case the correct pid to use is GM.AFR_B, it is intended for the LS2... post some logs of this.Here's a log and pid list with GM.AFR and GM.AFR_B. NOTE: While in vehicle data shows as N/A for GM.AFR. In log it shows as 0.00. GM.AFR_B works in vehicle and log.

[EagleMark]

Guess what happens if you get all the right PIDS and calc_pid file correct?



It works!

At this point I'm not sure which tutorial I followed, but the corrections for fuel and MAF are being done Closed Loop with MAF sensor hooked up in one log!


:jump:

[tokymon]

so can you post the correct calc_pid file ? i use this for ls all the time

[joecar]

Think I got procedure right. Not sure I have all correct changes done, going to test.

Understand that I have experiance with sytax from HTML. CGI etc... and learning how/what/why these entries work.Looks ok...

do you realize that CALC.LTFTBEN is defined twice...? Delete CLC-00-002 and the PRN that uses it (see attached).

[EagleMark]

I will if you want to play and help, but this is strictly beta, I have no idea if anything is accurate. Right now I have data spitting out the MAPs several ways, even WB.

Biggest issue the entire time was no Commanded AFR. Right now I'm using a PID named LS2 (read earlier posts), so we need to make sure it is accurate as well.

Have to use Commanded Air Fuel Ratio B LS-2 GM.AFR_B

[EagleMark]

Looks ok...

do you realize that CALC.LTFTBEN is defined twice...? Delete CLC-00-002 and the PRN that uses it (see attached).Yup, Thanks Joe, I caught that as soon as I connected to the truck.

Look up one post and see if that calc_pid-Vortec-Bets has all it needs for other WB stuff for me please?

[ScarabEpic22]

Good to know, I wonder if the P10 uses GM.AFR_B as its commanded AFR PID instead of GM.AFR...hmmm. But it has a problem that the VE tables are Load % vs RPM (hybrid SD/alpha-n fueling) and the Load PID doesnt work.

[joecar]

Yup, Thanks Joe, I caught that as soon as I connected to the truck.

Look up one post and see if that calc_pid-Vortec-Bets has all it needs for other WB stuff for me please?calc_pids-Vortec-Beta.txt looks good and clean... I tried it out and all the calc pids it defines select ok.

[joecar]

Good to know, I wonder if the P10 uses GM.AFR_B as its commanded AFR PID instead of GM.AFR...hmmm. But it has a problem that the VE tables are Load % vs RPM (hybrid SD/alpha-n fueling) and the Load PID doesnt work.It might use GM.AFR_B... or it might use SAE.LAMBDA.

Too bad about the load pid... can SAE.MAP be used as load...?

[EagleMark]

VERIFIED: GM.AFR_B does change commanded AFR when stoichiometric is changed, checked at 14.7 and 14.2, verified both of them through serial WB.

[ScarabEpic22]

It might use GM.AFR_B... or it might use SAE.LAMBDA.

Too bad about the load pid... can SAE.MAP be used as load...?

SAE.LAMBDA reports invalid data last I checked on the P10.

If I knew how to use SAE.MAP and make a load PID out of that, would make my life easier.


OK, sorry for the thread hijack EagleMark.

[EagleMark]

OK, sorry for the thread hijack EagleMark.It's OK, I owe you one! :anitoof:

Had some time to work on this again, got data but some or all not correct at this point. Some things are still missing or done in VE% and for this PCM VE is in g*K/kPa.

One of the hurdles was already done in another thread by joecar.

*CLC-00-273
C 0.0 100.0 .1 "{GM.DYNAIRTMP_DMA.C}"
F 40.0 220.0 .1 "{GM.DYNAIRTMP_DMA.F}"
K 280.0 380.0 .1 "{GM.DYNAIRTMP_DMA.C}+273.15"
R 500.0 680.0 .1 "{GM.DYNAIRTMP_DMA.F}+459.67"

Changed to:

*CLC-00-273
C 0.0 100.0 .1 "{SAE.IAT.C}+({SAE.ECT.C}-{SAE.IAT.C})*{CALC.B4901}"
F 40.0 220.0 .1 "{SAE.IAT.F}+({SAE.ECT.F}-{SAE.IAT.F})*{CALC.B4901}"
K 280.0 380.0 .1 "{CALC.DAT.C}+273.15"
R 500.0 680.0 .1 "{CALC.DAT.F}+459.67"

With that do the degrees F and C need to be defined in calc_pids file?

*UNITS

#Code System Abbr Description
#-------- ---------- -------- -------------------------------------------------------------
None None "" "No units"
K Metric K "Degrees Kelvin"
R Imperial R "Degrees Rankine"

Some of the Calcs are in VE%? I need VE is in g*K/kPa. So does this need other PIDS or can it be converted?

CALC.VEN F300 CLC-00-300 "%,VE" Tuning "Calculated VE, not corrected"
CALC.VET F305 CLC-00-305 "%,VE" Tuning "Calculated VE, BEN corrected"

Then there is this issue? This PCM does not have GM.EQIVRATIO, is there another way like the Dynamic air to blend of IAT and ECT with lookup?

*CLC-00-032
factor 0 4 .0 "{GM.EQIVRATIO}=1"

*CLC-00-110
factor 0.5 1.5 .4 "{GM.EQIVRATIO}*{EXT.WO2LAM1}"

I loaded a butt load of possible PIDs to validate and checked for data on ones that did not validate, here's an idea of what I have to work with. SOme show as valid but still do not put out proper data because of conversions or lack of other PIDs needed. Tried catching up and educating myslf on this but right now I have a headache and going blind looking, need a reality check!

[joecar]

My comments in red ink:




With that do the degrees F and C need to be defined in calc_pids file?

*UNITS

#Code System Abbr Description
#-------- ---------- -------- -------------------------------------------------------------
None None "" "No units"
K Metric K "Degrees Kelvin"
R Imperial R "Degrees Rankine"
No, F and C are already predefined.

Some of the Calcs are in VE%? I need VE is in g*K/kPa. So does this need other PIDS or can it be converted?

CALC.VEN F300 CLC-00-300 "%,VE" Tuning "Calculated VE, not corrected"
CALC.VET F305 CLC-00-305 "%,VE" Tuning "Calculated VE, BEN corrected"
"%,VE" indicates it has two units, % and VE, where VE is predefined as g* K/kPa.


Then there is this issue? This PCM does not have GM.EQIVRATIO, is there another way like the Dynamic air to blend of IAT and ECT with lookup?

*CLC-00-032
factor 0 4 .0 "{GM.EQIVRATIO}=1"

*CLC-00-110
factor 0.5 1.5 .4 "{GM.EQIVRATIO}*{EXT.WO2LAM1}"
Change the quoted part to read like this "{EXT.WO2AFR1}/{GM.AFR_B}"

Hmmm... a lookup would work for OL if it considers any/all tables which could be active (PE, OLFA, COTP, PPM, EPM) including any modifier tables... that might be beyond the ability of lookup; I'm not sure how it would work for CL.

I loaded a butt load of possible PIDs to validate and checked for data on ones that did not validate, here's an idea of what I have to work with. SOme show as valid but still do not put out proper data because of conversions or lack of other PIDs needed.

On any calc pid that has a red X, do rightclick->More Info to see what other pid is blocking it.

Any non-calc pids that have a red X are not valid for this PCM/OS or have not been validated (Info->Validate Pids).
. . .

[EagleMark]

Woo Hoo! Couple down..

That picture is validated.

Just checked again by right click then More Info and all of the non validated PIDS, all GM.xxx don't work for More info.

I have been doing this procedure and finding what is missing, but without More Info, don't know what to look for on what's left. None are for this PCM, but were included in tutorials so I chose them as reference.

[EagleMark]

Now with this change should *CLC-00-032 {GM.EQIVRATIO} also be changed to {EXT.WO2AFR1} ?



*CLC-00-032
factor 0 4 .0 "{GM.EQIVRATIO}=1"

*CLC-00-110
factor 0.5 1.5 .4 "{EXT.WO2AFR1}/{GM.AFR_B}"

[joecar]

Now with this change should *CLC-00-032 {GM.EQIVRATIO} also be changed to {EXT.WO2AFR1} ?



*CLC-00-032
factor 0 4 .0 "{GM.EQIVRATIO}=1"

*CLC-00-110
factor 0.5 1.5 .4 "{EXT.WO2AFR1}/{GM.AFR_B}" Ah, yes, of course...

CLC-00-032 will have to read like "{GM.AFR_B}=14.63" or whatever value B3601 is set to.

[EagleMark]

OK, so I am catching on, well close?

All the reading I have done it says do this, here's the calc_pids ... I've never seen the flow of how each PID works with another...

Is there any coralation between the *CLC number and PID it's attached to? I'm wonering if I should have new *CLC numbers that are unique?

[joecar]

OK, so I am catching on, well close?

All the reading I have done it says do this, here's the calc_pids ... I've never seen the flow of how each PID works with another...

Is there any coralation between the *CLC number and PID it's attached to? I'm wonering if I should have new *CLC numbers that are unique?
Each pid defined in the PRN section links the pid name (e.g. CALC.CL) to the CLC, for example:

CALC.CL F032 CLC-00-032 factor Tuning "Closed Loop (based on EQIVRATIO)"

And I'm told that the pids are evaluated in PRN numerical order (e.g. F032) or in CLC numerical order... (I don't remember which of the two).

So if a calc pid references other calc pids, those other calc pids must be fully defined at lower PRN/CLC numbers...

the easiest way to manage this is to order the PRN/CLC numerical order and the pid order from top to bottom.

[EagleMark]

Coming together Joe, I'm starting to understand how the calc_pid file works! :thankyou2:

Looks like VE fuel is done.

Now on MAF, I don't have available GM.VETABLE_DMA or GM.DYNCYLAIR_DMA nor do I understand what the value is? I do have an Air Flow Mass, Map of course and lots of other options in earlier photo. How can they be used to take place of GM.VETABLE_DMA or GM.DYNCYLAIR_DMA ?

*CLC-00-310
gps 0.0 400.0 .1 "{GM.VETABLE_DMA.VE}/{CALC.DAT.K}*{SAE.MAP.kPa}*{SAE.RPM}/15"

*CLC-00-315
gps 0.0 400.0 .1 "{CALC.SELBEN}*{CALC.MAFN.gps}"

*CLC-00-430
VE 0.0 4.0 .4 "{GM.DYNCYLAIR_DMA}*{CALC.DAT.K}/{SAE.MAP.kPa}"

*CLC-00-435
gcyl 0.0 1.0 .4 "{GM.VETABLE_DMA.VE}/{CALC.DAT.K}*{SAE.MAP.kPa}"

[joecar]

Coming together Joe, I'm starting to understand how the calc_pid file works! :thankyou2:

Looks like VE fuel is done.

Now on MAF, I don't have available GM.VETABLE_DMA or GM.DYNCYLAIR_DMA nor do I understand what the value is? I do have an Air Flow Mass, Map of course and lots of other options in earlier photo. How can they be used to take place of GM.VETABLE_DMA or GM.DYNCYLAIR_DMA ?

*CLC-00-310
gps 0.0 400.0 .1 "{GM.VETABLE_DMA.VE}/{CALC.DAT.K}*{SAE.MAP.kPa}*{SAE.RPM}/15"

*CLC-00-315
gps 0.0 400.0 .1 "{CALC.SELBEN}*{CALC.MAFN.gps}"

*CLC-00-430
VE 0.0 4.0 .4 "{GM.DYNCYLAIR_DMA}*{CALC.DAT.K}/{SAE.MAP.kPa}"

*CLC-00-435
gcyl 0.0 1.0 .4 "{GM.VETABLE_DMA.VE}/{CALC.DAT.K}*{SAE.MAP.kPa}" Only a few PCM/OS have the GM.VETABLE_DMA pid defined...

for the others, it would take a 2-dimensional lookup... I've never done this, but it involves N+1 lookups.

[joecar]

So far you did Calc.VET (which BEN-corrects MAF and calculates VE from it), is this so...?

You could now BEN correct the VE (same as AutoVE).

[EagleMark]

I think that is where this thread was going?
http://forum.efilive.com/showthread.php?20168-1998-and-calv-vet

But that is actually a dead end as well, there is no B4901 table in the 98-00 Vortec. I don't know if it is there or just not added by EFI Live.

There are other things missing as well that I know are there like
CL enable Temp
O2 Switch Points actually there is not even an O2 folder.

Commanded AFR (proper)
Transmission diagnostics folder, to disable full pressure without MAF
several more...

Hoping EFI Live could step up if I got this done!

I do have "BEN from Serial WB" "BEN from LTFT" "BEN selected from WB or LTFT" all working!

Any other direction for MAF?

[joecar]

For CALC.DAT you could use IAT or some blend of IAt and ECT (with IAT being dominant).

I don't think EFILive have the time to revisit the Vortec (what you see is all they found back when)... do you want me to ask...?

( hmmm, this means it becomes difficult to do AutoVE )


How does vehicle run with the Calc.VET corrected MAF and calculated VE...?

( notice I use the words "corrected" and "calculated" with specific semantics )

[EagleMark]

For CALC.DAT you could use IAT or some blend of IAt and ECT (with IAT being dominant).

How does vehicle run with the Calc.VET corrected MAF and calculated VE...?

( notice I use the words "corrected" and "calculated" with specific semantics )I'm catching up to your specific! :anitoof:

For now laymans terms.

My tune was close, done the old fashion way with WB, math and smoothing, not a lot of Mods, just a sweet clean shop truck I bouhgt. I then applied this tutorial stuff, calculated data OL and with WB made corrections to VE, checked data and was good. Then went CL and did the same and there was not much even worth changing. This was for VE.

Was working on MAF after that last post. Same thing, OL then CL, works well. MAF Freq was untouched before data today. After data it was spot on to 7000hz, from there to 9000hz needed correction. After correction data was spot on. I have not done anything SD/MAF disconnected.

Without the B4901 table being there to confirm it's just a guess... but it is working as is, just as it should so I'm guessing the table is there and accurate.

So AutoVE may be out for now, this PCM does have a back up VE table but it is half size of main VE. Not sure any more calc-pid work is needed for the GM.DYNxxx air stuff, we have a plan! I sure learned a lot about calc-pids! Reading the tutorials it tells you exactly what to do and in the end it works, but you never get an understanding of how and why! Man I am now trying to apply it to something else... still working on full understanding.

Truck runs awesome! :thankyou2:

[EagleMark]

I don't think EFILive have the time to revisit the Vortec (what you see is all they found back when)... do you want me to ask...?
Heck yeah! Besides what I noted there are a few other things, I'll beta test.

If I can find them I'm sure the pros could do better. Make this 98-00 vortec worthy of the EFI Live name! Want to really turn some heads? Lean Cruise!

Look at all the dead ends in this forum? Look all over the net and it's the same answer, swap to 0411! Why? I just found all the issues and answers! Most Vortec builds are done well within the means of this PCM and the limits of the intake, it's a truck after all, not a race car!

[ScarabEpic22]

Id love to see a little more Vortec support, but I doubt EFILive will invest the dev time. Jesse at Wait4Me might be persuaded to look for more tables depending on what exactly we need.

But Ross and Jesse know if they open this can o worms that Ill start bugging them for another P10 update...lol. I dont want to get banned from here!:unsure:

[EagleMark]

calc_pid low and high?

Since we changed this it does not look right for low and high?


#Units Low High Fmt Expression
#------------ ------------- ------------- ---- --------------------------------------------------------------

*CLC-00-032
factor 0 4 .0 "{GM.AFR_B}=14.20"

*CLC-00-110
factor 0.5 1.5 .4 "{EXT.WO2AFR1}/{GM.AFR_B}"

[joecar]

The low and high are the chart/gauge min/max tick marks.

[EagleMark]

calc_pid file is cool!

Is there a known list of *CLC-xx-xxx numbers? I'd like to re-number these as specific to what's needed here.

[EagleMark]

Nevermind, I see CLC in sae-genaric start at *CLC-00-900 so any below 900 would be OK...

[EagleMark]

OK looking for some testers!

Here's a calc-pid.txt file needed and a picture of PID selection. The calc_pid list has a few more then needed and so does PID selection, I'm still working on MAdisconnecteded because those PIDS do not exist on the Votec.

Some of the calc PIDS are same as others, the ones that have been modified for the Vortec version have been given new *CLC numbers.

All directions for all tutorials apply for what ever data your trying to get, read them and create your MAPS.

[joecar]

Looks good.

For CLC-00-033 (CALC.CL) I would make the low/high values something like 0/1 (full scale is whole chart) or 0/4 (full scale is lower 1/4 chart), -3/1 (full scale is upper 1/4 chart); and you can set the precision for this to .0 since you don't need decimal fraction digits (it's a true(1)/false(0) value).

[joecar]

I tried it and I was able to select all the calc pids ok (no red X thru any of them).

[EagleMark]

Done and uploaded new calc-pid text file.

[EagleMark]

I tried it and I was able to select all the calc pids ok (no red X thru any of them).Me too! And got correct looking data in MAPS... Gone a little blind here with the issues and learning so I'm hoping somone can give it a shot with fresh eyes on a rig.

If you have any luck with some new paremeters I think I found some:
Commanded AFR x 2560
Dynamic cylinder airmass
Dynamic airflow, val = g/sec x 81.92
SD grams/cyl airmass x 8192
MAF derived cylinder airmass x 8192
Mass airflow rate, g/sec = val/81.92
#1, P0101: MAF sensor
#2, P0102: MAF sensor
O2 Switch Point
Rear O2 sensor mv limits, to stop feedback

Closed Loop Enable temp
or
Min/Max INT and BLM either way WB tuning would work without disconnecting O2 sensors.

So the good stuff is there!

[EagleMark]

I don't think EFILive have the time to revisit the Vortec (what you see is all they found back when)... do you want me to ask...?

( hmmm, this means it becomes difficult to do AutoVE )

Any word back on adding whats needed? Or fixing SAE.AFR? Just seems wrong to use one marked SAE.AFR_B LS2...

Missing and can't find :B0120: Change RPM Threshold for Airflow Calculation from 4000 to 400
Eliminates any Airflow Correction from the VE Table

B1147 MPH description says engine speed.
Lots of stuff is there, way more then this list.

;Commanded AFR x 2560

;Dynamic cylinder airmass

;Dynamic airflow, val = g/sec x 81.92

;SD grams/cyl airmass x 8192

;MAF derived cylinder airmass x 8192

:Mass airflow rate, g/sec = val/81.92

;#1, P0101: MAF sensor
;#2, P0102: MAF sensor

;Short term fuel trim min and max
;Long term fuel trim min and max
;O2 Swing points
;Loads of O2 sensor paremeters.

That list is not all inclusive and some may not be needed to completly use all the tuning tutorials..

[skills4lou]

I know this was a while ago, but I'm gonna see if this works for my L29 over the holidays. Seems like it's been forever since I played with the truck, mostly just been working it hard. Towing a big 5th wheel around and I need all I can get out of it (safely of course).
So it'll be a bit, but I'll let you know how things work out.

[TunasTwins]

I know this was a while ago, but I'm gonna see if this works for my L29 over the holidays. Seems like it's been forever since I played with the truck, mostly just been working it hard. Towing a big 5th wheel around and I need all I can get out of it (safely of course).
So it'll be a bit, but I'll let you know how things work out.
Will be interested to hear how this works. Its hard for me to tell if the calc pids was finalized in the thread?

[joecar]

Make sure you understand the principles of the procedure...

you may need to improvise if a pid or two are not supported.