It didn't make this release ... got to work on that. Patience young Jedi ... I'm a one man army here. I also got burnt out a bit lately and worked on the logger I've written to keep me from quitting the project. I do this from time to time to break up the monotony. I took WAY too long to get this release out. I like to do a release every few weeks but this turned into 3 months. It was a rather large release with some major fixes in it. I removed a LOT of code in this release to get rid of unused portions of code, and cleaned up a bit. Its still a mess as far as code goes but it is getting better with each release. I know where everything is by heart but I like it to be clean and neat too. Ill get on that part of the next release asap.

 

THERE's NO MERCY IN THIS MOJO.

 

no mercy is how I roll

 

Digging this up as I just discovered the program today.

First off, this is a great tool...thanks for all the effort!

Second, I plugged in a 3rd gear pull and it's saying I'm only making ~50hp. What am I doing wrong? My car is running on ECMLink, exported to a .csv, with the correct car chosen (90-93 Miata 1.6L).

Thanks!

 

Then i guess you're only making 50hp. Did you confirm you're in 3rd gear and all the correct ratios and weights?

 

lol definitely making more than that

I'm entering the correct model year, checked that the weight and gear ratios are correct, tires are correct size, and that I had the correct gear selected for the runs I chose (tried a 3rd and a 4th gear pull). Odd.

Trying different csv's from a variety of pulls yields different results (showing 50-100hp depending on the run), so maybe there's something screwy with how my logger converts the information.

 

post up a log and ill take a look ... sometimes loggers like to change the formats and make my life hell

 

Thanks!

ECMLink is the software, running on a DSM ecu. I exported the log using the built in converter, and it is a 3rd gear pull. One thing to note is that the TPS signal reads 99, not 100...not sure if that last percentage is what is throwing this off, and I'm not literate enough in Excel to change the appropriate cells as a group to read 100 (one by one will take forever lol). If that's the problem, I'll recalibrate the TPS, make a run, and give this another shot.

 

TPS of 99% wont make a difference. It is smart enough to know that the 99% is WOT. Let me take a look at the log and figure this out.

 

The problem is that ECULink logs arent supported yet. They are showing up as AEM logs and those logs look for time to be in seconds and not milliseconds like this log. This is what is causing this problem.

 

Thanks for taking the time to look into this, Brad. If you ever get ECMLink logs integrated I'll be sure to support the cause

 

Hum ... may have to add it

 

When does the program start graphing a pull? Can it be setup to start graphing at a certain area manually in the program?
I have several pulls from 2k to 7k I would like to go over but when I open them they start around 6300 to 7k.

 

Send me your log as it sounds like something funny is going on. Probably with your TPS recording. Send me an unedited log. Ill PM you my email address.

 

sent

 

Brad, you're only supporting this because I jumped ship from GM and hp tuners. Haha.

 

Dang right Leafy!!!

 

ECMLink support would be great! Thanks!

 

To make sure I graph what I want, I typically trim my log file to only the run I'm interested in and then I manually make sure all of the cells for TPS are 100. I don't really use VDs built-in trimming.

For the ECMLink, use Excel to make a column in seconds. Graph away.

 

hornet ... dang son you like doing it the hard way. The trimming in VD is awesome!!!

You dont have to put them all to 100tps either as it is smart enough to look for the highest value and then include anything within 5% of that value.

Now if you have more than one pull per log file then yes you must separate them as VD assumes you have one run per log like you do on a normal dyno. (One run goes to one file there).