PDA

View Full Version : calc.vet pids and setup



db caissie
August 7th, 2018, 06:52 PM
can i have a few pairs of eyes look at what i've got setup for pids and calc.vet tune setup, in the first log i've done, something seems off, and i'm obviously not smart enough to figure this out...
I have a serial wideband aem 30-4100 on it and i feel like maybe the pids are not set up right for what i have?

info on vehicle is 05 yukon 5.3l 4l60e 4wd lowered 285-40/22 tire
5.3l lm7 with following mods...
gm asa grind cam .525 int/exh lift, 285exh/274int duration, 236exh/226int @.050, 106 intake centerline, 110lsa, howards part#197715-10.
1-3/4" longtube headers, no cats, single 3" flowmaster out the back exhaust
4l60e has a torque convertor from a i6 trailblazer, stalling at roughly 2200ish
22325
thanks
Dale22326

joecar
August 8th, 2018, 07:22 AM
Your log file shows that the pid EXT.WO2LAM1 has invalid data... i.e. lambda data is not being read correctly from wideband...

how did you configure FSV2 for wideband...?

db caissie
August 8th, 2018, 11:51 AM
I'll have to double check my device settings, I just read through the device setup sticky again, and i don't recall a couple of the steps, will check and report back tonight,

thanks

db caissie
August 8th, 2018, 02:58 PM
double checked my device setup, everything okay there, i'll have to double check my wiring setup for the serial coms input though, but i'm sure i triple checked that when i installed, is it maybe in the text file i wonder?

db caissie
August 8th, 2018, 04:47 PM
did some updating, triple checked a couple things, trying it again now, does this look better?

joecar
August 8th, 2018, 06:05 PM
WB looks much better :cheers:

What is the elevation of your location...?

joecar
August 8th, 2018, 06:09 PM
You log shows that you have current DTC's P0101 (failed MAF) and P0106 (MAP performance)...

are you intending to run VE-only (i.e. failed MAF)...?

you will have to fix P0106 (if MAP sensor checks out ok, then look at MAP sanity table in Engine Diagnostics section of the tune).

joecar
August 8th, 2018, 06:10 PM
...

you will have to fix P0106 (if MAP sensor checks out ok, then look at MAP sanity table in Engine Diagnostics section of the tune).

Try setting C5501 to 0 rpm.

db caissie
August 9th, 2018, 05:16 AM
I don't intend to run on VE only, i've made some adjustments in the tune file from the summary notes in the calc.vet sticky, to help with tuning, but otherwise i feel like the dtc's are stemming from the camshaft that i have in this thing, it has lots of overlap, not radical by anymeans but it has a pretty healthy chop to it.
i don't believe the maf or the map are faulty.

can i ask what the purpose of setting c5501 to 0 rpm is for? will that allow me to continue with the tuning of the calc.vet?

joecar
August 9th, 2018, 06:34 AM
...

can i ask what the purpose of setting c5501 to 0 rpm is for? will that allow me to continue with the tuning of the calc.vet?
If the MAP sensor checks out ok, then setting C5501 to zero avoids running the test for P0106... we want to avoid having this DTC trigger because its presence may affect what the PCM does (with other tables/modes).

db caissie
August 9th, 2018, 06:55 AM
ah, I see, would that explain the maf dtc aswell?

and also i'm at 1,130ft (345m)

joecar
August 9th, 2018, 09:03 AM
ah, I see, would that explain the maf dtc aswell?

Looking at your tune in post #1 above, I see that the MAF diagnostic parameters (C2901-10) are stock (their values do not force-fail the MAF)...

so it looks like you may also have a MAF problem (looking at your log, it seems to me that it is under-reporting).

db caissie
August 10th, 2018, 09:12 AM
I have a k/n panel filter in the stock oem filter box, that i am skeptical about its condition, as in it wasn't cleaned properly from the original owner, and may be giving me these issues, i will replace with an oem paper filter, and clean my maf, and try again this weekend

db caissie
August 10th, 2018, 05:37 PM
replaced filter, cleaned maf
no change
set c5501 to zero, p0106 goes away (which I think those kpa values looked about where they should anyways for the map sensor)
so does it appear my maf may be faulty?
I don't recall that this issue was present before the cam change, so i have a hard time believing it just failed, but i guess anything is possible, it is the oem original piece. I don't really want to do a speed density tune, due to the elevation changes, temperature changes (it was 40deg c yesterday, in a months time it can dip down to 0deg c in the mornings) throughout the summer season i will be driving this thing. or am i wrong in thinking the calc.vet maf tune is the better option for me?

joecar
August 11th, 2018, 01:25 PM
MAF sanity tests:

bump up the MAF table B5001 by 10% and see if the MAF pid now reports 10% higher.

at WOT 4500+ rpm MAF should report at least 270 g/s.

check logs to see if MAF pid lags/delays after throttle opens.

statesman
August 12th, 2018, 07:51 AM
I don't recall that this issue was present before the cam change, so i have a hard time believing it just failed, but i guess anything is possible, it is the oem original piece.

I don't think that anything has failed... your new cam is just making the engine breathe differently and you're failing the MAP rationality test. Any kind of idle surge with a decent size cam will send your MAP readings outside the rationality test limits. Look at tables {C3003} and {C3004} and make a map of your MAP readings from your log and see if any of those readings fall outside the high or low limits of those two tables. If they do, then change the cells which are causing the problem.


I don't really want to do a speed density tune, due to the elevation changes, temperature changes (it was 40deg c yesterday, in a months time it can dip down to 0deg c in the mornings) throughout the summer season i will be driving this thing. or am i wrong in thinking the calc.vet maf tune is the better option for me?

Your best option is to tune both MAF and VE... and then run an open loop MAF only tune (provided you've got decent injector data). If you go closed loop, then you're exhaust will stink without cats. VE is the computer's backup in the event of a MAF failure, so it's good to tune it even if you're not going to use it. If you tune your MAF and the curve ends up looking like a wild animal has attacked it, then your injector data is no good.

db caissie
September 15th, 2018, 04:32 PM
thank you guys for all the help, i've since abandoned this camshaft and went with a btr stage 2 truck cam, more lift, but milder on the duration and lsa, so it runs decent on a slightly modified stock tables, however i will still continue on with attempts to tune it. your help is much appreciated and will be good tools for me to proceed with this project. Funny enough like I mentioned earlier, here it is mid september, and it's been close to 0 deg C in the mornings, and winter weather is coming soon, so driving time and tuning time is dwindling as we speak, I'll keep this updated when do get time to do some data logging/tuning.
Thanks guys

joecar
September 17th, 2018, 09:55 AM
In what state are you located...?

db caissie
September 19th, 2018, 07:16 AM
British Columbia, Canada, the great white north, where 91 octane fuel is more then my mortgage payment...