EEHack 2019 update

[spfautsch]

kur4o made quite a few changes, his program is a fork, not an update.
...
i'll be updating the official eehack only

No worries.

have you tried simply modifying the definition file? (totally untested but might work)

As in adding a multiplier to the field i.e. 0.068027211? Doesn't seem to have any effect when I look at a datalog.

i'll think about adding a switch in preferences like i did for metric/imperial.

That, or an option in the wideband config to allow the user to directly modify the conversion formula. Or just a preset with N / 2.50.

Thinking about this makes me curious how the target afr is derived. That's a patch no?

[steveo]

No worries.



As in adding a multiplier to the field i.e. 0.068027211? Doesn't seem to have any effect when I look at a datalog.



That, or an option in the wideband config to allow the user to directly modify the conversion formula. Or just a preset with N / 2.50.

Thinking about this makes me curious how the target afr is derived. That's a patch no?

the target AFR is a patch, yeah. kur4o found out where in memory it was being stored and i modified the factory datastream over something useless (actually it's for the rarely-implemented EGR position, but no dataloggers ever read that anyway)

[spfautsch]

the target AFR is a patch, yeah. kur4o found out where in memory it was being stored and i modified the factory datastream

Curious, does the patch do something different to plug 14.7:1 in when in closed loop or is it simply reading the same target AFR byte from memory? The reason I ask is b/c I'm likely going to change the closed loop AFR (along with all the base AFR tables) in the tune to match the fuel.

[steveo]

nope it just reads the byte from memory

if you change the target it should read properly

[kur4o]

Some of the most annoying stuff I have found, that might get better.

Opening multiple log files or importing them. Now it is one by one.
Remember some of the settings. Com port, Log folder, Bin folder.


AFR target will affect only the trims. Pcm will remove more fuel, since it gets its data from 02s sensors and finds the fuel stoich from them. Bad news is that the stoich of etanol blended fuel is not the stoich the 02s are set for and at 14.2 they will be deep into the rich side. The 02s can read reliable only at 14.7 which will be around 0.454mv.
At 14.2 you will be at 0.700 range.

The afr target read by the patch is the afr target the pcm is currently using. At closed loop it is always 14.7. At open loop it gets it from the OPEN loop AFR table.
At power enrichment it is percentage taken from the closed loop target. If you change the closed loop target you will have to fix the PE tables also.

[lionelhutz]

Bad news is that the stoich of etanol blended fuel is not the stoich the 02s are set for and at 14.2 they will be deep into the rich side. The 02s can read reliable only at 14.7 which will be around 0.454mv.
At 14.2 you will be at 0.700 range.

O2 sensors read rich/lean or above/below stoichiometric. They have no clue what the fuel is and will switch at stoichiometric no matter what AFR stoichiometric occurs at. Used on E85 they would switch above and below .45V at around 9.7AFR just like they do it at 14.7AFR for straight gasoline.

That's why you often hear of lambda. If you set the AFR meter to display lambda then you always have the perfect AFR when lambda is 1. A lambda around 0.9 is a good place to begin for power enrichment.

If you set the AFR meter to display 14.7AFR when lambda=1 then you have the "perfect" stoichiometric fuel ratio when the meter displays 14.7 for straight gas, E10, E85 or any other fuel mix and it would be wrong to try to tune so the meter displays the proper AFR for the fuel in use.

[spfautsch]

kur4o, I love you like a brother, but you just made my central nervous system segfault.

AFR target will affect only the trims. Pcm will remove more fuel, since it gets its data from 02s sensors and finds the fuel stoich from them.

This is essentially a true statement. Oxygen sensors tell the ecu when the combustion process is at stoich. Stoich = 0.454v. Agreed?

Bad news is that the stoich of etanol blended fuel is not the stoich the 02s are set for and at 14.2 they will be deep into the rich side. The 02s can read reliable only at 14.7 which will be around 0.454mv.

I think this statement is a bit misguided.

A nernst cell a.k.a. oxygen sensor measures the concentration of oxygen in relation to the other gases in the exhaust stream. Stoichiometric combustion is stoichiometric combustion, whether you're burning nitromethane, methanol, ethanol, gasonline (aka iso-octane), gasoline-ethanol blends, or even coal. It identifies the complete conversion of all the carbon, hydrogen and sulfur components into their fully oxidized counterparts (CO2, H2O, SO2).

At 14.2 you will be at 0.700 range.

That statement is true if and only if the fuel being burned is pure iso-octane. However, if the fuel being burned is a blend of approximately 10% of oxygen carrying ethanol and 90% iso-octane a.k.a gasoline, at roughly 14.2:1 air to fuel you should still be at 0.454v because that's stoich for the mixture of fuel(s) being burned. Now I will concede that this isn't an accurate description of what pump gas is generally composed of, but that's a subject for a whole other discussion. Additives have their own stoichiometry, some of which are quite far from what we'd commonly consider to be a fuel-like substance.

The afr target read by the patch is the afr target the pcm is currently using. At closed loop it is always 14.7.

I would hope at closed loop it is at whatever values are stored in the "stoich afr target" table.

At power enrichment it is percentage taken from the closed loop target. If you change the closed loop target you will have to fix the PE tables also.

Yes, that's a beautifully correct assessment. In that statement you can replace the word "percentage" with "lambda". Which is a measure of how far from stoich the combustion process is.

[steveo]

Some of the most annoying stuff I have found, that might get better.
Opening multiple log files or importing them. Now it is one by one.
Remember some of the settings. Com port, Log folder, Bin folder.

damn i was sure i made it so you could drag/drop logs onto the dashboard window, and select multiple files in the log loading window. maybe i'm thinking of trimalyzer. that'll be an easy fix.

com port should always be remembered, i thought the log folder and bin folder was too, i'll have to check into that

[steveo]

kur4o i lost the thread where we discussed the timer that's preventing flash from working, what did you say, was it 10 seconds since last ECM reset?

[hbomb2k]

Maybe this is a bug that needs to be fixed for the 2019 update ??? Or maybe I am just a noob.

I am a new tuner and I have really been looking forward to getting into the EEHack and getting to work. Unfortunately I have an error.

Here is my log:

EEHack Version 4.70
Current OS : Windows 10
Built with THROTTLE_MS=2
Opened serial port COM7 Description USB Serial Port MFR FTDI
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet

Not very experienced with serial communication protocol so I don't really have much to add.

Other than that my cable works perfect with Scan9495

Really excited to get into tuning but I really need a hand figuring this out. Thank you all.

[roachjuice]

I’ll definitely download this and give it a shot! I love EEHACK!

[rharris]

Hi Steve,

I am new to the eehack program and apparently new to this computer. From what I see so far it looks like a master piece for LT1 owners, thank you! I have loaded the program on my computer but it will not run, the program does not recognize the USB port. The cable was recently purchased from OBD diagnosics for my application. I have a 1994 corvette so it is a unique cable with a USB port, not a seriel port connection. The program comes up but when I try to connect it gives me an error. The program does not recognize the serial port and gives none as an option in settings. I am retired and left the computer world years ago so please make it simple. What am I doing wrong?

Thank you,
Rich Harris

[kur4o]

Hi Steve,

I am new to the eehack program and apparently new to this computer. From what I see so far it looks like a master piece for LT1 owners, thank you! I have loaded the program on my computer but it will not run, the program does not recognize the USB port. The cable was recently purchased from OBD diagnosics for my application. I have a 1994 corvette so it is a unique cable with a USB port, not a seriel port connection. The program comes up but when I try to connect it gives me an error. The program does not recognize the serial port and gives none as an option in settings. I am retired and left the computer world years ago so please make it simple. What am I doing wrong?

Thank you,
Rich Harris

Start troublshooting with the most obvious. Check if the device is installed properly. Open device manager and see if there are any available com ports. If non are present it might be a driver issue.

[NomakeWan]

Hi Steve,

I am new to the eehack program and apparently new to this computer. From what I see so far it looks like a master piece for LT1 owners, thank you! I have loaded the program on my computer but it will not run, the program does not recognize the USB port. The cable was recently purchased from OBD diagnosics for my application. I have a 1994 corvette so it is a unique cable with a USB port, not a seriel port connection. The program comes up but when I try to connect it gives me an error. The program does not recognize the serial port and gives none as an option in settings. I am retired and left the computer world years ago so please make it simple. What am I doing wrong?

Thank you,
Rich Harris

What kur4o said is correct. The most likely answer is that you do not have the correct driver for the cable. The cable is intended to use FTDI's VCP (Virtual COM Port) driver. If your system mistakenly installed a non-VCP driver (such as a D2XX driver), that means it's not exposing a COM Port to the system, which means $EEhack won't see it either. Please make sure you're using the latest VCP driver from FTDI, which can be found here: https://www.ftdichip.com/Drivers/VCP.htm


steveo,
I would've noticed the bug in 4.70 had either of my cars been patched, but as you recall the whole comms error thing on my '94 had me too spooked to use the flashing function in $EEhack. It was only once those problems started getting ironed out that I had enough confidence to try it on the '95, which led to finding the bug. I did go ahead and get a log for you on 4.70 regardless, and indeed, it works fine (except the analyzer, as you found out). I also noticed the message selection thing when testing graphing, but I guess I never spotted it in 4.8.2. That's my bad. I've attached the log just for completion's sake.

To be honest the only non-bug-related suggestions I could provide for features would be potentially rolling real-time analysis in, and having patches be individually selectable (for instance, if I want speedlog but not E-side comms). By real-time analysis I mean something like what tuning suites like Crome or Hondata have, where you can sit on a dyno with the laptop plugged in and work through your cells by changing throttle and load and watching the O2s. The Analyzer/Trimalyzer do this after the fact once data is collected, but I wonder if there's a way to have a realtime graphical representation so that you know when you have sufficient data collected to make cell adjustments?

Just thinking out loud. As I've said tons of times before, I love this program even as it is. :)

[steveo]

i could do realtime analysis but id rather you just hit the analyze button. it will work with the car running wont it? imo real tuning either happens at home sitting at a desk studying the data......or with an emulator