Once you guys explained it..it seems so obvious.
Thanks for explaining and for the CALC PIDS..
Printable View
Once you guys explained it..it seems so obvious.
Thanks for explaining and for the CALC PIDS..
In the calc_pids.txt attached to post#59 you may have noticed that I multiplied {SAE.MAP.kPa} by 1000... this allows CALC.VE_Table.VEpcm to be in grams instead of milligrams...
actually VE units map to g*K/kPa.
I applied this to some of my log files, I didn't have DYNAIRTMP logged, so I changed the calc pid to use IAT instead...
this is what it produces, VE_Table looks pretty close...
:)
Hows it looking?(CALC VE).
I updated the calc_pid.txt file... see attached.
Changes:
- in equation for VEpcm, multiplied MAP.kPa by1000.
- changed VEpcm units to VE units (i.e. g*K/kPa).
- changed VEpcm range from 0-3000 to 0-3.
- changed LTFTBEN % range from 0-2 to 0.5-1.5 for more resolution.
- removed extra set of parenthesis from around displacement multiplication.
:)
Would changing the high for the calc_VE to something like 110 be O.K. for boosted applications? I'm trying to understand the calc_pids boundaries in general. The only hurdle I see in this is my VE table isnt in %VE but grams/cyl. I think I need to make a BEN table to multiply my stock table with OR convert my table to %, find the difference, and go from there? Either way, I work at 3AM and will hopefully log the truck when I get home.
Yes, that's the gauge/chart high tickmark display mark, it doesn't affect the calculation.
High = highest tickmark on gauge/chart,
Low = lowest tickmark
Fmt = how many decimal places
Try the VE_Table with VE units in the calc_pids.txt I posted in post #65... not g/cyl but g*K/kPa (same as B0101).
The calc_ve PID still doesn't work. :frown:
Mr. Prick, is it a displacement issue? (all zero's), and it just won't validate?
Remember, we have two VE type PIDS. The 'newer' one that utilizes DYNAIRTMP is under Tuning..