RomRaider

I am pretty sure you did not copy the headers (engine load and/or RPM ) into the Base Timing and Advance pages.

Sweet, this fixed it. I had actually used the WOT filter initially and was left with several islands of WOT data (various short WOT runs). I wanted to just look at one of them so deleted some of the data manually. I'll watch out for that next time.

Thanks!
-Adrian

Airboy, as you probably realize, your spreadsheets aren't usable unless Microsoft Excel is installed, because OpenOffice.org (OO.o) freeware doesn't support VBA for CALC (the OO.o version of Excel). I've just come upon a version of OO.o from Novell which seems to have some support for VBA under CALC. The Windows version can be downloaded from http://download.novell.com/Download?buildid=ESNg0tedRGs~. You'll need to register in order to download, but registration is free.

I've tried running your spreadsheet using Novell CALC. I got a syntax error for the statement "If Max > Min = True Then" which does seem to be a mistake, and eliminating the "= True" part should fix it. That statement was found in: Module 1, Sheet 3, Sheet 4 and Sheet 6. I also got a syntax error for trying to use the "Step" reserved keyword as a variable name in Module 3.

If you get runtime errors, consider being very explicit and avoiding shorthand. In other words use fully qualified names, spelling everything out as if there weren't any defaults. Also consider how to accomplish the same thing if the spreadsheet had to work under Office 98. I suspect the longer a feature has been available, the more likely it's supported by Novell OO.o.

I haven't found a clear description of what's supported and what isn't. Supposedly, this file should work: http://www.linuxtalk.co.uk/linuxformat/hypocycloid-demo.xls, although I got an Undefined variable error pressing one of the buttons.

Some relevant links:
http://marketing.openoffice.org/ooocon2 ... day_g1.pdf
http://www.linux.com/article.pl?sid=06/11/08/1726205
http://wiki.services.openoffice.org/wiki/VBA

If you can get your macros to work with Novell OO.o, you'll be rated a hero by everyone who doesn't have Excel, including Linux and Mac users.

Jon
I would love to be able to port the spreadsheet over to Open Office. I had downloaded the Novell version of the software some months ago. The first thing that I wanted to find out how do was to import the csv files. Spent a bunch of time but couldn't find the relevant info from the help file/pages.

My VBA "skillz" is very limited; pretty much everything comes from recording macros in Excel and then reviewing the code that the program generated. Heck, you have seen the "code" so you know I am not kidding. So, rebuilding the macros in OpenOffice will be a daunting project for me. Having said that, I'll make a note to have another kick at it when I have some time.

Sunny

Airboy, first off thanks for your work on this tool. I didn't start using it until recently but I love it.

One question- have you or someone else incorporated AVCS tables and interpolation?

Admins - Can this thread be made a sticky?

I have sort of done that -- when working with AVCS, I would simply replace the fuel map table with my AVCS one and then run the macro.

Interpolation, like whats in RomRaider?

No, nothing fancy like that. Just plotting the logged results against the map values, interpolating between map cells like the timing interpolation page.

Ok, gotcha.

BTW, great stuff man. I really want to capture all this functionality in RomRaider some day. I'm really really impressed.

I wasn't sure if the acceleration module would work with automatic transmissions, but I just tried it and now think it will work as long as rpm and mph are both logged. The resulting acceleration plot would be similar to a torque curve from a dyno using an induction pickup.

Here's an example. A few members on legacygt.com with 5EAT transmissions have had some bad tunes recently. For comparison purposes, I plotted their acceleration. subyroo is in CO so his acceleration will be lower period but you can see how lumpy it is. His tune was knocking big time.

The VF40-18G was also pulling a lot of timing and I think his boost was set too high (wastegate closed too tight) causing his turbine wheel to restrict air flow. For those who have never seen a VF40, it has a very small turbine wheel (less than 40 mm exducer).

Anyway, I think there is some value to plotting acceleration and using the accel as a comparison between changes to your tune or hard changes. The key of course is to use the same road and try to keep environmental conditions the same.

BTW, I haven't had much luck in calibrating it. No one wants to post log data.



NOTE: I have found that you should use 4 for the smoothing factor and there is a bug in the spreadsheet that requires the time variable not start from 0 milliseconds. Also, if the time variable is too large, it will crash. I'll correct this later but all you need to do is create a new time variable and either add a constant or subtract a constant value.

Airboy,

Once again thanks for all the hard work on this spreadsheet. It saves a ton of time when evaluating logs.

2 comments/ questions-

1. I found there is an error I get when I select the 16-bit ECU for fiel comparison as macro on the boost interpolation worksheet is calling for the "16-b" worksheet that doesn't exist. I change tehe refernce to 32b in the debugger and then it will run.

2. Would it be possible to add some sort of macro that would take the MAF g/s and V readings and logged AFR from a wideband (LC-1 or other know that you can log directly in RomRaider) and compare it to the fuel table and MAF table and adjust the MAF table? I have been doing this manually and it can be time consuming.


Thanks!

Could you pm me the log file and/or the spreadsheet that is giving you problems? I have tried the 16/32 bit switch in the boost interpolation page and it works fine here.

You didn't delete any pages from the spreadsheet, did you?

Sunny, you're right. For soem reason the WG Limits 16b worksheet got deleted. No issue now.

Any thoughts on MAF tuning?

airboy love the spreadsheet thanks for the hard work

question - with the new logger defs for my usdm 02 wrx (a4sgcooc) i've lost the knock correction field... it's seemed to be replaced with new extended parameters that make up the old KC field.

could someone please give my head a slap and help me make sense of this so i can through my logs into airboys (tm) spreadsheet??

thanks in advance

dm