Page 4 of 11 FirstFirst 123456789 ... LastLast
Results 46 to 60 of 155

Thread: EEHack 2019 update

  1. #46
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    they're set to read lambda at 0.454v
    I completely agree with this statement. Maybe we are using different terminology for the same thing.

    Was the signal stable over the serial output or was the modulation only present on the analog output?
    i didn`t compare it with the gauge serial datastream. I guess there will be no variation on the serial output. It Affects only the 0-5 output.

    Which reminds for a past eehack addition request.

    Steveo, can you add a wideband stream through a second serial port. Most of the wideband gauges have a serial output. That way we eliminate all the havock related with setting accurate reading through a 0-5v input.


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

    The v4 patch is backwards compatible with all previous version of eehack. The stock mode4 message structure is intact. I added new stuff to some unused bits and extended the message on request. So is it pretty safe to use and all controls will work as expected.

  2. #47
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    Quote Originally Posted by kur4o View Post
    Maybe we are using different terminology for the same thing.
    No, you're just assuming I'm burning iso-octane when in fact it's a blend of ethanol, gasoline, and other stuff.

    Quote Originally Posted by kur4o View Post
    Steveo, can you add a wideband stream through a second serial port. Most of the wideband gauges have a serial output.
    This is where I was heading. The problem is that we would have to reverse engineer the serial datastream for each vendor.

    Quote Originally Posted by kur4o View Post
    The v4 patch is backwards compatible with all previous version of eehack. The stock mode4 message structure is intact. I added new stuff to some unused bits and extended the message on request. So is it pretty safe to use and all controls will work as expected.
    Thank you - I thought this was the case but didn't want to find out I was wrong at 75mph.

  3. #48
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i can't imagine i'll have the time to implement and test supporting another serial port wideband input, the way eehack is written that'd be an entirely different datastream, it wasn't written with this kind of stuff in mind so it'd either be really hacky or a lot of work.

    i know there's lots of stuff it'd be nice to have guys but i'm still focusing on bug fixes, i have other stuff to work on too

  4. #49
    Fuel Injected!
    Join Date
    Oct 2013
    Posts
    1,022
    Quote Originally Posted by kur4o View Post
    I am sure the narrowbands 02s are set to read 14.7 at 0.454v.

    Not one O2 or UEGO sensor made has a clue about AFR numbers. Every O2 sensor display of AFR is due to someone having programming a lambda to AFR lookup for the display.

    Do you happen to mean that the PCM is programmed to interpret the 0.454V output from the O2 sensor as an AFR of 14.7:1????

    In reality, the PCM will closed loop tune to the fuel assuming the base VE and MAF tables are close and the fuel stoichiometric ratio doesn't deviate too far (and BLM limits allow it). I would expect it could close loop tune to the various typical ethanol blends other than E85, it would likely tune OK in the 0-15% blend range.

  5. #50
    Fuel Injected!
    Join Date
    Mar 2017
    Location
    Utica, IL
    Age
    46
    Posts
    42
    Would it be possible to add an easy way to switch off PE mode? It would be kind of convenient to do that when tuning VE tables and not have to flash a separate tune with PE disabled.
    1996 Camaro SS #308, M6, 4.10, OBD-I Conv, OBX 1-7/8" Stainless Headers, Custom 3" Stainless Y Pipe, 2OTL
    355-Stock Crank, 6" Forged Rods, Forged Pistons-11.5:1 SCR, LE2 Heads, LE2 Ported Intake,
    LE/Lunati 231/239 110 LSA Cam, Comp Pro Mag 1.6 RRA, Ford LU34 36-lb Injectors, 58mm TB, SD Tune

  6. #51
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    Quote Originally Posted by steveo View Post
    i can't imagine i'll have the time to implement and test supporting another serial port wideband input
    Sorry, I wasn't implying you should do the work.

    Quote Originally Posted by steveo View Post
    the way eehack is written that'd be an entirely different datastream, it wasn't written with this kind of stuff in mind so it'd either be really hacky or a lot of work.
    I'm pretty good at "hacky". ;-)

    I may attempt this for the Innovate controllers once you're finished with the bugfix release (as a fork). Offhand, how much work do you think it would entail to define an input that derives it's data from something other than the ALDL data? I'm guessing a bunch... This will probably be a good project for next winter, if at all.

    Edit: hmmm, splicing another datastream into the .eedata would be really useful with my ignition controller.

    In the mean time I'll have to play around with narrowing the output range of the LC2 and see how much it improves the nonlinearity.

    Quote Originally Posted by steveo View Post
    i have other stuff to work on too
    What nerve? You mean you have a life outside of writing software for us freeloading bums? ;-)

  7. #52
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    if you do want to do it

    eehack's log format is obviously designed to differentiate between data packets based on a pair of 8 bit values, the device and the message number

    so one approach is perhaps use a false device like 0xFF that'd never be used, but then make an exception in the datalogger so when device $FF is requested the request never happens, and another function is used to fill that array with data from your separate port. at least this approach would allow use of the already working timecoding, request rates, etc.

    the other approach would be to maximize data rate by using interrupts from the second serial port then insert that data into the log, bypassing the existing request/response functions, conversion with the definition file, etc.. maybe even in a separate thread would be a good idea.

    the ui and the datalogging are separate enough in current versions, where if you had a thread grabbing serial data, and you formed a proper log 'packet' or whatever i called it, you just have to generate a QT signal to tell the rest of the program that new data has arrived and it'll probably handle the rest of displaying, realtime graph updating, etc. without complaining

    there's a bit more involved to doing it properly, such as another serial port selection area in the settings dialog (and related back end in the settings storage)

  8. #53
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    Some of the innovate documents I have gathered regarding serial datastream. If the interest arise I will make some serial logs of actual communication between gauge and innovate`s Logworks3.
    Attached Files Attached Files

  9. #54
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    Unless you're willing to tackle it I wouldn't spend much time on it right now kur4o. As mentioned I probably won't have time to work on anything like this for 5-6 months.

    steveo I think your first approach with the dummy device ID might be the smart way to go. I'm envisioning parsing the UEGO controller stream in a separate thread and handing the data off to the datalogger.

    This is all conjecture because I've got my plate full. This week aside from trying to get my yard work done in between rain showers, I'm pulling my engine back out because the shaft mount rockers work so well that I think I've bent an intake valve.

  10. #55
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    just so you guys know i've been working on this a bit still in my spare time

    looking back at it, i decided to spend time to redo some of the ui.

    when i wrote it i just slapped some qt library fields and widgets together for a lot of the ui elements like the dashboard, but that was before i knew anything about qt ui design, so i'm going to remake the dashboard.

    for example i used QTextEdit and QPlainTextEdit for a lot of output fields. QTextEdit is like a mini web browser.. so actually the dashboard is like 50 mini web browsers. you can display images, html links, and table in the packet rate field if you wanted to.

    it's a testament to how good the QT ui library is that nobody has noticed

    should improve performance as well as make it more scaleable/resizeable on different/newer operating systems

  11. #56
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    new beta please test, includes source: http://fbodytech.com/files/eehack-beta4.8.zip

    here are some of the changes

    Combine the launcher and datalog window as the primary window, I always liked it better that way
    Major UI overhaul to fix scaling and performance issues with dashboard and other modules
    .. Use more dynamic layouts in most areas
    .. Analyzer and autospark not done yet, but still functional
    Ensure packet checksums are actually checked everywhere
    Allow multiple graphing windows to be opened at once (just click the graph button again)
    Add timestamp to moouseover of each knock event in analyzer
    Fix a bug that prevented the 'bad checksum' override for bin reading to fail
    Fix colored field indicator operation in dashboard for high/low conditions in the definition file
    Fix hard crash when selecting custom dashboard parameter with no parameter selected
    Code cleanup to fix compliation with newer QT versions
    Maybe fix a bug that causes flash write to fail sometimes (initial connect timer)
    Allow multiple log selections in the load log dialog
    Dropping github RCS so remove references to it in 'about' dialog
    Fix minor bug that prevented settings from propogating to the dashboard

  12. #57
    Fuel Injected! Terminal_Crazy's Avatar
    Join Date
    Oct 2015
    Location
    Lancashire England
    Posts
    410
    Hi Steveo, Just having a play.

    I like the single main page. I didn't like having to move the panel to the side everytime I ran it.

    I'm running it on my desktop atm as my in car laptop screen has cracked. Will that still fit in a 1024x800 screen ? (obviously i need a better laptop)
    I guess it still auto connects with the ignition switched on ? That was awesome when I took it for a dyno run. I just gave it to the lads & it recorded every run.

    I loaded a log and had a play.
    In the graph window logged some data. opened a second one and tried to view more data. Nothing plotted in the second+ screen.
    checked in the first and it displays. I've lost the 1st graph and none of the others plot any data
    ... Settings definition file was set to a previous version (Kur4o's) so reset that & re run EEHack. No data is being displayed

    In the Analyzer window, hovering over the knock count does display the timestamp but needs reducing by1000. #5741@ 788.9 displays as 788949

    I've just ordered some Speed Engineering 1 3/4 Longtubes.
    Can EEHack be configured to display Dual Wideband inputs in AFR & Lambda equivalent ?
    Are the input curves of the AC Pressure & D27 similar enough for this?

    Playback: Fast button doesn't seem to run any faster on or off.

    Excellent stuff Steveo.
    Thankyou

    Mitch
    '95 Z28 M6 -Just the odd mod.
    '80 350 A3 C3 Corvette - recent addition.

  13. #58
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    thanks i'll check that stuff out. i just noticed cpu use when in 'fast' is pretty high, im pegging your CPU, so i'll have to do some profiling. it should fit in 1024x800 ...

  14. #59

  15. #60
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    Another quick update, this one makes the graphing work properly again, makes the UI look a bit nicer (missed a library in the last release..) but I also re-implemented the dashboard’s caching engine so processor use should be reduced dramatically. Thanks to Mitch for the quick testing. Please let me know how it works for you!

    http://fbodytech.com/files/eehack-beta4.8.1.zip

Similar Threads

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

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
  •