Hahaha ... ummm maybe I should take that 30 minute 'screw with silicontek' timer out of it

What was it doing that wouldnt let you graph?

 

I think I found the problem and why it kept coming and going. Excel was fixing the file for me sometimes when I was cropping off 4th gear from my 3rd gear logs.

The logs are from OpenPort standalone, when there is a <time> value that doesn't include a decimal place the graph calculation pukes. I have attached an image of the same log plotted in VD twice, one time with raw format and the second plot using Excel to set the <time> column to Number format <1234.0>, one decimal place. After adding the .0 to any value that was previously a whole number the graphing starts working properly. For example, everytime you see a dip in the Raw Time graph there is a corresponding time value that is of the format 300 instead of 300.0. I mearly changed all the whole numbers to a decimal number to the tenth's place and it works fine. I will send you the logs via email that go with this plot.

So the problem seems to be with Excel and how it is resaving the CSV file. Once I resave a log back to CSV format it breaks until I go and format the column and resave. Winblows strikes again...

 

Good catch ill look at this.

 

Question:

Would it be beneficial to add timing and Knock data to VDR?

 

Knock can generally be seen by the timing being pulled. Plus knock doesn't affect the power curve, the timing changes do. So knock isn't really a necessity as long as you can see timing IMHO.

 

I would agree with that. Timing would be more beneficial than knock.

 

I could work on adding this but let me get 1.0.7 back together. Ive got the code torn to pieces changing up some things first.

 

1.0.7?



also can you change the TPS detection routine to pickup the LONGEST chunk of MAX(TPS) rather than all of them?

or just do the run's list like we said b4

good work otherwise :P

 

it should trim out all of the irrelevant data but it wont throw out any WOT sections as of now.

 

Randomly downloaded this program, works great - my friend was using it and we actually managed to diagnose his clutch slipping cuz of how high the torque gets lol

I use the WBO2 instead of the external wideband a/f ratio in evoscan; is it possible to have the program read this figure as the afr ratio?

 

sure send me a copy of the log so I can personally lay eyes on the column name and Ill add it in the next release. You can also put it in the custom column names in the options window.

 

well 1.0.7 is at the final beta tester. Hopefully it will get tested and back to me in a couple of days with the thumbs up.

 

Any news on 1.0.7? I've been looking forward to it.

 

Still waiting on beta testers to get back to me with their results. Just going through the normal process I go through with every release. I have cut off development on v7 and Im only going to fix bugs that beta testers send me. I am really pushing to get this out asap.

 

I didn't find anything new today Brad, did you get the last 3 screenshots I sent in email?