I may be dumb, but I can multiply..

[ChrisSK]

SO I started using HPT about a week ago, after doing A LOT of readin before getting started, I figured I would finally throw on my Volant on my GTO, descreen my MAF and start tuning on the road. I am starting to tune LTFT/STFT using Histograms. It took me some time to actually get used to using them and figuring out how to load them, but I got it.

Ok, here is the question.

I have a datalog, I loaded the histogram up and used the average LTFT to base tuning my VE tables with. I copy the entire table and go into my Primary VE table, select all and paste special> Multiply %. The problem here is that it doesn't seem to be doing the calculations correctly.

For example, @ 3200rpm, 15kpa, the cell reads "2255".

Now, the LTFT in the histogram reads "9"

(This is just one cell, but it's doing it to all of them)

The correct multiplication is 2255*1.09=2458

When I do a Paste Special > Multiply %, the calculation it comes up with is: "2462"

I know it has to be something I am doing, I just would like to know what exactly it is I am doing. Both tables in the Histogram and PVE are scaled exactly the same.

Thanks in advance.

[Russ K]

Well, that is only out .0016%. I think it has something to do with the available
numerals in the editor or the vcm, so the value is rounded up or down to the nearest value. I tried the same thing on a 2005 GTO file and it worked for me.
If your using your maf, then the VE table won't affect the fuel trims.

Russ Kemp

[S2H]

one other thing to remeber..you only see "9"
but it might be 8.7 or 9.4 and you just dont have it set to see the decimals..
set decimals to 1 and you wil see what the pcm is seeing(ever look at your LTFT/STFT in the scanner table....shows decimals )
even if it only shows whoel integers in the scanner histogram..its still copy and paste out to 5 decimals

adn then it comes down to pcm resolution after that

maybe a 1/16th decimal resolution?? so you haev a few factors tat can sway it slightly different than you are seeing
so 2255..has decimals also...
adn 9 has decimals...
I see that even if it was exactly 2255...all it would take is 9.1796%

2255 could be anywhere from 2254.50000~2255.43750
and 9% could be anywhere from 8.50000~9.49999

[ChrisSK]

You guys rock. Sure enough, that's what it was. I set the decimel setting to 1 and I saw the actual number. Makes sense now.

As for dialing in the VE table with the MAF on, I know, I was just testing/learning while watching soprano's (dumb huh?). I will be doing SD tuning in the next week.

Soundengineer - What band to you travel with?

[S2H]

Soundengineer - What band to you travel with?

I have done many bands
getting ready to work for a band called "Say Anything"
then to work later this summer with "Crossfade"

I do a large amount of Pro Concert touring for several sound companies..
so I get to work for a lot of different groups
and I haev been doing this Job for over 14 years

[ChrisSK]

That made my VE table really rough looking, once I'm tuning should I just interpolate the graph to smooth it out? Or is it better to leave it rough.

[ChrisSK]

I have done many bands
getting ready to work for a band called "Say Anything"
then to work later this summer with "Crossfade"

I do a large amount of Pro Concert touring for several sound companies..
so I get to work for a lot of different groups
and I haev been doing this Job for over 14 years

So you tune on the tour bus and help newbies out like us in your down time?

Crossfade is a pretty good band that should be a good show for you guys.

[S2H]

That made my VE table really rough looking, once I'm tuning should I just interpolate the graph to smooth it out? Or is it better to leave it rough.

it doeasnt have to be a nice smooth graph..it can have ridges and valleys...
you just dont want it looking like a mountain peak....

I usually use teh smoothing button once on the first pass or two...then I go in and hand smooth things so that the cells next to them make sense..
if you have data that is 2255 in one cell..and right next to it is 3750..that doesnt make sense.so bring it down to a more reasonable # that is kind of close to the cells around it

[ChrisSK]

Thanks.. I appreciate it.