after upgrading my EMU Black from firmware V2 to V3, I noticed a problem with the drive-by-wire (DBW) throttle behavior during engine start.
The throttle opens according to the Drive by Wire Target Table immediately after start, instead of using the throttle position from the Idle Control settings.
Even though the status indicator shows Idle Active, the actual throttle position remains at the DBW target value (in my case about 6–8°) instead of the idle target (around 4°).
If I briefly blip the throttle, it then switches correctly to the idle target position, and from that moment on behaves normally.
The issue is reproducible on every start — the throttle stays too far open until the first pedal input.
I’ve attached my calibration file and a log file showing the behavior (especially during the third start in the log, where the engine ran for about two minutes without change).
Could someone please check if this is a known issue in V3, or if I might have an error in my configuration?
This issue is quite important in my case, because I’m working with around 50 identical engines equipped with EMU Black units. These are not all different setups — they share the same calibration, and the DBW behavior I described above appears consistently across them.
I’m not sure whether this is a software-related issue in firmware V3 or something wrong in my configuration. I would really appreciate if someone from the support or development team could take a quick look at my files and let me know if I’ve maybe set something incorrectly — or if this might indeed be firmware-related.
Thanks in advance for your time and support,
Bruce
Hi
i had a look on ur log and settings. I seems that even after the throttle blip there is something strange…ur idle airflow always shows 0 or 50%(?ur cranking value). For me ur settings seem to be correct and u found a strange bug.
I would try to deactivate afterstart delay…i know that this caused strange stuff in the past and probably never was fixed well enough.
I’ll try disabling the afterstart delay as you suggested and see if that changes the behavior.
It would still be great if someone from the ECUMaster team could take a look at this as well, just to confirm whether it’s a configuration detail or something firmware-related.
I have another problem where i maybe need your help.
Overrun fuelcut doesn`t work correctly. When, for example, i drive with 3000rpm downhill and take the foot off the PPS it works as it should. If I now operate the engine in idle with the clutch disengaged, and then engage the clutch while driving downhill, the engine revs up to 3000 rpm but the overrun cut-off does not activate. Please have again a look at the logging and the mapping.
Yes but at 5:17.0 it entered fuelcut as it should. At 5:24.00 i press clutch and engine drop to 1000rpm. At 5:27.0 i release clutch and the fuel cut did not engaged.
Hi, i wanted to check if you can also see in the logging that the overrun fuelcut does not activate as expected under certain conditions. I´d appreciate it if you could have another look and let me know your thoughts.
