new $EE tuning thing!

[fbody_Brian]

Just wanted to drop in here and say thanks again.
I compiled the latest version on linux. Seems to work fine, no issues to report as of now.
Haven't been doing much with the car because driving without 3rd and 4th gear puts a damper on things.
Got a new transmission in and ready to drive this thing!

[troutdog311]

Thanks again for the great work Steveo and others that put in work. Still use it almost every time I drive the car. I wanted to add that I ended up getting the PLX DM-6 Touchscreen + SM-AFR Wideband combo kit. I used Pin D27 and Innovative config tab in EEHack. After fully warm it's only about 0.5 lower than gauge though at times dead on as far as I can tell. The WB gauge is more steady than on EE that changes more rapidly. Not complaining just talking. Why didn't I buy a WB a long time ago. Probably one of the most useful things I've installed but EEHack is by far the most useful. The WB really does let me see exactly where I need adjusting.
Had about 60 errors today while flashing during the write period but double checked the bin after this and it had written everything needed. I was sweating buckshot because I just bricked my last one last month due to the battery literally took a crap in the middle of a flash. I will be connecting the charger for now on. Thanks again for everything!

[steveo]

widebands usually reduce sample rate by averaging internally, while their analog outputs are real-time, but the average of the analog output should be similar to what the gauge displays (this is why eehack has a smoothing option for the wideband in its settings)...

[spfautsch]

Per our discussion in the trimalyzer thread, can you speculate why eehack isn't discarding trashed frames?

Am I correct to assume that's what's supposed to happen here in aldl_read_reply()?

  // look for bad checksum
  if(checksum_test() == false) {
    serial_error_occurred();
    pkt_fail_counter++;
    return 0;
  }

Here are three adjacent frames from a log taken this morning. Note how knock count "jumps" in the middle. This one is actually pretty subtle but I've found frames like this where VSS will be 255mph and there are three or four trouble codes, MAF reading 400g/s, etc.

frame-37168.png
frame-37169.png
frame-37170.png

This is by no means a huge problem, but I've been chasing my tail on false knock and the huge knock events these generate make it really hard to see the "real" false knock.

BTW, I have some patches I want to send you relevant to the knock scope that adds the timestamp to the tool tip bubble. Will try to push to git today.

[steveo]

the only explanation is that the checksum is correct. so either you have a/d or whatever noise causing an actual blip or there's a bug of some kind in the ecm itself?

[spfautsch]

Blip? Bug? In the 90s we called stuff we didn't understand a "glitch".

It's simple to filter these out in trimalyzer b/c I just compare knock count from the last, current, and next frame and drop the frame if it "bumps" as in the example.

[Casey96SS]

Hi Guys! Trying to get EEHack to work with my Wideband. It seems that the wideband is causing interference with the serial connection.

I am getting the error in EEHack "SERIAL: ECHO CORRUPT! (bad serial interface?)

I am running an AEM wideband powered by the aux power wires by the shifter in my Camaro. Also using a Red Devil River cable if that matters.

EEHack connects fine if I disconnect the power to the wideband gauge. The gauge also causes an issue with Winflash too. It will only read or flash if I disconnect the gauge. Datamaster works fine with the gauge connected.

The only two things I can think of trying are powering the gauge from somewhere else or maybe a different cable. Any suggestions? Thanks!