ECMlink Locking in Open Loop, wideband switch point

[LiquidX]

Yeah, it's crazy, that's why I added the little poll. I tried to go and edit after posting it to put in "Yes, I'm going to bug Calan now about my setup" .

I'm still working on copying over Corey's table to use a a template then I'll head out and test some stuff out.

 

[Calan]

Yeah, it's crazy, that's why I added the little poll. I tried to go and edit after posting it to put in "Yes, I'm going to bug Calan now about my setup" .

Didn't even notice the poll...and... bite me.

I'm still working on copying over Corey's table to use a a template then I'll head out and test some stuff out.

Or... you could just copy the one out of the log that Sam posted here.

 

[LiquidX]

Well I have both now

They are both similar but the idle and low load cruising is the biggest difference IMO. I'll see which is more accurate for my setup.

Then again, I have a fellow DSMers wedding to get to at 1pm.

 

[Calan]

Then again, I have a fellow DSMers wedding to get to at 1pm.

If he has any sense, he'll ditch the reception (if not the ceremony) and take off with you to help tune your car.

 

[LiquidX]

, I've been trying to help him get his car running.

I'll see if I can get any progress today. After the wedding I have a dinner to attend and I'm unsure how long that will last. Hopefully something today, if not then it'll be tomorrow.

 

[LiquidX]

Ok Craig. I started off with the values you gave me, zeroed out my global, and uploaded Sams VE table. Needless to say it didn't start .

I had to add global to get it to idle, transfer that value to the injector battery table (IBT from now on) and then go back and zero out the global. It was ok, my AirflowPerRev was high so I lowered all the values in the VE table by the same amount and a little less in other areas to get it where I wanted.

I found out that trying to go below 0uSec global actually shuts the car off (with me it did) even though the values in the IBT were set to have a 0 global. I decided to just raise it to 100uSec global and adjust the IBT accordingly. This way I still have some play if I need it without having to go back-and-forth to the IBT and make minute adjustments.

Our gas around here 91 oct has 10% ethanol added if that means anything for you.

The values on the IBT currently are where my idle is set good and when the fan kicks on, my RPMs don't suffer and make the car sputter. I still need to transfer the values to the lower voltage levels so they work as they should in case I would ever drop down that low.

I think the idle can be tweaked a little more to get me closer to 0% combined FT but overall I think it's looking good.

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

 

[Calan]

I found out that trying to go below 0uSec global actually shuts the car off (with me it did) even though the values in the IBT were set to have a 0 global.

Which is why I said:

...If you want to use a global value and have it represent an offset from the stock values (which I would recommend), then you ...

Why are you against setting the global value to the 435us and just tweaking it as needed? I think you are making this way harder than you need to with all the transferring to the table, zeroing out, etc.

I would set the global to 435us, use the adjusted voltage table values (second example up there ^^^), and not even mess with the table until way on down the line when you get everything dialed in pretty close. Simply adjust that initial 435us global value to dial everything in and ignore the table for now.

Our gas around here 91 oct has 10% ethanol added if that means anything for you.

That would put your global fuel to something around -62.6%, instead of -64.2%. As shown in this post over on the ECMLink forums, that can make a big difference at higher points in the VE table.

How does the offset uSec work under AFRationEst?... I'm assuming its for a delay?

...

Oh what's this, the master fuel tuner doesn't know this feature?

Ok...since you challenged me to find out:

Think of fuel flow factor as a global scale and "offset" as a deadtime adjustment. But please don't bother changing those values or suggesting to anyone else that they change them. They can be used, for example, to force AFRatioEst to match a wideband reading, but that's *really* not the right approach and we intentionally named those fields in an ambiguous manner to discourage anyone else from fiddling with them

 

[LiquidX]

Well Craig, here is a log I just did. I've been out and about and been doing logs while driving. I did a few VE table adjustments for CombinedFT. Here is the latest, it's just an idle but it's even better than before and the VE table so far is looking good. I'll prob. do a few more tomorrow if I go out anywhere but it's coming along pretty well now.

Honestly, I just think it was a "look at me, I have a lower global deadtime, aren't you confused!?!?!? ", not to mention, it just seemed to work better for me? That or I just liked trying a new approach which seems to work well.

So don't bother messing with the offset for AFREst, it would be nice to have them match right up perfect buuuuut, it isn't the right way and wouldn't be as accurate for a reading.


Still just the 2 of us

 

[Calan]

That log looks good... although I would still rather see a global deadtime value that "makes sense" instead of a random value.