# Idle state problem need help **URL:** \ **Category:** V3 SOFTWARE\ **Created:** [October 20, 2025, 9:06am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603 "2025-10-20T09:06:24Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [October 20, 2025, 9:06am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/1 "2025-10-20T09:06:24Z")
[MN1075\_V3\_V4.emub3](https://community.ecumaster.com/uploads/short-url/p57C4SrB6Wloijq2zDEV9WhbgJ7.emub3) (67.6 KB) [20251020\_0801.emublog3](https://community.ecumaster.com/uploads/short-url/a3hPnrjZHvXZI8cjKKc9BK94bwo.emublog3) (571.7 KB) Hello everyone, 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? Thanks in advance, Bruce ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [October 23, 2025, 6:55am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/2 "2025-10-23T06:55:56Z")
Hi all, I just wanted to follow up on this topic. 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 ---
**Author:** ![derUltraTT](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@derUltraTT](https://community.ecumaster.com/u/derUltraTT)\ **Post date:** [October 23, 2025, 7:25pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/3 "2025-10-23T19:25:00Z")
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. ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [October 24, 2025, 7:08am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/4 "2025-10-24T07:08:02Z")
Thanks a lot for checking and your feedback! 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. ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [October 25, 2025, 10:27pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/5 "2025-10-25T22:27:58Z")
I will take a look at this. If it is firmware bug it will be fixed for next buld planned for next week. The log looks very suspicious. ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [October 25, 2025, 10:36pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/6 "2025-10-25T22:36:36Z")
What I can see is that you selected Spark / Fuel cut idle control. Try to disable it Idle/Spark fuel cut/ Cut parameters / Cut type set to none ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [October 27, 2025, 9:37am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/7 "2025-10-27T09:37:37Z")
Hello Jadzwin Thank you for your Help. I disable the Idle/spark cut/Cut parameter to “none” and it worked now perfect.💯 Regards Bruce ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 3, 2025, 1:40pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/8 "2025-11-03T13:40:19Z")
Hello Jadzwin 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. [MN1075\_V3\_V7.emub3](https://community.ecumaster.com/uploads/short-url/ogRlKPqphvnqBbNHYWrFBr9Cy9l.emub3) (68.1 KB) [03132406.BG3](https://community.ecumaster.com/uploads/short-url/hKa4zc6jm6vgdTmSt39suRyIctQ.BG3) (5.8 MB) ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [November 3, 2025, 2:44pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/9 "2025-11-03T14:44:30Z")
Could you tell at what time on the log shoul I look ? ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 3, 2025, 3:27pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/10 "2025-11-03T15:27:03Z")
At 5:35.00s i tab the pedal ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [November 3, 2025, 3:31pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/11 "2025-11-03T15:31:38Z")
At 5:35 the overrung strategy is activated as soon you left the idle state ![image](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/0/0911214e9b61709565b6c15bd61ba6399bbcad77.png) ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 3, 2025, 3:37pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/12 "2025-11-03T15:37:15Z")
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. ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [November 3, 2025, 3:55pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/13 "2025-11-03T15:55:10Z")
You were still at idle control and it blocked the overrun ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 3, 2025, 3:56pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/14 "2025-11-03T15:56:25Z")
Yes i see that but i did not know why? ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 4, 2025, 11:25am UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/15 "2025-11-04T11:25:37Z")
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. ---
**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\ **Post date:** [November 4, 2025, 1:52pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/16 "2025-11-04T13:52:44Z")
It is in Idle because all condition are met to control idle RPM. You do not use MAP sensor. In this case you can set the minimum pressure to activate idle so during engine braking, the idle strategy is inactive. ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [November 4, 2025, 4:01pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/17 "2025-11-04T16:01:06Z")
![fuelcut-problem](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/d/dec473b3e68f3c8b8860e23f9814d27e453b9f73.jpeg) ---
**Author:** ![shrek69](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@shrek69](https://community.ecumaster.com/u/shrek69)\ **Post date:** [August 6, 2026, 12:17pm UTC](https://community.ecumaster.com/t/idle-state-problem-need-help/4603/18 "2026-08-06T12:17:47Z")
I understand that the MAP condition solves this for Speed Density engines. However, what about DBW / Alpha-N applications where MAP is not usable? Could a similar condition be added for engines without a valid MAP signal? Otherwise, the idle controller keeps blocking overrun after a normal downshift, even though the engine is clearly back in engine braking. Is there already a way to achieve this in the current V3 firmware, or is this still not implemented?