# Strange Idle Target RPM Increase **URL:** \ **Category:** V3 SOFTWARE\ **Created:** [August 11, 2024, 11:25am UTC](https://community.ecumaster.com/t/strange-idle-target-rpm-increase/2025 "2024-08-11T11:25:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![konrad](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/konrad/32/49_2.png) [@konrad](https://community.ecumaster.com/u/konrad)\ **Post date:** [August 11, 2024, 11:25am UTC](https://community.ecumaster.com/t/strange-idle-target-rpm-increase/2025/1 "2024-08-11T11:25:11Z")
First I indicated this here [Idle and warm up tuning](https://community.ecumaster.com/t/idle-and-warm-up-tuning/2024) But as this is something to take a closer look by itself I decided for a separate post. As I’m working on air-cooled engines, I expect the higher CLT temps and things related to them are not that much tested as with water cooled engines. The thing is I have Idle Target RPM table defined as below: ![Zrzut ekranu 2024-08-11 o 13.12.45](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/7/7154ab0f4bbf6351bde61c69a189bc124fba6b5b.png) And by some reason this target gets increased to almost 1400 RPM in the range of c.a 126+ deg Celsius by a reason not understand by me. This is something that is occurring every time I start the engine and bring it to the warmed up state (c.a. 150 deg Celsius). When I stop the engine and cool it to c.a. 126 Celsius, the target drops to the value defined in the table. ![Zrzut ekranu 2024-08-11 o 13.10.18](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/9/97bf77b482b51e757dc7044089f9bd3d8096c58c.png) What is interesting it seems when I stop the engine, the target still gets increased with the engine cooling gradually (which kinda makes sense without this “addon of ~300 RPM”, as I want more RPM with cooler engine to get a drop to “normal” around 126 deg). Attaching log with few start ups / warm ups / cool downs. [20240811\_1321-Idle-Target-RPM-Increase.emublog3](https://community.ecumaster.com/uploads/short-url/mHf6LxsBhsy4kDY14G8G269YaWS.emublog3) (2.3 MB) What I am missing? ---
**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:** [August 11, 2024, 11:44am UTC](https://community.ecumaster.com/t/strange-idle-target-rpm-increase/2025/2 "2024-08-11T11:44:14Z")
it looks like a type overflow error i code ---
**Author:** ![konrad](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/konrad/32/49_2.png) [@konrad](https://community.ecumaster.com/u/konrad)\ **Post date:** [August 11, 2024, 11:48am UTC](https://community.ecumaster.com/t/strange-idle-target-rpm-increase/2025/3 "2024-08-11T11:48:09Z")
So I think I found a clue, but not a solution I think. By some reason when I set up the after start RPM increase as follows ![Zrzut ekranu 2024-08-11 o 13.43.45](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/6/65ed49dd1933ac6b3b8c09504e91451330bac312.png) Even if the CLT temps are high it takes the 300 value from the lower left corner and adds it to the Idle RPM Target. Why? And it keeps it like that even after power cycle. When I zero that table, then obviously it’s not added to the Idle Target RPM. ---
**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:** [August 11, 2024, 12:04pm UTC](https://community.ecumaster.com/t/strange-idle-target-rpm-increase/2025/4 "2024-08-11T12:04:53Z")
> [@konrad](#): > > What is interesting it seems when I stop the engine, the target still gets increased with the engine cooling gradually (which kinda makes sense without this “addon of ~300 RPM”, as I want more RPM with cooler engine to get a drop to “normal” around 126 deg). Indeed this table is a problem. For the next version this table will be modified to allow enter higher values in Y axis bins. There is no workaround in this version. You need to keep this table 0.