[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/db/driver/mysqli.php on line 258: mysqli_fetch_assoc(): Couldn't fetch mysqli_result
[phpBB Debug] PHP Warning: in file [ROOT]/phpbb/db/driver/mysqli.php on line 320: mysqli_free_result(): Couldn't fetch mysqli_result
rusefi.com The most advanced open source ECU 2025-10-09T14:50:57 https://rusefi.com/forum/app.php/feed/topic/1546 2025-10-09T14:50:57 2025-10-09T14:50:57 https://rusefi.com/forum/viewtopic.php?t=1546&p=50991#p50991 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> the table is named tps-tps, but actually it has tps-from on the x axis and tps-to for the y.
immagine.png

Statistics: Posted by angor — Thu Oct 09, 2025 2:50 pm


]]>
2025-09-27T17:31:06 2025-09-27T17:31:06 https://rusefi.com/forum/viewtopic.php?t=1546&p=50912#p50912 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> Statistics: Posted by mpgmike — Sat Sep 27, 2025 5:31 pm


]]>
2025-09-24T10:10:15 2025-09-24T10:10:15 https://rusefi.com/forum/viewtopic.php?t=1546&p=50897#p50897 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> I know this is an old topic, but I've got the same problem: in the tps-tps table, the "cursor" move actually only over the diagonal. It seems that the ECU isn't able to see the transition from a tps to another.
Indeed, the accel enrichment is always 0.

It almost seems like the time constant for calculating the delta TPS is too low, meaning very fast movements are essentially needed to detect it.
I may have understand from previous posts that this time can be adjusted using the "cycles" parameter of the AE configuration. Is it right?

Statistics: Posted by angor — Wed Sep 24, 2025 10:10 am


]]>
2019-04-24T00:29:03 2019-04-24T00:29:03 https://rusefi.com/forum/viewtopic.php?t=1546&p=32876#p32876 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
With a perfectly functional method at the moment there is no reason this could not be shelved until more important things like the ETB are working.
The current method covers the most critical throttle movements so this would just be additional for drivability and final few % of power.

Statistics: Posted by Simon@FutureProof — Wed Apr 24, 2019 12:29 am


]]>
2019-04-24T00:07:15 2019-04-24T00:07:15 https://rusefi.com/forum/viewtopic.php?t=1546&p=32875#p32875 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
How hard do you think the change would be? I'm willing to give it a try and test it out.

If it works I could probably write the documentation, after all if "its your stupid idea, your write the notes" right? :)
How important do you think it is? If I can use your skills I would really prefer to use your skills somewhere else pretty please. Very little time to play with all this and too many ideas. At the moment my focus is around https://rusefi.com/forum/viewtopic.php?f=5&t=592

Statistics: Posted by AndreyB — Wed Apr 24, 2019 12:07 am


]]>
2019-04-23T23:42:59 2019-04-23T23:42:59 https://rusefi.com/forum/viewtopic.php?t=1546&p=32874#p32874 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
If it works I could probably write the documentation, after all if "its your stupid idea, your write the notes" right? :)

Statistics: Posted by Simon@FutureProof — Tue Apr 23, 2019 11:42 pm


]]>
2019-04-23T23:37:53 2019-04-23T23:37:53 https://rusefi.com/forum/viewtopic.php?t=1546&p=32873#p32873 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
The reason I ask about TPS delta as the Y axis is again, improved resolution.
I would never have time to make the change, AND notify all the users about the change, AND update existing documentation :(

Statistics: Posted by AndreyB — Tue Apr 23, 2019 11:37 pm


]]>
2019-04-23T23:39:37 2019-04-23T23:36:30 https://rusefi.com/forum/viewtopic.php?t=1546&p=32872#p32872 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> That log above was taken with the axis offset and for now it is probably better if the axis are offset.
Considering we never need the "TPS from" value to be 100% as we would never be able to do a TPS from 100%/ TPS to 100% acceleration.
Offest axis TPS AE.JPG
The reason I ask about TPS delta as the Y axis is again, improved resolution.
When considering the physics of the air/fuel in the inlet manifold it matters less what the numerical value of the TPS position reached and more how much change in air flow area we created and thus how much change to the air in the inlet ports.

Without digging too much into the physics we simply need to know what position the throttle was at when we started the change (the starting conditions of the air) and the TPS delta (how much we upset the air/fuel system).

Setting the table up as "TPS from" on X axis and "TPS Delta" on Y axis means we can set the table up as below and gain a lot of room for tuning.
The bese settings of the table is pretty simple as well, its just a curved surface, highest extra fuel at lowest "TPS from" and highest delta, lowest in the opposite corner and mid values at the other two corners. (see mock up below).
IPS Delta method.JPG
I think this is how some of the older OEM ECUs deal with this as well, when ROM space was much more of a premium a 5x4 table is enough to achieve pretty good enrichment once interpolated and corrections added.

