Finally got the car running correctly. Did a couple of 3rd gear pulls. I have a ? or two about how some of you are using data log lab.

how many data points are you using? mine is currently set at 1-51.

what plot range are you using for power graphs? i notice a discrepency depending on whether or not i use say 44 points or 51 points.

do you use sae corrections?

how do you attach the maps as jpegs? are you printing them then scanning them?

marc

ps - my run, sae corrected, using MJ's stage 1 buschur map netted 290hp and 258tq, with no knock events. not to bad at all!

 

I copy them to the clipboard and paste them into PBRUSH.. That usually works.. I don't use SAE corrections unless there's a severe change in my "Work environment" but lately I've been working at sea level with about 68 degrees.. How much more standard can you get?

Basically the discrepancy your seeing is due to the smoothing and averaging of points.. Since we're working with 6 samples per second, there are some assumptions made, if you pick a point on a downturn, the averaging and smoothing drags it down.. if you grab a point that is still "Rising" it will read higher due to it making assumptions that the next point may still be climbing.. Usually I trim a point or two off the plot so I get it to trim off the end without cutting off useful data, but not climb drastically giving a falsely higher number..

You actually should see around 290-300whp with your combo and my map using DataLogLab.. Keep in mind that the actual power probably isn't 300whp, its likely a bit lower, but run to run consistency is good with this software, and changes from mods will be reflected as gains, so you can at least tune "For real" without the innacuracies of guessing seat of the pants feel..

Remember to adjust the calibration file if you've changed to aftermarket wheels and tires (different tire size will slightly affect readings)

I haven't been able to calculate a real coefficient of drag, which means I can't accurately calculate how many HP at a particular speed that is needed to calculate the effect of drag on the readings. (Since on a real dyno this is not needed, but since we're moving through the air, wind resistence and aerodynamics are a factor).. However, I used the JDM WRX STI value which has similar aerodynamics and frontal area..

 

Oh, and you can pick up quite a bit of torque if you start working with timing, my car stock has pretty aggressive timing in areas, and I wanted to create a safe fuel map before I started tweaking timing.. But I found I can pick up 20+ lbft of torque by nudging the timing in the midrange..

 

i plan on doing some tuning later tonight.

you dont use any correction? without correction i am seeing only 245hp or so. my conditions are 85-95 degrees and 70- 95% humidity. 500ft above sea level.

 

yeah, I'm at sea level, with low humidity and average temp 65-68 degrees.. Thats pretty close to what the corrections do.. In your circumstances you do need to adjust for it.. But your corrected numbers sound right..

 

you probably could run your car right up to 7200rpm your HP was probably still climbing a little when you let off..

 

i will make sure i run it out later tonight. is the turboxs a/f the only one that can hook up to the utec. can i use an aem uego or something similar?

once again - thanks for all the help.

marc

 

if you want to get logging directly on the UTEC data logs you should use the Tuner.. But you can use any wideband you like, you just need to correlate your data based on RPM.. the output on the UEGO isn't something that can be passed directly to the UTEC though.. its really just an interface thing..

 

ok - i got it. just wish i didnt have to pay 700 bucks for a wideband. i know the $500 version will be out soon, but still it seems high.

 

$500 is pretty average for a Wideband setup.. it falls in the common price range.. the more expensive one has the equivalant of the "knock link" built into it.. Great for using as a standalone tuner, but not very useful since we already have knock detection built into the UTEC's data logging.. **HOWEVER** knock isn't always registered on the factory sensor, so its sometimes a good idea to tune with the Tuner's knock microphone to listen for pings and other weird noises, which I rarely hear over valvetrain noise anyway..