Recognising An OLV Crash - Please Report These

OpenLogViewer is a cross-platform data log viewing application originally written by Gufi and new developed and maintained by Ben and Fred. Discuss all things OLV here!
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Recognising An OLV Crash - Please Report These

Post by Fred »

If something goes wrong with OLV it will output a stack trace or some other message in the console. If you don't start it from the console you don't have access to that information, so for the time being, please launch it from a CMD or Bash window of some sort.

If something goes wrong with a decoder you'll get this:

Image

Or something similar. If you see this, please report it, preferably with the log file, a set of actions leading to it, and the text from the console.

If you don't report bugs, we can't fix them! :-)

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Peter
LQFP144 - On Top Of The Game
Posts: 268
Joined: Tue Dec 27, 2011 5:37 am

Re: Recognising An OLV Crash - Please Report These

Post by Peter »

Fred wrote:please launch it from a CMD or Bash window of some sort
Sorry, I'm a lazy double click windows user.

I opened the OLV by double clicking it on the desktop, File->Open->JSeriesFeb24rdTuning.bin waited a little bit for it to load and then when it showed me the Graphing Option Pane I pulled EGO down to be graphed. Then it kinda froze, and ended up displaying this.
Attachments
JSeriesFeb24rdTuning.zip
(2.39 MiB) Downloaded 909 times
OLVcrash.png
:-p
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Fred »

Fair enough, I might add a force console option to the jar, if I can do it in a platform independent way.

Re your "crash" what were the symptoms? No response from anything? Did you try closing the "graphing option pane" and reopening it or could you not even do that? There wasn't a "do you want to grant this app permission to do something" window in the background was there? Which version was this exactly? The last release or current from source? If it was the last release, please get the latest. If it was from source, please provide a hash to go with this report. Also, if you don't launch with a console, any stack traces are not visible and there is absolutely no way to diagnose what happened.

Hope that helps a little :-)

BTW, it's easy to get JDK + Maven3 on a win box so you can run the latest by typing "git pull;mvn"
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Peter
LQFP144 - On Top Of The Game
Posts: 268
Joined: Tue Dec 27, 2011 5:37 am

Re: Recognising An OLV Crash - Please Report These

Post by Peter »

I didn't try closing the graphing option pane. It still let me drag the boxes around in it so I assume it would have opened and closed. I have the security thing that asks you if you trust this program turned off on this computer. It is version 0.0.2, the latest release. I can get it to do it consistently if the graphing pane is already open from a previous log and I don't let it finish loading a new log before I drag one of the boxes down to be graphed, but that's not what I did the first time. Pretty similar error though.
:-p
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Fred »

If you can install msysgit and maven and run the latest from source and duplicate the error, that would be useful. It's probably/possibly still happening in the latest and it sounds like you know how to generate the conditions. One thing, though, there are known issues with loading second files in terms of memory usage, so it's unlikely to work well for you. Having said that, I do it a lot and suffer no ill effects, so mileage may vary, and may be good.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
User avatar
Kennybug
QFP80 - Contributor
Posts: 79
Joined: Sat Mar 31, 2012 6:01 pm
Location: Hong Kong
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Kennybug »

OLV log files not displayed correctly in Win32.

My setup in office computer:
WinXP 32 bit with JDK1.7 & maven3

OLV plugin is latest from Ben's GIT with POM fixed 11 days ago

Installation and compile of OLV is smooth without error.
Only one issue is I use mirror on repo1 server (it seems repo server is dead)

All bin, csv files can be loaded correctly. The log is able to run and stop.

But there is no log graphics on display. (or the graph displayed in black color only)
I have changed the color pane and setup. There is still no trace graphic at all.
:indiff:

Then i had tried Fred's GIT version, but it got the same issue.
Attachments
olv.jpg
olv2.jpg
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Fred »

Hey Kenny,

That's probably not a bug, your data is probably corrupt. Take the data file and run it through the freeemsParser.c file (after compiling it) and compare the output, it will match OLV almost exactly.

How have you recorded this data? You need to use a reliable program with the correct settings or you'll just record garbage.

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Fred »

BTW, I've got a man writing a tiny utility so that you can verify that OLV is working properly. It'll be something like this:

Double click application
Type in file name of log
Find output.txt file
Open output.txt file
Copy contents
Paste into forum
Be happy :-)

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
User avatar
Kennybug
QFP80 - Contributor
Posts: 79
Joined: Sat Mar 31, 2012 6:01 pm
Location: Hong Kong
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Kennybug »

fred, thanks. will try to run the C program.
I still not get any running engine
My log is from pete:
viewtopic.php?f=62&t=1533&hilit=maven&start=20

I have try another csv file from hot cat, it was a clean csv table. it also not working.
viewtopic.php?f=32&t=1604&p=24413

I think it may due to the latest jdk 1.7.0_u04

will get OLV run on debian & OS X tonite for double check :P
User avatar
Fred
Moderator
Posts: 15431
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: Recognising An OLV Crash - Please Report These

Post by Fred »

Try this one: http://stuff.fredcooke.com/forMal.bin

The firmware and OLV versions have to match or it will just reject them. Look at your console for info. The above linked file should work with the latest OLV from all three repos. The hash is: c43d3f8e796e8a4e80c42668ce51c380eac473fd

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Post Reply