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:

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.

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.

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"

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.

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.

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

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum