Maybe something was wrong with my log we will never know because I deleted the 3000 useless lines and saved the .csv with only the 100tps measures sorry

On my first few logs I checked every box that seeemed to read something and when doing my run in 4th gear I ended up with :
around 2-3 measures per second = 35 lines at 100% tps between 1656-7781rpm
I had a good 10minutes of log like that and virtual dyno auto-trimmed the cruising without problems.

so I tried deselecting everything else thand TPS-speed-rpms and had :
around 43 measures per second = 506 lines at 100% tps between 1906-7500rpm
With this log the auto-trim wasn't working.
Evoscan seems to be over-logging when you have almost nothing checked because I have 2-6x the same rpm values, on those 506 lines maybe 200 are useful.

edit : thanks for the reply Brad, no need to waste your time on this, I'm sure you have more important things to do and I don't have the "bugged" log anymore

 

anyone having a perceived problem with vd should zip their log file up and attach it to their post along with the pertinent details about their car
year
model
transmission
gear
weight with passengers/items

 

Thats a great idea!!! Welcome back to this thread Mellon!!!!

 

I never left buddy, just lurking

 

What coud be the problem ?!

here is my log

The problem :



and my settings :



Woud someone please check it ? I tried everything but not working..

 

I think deleting all the unneeded custom column names in the options menu will fix your problem. but thats just a guess.

 

no succes someone coud post a working ?

 

I see some TPS values over 100 which are invalid, it could be picking those up


example from your log:

 

in open office i didnt see TPS value over 100 :O

 

If you open this file up in notepad you will see the problem. The values it records uses commas for decimal points. Its causing havoc in my CSV (comma seperated values) file reader.

Id bet these are the issues. Commas are used to seperate the columns in each row, and when data has commas in them it throws this all off.

Mellon:
I saw that too, I know one thing for sure, its not TPS. That would also cause havoc with my program if you have TPS trimming on and you are logging garbage in the TPS column.

 

I just set the appropriate tire height and set the smoothing to 1 and it seemed to be within 10hp/tq.

I did notice that the first calculation seemed to differ about 30hp from what I expect. But if I set the smoothing it straightens out.

For instance if I load the log and set the tire height it will show 340hp at 1 smoothing. if I set the smoothing to 2 it will go to 29Xhp, I set it back to 1 and it's at about 310 which is pretty close to the MD.

Good luck keep up the hard work. What language was this written in? I'm a programmer, just curious .

 

The smoothing makes a difference in that it gets rid of the humps in the graph. If you were to see 0 smoothing you would be thankful for smoothing its VERY bumpy to say the least.

Its written in C#. Its a straight .NET app (.NET 3.5).

 

Yeah 0 smoothing reminds me of shark teeh

ahhh good ol C# I started studying C# to build a game. I caught on pretty quick because it's similar to Java. But I lost interest.

 

Ive been writing in C# since the language/framework was in beta

 

Very impressive sir. I'm still an amateur when it comes to compiled languages. I do mainly web based work / server administration. So everything past that is a hobby.