Guess this would be considered a bug.. I tried to open that log the other guy posted and I'm getting that error of course thought maybe it was his machine.. Now no log will open on mine same error even after a full un-install removal of all xml files.. Does the software write to the registry as well? If so what HKEY?

 

No registry entries. Only the xml files.

What 'log the other guy posted'? What error exactly did you get, and all you did was load it? Just trying to get to the bottom of this problem and find what the culprit is (program or not).

 

The guy that posted the evoscan log that had the TPS trimm error. I just opened it up and got the error. All data has been trimmed out. I removed the entire program re-installed and got the same error when opening my own log.

 

Don - Have you finished your tune and where are you power wise ?

 

Guess that's a matter of who you ask haha.. According to tuner 42x.. According to virtual dyno with same log 370ish.. But right after you and tephra helped me find the problem it did 432 w/ a 1.10 correction factor smoothing 2. Ever since then it's been downhill.. I made it a point to show him that too..

http://www.whendarknessfalls.org/evo/compare.jpg

You can see the drop there.. Green line was right after we fixed it and you can see the pattern after that.. I figured I may as well let him finish what he started.. Thankfully for me I saved all my logs and maps so if I wanted to go back and work off the other I can..

To the OP I tried to open another log and it opened just fine.. It appears to be certain logs that it causes the problem.. I'll check tonight which one it was and send you a link to it.

 

Well if I am reading your Green data correctly - it looks like your boost is ~28psi at 7000+ rpm, so we have solved that issue. From your previous posts on timing, your timing seemed REALLY low in the upper range (I believe 10 * at redline if my memory is right)....Try adding 1 - 2 degrees from 5500 up until your car starts knocking....Make sure you keep AFRs good too....I believe that most 8's w/ Reds on 93 should be somewhere north of 20* at redline (but you'll have to do some research and testing)...

Also, with your cams, you should have a MUCH better top end .....My guess you'll be north of 460 whp and your hp curve will be much broader/better when you get this resolved.

 

This is not an error. This is when you have selected a TPS value that is higher than all the TPS values in your log, therefore trimming out the entire log. This was just put in there to let you know that has happened.

 

Brad Barnhill ftw !!!!!!!!!!

 

Thanks Gary. Glad you love the program. Its got its quirks but we are getting those slowly but surely worked out.

 

hi mate, how's the new version comming along?

I'd recommend releasing it without fixing the bug i mentioned (with my previous log loading incorrect) and just have that bug as a known issue.

 

rnbguy:

The new version is getting close. I am just taking my time and there are a few other little features and bugs to fix. I try not to put the next version out right on top of the previous version so it gives me time to fix a list of bugs and add some new functionality. The new version changes the whole smoothing functionality. From first reports it looks like the betas really like it better. It tends to smooth out those rough graphs a little more. We lost a little resolution but I think its probably best for the end result we are looking for. Its shaping up to be a good release. Im just trying to fix some of the small issues that cropped up after v5 release. v5 was a BIG release so it was expected to have some issues. v6 is a smaller release but it has some major upgrades in it too. I hope v5 is usable till I can get v6 out. It should be done in a few days but I want to make sure my betas are happy before I release it. It just keeps even more bugs out of your version for me to listen to them and fix what they say. We are having a disagreement right now on a point and Im afraid Im going to have to just put my foot down on one side of the fence and say this is how its going to be. Dang was that wordy?

The 'bug' you mentioned is not really a bug ... its just a warning to let you know that you have selected a TPS value in the settings that is higher than all the ones in your log and that all the values are trimmed out so you know to lower that value in your settings. Otherwise without a message you would have no graph and not know why Thanks for paying attention to detail and reporting it though. If you think the wording of that message should be changed to read differently, or you think its misleading let me know. (Im not an english major hahaha).

 

sounds good i look forward to it. With regards to the bug i mentioned, it's not that it says the TPS message, that was another poster, the one I mentioned was it just loads dots with my previously pasted log, even with no TPS trimming and the log does have 100 TPS

 

If that is the case get me the log and let me know what car settings you used and Ill recreate it here in the development environment and try to find the problem. There is one bug that if there is a 'erroneous' record at the bottom of the file ( I dont know how else to describe it ) then it will throw an error. I plan on fixing that. I wish evoscan wouldnt put those weird ending records in there every now and then.

 

Hope this hasnt been asked before but Can I use the Evo8 GSR setting for an Evo 7 GSR?

 

The program uses those settings to calculate HP and TQ ... make sure the weight, tire diameter it populates are what match your car. Then you should be fine.