Inconsistent Injector PW at WOT?

[90Vette]

That's very helpful, thanks! I've read and re-read your post several times over the past couple of weeks as I've been working through this. I've also revisited various parts of that doc a few times.

Very interesting that AE-MAP is shown in BPW but not AE-TPS. And you nailed it pointing me to BPW, as you have seen on the Thirdgen thread.

Your document indicates that open loop enrichment values modify the AFR when in open loop. However, I'm not seeing that in my datalogs - it seems that startup enrichment shows in target AFR, but that quickly tapers off to show a target lambda of 1 (even when I'm certain the engine still is in OL). Did I misunderstand your document, or am I missing something?

[84Elky]

TYour document indicates that open loop enrichment values modify the AFR when in open loop. However, I'm not seeing that in my datalogs - it seems that startup enrichment shows in target AFR, but that quickly tapers off to show a target lambda of 1 (even when I'm certain the engine still is in OL). Did I misunderstand your document, or am I missing something?

Would like to respond to your question, but am having difficulty relating it to the document. Would you please expand the question or point me to the document page/area so I can review in context.
Tks.

[90Vette]

Would like to respond to your question, but am having difficulty relating it to the document. Would you please expand the question or point me to the document page/area so I can review in context.
Tks.

Yeah, referring to the section "OL NOT in PE AFR" starting at the bottom of page 30. If I understand the logic correctly, the startup enrichment and the open loop enrichment terms (like 0x41F, OL % change at idle) have the same effect on AFR. However, my datalogs show a target AFR of 1 (lambda, so stoich) as soon as the startup fuel tapers out in the first few seconds, despite there definitely being active open loop enrichment. I've changed open loop idle enrichment from 0% to 15%, and the datalog still shows lambda = 1 in open loop despite wideband readings showing a definite difference in actual AFR.

I guess that's probably just an inconsistency between how the code computes desired AFR and what it reports to the datastream?

[84Elky]

Yeah, referring to the section "OL NOT in PE AFR" starting at the bottom of page 30. If I understand the logic correctly, the startup enrichment and the open loop enrichment terms (like 0x41F, OL % change at idle) have the same effect on AFR. However, my datalogs show a target AFR of 1 (lambda, so stoich) as soon as the startup fuel tapers out in the first few seconds, despite there definitely being active open loop enrichment. I've changed open loop idle enrichment from 0% to 15%, and the datalog still shows lambda = 1 in open loop despite wideband readings showing a definite difference in actual AFR.

I guess that's probably just an inconsistency between how the code computes desired AFR and what it reports to the datastream?

I've rechecked the code against what my doc says and the doc is accurate. Also, there is no difference between what the code computes and what it reports. Once an AFR is computed, it is loaded to variable L00F1. L00F1 is then loaded for L00F3 for DDS reporting. L00F1 = L00F3 is the calculated/commanded value unless in OL (where it is Stoich AFR). So still don't understand why you are seeing other values.

To clear this up and to help my understanding, it would be helpful if you could do the following and then post a .csv file exported from TunerPro:
- Begin logging with key off 2-3 seconds
- Turn key on for 2-3 seconds before starting (reported AFR should be your Scalar Stoich value)
-----EDIT: Discovered that this does not occur. At initialization, $8d does not load Stoich AFR to the Mode 1 DDS AFR variable. Only see zero until engine running. Only then is AFR reported.
- Start engine and let run for 15-20 seconds (Computed AFR should reflect startup enrichment, gradually decayed out in a few seconds and then stabilize)
- Stop log
This will show exactly what's happening.

Please also include the .XDL file in case I need to go deeper with my ADX.

Elky

[90Vette]

I've rechecked the code against what my doc says and the doc is accurate. Also, there is no difference between what the code computes and what it reports. Once an AFR is computed, it is loaded to variable L00F1. L00F1 is then loaded for L00F3 for DDS reporting. L00F1 = L00F3 is the calculated/commanded value unless in OL (where it is Stoich AFR). So still don't understand why you are seeing other values.

To clear this up and to help my understanding, it would be helpful if you could do the following and then post a .csv file exported from TunerPro:
- Begin logging with key off 2-3 seconds
- Turn key on for 2-3 seconds before starting (reported AFR should be your Scalar Stoich value)
-----EDIT: Discovered that this does not occur. At initialization, $8d does not load Stoich AFR to the Mode 1 DDS AFR variable. Only see zero until engine running. Only then is AFR reported.
- Start engine and let run for 15-20 seconds (Computed AFR should reflect startup enrichment, gradually decayed out in a few seconds and then stabilize)
- Stop log
This will show exactly what's happening.

Please also include the .XDL file in case I need to go deeper with my ADX.

Elky

Hey Elky,

Sorry for the delay - haven't forgotten about this, my datalogging is just on the fritz. Once I get datalogging and a few other issues sorted out I can get a TP log of startup. In case it helps, here's a CSV log (from ALDL Scan) of startup. It matches your observation that Target AFR is 0 until the engine is running. Otherwise I'll post another log as soon as I can.

[90Vette]

As promised, here's a TunerPro log. It was taken with ALDLDroid, but it should be identical to one taken with TP.

[84Elky]

That log looks perfectly normal. Startup enrichment has been applied and is slowly being decayed-out as time passes. Perhaps I've lost what the issue is.

[stew86MCSS396]

As promised, here's a TunerPro log. It was taken with ALDLDroid, but it should be identical to one taken with TP.

Sorry for the OT post but I can connect just fine with ALDL Droid but using the same ADX, TunerproRT doesn't connect. Care to share any insights or the ADX you're using to quiet the CCM? thanx!