First time logger, base map & MickeyD stage 1 maps

So I decided to go the open source route and logged some base runs, as well as MickeyD's stage 1 runs. Please give me some constructive information and/or help if needed. Also included is a Learningview screen shot. Car feels good and seems to have an increase in power. Thanks.

 

I didn't use all of the same parameters, but I hope it will be enough to help. Also, the larger logs include some normal driving. The others are 3rd gear WOT and a 2nd gear WOT.

 

Please be gental, this is my first attempt at tuning:spin:

 

Let me know needed parameter changes for my next log.

romraiderlog_Base 1.csv

romraiderlog_Base 2.csv

romraiderlog_20091006_213155.csv

romraiderlog_20091006_213325.csv

romraiderlog_20091006_213453.csv

romraiderlog_20091006_213528.csv

I noticed my base and total timing are most off at about 50% accelerator pedal angle, should I adjust my base timing to reflect the total timing?

You need to log fewer parameters. The logging interval is too great.

 

Get some logs done like this.

 

http://www.romraider.com/forum/topic4254-30.html

 

You want to look for knock sum incrementing. When knock sum increments, that's perceived knock. At low rpm (<2000) and/or low load (< 0.8 g/rev), the knock that the ecu thinks it hears might be noise.

I downloaded the new logger and ecu data from romraider yesterday and I noticed there are a lot of new parameters, but some are missing (target boost, knock sum)

Anyone know why this is?

I believe you need to connect to the ECU to see those parameters; they're still there

Yeah, I figured it out. Here are two 3rd gear WOT logs using the parameters from MickeyD, with a learning view screenshot after the pulls. It looks pretty odd, especially my IAM number Feedback appreciated!!!

romraiderlog_20091007_163034.csv

romraiderlog_20091007_163143.csv

What octane are you using?

 

Subtract about 1.4 degree of timing at 5200 rpm and 2.0 g/rev. Subtract 1.4 degree of timing at 5200 rpm and all columns above 2.0 g/rev. Then take a look at what it looks like around it and subtract timing around it to clean it up.

 

Don't be afraid to log your entire drive. It'll end up as about 250 kilobytes but it's easy to process it using EXCEL. The whole log will give you more info.

Thanks for the info. I'm running crappy 91 octane from Utah, but I always use Chevron. I also noticed my peak boost is around 13.1 psi, instead of the 15.9 on my table. I take it's because my atmosphere pressure is in the 12's and the table is set for sea level? Is it safe to increase boost to compensate? I'll try to fix the timing first, then mess with the boost. Thanks again for the info.

Thanks for the info. I'm running crappy 91 octane from Utah, but I always use Chevron. I also noticed my peak boost is around 13.1 psi, instead of the 15.9 on my table. I take it's because my atmosphere pressure is in the 12's and the table is set for sea level? Is it safe to increase boost to compensate? I'll try to fix the timing first, then mess with the boost. Thanks again for the info.

 

I think you would want to adjust your WGDC table. The target does not change, how you try and get there is what needs to change.

Thanks for the info. I'm running crappy 91 octane from Utah, but I always use Chevron. I also noticed my peak boost is around 13.1 psi, instead of the 15.9 on my table. I take it's because my atmosphere pressure is in the 12's and the table is set for sea level? Is it safe to increase boost to compensate? I'll try to fix the timing first, then mess with the boost. Thanks again for the info.

 

The target boost table is for sealevel. There is an atmospheric compensation table. Then use Airboy's spreadsheet to calculate your corrected target boost.

 

You shouldn't have to change your target boost.

 

When starting with an base map (not customized for your car), it's alwasy best to start with a lower WGDC (lower BOTH WGDC initial and WGDC max by the same percent). This will cap your boost. Then slowly up the WGDC as you check for knock and overboosting.

 

For example, you may have other cells that are knock prone but you haven't discovered them yet because you haven't driven through that range.

Ok, I will drop both WGDC parameters by 2%, does that like a good number?

I was thinking more like 20%.

 

Then raise it 10%.

 

Then raise it again 10%

Oh, ok. I have not made the changes to romraider yet, but I'll do it now and reflash

Alright, I used the logging parameters MickeyD suggested, as well as dropping both WDGC's 20%. here are two WOT logs in 3rd gear.

romraiderlog_20091009_143008.csv

romraiderlog_20091009_142802.csv

I would subtract 1.05 degrees in the cells 6000-7000 rpm and between 1.7 and 3.2 g/rev. Basically, remove 1.05 degrees from the lower right corner of the base timing table. Do this in ALL the base timing tables.

Thanks for the help MickeyD, I'll post some more logs and learning view tomorrow. Is the another map aside from the ingition timing advance base map I need to change?

Here are some logs after some tweaking. I already pulled timing in the areas needed, but have not reflashed. I've only driven about 10 miles so far with these settings. Included are 2 3rd gear WOT runs. Any other areas of concern, aside from the timing I've already addressed? I will reflash in the morning and hope for better results. I'm also hoping once I get the settings fairly knock free to feel some extra power. So far I really haven't much of a difference, but I've also not let the ecu "learn" as I've been reflashing trying to dial in safe settings.

romraiderlog_20091012_211738.csv

romraiderlog_20091012_211907.csv

It's knocking like crazy.

 

If you already knew it was knocking, you shouldn't do anymore WOT logs until you reduce timing.

Those were the only 2 WOT I've done. I brought WGDC up 10% from a 20% decrease and tried to clean up the timing. I will drop back WGDC 10% again and reflash. I've reduced the timing and tried to clean up the areas around the really bad timing in RR. Any other suggestions mickeyd? I might flash back to stock and do some better logs if these changes do not fix my knock problems.

What changed from post #14 to post #17?

 

Take it one step at a time.

 

Your WOT logs in post #14 weren't too far off. Clean up your timing from there FIRST. Then bump up WGDC.

Ok, I fixed the map and the logging looks much better. Also attached are 2 learning view shoots. One right after both pulls and the other after driving around for another 10 miles or so. I noticed my knock correction advanced were all in the positive, going all the way up to 6 degrees. So I'm guessing it's adding timing in those areas. Do I need to do anything about that?

romraiderlog_20091013_102659.csv

romraiderlog_20091013_102529.csv

Don't log AF correction.

 

I also don't log Knock Correction Advance or Vehicle Speed, or Fine Learning Knock Correction Advance. If you do a learning view before and after the logs, those values aren't needed.

 

The big thing to look for is Knock Sum and Ignition Total timing. That pretty much tells you everything you need to know about knock.

 

Vehicle speed is only necessary if you have a 5EAT or if you are trying to figure out if your clutch is going.

 

Anyway, this set of logs look good.

 

I would do another log and take it up to redline to make sure that the high rpm knock is gone.

 

After that, bump up WGDC and see if you still knock.

Here is a learning view shot from the end of the day. should I let the -1.05 work itself out, or pull timing in the parameters where it's present.

So, with increasing the WGDC this causes more boost to build up before the wastgate opens, thus increasing power, is that correct? (I'm new to this, so forgive my ignorance)

Log more of your driving.

 

The -1.05 was probably one knock event. It would be nice to know where it occurred so that you only pull timing in the area where it knocked.

 

I recommend that you go ahead and log 100% of your driving AFTER the engine has warmed up. If you are using the new Tactrix 2.0 cable, the microSD logger is in beta testing. There's a thread on openecu.org about it.