Calc vet.

[dirtymaxlb7]

I've looked over and over cant find what I'm doing wrong every time I try vet table log strange numbers like .1-.6 anyone have any ideas TIA

[joecar]

Post your:
- calc_pid.txt
- tune file
- log file

and some pics of your map.

[dirtymaxlb7]

19631 19630 19632

[dirtymaxlb7]

hope that worked

[joecar]

Your EXT.WO2LAM1 pid is pegged at 1.7... your wideband is not working.

[dirtymaxlb7]

wow im sorry was so sure i did something wrong i didnt even look at that had the blinky light on v2 thought all was grand

[dirtymaxlb7]

wo2 seems to be working but still giving me same numbers and it was working in other logs as well i must have sent one it wasn't is possible i need to configure them differently i'm using inovate lm2 (which apparently i could have used a much cheaper version and got same result maybe less confusing)

[dirtymaxlb7]

19643

[joecar]

19643
Ok, it looks like wideband is now working... it shows lean on throttle close, maybe turn off DFCO during tuning.

Post screenshots of:
- your MAF map (SELBEN vs MAFFREQ Hz),
- your VE map (VET g*K/kPa vs MAP kPa vs RPM).


You don't have enough data, you need to drive around for about 20-30 mins, use steady /progressive throttle, don't jerk the throttle.

[joecar]

BTW: when throttle opens significantly, you get bare any PE...

check this:
- B3616: set to 65% below 3200 rpm, 35% above 3200 rpm.
- B3609, B3610: set both to 0.020 seconds.
- B3613: make sure this is less than 100 kPa (set it to either 50 kPa or 70 kPa).
- B3618: set this to EQR 1.175.

[dirtymaxlb7]

i havent been able to figure out screen shots yet do i need to disable ve to do this i will check those tables above thank you for your help someday i hope to make better sense of it all

[dirtymaxlb7]

my b3618 is in lambda not sure what to do to set eqr to 1.175 or what you mean and why 0.020 on b3609 b3610 just curious as to why not 0.......and again thank you for all help

[dirtymaxlb7]

maybe I'm closer than i think i changed units on my b0101 to g*k/kpa which is what my map shows and they have a closer relationship did short log on way home from work getting map data from 0.0 -1.5 might go for drive see what happens. Before i was getting numbers like 0.1-0.3 and was looking at B0101 with numbers 13.23-19... and got real frustrated hope im not setting my self up

[joecar]

i havent been able to figure out screen shots yet do i need to disable ve to do this i will check those tables above thank you for your help someday i hope to make better sense of it allSee post #2 here: Hosting-an-Image (https://forum.efilive.com/showthread.php?3064-Hosting-an-Image)

[joecar]

my b3618 is in lambda not sure what to do to set eqr to 1.175 or what you mean and why 0.020 on b3609 b3610 just curious as to why not 0.......and again thank you for all help
In tunetool, go Edit->Properties->Display and set Commanded Fuel Units to EQR.


We're using this convention to avoid ambiguity:
- commanded fueling is in EQR.
- wideband measurement is in Lambda.

The correction factor (aka BEN) is then easier to remember:
wideband_lambda x commanded_eqr


0.020 s on B3609, B3610:
this avoids zero which may have a special meaning (depending on who's experiment you look at).

[joecar]

maybe I'm closer than i think i changed units on my b0101 to g*k/kpa which is what my map shows and they have a closer relationship did short log on way home from work getting map data from 0.0 -1.5 might go for drive see what happens. Before i was getting numbers like 0.1-0.3 and was looking at B0101 with numbers 13.23-19... and got real frustrated hope im not setting my self upAs you do this, are you also applying the SELBEN correction to B5001 MAF table...?

I need to see both maps...


See post #2 here: Hosting-an-Image (https://forum.efilive.com/showthread.php?3064-Hosting-an-Image)

[dirtymaxlb7]

19654 19655 and this is new log 19656

[dirtymaxlb7]

19657 19658 are these what you wanted?

[dirtymaxlb7]

my dynamic air pid stopped working no idea why it was working and I'm not sure how i got it to then i fought with it for days then all of sudden it worked made log and wideband didn't now opposite this os is not in list so i'v been trying to figure that out but i get lost wish i could just lock myself in a room for couple days and work this out the guidance has been awesome though my navigation skills are picking up and thats bound to make things easier to remember and understand

[joecar]

19654 19655 and this is new log 19656In both map properties, on the Data tab, set Precision to 3.

( also, in the MAF-like map properties, goto the Cell tab and constrain the cell width )


Without seeing more decimal digits, MAF looks to be close, and VE seems close.

[joecar]

19657 19658 are these what you wanted?
MAF table:: make the 2D area taller so we can better see the shape and how smooth it is.

VE: that trough should not be there, have to adjust it or its surroundings depending on where the cell hits were.

[joecar]

my dynamic air pid stopped working no idea why it was working and I'm not sure how i got it to then i fought with it for days then all of sudden it worked made log and wideband didn't now opposite this os is not in list so i'v been trying to figure that out but i get lost wish i could just lock myself in a room for couple days and work this out the guidance has been awesome though my navigation skills are picking up and thats bound to make things easier to remember and understandWhich pid specifically...?

Post sceenshot of PIDs and Data tab when this happens.

[dirtymaxlb7]

In both map properties, on the Data tab, set Precision to 3.

( also, in the MAF-like map properties, goto the Cell tab and constrain the cell width )


Without seeing more decimal digits, MAF looks to be close, and VE seems close. 19663 19664

[joecar]

19663 When you apply the low cell count filter and the transient filter, hopefully that 0.728 cell will go away (otherwise hand smooth it if it shows up in the MAF table).

Your MAF correction map shows your MAF is close, at worst it is about 6% too low.

[joecar]

19664When you paste this into the VE table, you will have to do this:
- flatten out any large spikes or holes,
- bring the surrounding (i.e. unhit) cells to the same values (i.e. interpolate).

VE seems to go up quite alot in higher RPM/MAP area (lower right corner), what are your engine mods...?

[joecar]

I see that you applied the low cell count filter... you also need to apply the transient filter.

[dirtymaxlb7]

MAF table:: make the 2D area taller so we can better see the shape and how smooth it is.

VE: that trough should not be there, have to adjust it or its surroundings depending on where the cell hits were.19665

That ve table is the original unchanged one i haven't tried pasting yet but when i do i want to bring high or low spots towards pasted number correct?

[dirtymaxlb7]

When you paste this into the VE table, you will have to do this:
- flatten out any large spikes or holes,
- bring the surrounding (i.e. unhit) cells to the same values (i.e. interpolate).

VE seems to go up quite alot in higher RPM/MAP area (lower right corner), what are your engine mods...?

Its all stock with cam springs and headers

[dirtymaxlb7]

19666 19667
before after No blending done
does this look right and is there a way to interpolate all at once or is it a manual thing?

[joecar]

19666 19667
before after No blending done
does this look right and is there a way to interpolate all at once or is it a manual thing?

That does not look right...

you have to manually fill in the trench and/or reduce the hills on either side of it, depending on where the logged data cell hits were.

[dirtymaxlb7]

19668
playing around

[dirtymaxlb7]

19669 19670
PIDs and Data the K units are gone

[joecar]

19666
before...Take this one, and fill in the gap by hand... see how the peak is at about 2.xx g*K/kPa.

[joecar]

Post your current log file and the tune file that produced it, I'll look at them later tonite.

[dirtymaxlb7]

Post your current log file and the tune file that produced it, I'll look at them later tonite.196711967219671 19672
current tune current log

[dirtymaxlb7]

This poor truck went thru some paces today.....I went back and had a peek at original tune i see what you are talking about with B0101 I'm not sure how or when it got changed but i went back to original and made new log ......some of those boxes are very hard to hit especially with ETC in a bouncy old truck
19673 __ 19674

[joecar]

196711967219671 19672
current tune current log


This poor truck went thru some paces today.....I went back and had a peek at original tune i see what you are talking about with B0101 I'm not sure how or when it got changed but i went back to original and made new log ......some of those boxes are very hard to hit especially with ETC in a bouncy old truck
19673 __ 19674Several things are going wrong...

GM.DYNAIRTMP_DMA has the wrong values, this causes CALC.VET to be wrong... you will have to use the B4901 variant of Calc.VET (i.e. not log GM.DYNAIRTMP_DMA anymore, we can't rely on it), in the Calc.VET thread post #1 see III. Appendix point # 6... so we'll have to then start from scratch.

MAP peaks at 87 kPa... what elevation is your physical location...?

In the log I see WOT but RPM does not increase, what is going on here...?

19675

[dirtymaxlb7]

i do not understand how to create or use calc. pids it shows up in pid list but is not valid i read the how to create pids tutorial several times but cant make sense of it ill play around with it some more......i'm at 3500 ft I don't know why throttle is doing that ill have to dig into that i shifted up on a hill to try and get lower rpm/higher kpa cells and it just didn't do anything

[dirtymaxlb7]

this old truck is so bouncy and jerky throttle control is very difficult those homemade dyno guys on youtube got me thinking lol

[dirtymaxlb7]

19676 19677 :throw: Think getting closer

[joecar]

i do not understand how to create or use calc. pids it shows up in pid list but is not valid i read the how to create pids tutorial several times but cant make sense of it ill play around with it some more...
I can help with that.


...im at 3500 ft I dont know why throttle is doing that it bounces around at idle also i've noticed ill have to dig into that i shifted up on a hill ti try and get lower rpm/higher kpa cells and it just didnt do anythingOk, 3500 ft explains 87 kPa maximum MAP (BARO).

The RPM holding steady at WOT indicates something is not as it seems... either the engine is bogging down, or something is wrong with the PCM.

[joecar]

19676 19677 :throw: Think getting closerOk, CALC.DAT pegged at 32*F does seem to help the CALC.VET calculation...

but we really need the B4901 heatsoak air temperature... I'll make a calc pid for you.

[dirtymaxlb7]

not sure how to find that info but ill give you B490119691

[joecar]

not sure how to find that info but ill give you B490119691Ok, thanks, I'll make you a calc pid tonite...

[dirtymaxlb7]

Ok, thanks, I'll make you a calc pid tonite...

so the lookup pid in last log was not right?

[joecar]

so the lookup pid in last log was not right?Yes, that is the data, we just need to put it in calc pid form (see Appendix III in the Calc.VET thread post #1)... have you already done this (sorry, I got home late last night)...?

[dirtymaxlb7]

i guess if that is not right i have not figured in out yet dang it!

[joecar]

Ok, I got time this morning to insert your B4901 data into a CALC.B4901 pid (which is referenced by CALC.DAT so you don't have to log GM.DYNAIRTMP_DMA anymore), see attached, use this calc_pids.txt file instead.

So now, remove GM.DYNAIRTMP_DMA from your pid list, and add the new pid CALC.B4901.

[dirtymaxlb7]

Ok, I got time this morning to insert your B4901 data into a CALC.B4901 pid (which is referenced by CALC.DAT so you don't have to log GM.DYNAIRTMP_DMA anymore), see attached, use this calc_pids.txt file instead.

So now, remove GM.DYNAIRTMP_DMA from your pid list, and add the new pid CALC.B4901.

ok that is where is gets confusing I save it then cant find it... open it it just opens in notpad

[dirtymaxlb7]

19696
this is what i have not sure if that is pid from you or same one as last log

[joecar]

ok that is where is gets confusing I save it then cant find it... open it it just opens in notpadRightclick on it, go Save Link As, then browse to C:/Users/<you>/Documents\EFILive\V7.5\User Configuration, make sure the filename box says calc_pids.txt, click Ok.

[joecar]

19696
this is what i have not sure if that is pid from you or same one as last logThat calc_pid.txt is the one from Appendix III in the Calc.Vet thread, from the last log...

replace it with the new one from post # 48 above (the new one has your specific B4901 data).

[dirtymaxlb7]

ok think i have it would you have a look please i'm trying to avoid the expense of having to make pointless logs glad fuel prices are somewhat low 19700

[joecar]

ok think i have it would you have a look please i'm trying to avoid the expense of having to make pointless logs glad fuel prices are somewhat low 19700Ok, that looks correct... for sanity check take a quick 5 minute log and post it.

[dirtymaxlb7]

Ok, that looks correct... for sanity check take a quick 5 minute log and post it.

ok i will do that on way home tonight

[dirtymaxlb7]

19702 looks better i think

[dirtymaxlb7]

19707

[joecar]

19702 looks better i thinkThat does look much better.

[dirtymaxlb7]

19725 19726 let me know what you think i think alot closer

[joecar]

19725 ... let me know what you think i think alot closer

From this log, I see that the LTFT's are much tighter in a lot of places... but there are some places where I see them going out too far, and some places where VE may be a little low.

It may be easier if we disable DFCO... set each of B3308 , B3309 , B3313, B3314 to max (and make a note of this for later).


Also note: you're logging HO2S12 (bank 1 post-cat) instead of HO2S21 (log this one instead).


See if you can add these pids:
SAE.SPARKADV
GM.DYNAIR
GM.DYNCYLAIR
( this should bring you to 24 pid channels )

You are logging two MAF pids, you could drop GM.MAF and add SAE.VSS, this should bring you to 23 pid channels (see bottom of pids tab).


You can drop the pid EXT.FPEGPSSPD if you're not using it.


Since you're using two widebands (they both look like they'working)...
I think we should edit the BEN pid to take this into account (dynamically apply the leanest wideband)...
see attached calc_pids.txt... you'll be the second person who has ever done this (unless someone chimes in).

Also:
- copy attached .pid file to PIDs folder, open the file CALC-VET-LS1B-B4901-2WB.pids in the PIDs tab before logging.
- unzip .zip file to the VDash folder, open the file LS1B-0011.vdb on the Dashboard B tab.

[joecar]

Make those changes to tune file, take a new log, post tune file and log file.

( make sure that the pid channel count is no more than 24 )

[joecar]

Also, what is your engine's displacement...?

[dirtymaxlb7]

sorry joe truck has been at interior shop and decided to change gearing so gonna be i little while before can continue with tuning been working on changes you recommended in mean time i hope to seek your advice again when get back to it

[joecar]

No worries, take your time, I've been slowed up by a number of things.