new $EE tuning thing!

[steveo]

That is a very good idea about the flat lines being at idle in park.

you misunderstand

the data flatlines when the logging stops

if you disconnect, that's dead time.. if you connect again 20 minutes later, your data shows up after 20 minutes of dead air in the graph. the very first record recorded in a session is considered 'timestamp zero'.

it's a side effect of doing time-domain graphing and logging instead of per-record, but that's just how it is.

at least it shows the user the reality of the situation, and the graphs are very good at zooming across hours of data.

it does mean that saving and clearing the log when you park is a good idea if you're going to leave eehack open

there may be a way to do an 'overview' graph to visualize the entire scope of data, or highlight dead sections by greying them out or something. i'll work on that later.

[fbody_Brian]

Thank you Steve and Brian for the hard work!

I can't take any credit for this, it's all steve. I'm just enjoying using the software and giving feedback.

I haven't had any issues loading older logs. I'll double check with the newest version though.

[troutdog311]

I did misunderstand and does explain the flat line. I just took a few quick 30 sec logs just to look with no data in the graph. It must be something on my end and I'll double check everything in the morning. If I'm the only one having this issue then no biggie. Attachment 10081

I am also running open loop no MAF. Edit: I did press Re-Plot and many things to get graph up but nothing.

[steveo]

I haven't had any issues loading older logs. I'll double check with the newest version though.

the log format is unchanged, since the first version that you could save logs with.

Edit: I did press Re-Plot and many things to get graph up but nothing.

your log is borked, man, look at your timestamp. no wonder it wont plot.

they're human readable, you can open the log in notepad and see what's up

edit: very old versions had issues stacking logs. if you stacked this log with an old version THEN saved it, that might explain what's up.

other than that, it must be some wacked out clock skew that did this? like maybe your system clock was set ahead by a few years while eehack was running?

[steveo]

eehack doesn't actually deal with negative clock skew well, i'll have to fix that.

like it's possible if your system clock goes back in time, it could wrap around to max time.

im fairly suprised eehack doesn't crash with that large of a timestamp

system clocks are really shitty as a time source especially when you have things like windows NTP client which just steps a clock wherever.. linux NTP will slowly drift the clock to the proper position so software doesn't break. i'll play with other clock sources in the future to avoid crap like this

[troutdog311]

I did notice the time stamp, this wasn't a stacked log and system clock is correct. Since the log format hasn't changed then it must be something on my end. I'll try a few things, no problem.

[steveo]

like i said open the log in a text editor (or send it to me)

the format is simply TIMESTAMP+DATADATADATADATA

[steveo]

eehack just failed to erase the ecm in my car.

im hoping it isn't a problem with old XP laptop, has anyone else tested the new version on an XP computer?

hoping the update to qt 5.5 didn't screw over xp users or something.

it might have just been time for that ECM to die, i did flash it a lot..

[fbody_Brian]

eehack just failed to erase the ecm in my car.

im hoping it isn't a problem with old XP laptop, has anyone else tested the new version on an XP computer?

hoping the update to qt 5.5 didn't screw over xp users or something.

it might have just been time for that ECM to die, i did flash it a lot..

My xp laptop has died. I can only test on 7 and nix.
But I haven't flashed in a while. Hoping that recent changes didn't mess up flashing. I'll have to do some flashing, but can't currently help you verify the xp issue.

Is it bricked?

[steveo]

yeah it's dead.

the only recent changes have been a QT upgrade which may have changed timer behavior, but the weird thing is flash read worked just fine, write worked just fine, but erase threw a fit.

i know other people have been flashing with 4.0 with success so i think my ECM just finally died. looking back, i had flashed it many hundreds of times.

[jthompson122183]

You need to patch it in the datastream to show up. It is at byte_11e
Can you add the aldl data in the modified xdf you are working on. I will really appreciate it.

Well I have no problem adding that in , but I'm not sure which values need changed and to what.

[kur4o]

Here is the list of ALDL mode 1 msg 0 to 6.

You can label it mode1 msg ?? command
and mode1 msg ?? memory location.

In your case:
The most used mode is mode1 msg0 [It is the main mode for most known dataloggers]
If you want to add other known memory byte to the stream, pick one of the existing that you don`t need in the data stream and change the memory location value to the to 011e.
When the PCM is flashed with new data You need to add the corresponding information to the logger programm so that it knows that at that byte now is 011e memory byte.

[fbody_Brian]

Congratulations Steveo

You have managed to make an app that flashes LT1 PCMs natively under linux.



Flashing worked for me, no errors, everything went perfectly. The app looked just like the win version during the flash, going full screen, etc.

all I can really say is HELL YEAH!!!

[jthompson122183]

had a error after flashing. attached a log. it'll need unzip Attachment 10093
using 4.0 release

[zebdeming]

Hey Steve, just wanted to give out a big thanks! I haven't had much time to play with this, but I did successfully download my .bin and flash the modified .bin using this yesterday. No problems to speak of. Will be playing with this much more soon.

Zeb