I meant the predefined one.
I hacked the sae.generic.txt to see what it looks like after a log w/MAF.
I meant the predefined one.
I hacked the sae.generic.txt to see what it looks like after a log w/MAF.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
Mike, are you using the pid CALC.VE_Table under system Tuning like Shawn said...?
Code:. . . CALC.LTFT F001 CLC-00-001 % Tuning "LTFT Average" CALC.LTFTBEN F002 CLC-00-002 factor Tuning "LTFT BEN" CALC.VE_Table F003 CLC-00-003 "%,VE" Tuning "CALC VE Table"
I assume it may still relate to displacement..
http://forum.efilive.com/showpost.ph...9&postcount=41
I replaced the displacement() part of the sae_generic.txt with my engine's size in CC.
I don't think {CALC.VE} has been working for a while even tho the
displacement in the customer details has been fixed.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
Mr. P., mine has been working. I just use the V2 right now, not BBL. Don't know if that is the issue, but both my PIDs worked perfectly on a run 1 day ago..???
************************************************** ******
On the 'issue' of the EFILives pre-defined CALC.VE Pid vs the CALC. VE Table Pid.
The CALC VE Table Pid includes the calculation of charge temperature to more accurately 'convert' a MAF based-airflow into a dynamically calculated airflow.
Here is an example of using just the predefined EFILive CALC.VE Pid..and simulating a total MAF failure.
The second MAP shows how adding the ECT & IAT blending (charge temperature), again assuming a total MAF failure, greatly enhances the accuracy of the VE Table calculation.
The second example is utilizing the CALC VE Table Pid..
Using the new CALC VE Table Pid, will increase your VE Table values ~ 5-10% in high ECT, low airflow situations, and ~ 1-3% at WOT..where the PCM uses almost exclusively IAT in its calculations.
Hope that makes sense..
Last edited by WeathermanShawn; April 12th, 2010 at 08:27 AM.
I was just adding the {CALC_VE} pid to a log I already had to check it out.
I don't normally log {GM.DYNAIRTMP_DMA}.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
The only other thing I can think of..since I may have a similar problem once...
I recall making sure every unit in my scan pid selection was all metric. I think I got hung up once on the MAF units..made sure they were g/s.
Occasionally on my desktop I could not utilize the CALC VE Pid, unless I had a run transferred from my laptop. The laptop of course I had validated all the pids etc., and I had the Pid working (prior to a run).
I am probably getting in over my head on the computer end..Perhaps there is still a 'bug' somewhere??
Mike, does your log contain GM.MAF or SAE.MAF...?
We might need to make a set of pids for GM.MAF, and to manually blend ECT and IAT...
this will allow CALC.VE_Table_Handraulic to be applied to old logs.
Try this calc_pids.txt (I haven't tested it yet)...
In CLC-00-004 and CLC-00-005 you may have to replace SAE.IAT with some blend of SAE.IAT and SAE.ECT...
e.g. 0.90*{SAE.IAT} + 0.10*{SAE.ECT} (where the two fractions add up to 1.0)
Change 5.669 to your actual displacement in litres.
Shawn, good point on Metric units.
Mike, on the PIDs tab, highlight every pid (ctrl-A) and do rightclick->Metric.