Page 2 of 16 FirstFirst 123456712 ... LastLast
Results 16 to 30 of 238

Thread: Narrowband Tuning Tool

  1. #16
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    Quote Originally Posted by Xnke View Post
    This would be great to use with the P66 ADX that Robert built-I'd definitely use it! Seeing as he's written the stuff for most of the 60*v6 computers, I'm sure the fields would be close enough to the same to let it work for most of them, too.
    this program will definitely work with any log that has rpm, map, and at least one BLM value in it. it isn't going to use the ADX file in any way (you'll have to export the log as CSV for it to function)

    the only caveat is that if you have a stupid or uncommon name for any of those fields in your ADX, you're going to have to manually select the field before it'll let you analyze the log, but that will be really easy to do....

  2. #17
    Fuel Injected!
    Join Date
    Dec 2016
    Location
    Colorado
    Age
    39
    Posts
    120
    I will def try this out...Im using 16168625, $E6. Count me in! I will change to $0D if needed...$E6 is stock Im working with now

  3. #18
    Fuel Injected!
    Join Date
    Sep 2016
    Age
    37
    Posts
    38
    You guys on this site never cease to amaze me. I spent the last six months attempting to learn tuning, though i was a hot shot, only to get on here and get blown away by how knowledgeable everyone is. Incredible stuff... can't wait to see the finished product

  4. #19
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    progress so far:

    - it loads logs (any number of logs) into efficient data structures for analysis
    - it removes logs from these data structures without crashing.. this part took a lot of head scratching
    - it 'maps' parameter columns, kinda, but not automatically yet. the important part is the column mapping data structures are complete
    - the ui properly handles one and two o2 sensor vehicles in a way that doesn't look too crappy, this took a bit of work

    i know it's not much, but it's a start.

    next i work on the filtering engine including it's automated configuration, and try to build a dictionary system so i can get the parameter automapping off the ground

    so here's where i could use some help

    need to build lists of common adx column names for my dictionary file

    LBLM=Left Blm,Bank 1 BLM,Left LTFT, they ideally are in order of rough likelyhood. not case sensitive

    anyone care to browse some ADX files and help me with that? or at the very least, read their own ADX and give me the column names for:

    BLM (L/R/SINGLE):
    INT (L/R/SINGLE):
    RPM:
    MAP:
    COOLANT TEMP:
    MAF:
    CLOSED LOOP ENABLE FLAG:
    BLM ENABLE FLAG:
    CURRENT BLM CELL:
    WOT ENABLE FLAG:

  5. #20
    Fuel Injected!
    Join Date
    Dec 2016
    Location
    Colorado
    Age
    39
    Posts
    120
    Quote Originally Posted by steveo View Post
    progress so far:

    - it loads logs (any number of logs) into efficient data structures for analysis
    - it removes logs from these data structures without crashing.. this part took a lot of head scratching
    - it 'maps' parameter columns, kinda, but not automatically yet. the important part is the column mapping data structures are complete
    - the ui properly handles one and two o2 sensor vehicles in a way that doesn't look too crappy, this took a bit of work

    i know it's not much, but it's a start.

    next i work on the filtering engine including it's automated configuration, and try to build a dictionary system so i can get the parameter automapping off the ground

    so here's where i could use some help

    need to build lists of common adx column names for my dictionary file

    LBLM=Left Blm,Bank 1 BLM,Left LTFT, they ideally are in order of rough likelyhood. not case sensitive

    anyone care to browse some ADX files and help me with that? or at the very least, read their own ADX and give me the column names for:

    BLM (L/R/SINGLE):
    INT (L/R/SINGLE):
    RPM:
    MAP:
    COOLANT TEMP:
    MAF:
    CLOSED LOOP ENABLE FLAG:
    BLM ENABLE FLAG:
    CURRENT BLM CELL:
    WOT ENABLE FLAG:
    I will take a look at my file tonight when I get home and let you know

  6. #21

  7. #22
    Fuel Injected!
    Join Date
    Sep 2013
    Location
    Tulsa, Ok
    Age
    48
    Posts
    457
    I may have to give this a whirl, have a friend with an LT1 that is in desperate need of a tune. Keep up the great work Steveo!

    Bud
    If it don't fit force it, if it don't force fit f&%@ it!

  8. #23
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    Quote Originally Posted by buddrow View Post
    I may have to give this a whirl, have a friend with an LT1 that is in desperate need of a tune. Keep up the great work Steveo!

    Bud
    for an LT1, this isn't really going to do much that eehack doesn't already do, though

  9. #24
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    running into a snag with my dictionary thing, i tried to over-optimize it and ran into some kind of hash table maintainance nightmare that i can't seem to debug. i think i'll just rewrite it and give up some speed, i guess nobody minds an extra few hundred milliseconds on the first log load.

  10. #25
    Fuel Injected!
    Join Date
    Feb 2014
    Location
    Upstate, NY
    Posts
    416
    This sounds sweet. Keep up the good work.

  11. #26
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    progress is slow, moving soon, but i have auto-detection of fields working.

    it also seems to detect single and dual bank closed loop configurations.

    next i'll do some automatically filled filters. this will be like (pseudocode):

    if (coolant temperature field exists) then add filter coolant temp > 80

    but where i'm struggling is, how do i know the unit of measure?

    i'm pondering a system where i'll run a min/max value tally when the thing is loaded, so at least i can 'guess' if it's farenheit or celcius.

    the alternative is to leave it up to the user, but i find that to be not noob-proof enough

  12. #27

  13. #28
    Super Moderator dave w's Avatar
    Join Date
    Feb 2011
    Posts
    6,268
    I'm an Excel user. The attached screen shots are from my WBO2 Tuning Spreadsheet. The example posted is the average if formula for 1000 RPM _ 50 Kpa filtering out AE / PE / Open Loop then using the Idle Flag for averaging the AFR's of RPM's greater than 900, RPM's less than 1100 and Kpa's greater than 45 and less than 55 Kpa's. The average if formula processes the data on the sheet named "Insert Datalog". Maybe this type of logic will help with your Narrow Band Tuning? There are similar formulas for Count If, along with Standard Deviation forumlas if desired.

    dave w
    Attached Images Attached Images

  14. #29
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    you have a hell of a spreadsheet setup, dave. i did glance at one of your spreadsheets when i wrote eehack's analyzer routines, it verified that at least real tuners were doing what i assumed would work well. after filtering to determine valid data points, it basically does a cell selection routine then does a gigantic average. you're doing the same stuff, but in implementation you're using formulas, and i'm doing it functionally with operational loops on each row. the result is the same.

    i will build my initial versions like that for sure

    ...but in the end my plan is to have a decaying radius of trim for each data point, kind of like a heat map, so each point will affect a spread of cells in that region instead of just a single cell selection. if tuned correctly this would allow a reasonable amount of interpolation in areas where data isn't present.

    think about it from doing hand-tuning without such analysis tools, which we have all done. i want to mimic that effect, so that minimal initial data coverage can result in way more reasonable corrections. if you're making a 30% correction to a particular cell, that means that the adjacent cells are guaranteed (or almost guaranteed) to require at least 15% (or 1/2 of that adjustment) and even that 2 cells away might still require 5% adjustment. whereas if you're making a 5% adjustment to a cell it might be localized.

    this might involve mapping all of the data at a much higher resolution, then downscaling it to the target size, which is pretty easy. kind of like painting a picture of your fueling corrections, then pixelating it at whatever resolution your VE or MAF table happens to be.

  15. #30
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    longer project than anticipated, but i make a bit more progress every day.

    i have the filter system working, as well as its interface. it now has a really fast system in place to identify 'boolean' values based on a dictionary, so it can work with on/off fields such as power enrichment, closed loop, errors, whatever else, as long as they use a string that's known by the dictionary.

Similar Threads

  1. LS1 Flash Tool Released
    By antus in forum OBDII Tuning
    Replies: 118
    Last Post: 4 Weeks Ago, 07:02 PM
  2. Scan Tool Data Help
    By Kaweh in forum TunerPro Tuning Talk
    Replies: 1
    Last Post: 05-12-2015, 12:15 AM
  3. LT1 auto-tuning tool (web based)
    By steveo in forum GM EFI Systems
    Replies: 3
    Last Post: 10-17-2014, 08:07 AM
  4. Narrowband o2 sensors all created equal?
    By Accrdwgnguy in forum GM EFI Systems
    Replies: 4
    Last Post: 12-19-2013, 12:46 AM
  5. TunerPro Rt used as a scan tool?
    By mudbuggy in forum TunerPro Tuning Talk
    Replies: 21
    Last Post: 01-10-2012, 03:38 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
  •