TPV5 BLM History table...

Discuss anything TunerPro related.

Moderators: Mangus, robertisaar, dex

Post Reply
pbsch
Posts: 2
Joined: Fri Sep 14, 2012 1:05 pm

TPV5 BLM History table...

Post by pbsch »

Hi Everyone,
I have been learning more and more daily and I think I understand the meaning of the table, but as I am about to embark on my first VE table tweak, I figured I better ask - If my table has a bunch of .90 and other numbers under 1 does that mean the ECM is reducing the VE to that amount and therefore, i should reduce the VE table for that cell by that amount to try and get it as spot on as possible?

This seems a whole lot easier than trying to hold the engine at a particular rev and map position to get a BLM reading

Thanks,
Paul
JP86SS
Posts: 218
Joined: Thu Apr 22, 2004 5:49 pm
Location: Strongsville, Ohio
Contact:

Post by JP86SS »

The values in the table will be based on how the definition file is setup.
Each person who created it could do it differently.
I don't know what file you are using so its difficult to answer that question.
The BLM table I use for $8D has MAP (Kpa) from left to right, RPM from top to bottom and fills the cells with the actual BLM value.
Format the history table to match your VE table layout is helpful.
values of 128 are perfect (no change needed to the fuel)
Less than 128 means fuel is too much and should be lowered.
Greater than 128 and fuel should be added.
I take that and use an Excell spreadsheet to figure out the differences and then apply a "factor" to multiply the existing VE table values by.

Paste the corrected table back into the bin and drive some more.
I like to make around a 60% correction instead of trying to make them the full correction value needed. Putting the full correction in can make you overshoot and then be wrong on the opposite side next time.
HTH
Image
pbsch
Posts: 2
Joined: Fri Sep 14, 2012 1:05 pm

Post by pbsch »

Sorry, didn't think about that - I'm using a $a1.adx from I believe the downloads section. Looking at the code in texpad, Robertisaar created it.

Here's the actual code for the histogram in question
<ADXHISTOGRAM id="totaltrimhisto" idhash="0xA04E4D28" title="Total Trim">
<rows>13</rows>
<cols>10</cols>
<xmin>800.000000</xmin>
<xmax>4000.000000</xmax>
<ymin>20.000000</ymin>
<ymax>100.000000</ymax>
<rowval index="0" val="20.000000" />
<rowval index="1" val="25.000000" />
<rowval index="2" val="30.000000" />
<rowval index="3" val="35.000000" />
<rowval index="4" val="40.000000" />
<rowval index="5" val="45.000000" />
<rowval index="6" val="50.000000" />
<rowval index="7" val="55.000000" />
<rowval index="8" val="60.000000" />
<rowval index="9" val="70.000000" />
<rowval index="10" val="80.000000" />
<rowval index="11" val="90.000000" />
<rowval index="12" val="100.000000" />
<colval index="0" val="600.000000" />
<colval index="1" val="800.000000" />
<colval index="2" val="1200.000000" />
<colval index="3" val="1600.000000" />
<colval index="4" val="2000.000000" />
<colval index="5" val="2400.000000" />
<colval index="6" val="2800.000000" />
<colval index="7" val="3200.000000" />
<colval index="8" val="3600.000000" />
<colval index="9" val="4000.000000" />
<historysize>10</historysize>
<xidhash>0xDE6A2DB0</xidhash>
<yidhash>0xDE6881B0</yidhash>
<zidhash>0xC40D24D1</zidhash>
</ADXHISTOGRAM>

I'm guessing we'd have to know what's stored at those hex addresses to know for sure.

Anecdotally, I adjusted the VE table based on these numbers and the next run this table had many more 1's and .9x's and 1.0x's so I think I have interpreted it correctly.

I need to get out and log some hill climbs so I can see the other areas of the table - the garage is only good for a diagonal band through the middle of it.
robertisaar
Author of Defs
Posts: 962
Joined: Sat Feb 21, 2009 3:18 pm
Location: Camden, MI

Post by robertisaar »

with the way i set it up, 128 is 1.00 (meaning 0% fueling change in either direction), under 128 will show up as .99 and under(implying that the ECM is pulling fuel from closed loop correction), above 129 will show up as 1.01 and above (fuel added from closed loop correction).

the table could be changed back to using straight BLM instead of the "LTFT" value that i created from it with reltive ease, if you so desired.
Post Reply