Calc.vet on 1999 5.3 Silverado: dynamic air temp will not validate?

[thunderstruck507]

I am trying to get a tune on my truck for a new cam I am testing for Cam Motion, but can't seem to correctly run Calc.vet due to this PID not validating. I have searched around but I must not be using the right keywords.

What do I need to do to be able to run calc.vet correctly?

[darcy]

Dynamic Air Temp may not exist in your OS.

Go back to the CALC.VET thread, and look at the instructions for how to deal with this. (Post 1 > III Appendix, Additional Links and Resources > 6)
You need to use a slightly different calc_pids file that calculates DAT from a lookup table.

[joecar]

+ 1 what darcy said... you will have to fabricate DAT from your B4901.

see Calc.VET thread post #1 section III.6 (quoted below):


(http://forum.efilive.com/showthread.php?16849-In-Memory-of-Shawn-Sankey)...III. APPENDIX:

Additional Links & Resources

1. Advanced CALC.VET Summary Notes: CALC-VET-Summary-Notes (http://forum.efilive.com/showthread.php?16280-CALC-VET-Summary-Notes)

2. Calculating MAF Airflow From VE Table (CALC.VET In Reverse): Calculating-MAF-Airflow-From-VE-Table..CALC-VET-In-Reverse (http://forum.efilive.com/showthread.php?16413-Calculating-MAF-Airflow-From-VE-Table..CALC-VET-In-Reverse)

3. CALC.VET utilizes EQIVRATIO which is superior to AFR (avoids different stoich AFR's of different fuels).

4. How-to-match-wideband-output-to-B3601 (http://forum.efilive.com/showthread.php?13229-How-to-match-wideband-output-to-B3601&p=117265#post117265)

5. Two Methods for Calculating Analog Wideband Lambda (http://forum.efilive.com/showthread.php?15236-A-New-Twist-on-CALC.-VE-Table..Computing-the-Entire-VE-Table.&p=137997&viewfull=1#post137997)

6. The pid GM.DYNAIRTMP_DMA is not defined for OS's 19980100, 1998020, 19980400, and some others...
but you can create a CALC.B4901 lookup pid instead, see the following alternate calc_pids.txt:
14797 <-- check that this contains the same B4901 data as your tune file.

The pid GM.DYNAIRTMP_DMA is defined only for these LS1 OS's:
12202088 92111922 12208322 12225074 12212156 12221588 12216125 12577216 12579405 12580055 12585318 12593058 12509967 12587604
12588804 12592433 12585950 12587603 12592425 12606960 12592618 12593555 12606961 12612115 12587811 12606807 12608669 12597120
For the OS's listed ^ here you do not need to create the pid CALC.B4901.
For any OS not listed here you have to create the pid CALC.B4901 using your own B4901 data (see the calc_pids.txt immediately above).

1997 Corvette & 1998 Corvette/Camaro/Firebird Pids:
( include all the same pids as in section I.2 above, and include CALC.B4901, and exclude GM.DYNAIRTMP_DMA )

...

[joecar]

Thunderstruck,

What are your new cam specs...?

Let us know how you go with it all.

[thunderstruck507]

I had that thread printed and in my tuning binder but it did not have the revisions. I went back and copy pasted joecars calc_pids.txt file over my old one and that added the calc.b4901 PID I needed.

But it also invalidated my PID for calculated VE uncorrected. I read the "more info" but did not write down what it said, it was missing a parameter (I think it had a K in the name) so I tried selecting it. I got an error telling me that parameter was "invalid" but it let the calculated VE pid work so I tried it. The result was my MAF correction mapped correctly but the VE map did not, it all came out to 1s or .8-.9 decimals. I'm not 100% sure if the problem was due to the PID fiasco or if something is wrong with my VE map settings since when I updated to V8 it cleared everything in my scan tool (gauges reset to metric, maps were not stored, etc). It was so dang hot yesterday and I was still exhausted so I just give up.

I can get more details on lunch or this evening to try to pinpoint the problem if you guys aren't able to take a stab at it from what I posted above.

I probably sound like a complete idiot, but programming and coding are well beyond me and even some of the simple stuff with this software confuses me sometimes.



The cam is a Cam Motion Stage 2 "drop in" cam for the 5.3, it is only a tiny 205/210 .510/.510 115+4. The truck started and ran fine on the stock tune, you would never know it was there honestly. I just wanted to dial it in 100%. With the MAF corrections I was able to get my WOT fueling correct. Part throttle fuel trims are kinda scattered and response feels a little soggy so I think some work to VE will help.

For some reason the truck does not want to take timing. It pulls 8* KR on initial WOT and then holds 5*+ KR through a whole pull. I kept reducing the timing and it did not change so I think it is "false knock". Burst knock has been zeroed in the tune. It was REALLY hot so it might be IAT related. If anyone has any other ideas on where to look for that I would appreciate it. I even tried reducing the knock sensor sensitivity table (the one on my car is zeroed out but not sure how safe that is for a vehicle that will not always receive premium fuel).

[joecar]

On invalid pids, do rightclick->More Info to see which other pid(s) need to be selected.

You need to select both pids CALC.DAT and CALC.B4901.

Post a screenshot showing your invalid pids.

[joecar]

205/210 115 +4 is similar to the LS6 cam (204/218 117.5 -2.5) so the stock tune will be able to start and idle just fine.

If you see KR, look at the CALC.WO2BEN and CALC.LTFTBEN, and look at PE EQR B3618 and PE enable B3616.

[joecar]

Post tune file and log file.

[thunderstruck507]

17206 17205

Here the current versions of the tune and log. Runs WAAAY better with the 02 OS and will take timing now so I used a ls1 timing map.

I tried to do an updated CALC.VET but the numbers on the upper rpm end seem very excessive. I think I have something wrong. Maybe something related to injector data?

I also am not sure why bank 2 is so much richer than bank 1. Faulty 02 sensor maybe?

[thunderstruck507]

logging will work better if I get 12v to the wideband....noob mistake

[joecar]

How is your wideband wired up...?

[thunderstruck507]

It wasn't connected for that log. I made a mistake and forgot to hook the power wire up. I appreciate your patience joe...most would probably shake their head and call me a goofball.

Just got it taken care of and got a great long log. VE table and MAF both came out really smooth. I will do some logs tomorrow to check everything out and see how the results work.

In the meantime, if anyone knows how to get the alternator warning light to go away that would be great. I am going to try turning off the Gen F terminal value in G1207. I am going to check the C6001 and C6002 for anything I might have missed as well.

[joecar]

No worries... (I apologize if I seem a little slow these last few days... I was laid off my daytime job on Friday, so I'm a bit stunned).

Post new log file.

Yes, look at G1207.

[statesman]

I was laid off my daytime job on Friday, so I'm a bit stunned

That's a real bummer. Sorry to hear that.

[thunderstruck507]

That's terrible news Joe.

The changes to G1207 and selecting "not reported" on a diagnostic item has removed the light.

I will post the log and new version of the tune as soon as I can. It drives much better, but seems to have a slight hanging idle when coasting. The only changes made were to VE and MAF tables. It isn't consistent so it might be a matter of the truck learning idle? It's very subtle.

[joecar]

That's a real bummer. Sorry to hear that.

That's terrible news Joe.

Yes, it is a real bummer... maybe this is an opportunity to reinvent myself.

[joecar]

...

The changes to G1207 and selecting "not reported" on a diagnostic item has removed the light.

I will post the log and new version of the tune as soon as I can. It drives much better, but seems to have a slight hanging idle when coasting. The only changes made were to VE and MAF tables. It isn't consistent so it might be a matter of the truck learning idle? It's very subtle.Ok, good job on silencing the light.

Hanging idle on coasting may requiring looking at Throttle Follower and possibly Throttle Cracker.