ECMlink Starting to tune pointers needed

[gofer]

Usually I don't look at rev limit because it's set for 8k from Link, yours, however, is set at 6k so that's why that's happening. Still though, it wouldn't hurt to have a bigger injector in there or, at the least, raising base fuel pressure to 48psi to stretch them a bit more.

This will fix your 6k rev limit ohdamn and should be the last tune I have to put on it before things are good to go. Hopefully that cleans up that little bit of knock you saw, you doing these on flat roads?

You must be logged in to view this image or video.

You must be logged in to view this image or video.

 

[PrimerPLus]

OK I turned up my fuel pressure to 48psi, which helped my injector duty
Also I adjusted my global.

I noticed some knock and I don't know if that is because I increased my fuel pressure?

On a positive note my engine can go past 6k now

 

[gofer]

Unfortunately, I'm working 5:30am to 6:15pm everyday until Sunday now so you'll have to wait for me to get home and pull up the logs. Some knock, 0.4-0.7, I can live but if it's higher then we'll have to pull some timing wherever it starts.

I'll be back in here tonight with an update.

 

[snowborder714]

Are you adjusting your global by changing your injector size even though there's a value in the global calculator for base fuel pressure? If so, change it back and then adjust the base fuel pressure value in the global calculator.

You need to go through and adjust your MAF Comp sliders as your wideband is not lining up with AFRatioEst. The easiest way to see this is to hide all the lines on the graph except for those two. Go through and look at the MAFRaw value and find where it lines up with a Hz value in the MAF Comp tab. Then look at your WBFactor value and adjust by how much displayed in the direction it indicates. For example, at 2000Hz your WBFactor is 7.5%. So go to your MAF Comp tab, find the 2000Hz dot, and move it up 7.5%. Since it's currently at -7%, I'd move it up to 0%. Do this for all the values hit in the pull and then smooth the curve if you see any odd points that stick out. Keep in mind this will raise your IDC %.

In the timing sliders, just to see how the car reacts, I'd drop timing this way:
5000 RPM: 2°
5500 RPM: 3°
6000 to 8000 RPM: 4°



And just to make sure, you did read this all and verify before starting this thread, right?
http://www.dsmtuners.com/forums/ecm...efore-you-ask-ecmlink-dsmlink-log-advice.html

 

[PrimerPLus]

Of course trust me i'm in no rush. You are helping me and I am happy

But as far as knock goes the 1st log peaked at 4.2* and the 2nd was 3.2*
So I will take it easy.

"Are you adjusting your global by changing your injector size even though there's a value in the global calculator for base fuel pressure? If so, change it back and then adjust the base fuel pressure value in the global calculator."

I did not change my injector size. I went to my afpr turned it up to 48psi then I went into link and typed in my injector size (680cc) put in the fuel pressure (48psi) then pressed calculate then pressed use and that is how I got my new global fuel %.

I will go and look at that for the WB. But My gauge and what link reads is dead on.

Yes I looked at the thread. Did I miss something?
Edited: Yes I did not number I will do so now.

 

[snowborder714]

I did not change my injector size. I went to my afpr turned it up to 48psi then I went into link and typed in my injector size (680cc) put in the fuel pressure (48psi) then pressed calculate then pressed use and that is how I got my new global fuel %.

Hmm, that was something screwy on my end. I just closed and reopened your logs and now it shows correct injector size and base fuel pressure. Weird!

I will go and look at that for the WB. But My gauge and what link reads is dead on.

So if you setup your wideband properly in link, the logged wideband value and your gauge should read the same.

However, until you get your airflow dialed in properly, AFRatioEst and your logged wideband value will not. The latter is what I'm noticing in your log. Throughout most of the pull, the LinWideband is reading 11:1 (which I'm assuming is your target), but AFRatioEst is targeting roughly 10:1 (which is what is in your DA table). So you need to adjust MAF Comp sliders to bring the LinWideband reading up to what the AFRatioEst is targeting and line them up. Then you can go into you DA table and change your target (which is all a DA table is) to whatever you'd like. Since airflow is calibrated, it will automatically hit your new target.

 

[PrimerPLus]

Ok I went through and changed the MAF. I have not loaded this in yet but what do you think?

 

[snowborder714]

Looked a bit rough and some values didn't seem to match up with the MAF. Here's one I did. You can compare and see the differences and choose which one you want.

