new $EE tuning thing!

[fbody_Brian]

ahh damn ill fix those indicators. try generating random data (see the advanced tab) and then jiggle the slider around, its a good test.

The version check had a few issues im working out. the qt network stack is a bit odd.

None of my green indicators are working, p/n tcc, a/c fans, etc.


I flashed the e-side a couple of times. It completes the flash in roughly 50 seconds!

If you generate random data, go to the analysis tab, move min timestamp to 0, click analyze, $EEHack crashes, Floating point exception (core dumped). Not that that's something people will be doing often.

I like the verbose debug window

Using monotonic reference clock.
EEHack Version 4.20
Built for : x86_64 Currently running : x86_64
Current OS : openSUSE Tumbleweed (20160111) (x86_64)
Fetched version from network.

[steveo]

I know what I've done wrong. suprised nobody using the beta noticed. it's that new font size junk, everything has display properties from a style sheet now, which I suppose overrides background colors.

the random data doesn't have a timestamp but it's not supposed to crash. I'll look into that.

[steveo]

beta 2 fixed that problem (yes i know one of the buttons is a different shade of grey..)

http://fbodytech.com/eehack-2/beta/

this adds all the t-side stuff, im pretty happy with the potential speed improvements. i'd love it if someone with a manual trans would test a flash write it to make sure their car still starts.

no more new features in this version, will release as soon as flash write is fully tested and im sure nothing breaks.

[jthompson122183]

using eehack4.2BETA2 had some errors when flashing. pcm is ok.

[steveo]

what kinda errors?

edit: just so you know, eehack's logs only record acquired engine data, they contain nothing about the flashing procedure.

[jthompson122183]

Attachment 10138 this is with just t and e side checked nothing else is checked.

[jthompson122183]

Attachment 10139 then this is with the t and e side checked plus the lower write latency checked. when i first tried with the lower latency checked it did this error twice on the t side plus had the error from the previous pic i posted.. so just for shits and giggles i did it again and it was only one error this time.



hold on a min and let me do some port setting investigation on my pc.