Bringing TBI and Multi Port Fuel Injection to a New Level.     EFI Conversions and Tuning! Seattle to Portland! E-mail Tuning Consultant!
Page 11 of 16 FirstFirst ... 678910111213141516 LastLast
Results 151 to 165 of 238

Thread: Narrowband Tuning Tool

  1. #151
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    1.1 BETA:
    - display busy cursor more often when the interface is locked up
    - add maximum and minimum trim specifications
    - don't lose analyzer method setting when switching between similar layouts
    - enforce appropriate range in advanced settings
    - error checking on dictionary
    - remember last used directory when loading log files
    - allow drag and drop of logs onto main window

    http://fbodytech.com/trimalyzer/trimalyzer-download/

  2. #152
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    123
    So, I've made some tuning over the weekend, and logged data using EEhack. After that I tried your tool but got stuck with EEhack datalog format. Is there a way to export eehack log files to .csv format?
    I'm not using Tuner Pro for $EE logging as I was never able to get stable data with it.

  3. #153
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    from my tutorial...

    You will need to export all of the logs as CSV format.

    Why? Because… Trimalyzer doesn’t use definition files, and doesn’t actually care what kind of car you have, or what datalogger you use. Universal is good.

    Most dataloggers allow CSV export.

    In EEHack, Datalog > *Main > Export CSV.

  4. #154

  5. #155
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    123
    Thanks, I don't know how did I miss that... It's always hardest to find things that are right in front of you ;)

  6. #156
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    Quote Originally Posted by dzidaV8 View Post
    Thanks, I don't know how did I miss that... It's always hardest to find things that are right in front of you ;)
    there's a lot of stuff in eehack.

    all i could do is design it kinda logically so most people can find most things.

    above example proves that even when i write a manual (http://fbodytech.com/trimalyzer/trimalyzer-how-to/) for something, people don't always know the manual is there, or still miss it just as easily

  7. #157
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    123
    Yeah, now I feel stupid... The fact is that you documented it well, I was just too lazy to look for it and asked straight away.

    But, back to the topic, now I'll try to mess around with it and I'll let you know how it turns out.

  8. #158
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    Quote Originally Posted by dzidaV8 View Post
    Yeah, now I feel stupid... The fact is that you documented it well, I was just too lazy to look for it and asked straight away.

    But, back to the topic, now I'll try to mess around with it and I'll let you know how it turns out.
    that's ok, you are average example user.

    if you didn't find it, i need to throw some more links up to it, or maybe a button in eehack that says 'export for trimalyzer' or something. i have that ability.

    things are obvious to me because i wrote the shit, how am i supposed to know if it's easy for other people to find?

    so your inability to find it yourself is honestly a big help.

  9. #159
    Fuel Injected!
    Join Date
    Jan 2012
    Location
    Poland
    Posts
    123
    One more thought, as for now this software is for NB tuning. Most of my logs are from driving with WB O2, so the BLMs and INT values are of course useless. My thought is that it would be more universal to add a function to compare two values to calculate an error, e.g. Desired AFR - Measured AFR = Fueling error with adjustable factoring, and then to use that calculated trim value as BLM trim map adjustments. What do you think?

  10. #160
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    Quote Originally Posted by dzidaV8 View Post
    One more thought, as for now this software is for NB tuning. Most of my logs are from driving with WB O2, so the BLMs and INT values are of course useless. My thought is that it would be more universal to add a function to compare two values to calculate an error, e.g. Desired AFR - Measured AFR = Fueling error with adjustable factoring, and then to use that calculated trim value as BLM trim map adjustments. What do you think?
    it already supports wideband or arbitrary input, but as far as calculating difference to target AFR and auto-populating your VE table like it already does for narrowband data, i doubt i'll do that. i never really intended this for wideband tuning anyway.

    although i think if you use wideband value as 'trim' and leave it in 'percentage' mode, then set your target 'percentage' to a fixed afr 'target' it should calculate the fueling error against a fixed target for you, so if you wanted to tune to a fixed open loop value, i think it'll work. (untested)

  11. #161
    Fuel Injected!
    Join Date
    Dec 2016
    Location
    Colorado
    Age
    35
    Posts
    110
    Just out of curiosity, what else are you doing with the program, or what is keeping it in beta? I could possibly try some more masks or maybe another pcm if it would help at all. Least I could do since it got my fuel table in check so quick, and for the extra help. I may switch over to $OD and try from another bin

  12. #162
    Fuel Injected! steveo's Avatar
    Join Date
    Aug 2013
    Posts
    2,639
    Quote Originally Posted by Stokes1114 View Post
    Just out of curiosity, what else are you doing with the program, or what is keeping it in beta?
    nothing, in particular. like all good software i think it should stay in beta until it has a few more users that have done real-world application testing. in other words, waiting for people to fault it or break it or recommend different advanced settings so it behaves better.

    i'd kinda like it to tune maf tables in the clipboard as well, but it's a side goal (and there are two distinct types of maf calibration and i'd have to do both of them).

  13. #163
    Fuel Injected! dud's Avatar
    Join Date
    Jan 2016
    Age
    50
    Posts
    28
    Quote Originally Posted by dzidaV8 View Post
    One more thought, as for now this software is for NB tuning. Most of my logs are from driving with WB O2, so the BLMs and INT values are of course useless. My thought is that it would be more universal to add a function to compare two values to calculate an error, e.g. Desired AFR - Measured AFR = Fueling error with adjustable factoring, and then to use that calculated trim value as BLM trim map adjustments. What do you think?
    I changed line 73 in analyzer_calc.cp from "return trim_in / 100;" to "return trim_in / 14.7;" and compiled the program and it seems to work very well as long as I use "Percentage" mode. Also have to set "BLM Bank A" to your WBO2 and disable the integrator. The WBO2 numbers and narrow band numbers work out to the same error from 14.7 and 128 respectively. Now I have clipboard function with WBO2.

    Please correct me if I'm wrong steveo.

    Here is a screen shot for comparison.
    Attached Images Attached Images

  14. #164
    Fuel Injected!
    Join Date
    Feb 2015
    Location
    Ogden, UT
    Age
    35
    Posts
    140
    Here's a log I took this morning. I'll make adjustments and burn a new chip when I get home tonight.

    Capture.jpg
    Attached Files Attached Files
    Last edited by Chewy1576; 04-19-2017 at 11:15 AM.
    1990 Chevrolet K2500, RCLB, Blueprint 383 TBI (16197427 ECM / 61 lb/hr / 16 psi FP), NV4500, NP241C, 4.10

  15. #165
    Fuel Injected!
    Join Date
    Dec 2016
    Location
    Colorado
    Age
    35
    Posts
    110
    Have decided to try the $OD MAF code.. Have all the parts to convert over and should have it all ready and installed within the week. I will be using the program to get the maf table in check. I will post my results as soon as I start. Thanks Steveo

Similar Threads

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