PDA

View Full Version : Display Freaking Out



dbaxter_ss
April 30th, 2005, 07:14 AM
Using version 7.1.10 - 225/364

Open after reboot, everything is fine: load a second log file and display freaks out.

I completely uninstalled and reinstalled this rev and same behavior.

Though maybe it was the calc pids, but that does not seem to be it. Once it goes bonkers even stopping and restarting EFI Scanner appears to not resolve the issue.

Loading previous version not to check.

http://www.purplegto.com/files/weird_display.PNG

dbaxter_ss
April 30th, 2005, 07:20 AM
New info:
Killed the process tree, not just the process.

Loaded up several times old log file from about a month ago, several in a row without a problem

then loaded up log files from this week with new revision and POOF, same display issue?

Dirk Diggler
April 30th, 2005, 08:46 AM
try the latest version and see if that cures the problem

John Skiba
April 30th, 2005, 08:54 AM
I've had this happen as well on my laptop

SS2win
April 30th, 2005, 09:20 AM
have you checked to see if there is a video driver update? Might be related.

dbaxter_ss
April 30th, 2005, 10:10 AM
I have the latest version, just downloaded. No luck.

Definitely not a driver problem. I can load up the previous logs ( not using the latest revision ) just fine.

Ok I just went through and checked one more time
ALL Logs after the 25th are not coming up, they look like the display above.

I can open up all logs previous without issue. Also the log file name vin is X'ed out at the end. I did not change this, it changed with the new rev I installed.

again. this is build 7.1.10 build 225/364 odbii.

Blacky
April 30th, 2005, 10:20 AM
It won't be anything wrong with the PC/drivers etc.
It is a bug in 7.1.10.
It is fixed in 7.2

Paul

dbaxter_ss
April 30th, 2005, 11:00 AM
Sweet, yah just gotta love service like this.

:D

GMPX
April 30th, 2005, 11:18 AM
I think it looks kinda cool!! :wink:
I thought it was a 4hr log set to display the entire log on the screen :)

Cheers,
Ross

Blacky
April 30th, 2005, 02:59 PM
It is a problem with the number of defined channels in the log file's meta data not matching the number of data channels that were saved in the log file.
That shifted each frame by two bytes for the entire file. Which makes the data look incredibly corrupt. It is fixed and will be available in the next release.

Just so I am 100% clear on version numbers:
Which version of EFILive was used to create the two files that you sent me?

Regards
Paul

dbaxter_ss
May 1st, 2005, 02:15 AM
Created with:
17,145,943 EFILiveV7110_225_215_Setup.exe

Still see on:
17,175,127 EFILiveV720_227_217_Setup.exe

dbaxter_ss
May 1st, 2005, 03:56 AM
Ok
Found it, although I didn't do it :D

They are NOTES??

just going through everything, figured instead of looking at the charts, lets just look at it through gages. Well when I hit run I say "NOTE 1,2, NOTE 4,5 etc. Knowing I didn't NOTE anything on these logs I then went into the charts again and saw under Dashboard - delete note:
So I did, and 1 of the lines went away. I attempted to clear a big selected bunch but that didn't work.

But I at least found it :D

dbaxter_ss
May 1st, 2005, 11:41 PM
After getting the latest patch from Paul, and it repaired some of my log files ( weird ) I found out it was MY FAULT :(

I have a calc_pids.txt with

*CLC-01-999
% 0.00 25.00 .2 "({SAE.LONGFT1}+{SAE.LONGFT2})/2"

And

CALC.LTAVG F601 CLC-01-999 % Fuel "Long Term Average"

If I rem this out completely or use the untouched default one everything works.

If I change this to the below everything works. I take it CLC-01-XXX you can only use CLC-00?? Although that’s pretty obvious now, 00 must be used.

Yah this is a dumb thing on my part.

*CLC-00-999
% 0.00 25.00 .2 "({SAE.LONGFT1}+{SAE.LONGFT2})/2"

And

CALC.LTAVG F601 CLC-00-999 % Fuel "Long Term Average"

So for you guys who like to make calc pids -
Make sure the 00 part is 00, after telling Paul he let me know that is a BYTE COUNT, NOT an IDENTIFIER.

Cool huh :D

Blacky
May 2nd, 2005, 12:07 AM
After getting the latest patch from Paul, and it repaired some of my log files ( weird ) I found out it was MY FAULT :(

No, not your fault, it is critical that the calculated PID SLOTS are CLC.00.xxx and there is no validation on them. My bad :(

By the way, thanks for tracking down the cause of the problem. I don't think I would have found it easily.

Paul

joecar
May 2nd, 2005, 12:20 PM
Looks like art... frame it it and hang it on the wall.
:D