gp90gta

iTrader: (1)

So I was asked in another post if I would share my BLM excel tool, so I decided to start a thread.

I'm going to attach the file and tell/show you how I use it and how I set it up. The formula is from Traxton's tuning thread= your recorded blm in a given cell at a given rpm&kpa/128*the ve cell that matches= new ve cell number.

I setup a histgram in TPv5 to record the blm's, then I do a datalog for about 15-20min, save then run it. You can view the histgram in different ways by the view tab at the top. I use the running adveage then do a Ctrl+c to copy it, then I paste it in my excel tool (not excel, its openoffice.org but works with excel), I then copy my ve table and paste that in the tool, the new values will be at the bottom, then copy paste to my ve table.

Okay things to note.
1. Make sure your in CLP before you start that data trace.
2. All things like CCP,AIR,EGR,PE should be disabled before.
3. Small throttle changes.
4. If you shut the car off and dont stop trace, the first cell keeps adding.
5. When you copy&paste new value, there will be cells with zero, just have two of you bins and do a compare, highlight the zero cells then hit the compare tab, copy, hit compare again, paste.
6. The obvious it that there are going to be high or low spots after, you need to smoothen out, you can do it with the smooth tab in TP or by hand in the graph.
7. If you only do the lower table you have to fix 1600rpm cells in the upper.
8. Set all things that need to be changed first like Inj constants, cyl vol, inj offsets, prop gains, the more things you correct first before, you will have better results.
9. I know there are more things, I just cant remember right now, I'll add later.

Next post I will show you how to make histograms in TPv5, it can be used for all kinds of things like spark, blm cell, knockand timing, basically you can do one for anything that comes out of the ALDL.

Also just for everyone to know, I have never worked with excel before making this, so feel free to change anything you like on it, as I have no idea of how to make it look better or lock the formula so that you cant change it, if thats even possible. I would have liked to add borders and color but like I said I have no idea of how to do that and since I made it some time ago and it works for what I want it to do, I'm okay with it.

DISCLAMER
I am not responsible for how you use this file or any damages done to yours or anyone else's property.

There is three sheets, first one is for lower ve table, second is upper and the third is for extended table.

BLMFIX.zip

gp90gta

iTrader: (1)

First I'd like to say that if your using TPv5 and you haven't made a donation that you should, I can only imagine the amount of time and work Mark put into making it, we should all be very thankful of his hard work.

Okay histogram time, load you adx file in tp, on top acquisition, edit definition, click on history table and add new item, give a name and id, output object is going to be blm, next click on rows, row count ( here were doing the lower table first) 13, this is going to be our rpm's so object here is rpm, fill in the row like your lower ve table, so 400rpm in the first and 1600rpm in the last, next click on columns, column count 13, fill in again like you ve table, starting in 20kpa all the way to 100kpa, for obvious reasons object is kpa, now save.






So now you have something that looks like this. Next up how to use it and how to use it with the excel tool.

EagleMark

Nice!

The only thing I could add to the recording of data for BLM is to have vehicle totally warmed up along with the things your mentioned turned off. Watch BLM (not while driving) and fill in as many cells as you can.

I did one similar awhile ago and I think it will help people understand how the rows and columns need to match the VE table of bin.
http://www.gearhead-efi.com/Fuel-Inj...es-in-TunerPro

When done the smoothing takes a little practice. You can use a setting from .01 to.99, I use .50 and start at cells outside the VE cells I have changed that are higher or lower and work them all around the cells you have changed, using the 3D graph really helps find the high or low points, but work all the ones around what you have adjusted. If you hold the CTRL key you can spin the 3D graph for any perspective!

I also agree with paying your small $30 donation for TunerPro so we can have an affordable tuning program with future updates. If you ever use it and realize the options built in you will see it is truly a totally customizable tuning program for bin and data recording and because of that you can also set up data tracing to see exactly where you are in bin file from data being recorded!

Again very nice work!

MikeT 88IROC350

Ok, good, so where is the rest of your post?
My ADX file came with the 3 histogram tables allready created, and they look correct except one thing. The BLM lower table has 14 rows, goes to rpm=1700.
There was some comment in the definition why there was a 1700 row.

Now i just cannot get any data to populate the table. I am playing back a recorded log, but nothing shows up in the table. I am sure i enabled data tracing for the log. I think the sample count is at 10. This looks like a very usefull tool, if i can get it to work. Thanks for any tips!

JP86SS

iTrader: (1)

even though your VE table only goes to 1600, anytime you log data and are higher than 1600 rpm the values will accumulate in the highest row.
this renders the 1600 row (if it the highest) unusable.
the 1700 row ensures your 1600 row has good data.

MikeT 88IROC350

OK, i think i understand......So having the extra row at 1700 ensures the 1600 row data is good? I was actually going to edit my table and take that row out, just to avoid the confusion. But i really need good data, in the 1600 row especially, since that rpm gets hit quite often.
I think i am going to take my ride out today for a scan and test of this histogram.

gp90gta

iTrader: (1)

JP is correct, I didn't realize this when I first made my histogram tables, the data collected by TP in the histogram will be incorrect in the last row of the lower and first row of the upper ve table, to correct this just add a 1700rpm row in the lower table histogram and 1500rpm in the upper ve.

Also one other note, if you have an emulator, like an ostrich or AUP1, you can really speed up your VE table corrections with the help of a second person, what I like to do is lock the car in open loop, then use data monitor in TP, set commanded AFR to stoich, pull up MAP, RPM, O2 and WB (if you have one) on the monitor, setup data tracing in TP, minimize the monitor and pullup your VE tables, this way you can see the VE tables and the monitors at the same time, adjust VE tables to match stoich by using the trace cells and the NB O2 & WB, make sure the person driving holds steady in the cells you need to adjust, smooth out VE tables once done and recheck, the reason I like to use stoich as the set point to adjust VE tables is because this way I have two sensors for readings, the NB does a good job at reading around stoich imo, at this point you should be very close to 128 blm's when turned back on, now you can use the tool to fine tune your BLM'S.

MikeT 88IROC350

Good to know. The ADX file i acquired already had the 3 histo tables created, and had the extra row. For the upper table, the first row is at 1200rpm. So i should be ok. The problem i had, was these tables did not have the X&Y axis defined, as well as the output Z. Once that was done, all was good. Did a good road scan the other day, only working on the lower table, pulled into Excel and made a new chip. Havent gotten any new data yet. So how close to 128 can you get with a SD setup? Most of my experience is with my camaro, with a MAF engine.
I dont have an emulator. Looks interesting. This '90 Y-body is mostly stock, so i am just doing what i can. My IROC has a LM1 WB, and i pull that data into the ALDL. It's all fun!

MrWillys

I want to thank the OP for this thread. I've been using Datamaster for well over 10 years and they are no longer supporting it. I paid for my license through Moates as Dave helped me yesterday. This thread helped me enabled the histogram which is even better. Next, I'm going to read up on how to use the spreadsheet. My goal is to build a webpage explaining how to use this software. As a retired Carpenter and former Apprenticeship instructor I would like to make a comment to the code writers. Please attempt to lower the difficulty of understanding. While I may know how to cut a roof. How can I make it easier for other to understand. We are all visual, audial and kinesthetic learners.

MrWillys

I have built my Histogram tables both ways as discussed in this thread and the upper and lower are not the same at 1600? The arrive at different averages?

MikeT 88IROC350

aaaa, yup, you will have different data for the row of 1600, from the upper and lower tables. I just made an extra row in my spreadsheet, and just averaged the data from the 2 tables, for 1600 rpm. Dont ask my why this happens, cuz i dont know!

Also, you may not have data populated in each column of kPA, so just use the values you get. HTH,
Mike

MrWillys

So thinking outside the box? Why do we have to have 2 tables? So I built a single table with 13 Columns and 23 Rows.

MikeT 88IROC350

No reason not to think out of the box! i like your 1 table for all values in the histogram. It was likely that the OP, made 2 histogram tables, to match the separate upper and lower tables in the $8D def file. So have you made a log scan with this single table? Is the data for row 1600 rpm valid? What about in the upper rpm areas, like 25kPa at 2000rpm? That data point was not in the upper histogram table by itself.

I might just make this one big table myself. Right now i am still playing with IROC camaro, (MAF car), but soon will get the laptop on my '90C4, and that one is a SD car.