Working on Calc.VET tune and getting odd data when logging

[Hyper99]

I have setup 7.5 as instructed and I pulled the CALC.VET in the latest thread about this method. When selecting this PID file and logging data, I get duplicate fields in the DATA section of 7.5.



There are duplicate entries for a couple of the PIDS, even though they are only enabled once.

Calculated VE - BEN corrected - the second one has valid data present, the first one stays at 0%??

If you look at the Dynamic temp fields, they are not really valid values for the label (F) -357 degrees?

DAT appears in the list twice, the second entry carries the proper Temp value - why is it showing two entries??

Don't want to use invalid data when tuning, so I need some clarification as to what might be going on here.

Log file and CALC_VET.PIDS file are attached.

Any help would be appreciated

[joecar]

If you're using VE[%] did you enter your engine displacement (Edit->Log File Information, find the tab with displacement, enter it in cc; remember to save log file)...?

[joecar]

What is the OS id of your tune file...?

[joecar]

Your GM.DYNAIRTMP_DMA pid is producing the wrong values...

What is the OS id of your tune file...?

Can you post your current tune file...


If that pid doesn't work right, we can edit calc_pids.txt to use your B4901 table for DAT.

[Hyper99]

Attached are the existing tune, new tune and calc_pids.txt files - with the existing tune is the one with today's date and that was the one that the log was made from. I did miss adding the Displacement in EDIT LOG, Is this something that I need to do each time? The calc_PIDS.txt does appear to have a variable called DISPLACEMENT - can I hard code that just for tuning this truck?

The existing tune has an OS of 09379910 and a cal of 9374401 - I intend to update to the other tune attached, it is for a 2002 and all the 99 settings that were proven on the truck are transfered. When loading the tune in the truck the Message center always displays "SECURITY".... Is there something I missed when updating? The truck starts and runs fine with the new OS (12212156) and CAL (12212431) but depend on this truck for days I am on call, so I put the old tune back in until I figure this out.

Calc_PIDS.TXT file attached. Please advise on what you find.

Thanks for the help

[joecar]

I'll look more closely at your files tomorrow...

what is the year/mode of your truck (is it the one in your sig...?)

[Hyper99]

Yes - 99 Silverado

Thanks!

[joecar]

Hi Hyper,

I'm sorry it's taken me so long to get back to you I have been utterly swamped...

...
I did miss adding the Displacement in EDIT LOG, Is this something that I need to do each time? The calc_PIDS.txt does appear to have a variable called DISPLACEMENT - can I hard code that just for tuning this truck?

If you use [%] units for VE, then yes, before analyzing a captured log you have to go Edit->Log File Information->Vehicle Options->Engine [cc] and enter the displacement and save the log file.

If you use [g*K/kPa] units for VE, then you don't need the displacement.

No, leave the reference to displacement() alone, it references the value you enter via Edit->Log File Information->Vehicle Options->Engine [cc].

The existing tune has an OS of 09379910 and a cal of 9374401 - I intend to update to the other tune attached, it is for a 2002 and all the 99 settings that were proven on the truck are transfered. When loading the tune in the truck the Message center always displays "SECURITY".... Is there something I missed when updating? The truck starts and runs fine with the new OS (12212156) and CAL (12212431) but depend on this truck for days I am on call, so I put the old tune back in until I figure this out.

If you changed the OS you might have to relink VATS, try this, but first log the various STATExx pids to see if it they give a reason for the security light/display.

[joecar]

Is the file 2002 Chevrolet Silverado Truck Automatic LQ4 6.0 Litre (12212156)_Updated with 99 Mod settings.tun what you're currently running...?

[joecar]

Ok, your GM.DYNAIRTMP_DMA pid doesn't work for your 9379910 OS...

does it work for your 12212156 OS (it should)(post a log file)...?