RomRaider

*Originally created on my MacBook, so it may look a bit different on windows



This is an excel spreadsheet that can be used to build a base map and (in future versions) tune the CarBerry ROM. You can use logged data from a MAF tune or SD tune to build a new VE base map, calculate an SD multiplier/offset, correct injector flow scaling, and build a new IAT compensation table.

Let me know if you guys have any issues, or discover any bugs. All the cells that shouldn't be changed are locked, so you shouldn't have to worry about changing the wrong values.



The Theoretical Engine VE values and strength values need to be tweaked. Right now they are just values that I guessed. If you have a lot of data you can try to adjust the values so that the calculated values follow the same curve as the logged data. When using an SD offset of "0", you can un-check the "Use Theoretical Engine VE" checkbox and the VE map will effect fueling in the same way as using the "calculated SD offset" with a VE map of all "1.0000".

Here is a 3D rendering of a VE map calculated entirely from a logged Map.vs.Load slope, using a "0" offset, and using the standard "Theoretical Engine VE" settings.

Does this work with excel 2003?

Do the cells need to be given exact names (as in the intro section)? I cannot get it to import the data.

Thanks

Thanks, going to try it over the weekend.

I found a couple bugs in the spreadsheet this morning. v1.0 may give incorrect results depending on the options you have selected. Please use v1.2+.

@fastblueufo - I don't think excel2003 will do the macros with .xlsm. And my Mac doesn't have the option to save in the old format. But this might work (lmk if it does) --> http://www.microsoft.com/download/en/de ... ng=en&id=3

@td-d - The spreadsheet looks for specific logged parameters(from romraider logger) as described in the intro section. If it doesn't find these it won't fill the data columns. Also, you may have to give it a second to import the data. Ive noticed on my Mac that it can take 20-30seconds to import, and much longer if you have it setup to correct the data based on IAT. I have heard that Mac takes a long time to do excel calculations, so it should be faster on windows. But just so I know there isn't some kind of program bug, could you PM me the log you are trying to use?

Ah... that would explain it, I'm using onboard SD logging, and I've renamed the parameters. Normally I'd just go in to the VB code and change it, but I see you've locked it

If you can post the exact titles that it's expecting, I can change the headings. I want to try and use this to tune the 32bit SD hack that Merp wrote and I've ported for my rom.

Thanks - btw - as a 32 bit ECU owner, I'm very jealously looking at this project, incredible work!

Thanks, hopefully we will see more 32bit developments in the near future. Im sure between Merp and NSFW we should see some good stuff

Right now the spreadsheet just builds the base map. I have another spreadsheet that I made over the summer that does CL/OL tuning, it just wasn't very user friendly. Im planning to transfer all the code over from that and add the functionality to this spreadsheet (and clean things up at the same time).

Does the 32bit SD use a constant that MAP is multiplied against? The SD multiplier in this spreadsheet is created from the ideal gas law combined with a base(pivot) air temperature, engine displacement, and revolutions per cycle. If the 32bit system is the same or similar I would assume the base map function would work. When I finish the tuning part, I think tuning will work regardless since its just averaging values into a 3D table and applying corrections based on AFR targets or, in the case of closed loop, A/F correction.


To help your issue, I will add the ability to define the header names in the spreadsheet. Right now it just looks for the parameters as they are listed in the intro followed by the units ex. Manifold Absolute Pressure (Direct)* (psi absolute) or Engine Speed (rpm)

I'll take a look at this tomorrow morning at work. Anybody able to save it as a 2000 or 2003 file?

New version up, you can change the parameter headers that the spreadsheet looks for when importing a log. Also added a "strength modifier" to the Theoretical Engine VE calculations (this is still experimental).

The new version is giving me a " run time error". I using Office 2010 Windows 7.

Did you enable macros? Usually at the top it will say something about security and it will have a button that says "enable content". You have to click that button.


When are you getting the error? When trying to import a log?

Yes , I enable macros. I get the error when importing logs and building map.

^^^ could you PM me your log and a screenshot of the "run time error"?

Do we set IAT pivot to the average temp recorded on a MAF log for conversion?

In theory, if you have the "autocorrect load based on IAT" checked you could set the IAT pivot to anything you want (as long as you don't change it after you import the data). The IAT pivot would probably be best, set to the average IAT values of the engine through its operating range (vacuum to full boost).

From my experience, if you are using the MAF for the IAT sensor, its best to un-check the "autocorrect load based on IAT" and set the IAT pivot to the average IAT temp recorded in your logs, as you stated.


If you were using an IAT mounted in the intake manifold, I think the "autocorrect load based on IAT" should be checked and you should set your IAT pivot to the average logged IAT (must be set before importing log). Average IAT would probably be much higher with an IAT mounted in the intake manifold. However, I haven't tested the Map Builder on a car with the IAT in the intake manifold so I'm not sure what works best.