malcom2073's EMStudio development thread. (Comments welcome)

[malcom2073]

First of all nice work Malcom!

I have just installed EMStudio on one of my machines but it no work
I get an error message: Something has gone serious wrong, one of the commands timed out during interrogation. This should be properly investigated before continuing.

OS: Windows 7 Ultimate, 32bit.
Hardware : Laptop

What other information can help with a solution?

Wickey
Preston.

Thanks!

My guess would be that you are running an older firmware. EMStudio is set up to work with the newest firmware. You can upload the .bin and .meta.json log files from the emstudio directory and it will show us where it failed.

[Fred]

Ahh, the data mismatch stuff, I guess, cool! :-) I'll get him an up-to-date hacked firmware for the car.

If you don't already, Mike, you need to display all of the exact details of the mismatch such that people can make it work without help, if they understand what they're doing.

Fred.

[malcom2073]

Ahh, the data mismatch stuff, I guess, cool! I'll get him an up-to-date hacked firmware for the car.

If you don't already, Mike, you need to display all of the exact details of the mismatch such that people can make it work without help, if they understand what they're doing.

Fred.

It's currently hardcoded to send a certain set of commands, like firmware version, OS version, build date, etc. If the firmware dosen't handle that, it dies.

[Fred]

None of that stuff has changed since Presto's firmware. Things that have changed are data block sizes, number, metadata correctness, etc.

Dying is fine, and good, but it should fail slow and report everything it can about what it found as a diagnostic rather than leaving the user wasting your time and mine on the forum like this ;-)

A step by step of what's happening might be cool too in a sort of console window while loading. MTX does that and I quite like it. Much like Linux booting up without a splash screen.

Checking xyz... OK.
Checking abc... OK.

Requesting version... "blah", OK.

or whatever.

Fred.

[Fred]

If they were coloured, green for good, red for bad, plain for info/incomplete or whatever, that might be nice.

[Preston]

Dan the Man! I have been observing from a far.... but never gone!

Malcom,

Actually the error occurred with the hotel connected and without.
After starting the app the error message comes up before a connection is made.

If there is some sort of error log report I can run I will.

Preston.

[malcom2073]

Dan the Man! I have been observing from a far.... but never gone!

Malcom,

Actually the error occurred with the hotel connected and without.
After starting the app the error message comes up before a connection is made.

If there is some sort of error log report I can run I will.

Preston.

Can you upload the .bin and .meta.json log files from the emstudio directory?

Also, if it does the same thing both with and without the ECU connected, I'd guess that perhaps it's pointing at the wrong com port? If you're on linux, and have it pointing to a pty, that can cause that issue.

None of that stuff has changed since Presto's firmware. Things that have changed are data block sizes, number, metadata correctness, etc.

Dying is fine, and good, but it should fail slow and report everything it can about what it found as a diagnostic rather than leaving the user wasting your time and mine on the forum like this

A step by step of what's happening might be cool too in a sort of console window while loading. MTX does that and I quite like it. Much like Linux booting up without a splash screen.

Checking xyz... OK.
Checking abc... OK.

Requesting version... "blah", OK.

or whatever.

Fred.

Good idea, I'll implement a kind of list view in the interrogation progress window to show at what point it's currently running.

[Fred]

Sweet! Can we get much more specific with the serial fails too? "No such device" for something that doesn't exist? "no default data stream" for a typical ecu dumping log packets to identify wrong ports? and/or "no reply to any/all interrogation requests" >> wrong device and/or wrong speed/wrong parity/wrong something, perhaps make some suggestions, where you can.

In the console thingy

Successfully opened port XYZ (or not)

Just more ideas, the reality could vary. In any case, whatever info you have, to distinguish different types of fails, it should be passed up to the user in the best way possible, not swallowed.

Fred.

[Preston]

Can you upload the .bin and .meta.json log files from the emstudio directory?

Are .bin and .meta.json log files created on a winblows install?

Also, if it does the same thing both with and without the ECU connected, I'd guess that perhaps it's pointing at the wrong com port?

I checked the COM port in winblows and it is correct (COM1) I'm using this laptop as it has a built in serial port to eliminate any adapter issues.

If you're on linux, and have it pointing to a pty, that can cause that issue.

Testing is what I'm here for, so I grabbed one my other laptops that's loaded with Debian and attempted a install of EMStudio, but failed at that also, I see there is information on installs for poobuntu.... any chance some info on whats needed to build this on Debian.

Dying is fine, and good, but it should fail slow and report everything it can about what it found as a diagnostic rather than leaving the user wasting your time and mine on the forum like this

A step by step of what's happening might be cool too in a sort of console window while loading. MTX does that and I quite like it. Much like Linux booting up without a splash screen.

Checking xyz... OK.
Checking abc... OK.

Requesting version... "blah", OK.

or whatever.

Fred.

I second that... I have no idea if it's me being a retard (highly likely) or just a software issue.

Also I have noticed that when I open EMStudio the lower and right hand side of app is off the screen.
If I select edit --> settings : the window has to be stretched to show the buttons.
I will try and get some screen shots and upload them shortly.

Preston.

[Fred]

Deb is same as ucuntu, but both need to be pretty new or they won't have required libs.

None of the windows behave nicely re sizes.