RomRaider

I just change the values in the table and re-interpolate using the existing log data to see where it puts the next revision. A couple of guesses and I can end up with a smooth timing curve.

Exactly what I do, after a while it becomes somewhat intuitive.

Jeff

"Mark Anchor Cells" is and the double verticals revealing the bias is pretty neat, Airboy. I hadn't realized the additional info. (more suggestive of the actual curve) revealed by doing this. Thanks again.

This is all well and good, but how do you determine where knocking ocurrs or problem areas using the spreadsheet for non WOT logs? Like everyday driving?

The spreadsheet will, as it is intended to, interpolate data logs at any TPS. It doesn't care what TPS is except on the Boost/WGDC interpolation page, where you can check part throttle boost control. The 100% TPS filter is there as a convenience. As long as you logged Engine Load, RPM, Timing, etc, you can see where timing is off.

^^ I decided to try this spreadsheet today as it is highly recommended by everyone but all I end up with is a lot of runtime errors..

I think the problem lies with the fact that the JDM maps are a different size to the ones you use. For example the base maps that came with the spreadsheet are 18x19 whilst the JDM one for my car is 18x16. Please correct me if I am wrong..

I am using Excel 2003.
I am logging 2*g/rev and not g/rev.
I have a 16bit ecu.

Any help would be greatly appreciated...

Did you read the instructions on the first page of the spreadsheet? Look for the description for "Align and Move Copied Table". The size of the table is not the problem. Does your transfered timing table look like the one in the screen shot on the first page of this thread (where the [Table3D] tag is in the top left corner of the table)?

As RomRaider definitions uses g/rev for engine load, logging 2*g/rev will not be useful for comparison with map data because the timing and fueling tables all reference g/rev. You'll need to manually convert the data that you have or log some more using g/rev.

If you are still having runtime issues after that, you can send me a copy of your spreadsheet and I'll have a look.

Hey, thanks for your reply. I did read the instructions, I guess manually moving it into place wasn't the solution

I will take some more logs with g/rev...

<offtopic>
I can whip up the forms you have into a window that may make life a little easier. As soon as I can get everything working and I understand the workings, I get to it
</offtopic>

its kinda late so i am to lazy to read thru this but does any other excel typ program run this? or am i goning to have to go and steal sx of P2P network lol. dont like doing that but for somereason i have vista office and yet it does not include excel hmm. it always use to be on the older windows version that office included excel and all those OFFICE programs lol. i guess they figured that the ppl who needed it would jus ripp it off anyways.

Like it says on the first post , the macros uses MS Visual Basic for Applications so it is specific to MS Excel. Sucks, I know. I tried to work with Open Office but that was even more painful than working with Excel.

Haven't heard of Office Vista before

I finally downloaded OpenOffice 2.0. The syntax appears to be totally different. Even my simplified interpolation function doesn't translate.

yeah i went ahead and tryed openoffice also it all loaded like it was going to work put nope. u think a old copy of excel like MS office 97 would work my dad said he had a copy collecting dust at work? and there is a trial version of MSoffice Xp i think its a 60 day trial. i really dont like ripping off microsofts software so hopefully ill find a cheap way out. oh maybe if gas wasnt almost 4$ a gallon here i would jus buy the dang thing

something wrong with the graph... please help

Post your csv or better, post your xls file that generated that plot.

I am going to guess that the log file has a lot of items (long sampling intervals) and contained data after you let off of the accelerator and was slowing down.

The calculations would have better resolution if only log RPM and throttle (so that you can filter it).