I use open office and can't change the correction factor. My car weighed in at 3220lbs. with half a tank of fuel when I had my coilovers corner balanced. If I input the true weight I get about 550hp & 540tq. It just seems a little high, maybe I underestimate the car.

 

Yes 5.71, My max trim is set at 7200 right now, kinda wierd all the pulls is the graph stop right at max power and torque lol. Good work regardless as I am mostly just interested in my max power althought its still nice to see how it goes after that

 

So far, you're doing a great job. For the tire size and curb weight options, I think the easiest solution is to setup a check box that enables "automatic" values.

 

How are you calculating the frontal area?

I use (height x width) x 0.91 = frontal area. For the Evo X I am getting 26.26 ft2

 

All of you OpenOffice users, I just fixed the drop-down problems for you, so REDOWNLOAD V5.71 please.



I don't calculate it. I went from data found online. I usually won't use a value unless I've confirmed with with a minimum of 2 totally different sources, or straight from the car manufacturer. Even if its off a little, as you can try, the difference it makes is probably about 0.33%

 

is this the "stand-alone" version?

 

God no,lol. This is just me trying to make the current version better until the stand-alone is completed. I'm not the one working on the stand-alone version so IDK how long it could take to come out, anf I finally found free time to work on this again so I figured I'd finally fix the bugs in it.

 

Just tried 5.71 in OpenOffice, works great, thanks...See sig for #'s.

 

I've got a run I made ~ 2 hrs after I pulled off of a dynojet. I'd be more than happy to send you the dyno sheet and a copy of my vdr file.

really, it'd be more useful to have a log of an actual dyno run. I'm trying to get a copy of mine.

 

Jack_of_Trades I just sent a PayPal donation your way. Thanks for spending so much time on a great program!

Dan (drb)

 

Thanks man dropdown works great now, any openoffice users having the same issue as me with the graph cutting off after like 4500 rpms? Wierd

 

That would be great. Please Email anything u have to "punkdivo78 at hotmail dot com".

Thank you so much Dan!!!! It helps more than you know right now.

I just loaded a few pulls in OpenOffice with no issues. If you aren't running OpenOffice version 3.1.1 I suggest updating it by clicking the HELP tab on the top and selecting "Check for Updates". If you are running that version or the problem persists, save a copy of the simulator with your pull pre-loaded in it and email it to me (my email is listed above in this post).

 

Ok I think I might have an idea. I have been graphing old pulls from when I ws using mitsulogger and for some reason they all were cut off. However today I did some new pulls using my evoscan and they are showing up just fine. Wierd but it is what it is not sure why it would do that but I dont use mitsulogger anymore anyways, Once again great work JOT!!!

 

A pull on a dyno jet would read differently then on the street i would think since its a toally different load. Best way IMO is to run on a dyno jet then right after go to a COMPLETELY FLAT road and do a few runs then compare. Thats how i did it with the VDR and its very accurate when it comes to uncorrected #s. VDR FTW no more having to travel and pay to get #s


BTW just sent you a donation. $ is very tight right now so i will have to send some more at a later date. This software is great and VERY consistent and i dont mind throwing donations at all. I know you have put a lot of work into it and its greatly appreciated!

PS. It came from my business email AB Mods.

 

Yeah, a Dynojet preloads a car a little differently than true ROAD conditions so I've found it best to dial-in the simulator with a datalogged street pull that was recorded just after the dyno session. Then I compare it to the dyno results. Mellon did this exact thing and he was able to mimic his dyno results with a correction factor of 1.12 (and you basically did this and found it to be 1.10) so I feel that the newest correction of 1.11 is good for now until more and more data is accumulated.


Thank you for the donation! I don't expect anything, so even 2 bucks from someone is greatly appreciated!