Bringing TBI and Multi Port Fuel Injection to a New Level.     EFI Conversions and Tuning! Seattle to Portland! E-mail Tuning Consultant!
Page 9 of 9 FirstFirst ... 456789
Results 121 to 135 of 135

Thread: EEHack 2019 update

  1. #121
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    652
    NomakeWan,

    data tracing is really not possible due to pcm limitation. If the eside didn`t stop talking with the engine running alot more could have been made.

    For now the extended version of eehack gives realtime control for any load dyno situation you have and for sure you can nail the tune in less than an hour with the real time VE table and Maf table control, add to that spark and fuel control and you can perfectly dial the engine with no analysis tools but only accurate wideband input.

    By load dyno I mean the ability to set the engine running at 2000rpm and 90kp map for example, first adjust the ve cell at that range than adjust best spark advance while playing with the fuel and watch for the dyno output to get the best settings.

    For the extended version of eehack search for a thread called the ultimate $EE patch thread.

  2. #122
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    84
    Oh, I believe it. But after seeing how the Analyzer/Trimalyzer work, it should be possible to create a pseudo-map-trace that is merely a visual representation of the MAF table or VE table, perhaps with colors for cells indicating at a glance whether that cell has sufficient data points to use for later analysis. Drive around as normal, logging the whole way, then glance and see if there is anything specific that was missed while still logging. Take care of those cells, then go ahead and run the analysis as normal.

  3. #123
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    ah, so what you're asking for is some kind of overview that tells you which areas of the log have enough data coverage. that could be useful. i just got confused because you asked for realtime analysis in the same sentence. that data is in trimalyzer (hover your mouse over a cell) but it's hard to overview in its current form.

    i started working on the analyzer a bit last night and i was struggling with it a bit, it was written really poorly. i wonder if i should just rip the analyzer right out and embed trimalyzer in its place (does the eehack analyzer do anything cool that trimalyzer doesn't...?)

  4. #124
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    482
    I really like the basic CL Performance tab, and the idle average data on the Cruising AFR tab. Gives me an idea of how the CL routine is working and where trims are at a quick glance.

    I also frequently look at knock events and then jump to that timestamp in dash to try and figure out what was happening around the time of the knock. In fact I would love to be able to double-click a knock event and have it jump to that point automatically like the graph does.

  5. #125
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    In fact I would love to be able to double-click a knock event and have it jump to that point automatically like the graph does.
    in the context of a graph jumping to a timestamp makes sense since it's always viewing a single log...

    ...but the knock timestamp is already a bit faulty in that the analyzer can be either in the scope of a single log or multiple logs. if analyzing multiple logs the timestamp becomes meaningless.

    i guess i could jump to the current record within the range of the current log and if it's in another log it's the user's problem, or if it's outside the range of the current log it'll just not do anything, but i hate being misleading (the timestamp is already potentially misleading).

    to do it properly we'd need to make each data point aware of which log its from and then switch to the correct log when jumping to that point, but that's needlessly complex and we'd need a system to switch to arbitrary logs avoiding all the potential crash points in doing so

    maybe a simpler solution is to make the analysis contain knowledge of whether it was generated from multiple logs or not, then disable things concerning timestamps subsystems if it was.

  6. #126
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    i should mention since we're talking about the knock analyzer, i was struggling to make the analyzer scale to different window sizes, so i went ahead and transplanted trimalyzer's knock analyzer into the next version. it was originally based on eehack's knock analyzer, but it's faster, has less rounding errors, scales for window size, labels inside the grid, etc

    i did add the extended tooltip per knock point data from eehack back in since i thought it was a bit nicer, since it has timestamp data it does counts per millsecond rather than counts per point (a more useful metric since the gap between knock count increments is arbitrary and has a huge potential effect on event magnitude) also merged the color coded WOT/non-WOT points.

    i think y'all will like it

  7. #127
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Posts
    482
    I realized all those limitations when I added the timestamp to the knock events, and have encountered plenty of instances where I've suffered the wrath of said laziness.

    I wouldn't over-complicate it - if it's easy to do just make it jump to the point in the log that's currently selected on the dashboard. The user can figure out whether or not it's the right log. And if the timestamp is greater than the length of said log do nothing. Or, just ignore this whole idea since it's kind of a nitpicky request.

  8. #128
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    84
    I'll also add that I like the PE analyzer in EEHack, so that's another thing it does that Trimalyzer doesn't. Just to glance at and make sure I'm good until I get a wideband and it becomes even more useful.

    Good stuff on the knock analysis! Can't wait!

  9. #129
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    trimalyzer can totally do that too. just use o2 voltage as an arbitrary input and filter for pe active rather than the default

  10. #130
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    652
    As you are already there please adjust the maf scaling in the analyzer from 0 to 77 cells. I have finally managed to convert the maf cell scalar to human readable and now it shows a value from 0.00-77.00 with the values after the dot showing the interpolation factor between 2 adjacent cells from .00 to 0.99.


    So if the value reads: cell 9.50, it means the maf value that is being used is taken exactly at the mid point between 9 and 10 cell. That way you can accuartely nail the maf curve. Also the fast tps changes must be excluded from the analysis, maybe adding some delta tps calculations with a threshold. With fast tps change the maf values change is smoothed down and does happen slowly over time.

  11. #131

  12. #132
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    652
    For sure It will be very cool to do it. Actually it will be exact cell number instead of hz/trim so 1468hz will be cell1, 1616 will be cell2 and so on. You will even know the exact interpolation between adjacent cells.
    I will slightly modify the patch to include the maf cell/hz value in the datastream.

    Right now I have it streaming at byte 34 and 35 and the conversion looks like
    34,MAF_FREQ_CELL,MAF CELL,,BASIC,16,2,0.00380625,1,0x00,0xFF,,1,77,1,77

    the ditched bytes are really unused
    34,B34RAW,Unused Byte 32,,HACKER,8,0,,,0x00,0xFF,RESEARCH,,,,
    35,DIAGO2B,Post-Cat O2 Voltage (Corvette),mv,EXTENDED,8,0,4.44,,0x00,0xFF,,,,,
    So it is not a big deal loosing them.

  13. #133
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    it'll be a bit of a pain as i need to handle both original and patched bins (so the old maf analysis has to stay too) but i'm into it. email me the patch and tell me how it works

  14. #134

  15. #135
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,710
    hey im getting a bit involved with the analyzer and im thinking that iíll just write a bit of extra code to allow the user to apply VE, MAF, and maybe even knock event changes directly to the bin. the stupid thing needs a rewrite anyway so i figure why not. i would leave smoothing up to the user. what do you think about that?

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
  •