RomRaider

I have been using this spreadsheet to tune a couple of cars. It's handy if you are usinig microSD logging and have really large files.

I haven't had time to write the full instructions for it. Just enter in data where the boxes are grey. Don't touch anything else.

The purpose is:

1. Keep track of knock sum
2. Tune the MAF scale for closed loop
3. Tune the MP correction table

Keep in mind that you can NOT tune the MP correction table until you are completely done with the MAF scale. I wouldn't try messing with both at the same time. It will make you go around in circles.

Nice work...

Will try get my head around it, and put it to the test this coming weekend...

To add a file, just type the name of the file in the gray filenames area? I tried that and all I get is a error '53' file not found

When I use the microSD logging, it spits out the logs as "log0001", "log0002", etc...

Here is the spreadsheet I tried it in, also the log, just a trial to see if I could get the spreadsheet to work, the engine load column is nonsense, have since changed to a engine load parameter that I know shows numbers that make sense

or do the logs need to be in a specific folder for the macro to find it?

Sorry if it's a dumb question, I can be quite dense at times

Thanks

I ran it. It works fine. You have to make sure that the spreadsheet and the .csv files are in the same subdirectory.

Your scaling for your microSD is off. For example, your engine load is way off. An engine load should be 0.2 to 4.0 g/rev. Yours is like 1051980000.

Ah ha! that was my problem, I had the log on the desktop and the spreadsheet in another folder- Thank you!!

I used the one microSD file generator online to create the code for the parameters, I have since switched to a load parameter that I know works, looks like my MAP parameter is the same way- numbers are way too high, I'll have to try another one

Can I assume that the MP table should be 0'd before adjustments are made to the closed loop section of MAF scaling? and then after the MAF is scaled, then move onto the MP table?

Thanks again!

Yes.

However, DOUBLE check that the rows and columns in the equations are correct. I think I hard coded the equations so it only works for one size... I really need to fix it.

Basically, the last row of the MP table and the far right row should be all zero.

Im trying to get this to work as well. I have the spread sheet and .csv (log) on the same folder. I get a runtime error 9 subscript out of range. Pressing debug, this is highlighted data_array(i) = Mid(line, old_pos, (new_pos - old_pos))

I removed the other data fields not needed and its now looking for knock sum. Macro will not run without knock sum? We only have fbkc and flkc.

It will run without knock sum. It just won't populate that table.

Most likely the log is not continuous. If you add or subtract a parameter while the log is recording, it adds another header table. Just do a search for "Time". If you have more than one header row than that's the problem.

Thx Mickeyd....I'm going to give this a try over the next few days. I zero'd out the MP correction table and I'll first use the MAF tab in RR to scale the CL MAF then use this new sheet to finally scale the MP correction table..

Can someone post up a logcfg file that will work with this tool?

One more thing...if you're logging absolute and relative pressure, do you still need to enter the atmospheric pressure? I last checked mine at 12.33, but don't know if this is a required field.

I have been using this to clean up my MAF scaling and it's doing wonders! LV looks better, and the stuttering is going away. Thanks!

You only need to enter the atmospheric pressure if you are using relative pressure.

I recommend that you use manifold absolute pressure. Just tune everything using manifold absolute.

I am currently using this spreadsheet to tune MAF for the new Cobb intake. When above it is mentioned to 0 out MP correction cruise/non-cruise tables, what I do not understand is whether I should zero them out prior to scaling the MAF (closed loop, cruise MP table). Neither table is currently zero and I am running a stage 2 map (car is stage 2) with my imported from Accesstuner MAF scaling and MP correction tables. The Cobb Stg2+ map ran fine in my car but on this new tune in the ECU now, I have a pretty wicked lean spot in the 2600-3000RPM range that happens very fast, under very light loads like pulling away gently from a stoplight. It is far more apparent in 1/2 gear. I chalked it up to needing MAF rescaled so that is what I was planning on. So, should MP correction tables be zero'd out prior to the closed loop scaling and data collection? And then once the MAF scaling is dialed in within 3% or so, can start tuning the MP correction tables back up from 0?

Thanks in advance!

- Justin