Good point! I read the help menu and you’re right, this is directly reducing the fuel dose by that 8-9% - so that would be it.
Which settings did you notice are different? I can’t see anything obvious.
I’m guessing that the new fuel model is now compensating for effective fuel pressure, while the previous version possibly did not - so this been baked into by VE table?
Would it be complicated to do something like a boost dc based gear scale boost setup? As the standard boost by gear setup will reduce the complete boost dc, and customer wants to raise boost by rpm in lower gears. as there is less load in lower gears you normaly turn up gear scale but once you reached boost you get wheelspin. so his plan is to reduce boost dc in lower rpms in 1-3rd gear and raise it with the rpm. and in higher gears you could maybe kill overboost jumps.
i hope its not that complicated how i discribe our problem
You do not alter boost DC, you alter Boost target.
You can limit it, using Target limits, or use Gear correction you can rise / lower boost target for given gear.
Yes is it possible to get different boost on different rpm’s in different gears? Somehow? As if I reduce punch in 1-3 it gets lame in 4/6th. But if I keep early punch I get wheelspin in lower gears.
It’s just for the first punch. Once boost is on I could go with higher boost.
It’s just the question of a fwd customer. We thinking of trying traction control but it never worked out that good. Maybe a dbw traction control would be interesting.
Use 2nd boost target table and switch to it when throttle pressed and eg gear is lower than 3
Use timers that will reduce boost in a function of time when the condition met (this option desont work properly, it is already fixed and will be released in 3.036)
I found the reason. In the 3.032 and earlier I found the bug that fuel pressure correction didn’t work properly when there was no fuel pressure sensor.
In 3.033 the rail type code was rewritten and now it works as it should.
So if you have fixed pressure fuel regulator, if the manifold pressure drops, the effective pressure increases so the fuel dose must be reduced.
And now it reduces PW by 7-10% on idle.
So now even without pressure sensor you will get much better VE table as it will not compensate the change in effective fuel pressure.
Summarizing, now it works correctly, you need to adjsut your ve table
In LOGwindow with measurement channels its not posible to adjust width of each column. Column for measured value is unnecessarily wide.
Also its not possible to adjust height of the window less then displayed data (like in v2).
Hope it will be more understandable with pictures . . .
I didn’t have chance to fully test on 3.033, but since that version I switched to BARO + Fuel Pressure Sensor (fixed 400kPa base pressure). I am now on 3.035 where I have had more chance to test…
In my case I have noticed a great improvement in idle. My injectors are large for the engine so I am only at around 1% duty cycle on warm idle, but it is much much better now.
The VE table overall didn’t want that much in the way of changes (I was previously just on MAP reference, but with it not working correctly on the old version), but the new log channels are helpful in seeing the correction factor working as it should
I seem to be experiencing issues with the overrun fuel strategy. I’ve attached a couple of logs and my file. Basically, the overrun will not shut off below the set rpm value, causing a severe misfire. 3RZ-FEZ 9.15.emub3 (65.5 KB) 20240915_2214.emublog3 (4.7 MB) 20240915_1754.emublog3 (1.5 MB)
but still if the error is 0 the integral term of air pid doesnt change. It is how the PID is working.
If the rpm are too low the igniton angle should advance and there should be an error so the air PID should change.
Probably your ignition target and Idle DC ref are set wrong. For most engines the ignition tarhet at idle should be around 5 deg what allows easy control the rpm up and down.