srry double post...browser di not update the page correctly

 

apparently that's not the case, I logged : rpm - speed - TPS
and ended up with a curve going backwards and 1200hp when I loaded the CSV, same problem with dynovision btw, there is no problem with my log because if I copy the logentryseconds and rpm in virtual dyno room excel sheet my curves are ok

 

What value are you trimming tps at? Can you post the log?

 

Technically all you need is rpm and time but youll have to trim it yourself like in VDR. If you have tps you can trim it automatically. tps is used to find the wot section sense thats all you look at.

The loops you see are where the wot and the part throttle are being graphed. Log tps and adjust your tps trim value.

Let me know if this helps.

 

For AEM logs boost just needs to look for the parameter "Engine Load" (no quotes) in the txt file.

Once thing I noticed...it would be killer if we could drop a verticle line onto the graph to see the exact HP and torque is at the RPM where we dropped the line.

That and having the RPM axis labeled when you zoom in.

 

Just click on "Show Data Points" in the options menu

Ya, but for AEM guys, it saves the column name in the profile, so you dont have to type "engine load" next to BOOST

 

Engine Load has been added as a default boost column for AEM logs, in 1.0.7

Also the drawing the line up and down ... you already have that option without the line. Show data points shows the points on the graph. If you move your mouse over them it shows you the values.

The zoom issue hasnt been mentioned till now. I need to get the graphs synced to zoom together if I can. If this is possible Ill do it. If not ... *shrug* I dont know what to do.

 

SICK program brad! this will come in very handy without access to an awd dyno
i'll send you a donation in the morning.

 

Thanks!!! I am stoked that everyone thinks this thing is useful. Keep using it and Ill keep developing on it.

Im already working on 1.0.7 so hopefully its getting even better. I sent a beta of it out to a tester last night to get an opinion.

 

I manually removed everything else than the 100% tps measures on my csv and it worked
it seems my logs this time had too many measures for the auto-trim to work..like 9000+ lines on the .csv lol
with "only" the 500lines left from 1900rpm to 7500rpm it worked perfectly

...and confirmed my feelings that I have a drop in power around 5k rpm and it's also going down near the rev limit which should not be the case :/

 

That's pretty cool,

Seemed to work well with my evoscan log, and fairly accurate to what I put down on a mustang dyno not too long ago.

 

It shouldnt care how many lines you have in the log file since it loads the CSVs to memory when loading them. Also Ive loaded AEM logs that were WAY longer than this (19628 lines to be exact). If this is with EvoScan are you driving all over town logging to one log file? Thats a LOOOOONG log file for it to log. Are you doing more than one run in a log? Its got to be something else going on with the log other than too many lines.

Got the log for me to look at and maybe find out what the issue is? That way if its something with the program I can find it, and if its something with the log Ill notify the public so they know.

Let me know if you modified the correction factor to get it to match your mustang dyno run and if so what did you modify it to. Im trying to verify how accurate the mustang correction factor is.

Thanks,

Brad Barnhill
Virtual Dyno Developer

 

Awesome app! Keep up the good work!

 

Silicontek ... you bet.

 

Did you look at those STI ap logs yet?

I'll drop some donations this week or next week, waiting to get paid and some more tunes to roll in.