I thought STFT & LTFT range from -25 through +25?
06-17-2005, 09:10 AM
#1
Launching!
Thread Starter
Join Date: Mar 2004
Location: Dallas Texas
Posts: 233
Likes: 0
Received 0 Likes
on
0 Posts
I thought STFT & LTFT range from -25 through +25? I thought STFT & LTFT range from -25 through +25?
I have been looking through the CSV files of my recent scans and noticed that my STFT's have been ranging from -50 to +18 and I thought that the PCM only had range to self adjust to -25 and +25?
I'm just trying to figure out if those are valid readings or if something else is going on and causing HP Tuners to read bogus values?
Thanks for the Help!
I have been looking through the CSV files of my recent scans and noticed that my STFT's have been ranging from -50 to +18 and I thought that the PCM only had range to self adjust to -25 and +25?
I'm just trying to figure out if those are valid readings or if something else is going on and causing HP Tuners to read bogus values?
Thanks for the Help!
06-17-2005, 09:20 AM
#2
PCM should throw a code if the values are bigger than 25 (either way, plus or minus). sometimes you just get garbled/junk data, and you want to filter these out. HPT doesn't do the greatest job on filtering, so i just get the raw data, clean it up, and create my own histograms. kinda annoying, but i gotta do something while waiting for 2.0 
06-17-2005, 09:34 AM
#3
Staging Lane
Join Date: May 2005
Posts: 54
Likes: 0
Received 0 Likes
on
0 Posts
What he said. 
I've seen trims in my histogram read 00 and even 99, almost always in the lowest MAP range at lower RPM. Really threw me at first. If you look at these spots in the chart data you can see the other data params are usually crap too. Like Marcin said, you chuck it so it doesn't mess with any other data you're massaging.
I've seen trims in my histogram read 00 and even 99, almost always in the lowest MAP range at lower RPM. Really threw me at first. If you look at these spots in the chart data you can see the other data params are usually crap too. Like Marcin said, you chuck it so it doesn't mess with any other data you're massaging.
06-17-2005, 10:01 AM
#4
Launching!
Thread Starter
Join Date: Mar 2004
Location: Dallas Texas
Posts: 233
Likes: 0
Received 0 Likes
on
0 Posts
Cool that’s what I was thinking too. I'll just sort data by STFT and Delete any lines with values above or below the 25 mark. I knew it geeks out on some of the LTFT I'll see values of -100 or +100 and have always deleted them out, but up tell now I've never really sorted by STFT and checked to see if those values were with in the valid range. Believe it or not in the log I did on the way into work this morning there were 100 lines that were below the -25 boundary and I normally only see like 2 to 6 lines of invalid -100 for the LTFT so it made me wonder why so many out of range for STFT (100 out of a total of 4700 lines in the CSV file).
Thanks again for your input on this!
Thanks again for your input on this!
Last edited by God Forgives I Dont; 06-17-2005 at 10:19 AM.
06-17-2005, 10:38 AM
#5
the only way to do it 'easy' is to log a crapload of data, if you have 100 '+3' and 1 '-30' then the result is gonna be (3*100-30)/101=2.67 instead of 3, so that's not too far off.
the problem is when you get these 'funky' values in 'edge' cells, high or low map/rpm values, because you don't hit them as often.
with raw data in excel, use the auto filtering, and set up rules that make sense (map!=0, -25<LTFT/STFT<25, 0<=TPS<=100 etc) THEN you use that data...you'd be suprised how much junk is in there.
the problem is when you get these 'funky' values in 'edge' cells, high or low map/rpm values, because you don't hit them as often.
with raw data in excel, use the auto filtering, and set up rules that make sense (map!=0, -25<LTFT/STFT<25, 0<=TPS<=100 etc) THEN you use that data...you'd be suprised how much junk is in there.