Statistics: Posted by Simon@FutureProof — Tue Apr 23, 2019 11:36 pm


]]>
2019-04-23T22:42:12 2019-04-23T22:42:12 https://rusefi.com/forum/viewtopic.php?t=1546&p=32869#p32869 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
Is there any reason I cannot set my X axis different to my Y axis?

So have 0, 1, 3, 8, 13, 25, 40, 65 on my X axis and Y set 1, 3, 8, 13, 25, 40, 65, 100?
I would expect that you should be able to change X and Y independently?

Code:

      xBins       = tpsTpsAccelFromRpmBins,  TPSValue      yBins       = tpsTpsAccelToRpmBins,  TPSValue      zBins       = tpsTpsAccelTable

Statistics: Posted by AndreyB — Tue Apr 23, 2019 10:42 pm


]]>
2019-04-23T18:53:01 2019-04-23T18:53:01 https://rusefi.com/forum/viewtopic.php?t=1546&p=32862#p32862 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> 1. Enough room to manage that,
2. Enough of a base map to manage that,
3. A strong enough handbrake to manage that.

:lol:

Here is a log of it working much more effectively though. I did some cranking/idle fixing and tested the enrichment on some quick taps of the throttle at the same time.

Statistics: Posted by Simon@FutureProof — Tue Apr 23, 2019 6:53 pm


]]>
2019-04-23T01:26:23 2019-04-23T01:26:23 https://rusefi.com/forum/viewtopic.php?t=1546&p=32828#p32828 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
even just turning the car around on the drive
Was that with the e-brake, or did you turn it around purely with the long pedal :)

Statistics: Posted by kb1gtt — Tue Apr 23, 2019 1:26 am


]]>
2019-04-22T18:39:31 2019-04-22T18:39:31 https://rusefi.com/forum/viewtopic.php?t=1546&p=32825#p32825 <![CDATA[Re: Alpha/N and Acceleration enrichment]]> Statistics: Posted by Simon@FutureProof — Mon Apr 22, 2019 6:39 pm


]]>
2019-04-21T20:58:25 2019-04-21T20:58:25 https://rusefi.com/forum/viewtopic.php?t=1546&p=32811#p32811 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
What I am seeing is much better DeltaTPS response but limited enrichment shots. This seems to be purely due to the number of cells and break points available and how I had them set.
I don't think the steps were set fine enough for the low throttle opening points. So partly a tuning issue, partly a software issue.

Is there any reason I cannot set my X axis different to my Y axis?

So have 0, 1, 3, 8, 13, 25, 40, 65 on my X axis and Y set 1, 3, 8, 13, 25, 40, 65, 100?

This would offset my throttle start position by 1 cell and free up 8 more cells for tuning. I assume the software won't care what the axis on the table is it will just look at the "TPS Value" axis and check the correct "TPS Value to" cell?

Finally, is there any reason the table is not "TPS Value" on X axis and the value at the start of the current enrichment period and "TPS Delta" on the Y axis?
The reason I ask is it would solve the issue with only being able to use half the table and probably smooth the fuel enrichment out a bit as well.
If it's an easy change to make it "TPS Delta" instead of "TPS Value to" then I can flesh the concept out and even do a bit of testing now things are working.

Statistics: Posted by Simon@FutureProof — Sun Apr 21, 2019 8:58 pm


]]>
2019-04-20T21:59:37 2019-04-20T21:59:37 https://rusefi.com/forum/viewtopic.php?t=1546&p=32781#p32781 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
https://rusefi.com/wiki/index.php?title=Manual%3ASoftware%3AFuel_Control&type=revision&diff=3931&oldid=3929

Statistics: Posted by AndreyB — Sat Apr 20, 2019 9:59 pm


]]>
2019-04-20T21:53:58 2019-04-20T21:53:58 https://rusefi.com/forum/viewtopic.php?t=1546&p=32780#p32780 <![CDATA[Re: Alpha/N and Acceleration enrichment]]>
I did wonder about the "length" and if it was too short, the note on the wiki had me thinking it was the length of time enrichment was active for after the trigger event.
From the wiki - "The Length(cycles) specifies how many ignition events will be affected by the enrichment. This should probably be at least the number of cylinders in the engine, so each cylinder is a beneficiary of the enrichment."

Am I correct in thinking that this is actually the length of time to consider when checking for the TPS Delta? So a longer length is more time to achieve the throttle opening?
If so then I will absolutely go for a longer duration.

Statistics: Posted by Simon@FutureProof — Sat Apr 20, 2019 9:53 pm


]]>