Or load one and do a pull to see how it is and then load the other and do a pull and see if it made it better or worse. Then choose the closest and continue to tweak it to make it better

 

[PrimerPLus]

Haha yah yours definitely looks smoother. I will load it.

Also is this what you meant by dropping the sliders?

 

[snowborder714]

You got it.

 

[PrimerPLus]

How's this look?

 

[snowborder714]

1. Lines are looking much closer. You can now see during most of the pull your WBFactor is only about 1-2%. I'm not really sure what's going on at the beginning of the pull though with that big lean spike. I would start at 1.347 seconds in the log and go from there with your adjustments. They'll be minor, but you can still get the lines closer.

Corey - any input on the lean spike?


2. Your knock is gone, which is good. That means it was real knock. Lets keep it as is for now until we get everything lined up and your AFR's all in check. Then we can slowly start upping it until we see knock again.

3. Your ICD %'s are too high. So, you can either drop the boost a bit or get bigger injectors. We can also lean it out a bit, considering the ideal AFR is around 11:1.

4. Can you post up an idle log after the car is up to temp?

 

[PrimerPLus]

Yes I will post a log at idle. It will be a little bit from now though.

As far as injectors go, any recommendations on what to get?

My HP goal is 350-400.

 

[snowborder714]

Idle looks dialed in well.

For 400hp, nothing smaller than 850's. I'd personally recommend FIC 1150's. They'll give you some extra room and work very well.

 

[NewTurboTuner]

gofer you're a hellova guy to help out like this ...Rep recommendation sent!

 

[c2ypt1c]

At idle, airflowperrev is a little high, combinedft a little low. 0-50hz needs to be lowered a little.

OP - on the next pull, try easing into wot so we can see what the lower freqs look like.

As for the lean spike, it corresponds to the negative values in the 900-1400 range. Also, he's running out of hz at the top (2400hz max). I would do something more like this:

 

[snowborder714]

It averages out to .27 over that whole log. Ya, you can try to get it down to the recommended .26 but it might be more work than worth it.

Yup, CombinedFT is a bit low (-2% average).

Good catch on outflowing the MAF. This really can't be corrected with this version of ECMlink as the MAF Clamp function isn't available.

I'd want to see another pull from 2k (or a bit lower) to capture some good data on those middle Hz points. The last one started right at it, so I probably wouldn't go by it as much. Yes, the dip in the MAF values might attribute to this, but the WBFactor shows more adjustment is needed to get them in line than he currently has adjusted at those Hz values.

 

[c2ypt1c]

This really can't be corrected with this version of ECMlink as the MAF Clamp function isn't available.

I believe the 2g maf limit is 2700hz. I think it's more a matter of it being the lite version, perhaps a 2400hz cap? But, mafclamp would still be useful

the WBFactor shows more adjustment is needed to get them in line than he currently has adjusted at those Hz values.

Yeah, I'm just curious to see how it reacts.

 

[PrimerPLus]

I will make adjustments and do another pull.

 

[snowborder714]

I believe the 2g maf limit is 2700hz. I think it's more a matter of it being the lite version, perhaps a 2400hz cap?

You might be right. I just opened up a log of mine and it goes up to 3600Hz.

 

[PrimerPLus]

Are suggesting I should upgrade to full version?

 

[c2ypt1c]

I just opened up a log of mine and it goes up to 3600Hz.

Yup, same on my end.

Are suggesting I should upgrade to full version?

Well, it looks like you are reaching the limits of v3 Lite. In addition to the mafcomp frequencies, if you track your timing in DA, you can see you're on the max load row. If it was me, I would

* the wind wispers "speed density" *

 

[snowborder714]

It doesn't look to be a necessity at the moment as you're just passed the adjustment range of lite. But if you plan on upping the boost and/or going to a bigger turbo, then you would want to so you can control the extra air.

 

[PrimerPLus]

Sounds good. I am not plannin on going to a bigger turbo anytime soon.

 

[snowborder714]

Well, it looks like you are reaching the limits of v3 Lite. In addition to the mafcomp frequencies, if you track your timing in DA, you can see you're on the max load row. If it was me, I would

* the wind wispers "speed density" *

As long as he stays at the same power level, this shouldn't be an issue. Even if he were to jump up one row on the load (just off the chart), it'd still use whatever's in the last row.

OP, just know if you plan on upping the boost, you'll have some data points that won't directly be controllable because of the firmware limitations of Lite.


Now, speed density....