Bringing TBI and Multi Port Fuel Injection to a New Level.     EFI Conversions and Tuning! Seattle to Portland! E-mail Tuning Consultant!
Page 3 of 9 FirstFirst 12345678 ... LastLast
Results 31 to 45 of 133

Thread: EEHack 2019 update

  1. #31

  2. #32
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Quote Originally Posted by kur4o View Post
    It is there a green button labelled SD mode between fuel and spark controls. If you are running speed density it will be labelled MAF mode.
    I'm not seeing it so I'll have to sift through the code and see what's up, maybe I have an older source tree. I'm hoping to get my ve tables remapped over the weekend so that would be very useful.

    I was going to beg steveo to include that, but it if could potentially stall by flooding maybe that's not a great idea for eehack-stable. I found with big injectors, max afgs signal from the maf can cause a really nasty flood condition really quick.

    steveo I had the pleasure of logging my commute today and thought of a couple minor things I'd added but might not have gotten to you back in 2017.

    * if it isn't already, would it be possible to make the knock count field the same size as the others on the dashboard?
    * could you add the frame # or timestamp to the mouseover info of a knock event?

  3. #33

  4. #34
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Oh, steveo. It's so ironic you would decide to do a 2019 bugfix release when I've just gotten my wideband functional. No good deed goes unpunished...

    So I finally had the opportunity to do some wideband tuning on my rig. I have a nice hilly road that's scarcely traveled where I can run at whatever speed in whatever gear I want and set the cruise control so I get nice conformal bands of data at 1400, 1600, 1800, 2000 rpm - you get the point - so I can baseline my VE table. Then I go into eehack's analyzer and am rudely reminded of the fact that it's hardcoded to 500 rpm divisions. I figure I can fix this easier than build my own analyzer spreadsheet. I may have underestimated my spreadsheet skills.

    Feature request: ->[you know what my feature request is for the speed-density analyzer table]<- Hell, I think most ppl would be thrilled with 0-4000 rpm because anything over that is better done on a dyno.

    If you're bored, another feature request would be ability to filter on another parameter (i.e. spark advance > 10 degrees) on the wideband analysis. I'm seeing results that are very obviously DFCO influenced and would like to filter them out of the very low load cells but have no mechanism to do so.

    I'm going to dive into some spreadsheet tools for a quick solution, but thought I'd make the request if you're so inclined. I know others have requested similar changes.

  5. #35
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,708
    use trimalyzer. i built it because eehack has suboptimal ve analysis. i know its not 'integrated' but its a fairly minimal step to export as csv. it allows arbitrary filtering.

  6. #36
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    I'll revisit trimalyzer after I've had some coffee but I don't recall being able to use it to analyze wideband data (i.e. target afr vs measured afr). Is the source tree on github the most current code?

    I had eehack sort of working using 200 rpm divisions, but couldn't get it to draw beyond rpm row 14. I guess the table needs scroll bars, etc. and I'm lazy.

    Edit: Thanks. Man, does eehack ever spoil a tuner. I was almost going to whine about having to massage the data in a spreadsheet to get trim based on wb afr / target afr so it could be used in trimalyzer. Now I know what it feels like to be my classmate that lives down the street. You know the type - asks for help working on his car, and then when you're underneath it with dirt falling in your eyes and need a socket he's busy taking a phone call.

    That's slick - I had missed the arbitrary input preset and had completely forgotten how universal it is.

  7. #37
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,708
    Quote Originally Posted by spfautsch View Post
    I'll revisit trimalyzer after I've had some coffee but I don't recall being able to use it to analyze wideband data (i.e. target afr vs measured afr). Is the source tree on github the most current code?
    it does analyze arbitrary values now, it was broken before.

    you can point it at anything and it'll plot the percentage difference against a single target value, but it wont use a secondary field as a target so it wont do the actual afr vs live open loop afr target that eehack does.

    it's not up to date on github. i'm starting to hate github, also microsoft owns it now. planning to delete that and just distribute tarballs. i'm a lone developer so collaborative revision control isn't really worth the time.

    i'll get you an up-to-date tarball for trimalyzer later today

    and i guess i'll consider making it match the real VE table in eehack, it does make sense

  8. #38
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    650
    I have never run into this issue, but might just ask.

    What will happen if the cable is disconnected mid flash from pc side or from pcm side. Is there any way to recover and what is the proper procedure. I know that the flash routine will stay in the pcm ram indefinite time, but will eehack be able to resume on that condition.

    I vote for a second arbitrary value on trimalyzer, value selectable or input of predefined value.

    How about a user configurable cells layout on maf and ve input in eehack to match the bin table size. Adding the maf cell at the datastream is not that hard and can give very accurate trims.


    If you want to add maf/ve switching and maf cell datalog I can improve the current v3 patch a little.
    The maf/ve switching doesn`t flood the engine at all, I have tested thorougly. If the rpms are real low on idle it can stall 1 to 5 ratio. It just needs some time to stabilize during the input switching.

    I also tested the cyl balance test on the dark magic v4.9 fork and eehack didn`t crash, so the problem lies somewhere else.

    I have been thinking for more tests added. Like opti signal test at idle. Super fast logging of cyl id at idle with mode 3 command and looking for cyl id deviations. I don`t know if it is possible but at least 50 frames per second will be needed for 20ms low res period, or 100 for 10ms resolution. Did you test the limit of mode3 refresh rate.

  9. #39
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,708
    What will happen if the cable is disconnected mid flash from pc side or from pcm side. Is there any way to recover and what is the proper procedure. I know that the flash routine will stay in the pcm ram indefinite time, but will eehack be able to resume on that condition.
    if you disconnect the PC side, eehack will probably just freeze.

    if you disconnect the cable side, theoretically, the ecm has not recieved the checksum of that packet and should discard it, never writing it. if it's connected again really quickly, it should re-send that packet.

    once a few attempts have been made to re-send the packet, it'll return to the erase state and start over. it'll do this indefinitely, as far as i know. as long as the ECM doesn't reset from the programming loop for some weird reason, theoretically it should be okay

    it's not that well tested, though. try not to yank the cable when programming.

    I have been thinking for more tests added. Like opti signal test at idle. Super fast logging of cyl id at idle with mode 3 command and looking for cyl id deviations. I don`t know if it is possible but at least 50 frames per second will be needed for 20ms low res period, or 100 for 10ms resolution. Did you test the limit of mode3 refresh rate.
    that's pretty cool for sure. actually lots of sensors could be tested more reliably with a huge acqusition rate. the mode3 is pretty fast with a regular parameter, i'm sure that'd work fine, but i never actually tested the timing.

  10. #40
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Quote Originally Posted by kur4o View Post
    I also tested the cyl balance test on the dark magic v4.9 fork and eehack didn`t crash, so the problem lies somewhere else.
    I think you can probably disregard that bug report if it's the first you've heard it.

    I've noticed all manner of strange things with what I've been using which I believe is from the zip you put in the $eehack thread here. But I routinely have about five different forks of eehack on my laptop at any given moment. Before last friday I'd never seen the MAF mode / SD mode become visible on controller.ui, so after looking at the source I did some searching and found the mode4 definition file. This worked a couple times (the buttons became visible), but when I try switching modes nothing happens. In addition I've noticed other very basic things like the play button on the datalogger window has stopped working.

    Quote Originally Posted by steveo View Post
    if you disconnect the PC side, eehack will probably just freeze.
    I've thankfully never seen this happen while flashing, but more than once I've had the usb adapter disconnect spontaneously while logging. I suspect the way the serial libraries handle stuff like this is different on windows. But with linux eehack shows a connection error and tries reconnecting while it holds a handle open to the device node. As I mentioned previously the adapter gets a new device node when the kernel reconnects to the ftdi bridge chip. I've re-connected to the new device node in eehack without crashing or restarting the program so it's theoretically possible. But I'd rather not test, thanks.

    What I did to analyze my wideband data was to take the delimited file from eehack and add a calculated field to the sheet i.e. =(AM3/L3)*100 where column L is target afr and AM is my wideband. The results seem to indicate it worked acceptably.

    trimalyzer.jpg

    Anyway, this leads me to my next question steveo. Is there documentation regarding how to do what you were talking about with lambda in the definition file? I attempted to customize mine to add the converted ADC voltage, but it doesn't seem to be working when looking at a pre-recorded .eedata file. I guess to summarize I'd like a idiot's guide to the eehack definition file, because it seems there's something I'm missing and I think there's a lot of hackish functionality I could create there if I simply understood how it was intended to work.

    EDIT: Nevermind, I think I figured it out. I can at least see lambda on the dashboard.

    Reason I'm looking for this is to try and determine the stoichiometry of what's in my tank. 14.2:1 is way too rich, and 14.7:1 seems lean. I'm planning to use my MAF and wideband in open loop and adjust the target AFR to see what I can come up with. Assuming my injector flow rate and MAF calibrations are within reason it should be more scientific than trial and error.

  11. #41
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    650
    I myself have at least 20 different version and sometimes it can get really messy what works.
    Anyway here is the really well latest tested version that should work better with you unless there is some linux compiler bugs thatI am unware of.

    For the SD/MAF button to show and some of the other goodies, you must connect to the pcm prior to starting the enigne. It needs it once on eehack session. It is a pcm bug preventing eside to communicate while the engine is running, and some of the controller config data is extracted from eside.
    For the best of all tuning experience you can test the realtime ve/maf tuning. The interface is some awkward to use but saves alot of time and reduce the flashes to a minimum.


    And don`t overtrust the wideband reading. It can be really off. ALways use as a reference the narrowband voltage reading 0.454v=14.7 afr=1 lambda.

    I constantly get 15-15.6 wideband afr readings on a closed loop run. The individual cyl trims can throw the afr form 12.5 to 16.5 if not properly tuned at idle. The idle tune should start with that.
    Attached Files Attached Files

  12. #42
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Thanks, I never caught that tidbit about connecting before startup. Honestly, the control interface is very difficult to use if you have to click on controls to do things. That's why I added all the key mappings and focus reassignments in steveos version - so sliders can be adjusted with the left/right arrow keys, and things like forcing AFR can be done by pressing the 'F' key. I'm not condoning doing stuff like that while driving, but there's no way I could with your fork. Even with a mouse it would be difficult with the car strapped to a dyno much less moving. Don't take offense - the work you've done is incredible. I simply hate all software that cannot be used without a mouse. It's (the mouse) the single biggest time-waster humans have ever invented for themselves.

    0.454v = 1 lambda <> necessarily equal 14.7:1

    I've seen similar things in closed loop. That's why I'm giving the wideband very little attention unless running in open loop. I don't want to see the integrator oscillations, just the raw baseline fueling calcs at work.

    We need to find a place to host your sources beside in posts here... or is there one and I just missed that? I just found steveo's sources on fbodytech and proudly became the first to download the trimalyzer-1.5b source. Knowing that github is owned by microsoft makes me want to pull my stuff down on principle alone, so that's out.

  13. #43
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Hey steveo I thought of one other thing when I was flashing earlier - I know it probably is dependent on the parameter being configured in the definition file, but if it's not a huge amount of trouble it would be really informative (and for newbs maybe you can make it bark at them about bricking their ecu) to show the input voltage on the flash window.

    kur4o I've been messing with the wideband with the Innovate serial logger and noticed the non-linearity of the D27 input - did putting the input on D25 improve this?

  14. #44
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    650
    I hard wired pin D25 to read injector voltage for my ls1 injector patch and didn`t have the chance to try it on the wideband input. I suppose it will be much more stable and accurate since there will be no voltage potential difference. The resolution will sucks but if you can reset the wideband to read 11-16afr = 0-5 volts it will have enough resolution. Innovate 1wire ground widebands design is bad due to using PWM modulated heater for the sensor. I did some experiments and could see the afr changing with the frequency of the PWM circuit. I also have some terrible emi noise from the gauge and used all kind of tricks to settle it down.

    0.454v = 1 lambda <> necessarily equal 14.7:1
    I am sure the narrowbands 02s are set to read 14.7 at 0.454v.
    1 Lambda is the perfect mixture of air to fuel[cleanest combustion process] and is different for different fuels.
    1 lambda equals to

    Petrol 14.7:1
    Diesel 14.6:1
    Methanol 6.4:1
    Ethanol 9:1
    LPG 15.5:1

    Here is good write up about it.
    AFRlink

    Given this to trick the narrowbands to read lower lamda, fattening the switch voltage of the o2s upto 0.545-0.57 might give you the best results. If you fatten more it can result with poor CL performance. Some real time play with 02 swing voltage will get you to the max of deviations.


    The key shortcuts for the eehack controller window are already there by your request and are working great. I had plans to expand them to more controls but never get there.

  15. #45
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    481
    Quote Originally Posted by kur4o View Post
    Innovate 1wire ground widebands design is bad due to using PWM modulated heater for the sensor. I did some experiments and could see the afr changing with the frequency of the PWM circuit. I also have some terrible emi noise from the gauge and used all kind of tricks to settle it down.
    Was the signal stable over the serial output or was the modulation only present on the analog output?

    Quote Originally Posted by kur4o View Post
    I am sure the narrowbands 02s are set to read 14.7 at 0.454v
    Sorry to have to continue to split hairs with you but no, they're set to read lambda at 0.454v. I will agree that with "petrol" that's 14.65 parts air to 1 part fuel.

    The problem is here in the states the retailers are no longer required to specify how much ethanol is in the product they're selling as gasoline, and our government heavily subsidizes corn ethanol production as a "clean" alternative fuel. They aren't even required to acknowledge it's presence. Yet I can pour a cup of distilled water in a gallon of this so-called gasoline, and it magically dissolves. What is it dissolving into? Water doesn't bond molecularly with petroleum based fuels. It's why I laugh hilariously when I see people buying methanol based fuel "drying" additives.

    Quote Originally Posted by kur4o View Post
    Some real time play with 02 swing voltage will get you to the max of deviations.
    I definitely want to work with this, but it will be a final finishing touch. Right now I'm painting in very broad strokes. I have a set of modified injectors that I need to find the flow constant of. They're rated at 42lb/hr, but it will barely idle with the injector constant below 42.3. It likes 42.7.

    Quote Originally Posted by kur4o View Post
    The key shortcuts for the eehack controller window are already there by your request and are working great. I had plans to expand them to more controls but never get there.
    I know - wasn't belittling your work, it's brilliant. Simply pointing out that clicking some of the controls while sitting in an idling car with a lumpy cam is difficult at best.

    Quick question while I'm thinking about it - is it safe to use steveo's version with the v4 patches?

Similar Threads

  1. $4D update
    By steveo in forum GM EFI Systems
    Replies: 4
    Last Post: 07-19-2014, 11:33 AM
  2. tunercat update.
    By doctortuned in forum TunerCat OBDII
    Replies: 3
    Last Post: 03-11-2014, 01:58 PM
  3. TunerPro RT update Virus?
    By roby in forum TunerPro Tuning Talk
    Replies: 7
    Last Post: 09-09-2013, 07:09 AM
  4. Tables won't update
    By POZE in forum TunerPro Tuning Talk
    Replies: 2
    Last Post: 02-16-2013, 11:48 PM
  5. TunerPro V5 update!
    By EagleMark in forum TunerPro Tuning Talk
    Replies: 27
    Last Post: 07-15-2012, 04:42 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •