New software 3.033c is available!

As per my previous post, would you be able to clarify how the new accel correction table functions? Is it simply a reduction/addition to the base accel correction value, or multiplier, or something else?

I tried some values with TPS Rate vs MAP, expecting a reduction of say -2%, but somehow get accel correction of +20%, when my accel is only set at 10% in the base table?

I have also tried the values as -100%, and +100%, and it seems to have no different effect.

Alternatively has anyone else used this correction table yet?

I’ve check on the simulator and everything works ok with ACC enrich.
The correction scales the value from Acc. enrich table.
For example if you have 100% in ACC enrich table, and -2% correction the result will be 98% of ACC. enrichment.
For 3.035 I’ve added a log channel with the ACC enrich correction value so it will be easier to analyze the log

1 Like

Could you please show your rev limiter settings ?
Do you limit the RPM with the DBW ?

I have attached screenshot of the limiter - No limiter with DBW.

Also another area of the addtional blips before the clutch has been released. noticed again how late the RPM Target appears after Rev limiter becomes armed.

I have attached the log and project file too for you to have a look at, but like I say the settings are identical to V2 and never had any issues with it.

E46 V3 EFI 5.2 Cadwell 2.emub3 (61.5 KB)
Rev Match issues.emublog3 (697.2 KB)

The code is exactly the same as in V2 so it is strange.
If the rev limiter would be DBW based then it would explaining the rev limiter issue as the blip DBW target source has higher priority than DBW Rev limiter (it must be changed).
I will simulate your project on the bench right now.

1 Like

Btw: you dont have any revlimiter enabled. Just a fuel cut over given rpm.
The logic is that during the blip the fuel cut is disabled, but in the case of fuel cut RPM limit, the cut should be performed. It will be fixed for the next build.
However you should use Rev limiters strategy to make nice and smooth rev limiter what will work ok.

Also I would lower the TPS target for rev matching as it should be the throttle opening that allows to get the maximum RPM. I think 20% is enough, 50% is a lot for non loaded engine, and keeping RPM target will be challenging.

Still looking for the reason the Rev matching behaves so odd in your project.

Wasn’t aware that the rev limiters weren’t activated with this new set up? I thought rev limiter 1 was always active and the drop down menu “Rev limiter switching input” was to swap to limiter two?

From the help menu I thought the Rev limiter 1 was working 200rpm prior to the 7000rpm limit set for fuel cut? I know it is only set for spark cut at the moment.
If I have missed something additionally here please explain.

I have dropped the TPS Target for rev matching down to a lower value.

Thanks for looking into it.

All your rev limiter RPM targets are set to 15000, so in practice it doesn’t work.

The fuel cut over RPM is enabled, but it doesn’t work during the blip (it is a bug, already fixed). However Rev limiters work independently.

I tested your project on the bench and everything works good. I cannot explain the big delay between Rev match active and the calculated RPM target.

I added some debug data to the strategy so we can gather more data.

Thanks for clarification.
It wasn’t clear that the tables had to be set in the rev limiter section. The assumption was that it would use the limiter set for Fuel Cut.
I have set these so will test next time.

When the next build is released I will do some testing.
I did notice that the ‘lag’ is always of 0.7 seconds every time from the rev match arming to the RPM target showing.

on the bench it is 0.2s as you defined in parameters.
Also the code looks good.

For the rev limiter set up CLT table.

I have added a 3.035 log and project into Software Opinions thread after testing today with the new log channel :+1: