Page 59 of 72 FirstFirst ... 949545556575859606162636469 ... LastLast
Results 871 to 885 of 1070

Thread: new $EE tuning thing!

  1. #871
    Fuel Injected! Terminal_Crazy's Avatar
    Join Date
    Oct 2015
    Location
    Lancashire England
    Posts
    410
    Quote Originally Posted by steveo View Post
    ... also any feature requests or anything? i hate to push out a release for three bug fixes...
    Yes. Analyse CL Performance BLM Average. Can we have L & R BLM averages please.



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

  2. #872
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by steveo View Post
    ... also any feature requests or anything? i hate to push out a release for three bug fixes...
    Tuning module? To edit/flash timing tables and MAF tables?

    Haven't installed my Innovate MTX-L yet, but ability to use/log/see lambda vs. AFR?
    Last time I used WB for tuning, I preferred to use lambda vs. AFR by simply changing .adx in TunerPro to display lambda.
    Last edited by babywag; 10-23-2016 at 07:01 PM.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  3. #873
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    Quote Originally Posted by Terminal_Crazy View Post
    Yes. Analyse CL Performance BLM Average. Can we have L & R BLM averages please.
    you mean the population analysis?

    i intended this analyzer module to be used to evaluate cell data distribution to determine more efficient rpm/map boundaries, have you found another reasonable use for it?

    it would be fairly easy for me to add a left and right column, so i will.. just curious...

  4. #874
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    Quote Originally Posted by babywag View Post
    Tuning module? To edit/flash timing tables and MAF tables?
    this gets asked for a lot

    theoretically if eehack did tune...

    one choice is to write something that'd be weaker than tunerpro, no graphing, math, crappy table editing. it would only be good for people that like eehack and do not like tunerpro (a type of person that i don't really deal with often). the advantage is that it could certainly could work alongside the analyzer to input data, but if i add a 'propogate fuel changes button', im afraid noobs would blindly trust the analyzer data without sanity checking it, making their car run worse and worse with every pass, and blaming eehack for it.

    ... or it would be a superior or equal tool to tunerpro and consume my life for easily a year or more, but i would want it to be general purpose (so it'd edit any bin) so that wouldn't make any sense to put into eehack, unless eehack also started working for other vehicles for all functions, this is something called 'scope creep'.

    neither of those scenarios make any sense, that's why as a design decision, eehack is an EE datastream tool and not more. it wont even change your bin on disk if you patch. that's a major reason why when i did require some slight bin changes to enable advanced features, i made them passive, to ensure i didn't cross the line into bin editing of any kind.

    Haven't installed my Innovate MTX-L yet, but ability to use/log/see lambda vs. AFR?
    Last time I used WB for tuning, I preferred to use lambda vs. AFR by simply changing .adx in TunerPro to display lambda.
    lambada display is already almost possible. there is very little except some 'labeling' of the field as AFR.

    to get a decent display, you can easily turn off the :1 suffix yourself, and increase the precision in the definition file. it's a human readable csv file easily edited in a spreadsheet program.

    unfortunately the stopping point is that i've restricted the linear scaling configuration (the low/high point thing) to some 'sane' values for AFR. if i unrestrict them, that'd make it happen for you, you'd just have to determine lambada @0v and 5v or whatever.

    would that be alright?

  5. #875
    Fuel Injected! Terminal_Crazy's Avatar
    Join Date
    Oct 2015
    Location
    Lancashire England
    Posts
    410
    Quote Originally Posted by steveo View Post
    you mean the population analysis?

    i intended this analyzer module to be used to evaluate cell data distribution to determine more efficient rpm/map boundaries, have you found another reasonable use for it?

    it would be fairly easy for me to add a left and right column, so i will.. just curious...
    Readjusting the VE Tables since i milled the inlet manifold.
    BLM's are running 120's - 128. MIles more stable than before. RHS BLM's are pretty much 128 in most cells. LHS varies between 122 & 132. Your average shows the average blm's running around 125.
    I've since written some code to average L&R Blm's so i know where they both sit.

    I wonder if others have struggled with split BLM's due to the manifold leaking underneath the ports. The stock LT1 was a far better fit when measured than the Edelbrock.

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

  6. #876
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    ah ok for splits, i've always preferred graphing for that, but i see your point. i'll add the column.

    edit: don't forget the analyzer has 'use leanest bank' designed specifically for tuning splitty engines based on trims..

  7. #877
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    please test

    http://fbodytech.com/4-61-beta/

    Code:
    Fix bug that prevented 'silence extra modules' setting from working
    Fix bug that sometimes prevented 'dump ram' setting from working
    Stop counting errors during initial connection (unnatural serial events may be normal...)
    Allow crazy values in linear voltage to AFR mapping (for lambada or edge cases)
    Seperate left and right BLM values in the closed loop performance analyzer

  8. #878

  9. #879
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i'm thinking i'll make the default view level for the parameter selector 'extended', it makes more sense now that it's 'searchable'

  10. #880
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    I know...I was just daydreaming. My thoughts were simply for ease of one app to tweak/fine tune.
    Definitely not asking for full blown tuning!
    Fully understand your reasoning on why not to do it.
    Your call/choice. I personally just thought it would be a handy addition.

    I yanked the WB from my Jeep, so I'll try to get it installed in the Caprice asap.
    Been meaning to, now I have more motivation.

    Thanks for the fixes!

    Edit: I can reprogram the Innovate WB pretty easily, so what you wrote above regarding Lambda display request should be doable?
    It took some playing with TunerPro, but I believe it was pretty dead on accurate.
    That was ~3yrs ago, so I'll have to find my thread and refresh my craptastic memory.
    Last edited by babywag; 10-24-2016 at 03:29 AM.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  11. #881
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    i'd like for you to test the definition file i posted above, and try to get your wideband in lambda mode working with the latest beta. that'll prove it can be done. otherwise i'll make more changes until you get it working.

    honestly though once you try eehack with patched bin and afr target percentage calcuations in the analyzer, you might not want it (it relates AFR target to perceived AFR directly, and builds you a percentage of correction required table vs ve or maf)

  12. #882
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by steveo View Post
    i'd like for you to test the definition file i posted above, and try to get your wideband in lambda mode working with the latest beta. that'll prove it can be done. otherwise i'll make more changes until you get it working.

    honestly though once you try eehack with patched bin and afr target percentage calcuations in the analyzer, you might not want it (it relates AFR target to perceived AFR directly, and builds you a percentage of correction required table vs ve or maf)
    I just prefer lambda, today's fuel isn't 14.7, honestly I doubt it's consistent w/ 14.13 either.
    You've got different blends for summer/winter, the added ethanol, and all the additives the dump in to supposedly decrease emissions.
    Not to mention the different additives that individual brands use, supposedly cleaning valves etc.. etc.

    I like seeing lambda on the WB display, I think it's more accurate. When mine was set to AF display it's a calculated number, and I just don't think it is as accurate.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  13. #883

  14. #884
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by steveo View Post
    anyone tested the new features? i need feedback since i don't even have a test bench working right now ...
    Connection working smoother now.
    No more ABS light coming on.
    Setting for silence extra modules "sticks" now when I uncheck the box.

    It actually rained here in SoCal today so no go on WB install or testing.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

  15. #885
    Fuel Injected! babywag's Avatar
    Join Date
    Dec 2011
    Posts
    219
    Quote Originally Posted by steveo View Post
    i'd like for you to test the definition file i posted above, and try to get your wideband in lambda mode working with the latest beta. that'll prove it can be done. otherwise i'll make more changes until you get it working.

    honestly though once you try eehack with patched bin and afr target percentage calcuations in the analyzer, you might not want it (it relates AFR target to perceived AFR directly, and builds you a percentage of correction required table vs ve or maf)
    The definition file works, and a minor adjustment to trim the voltage puts it in (what appears to be) sync with the actual gauge.

    But, as you mentioned above AFR is already working.
    Using lambda on analyze page doesn't yield much in terms of useful tuning calculations.
    I'm sure this could be changed?
    When run it simply shows all 1.0, or if changed to percentage 93%
    Since it already works using AFR, unless you want to pursue/test lambda more, I can just use AFR.
    Tony

    '88 Jeep Grand Wagoneer (aka Babywag)
    '67 Jeep J3000
    '07 Dodge Magnum SRT8

Similar Threads

  1. 1badcell and thats not the only thing
    By 1badcell in forum Introductions
    Replies: 2
    Last Post: 12-31-2013, 02:25 AM
  2. Replies: 6
    Last Post: 11-27-2012, 09:03 PM
  3. Replies: 2
    Last Post: 11-07-2012, 05:26 PM
  4. Minor thing.
    By historystamp in forum GearHead EFI Forum Support
    Replies: 7
    Last Post: 01-22-2012, 12:00 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
  •