If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Narrowband Tuning Tool

i'm writing a new tool for narrowband tuning as an alternative to using spreadsheet-based tools or tunerpro's history table thing. it will be based on eehack's analyzer, but way more general purpose and easy to use.

for input, you will provide CSV log files.

the program will build a 'log profile' when the very first log is loaded. the log will be parsed for header information and attempts will be made to automatically determine common fields like 'Coolant Temperature' or 'BLM Cell' or 'LTFT' or 'Power Enrichment Active' to build a profile of parameters that are used for BLM-based tuning. i will do some analysis of common XDF files to determine common names.

afterwards the user will be presented with a list of these parameters to confirm that they're correct, and offered the option to select alternative fields instead, or to 'fill in the blanks' if something has an uncommon name. the user can also select unit of measure for temperature based fields or whatever.

then the parameters available will automatically be parsed into a rough 'filter list', with parameters such as 'if closed loop active == true' and 'if coolant temperature > 50' to help reject rows with crappy data. the filter list will be user editable, arbitrary parameters can be added, and will be saved on exit.

this should provide fairly easy to use ecm-independant input from any sane datalogging tool, including scan9495, tunercat, tunerpro with nearly any adx file, eehack, whatever else, and given a reasonable log format, an inexperienced user can probably just press 'ok' at this point and get good results, but an advanced user can carry on adding their own filters to get the best data possible.

for output:

maf or speed density will be selectable. one or two bank o2s. integrator data can optionally be used with a tuneable strength parameter. this will not analyze wideband or power enrichment data.

there will be three modes, and i will work on getting the first mode functional right away.

first mode is the 'works-for-everyone' case to simply output a list of trim averages, so a list of corrections that need to be made to the existing table(s), exactly like eehack's analyzer works now.

second 'manual' mode will provide two VE tables with selectable number of rows/columns and intervals, etc. the user will manually mirror the VE table from their XDF, then they can paste the data in, and it'll spit back out a new VE table.

third 'automatic' mode will load the bin file and make the changes itself (within reason). this will be restricted to some very common masks that i'll add myself to ensure that we aren't breaking bin files by accident. the program will also do some fingerprinting to ensure that we're working on the correct mask. i will add new masks on request.

i'm thinking that new tuners will be able to get a new VE or MAF table nailed with a minimum amount of effort or knowledge with this kind of design.

This sounds a little like i've been trying to write but WAY more detailed.
I used to use TTS Datamaster. Years ago (around 10) i wrote some software to read the PCM data. Originally for the ABS system, then to filter and adjust the maf tables & BLM's.
I think there is a hell of a lot more knowledge around here than there was back then.

Then recently after building the 383 i started looking a better filtering tool to process the data. I only recently managed to start programming again because of this.
You are more than welcome to look at what i've got. It's basically command line type stuff but it does update a copy of the VE tables.
It will read in the CSV file and normalise the headings to a default reference that can be used in the program.
I have a list of matching headings for TTS Datamaster, EEHack, Scan9495, EEHackv2 and EEHack-speedlog, (as you seem to have changed the heading names).
It's a bit hard wired and really needs some form of scripting language that could be processed by the program and rerun.

Then recently after building the 383 i started looking a better filtering tool to process the data. I only recently managed to start programming again because of this.
You are more than welcome to look at what i've got. It's basically command line type stuff but it does update a copy of the VE tables.
It will read in the CSV file and normalise the headings to a default reference that can be used in the program.

yeah that's pretty much the idea. i think an automatic detection routine with a dictionary with manual overrides is key to making it universal but also noobable, i'm thinking a pop up a window with some drop-down boxes would be ideal (it automatically selects its best guess at an entry, but doesn't force you to do anything, and always asks the user if it's a sane choice). i will build a really idiot proof ui for it in qt.

I could help with beta. Runs well enough that I haven't made any changes for a year. BBC lightly modded. Running steady open loop with MAT input. 6395/7427 $OE. I data log in closed loop narrow band and then make my tune for open loop based on that data. If you think I could help just let me know.

My setup

I just completed installing a new motor 383, 10 1/2:1, 225/231 w/.540",114 lobe sep. 36 lb injectors in a Superram[ I've only got 200 miles on it, and the tune is ok, but far from done. I'm using S_aujp v5, attached is preliminary info.3_6_17 SR.binV5 WB.adx

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.