RomRaider

Thanks a lot!!
I will check it.

How can I define the scaling for "Map_Switching_Cruise_Switch_Min_Delay"?

This has made the open source speed density 32 bit almost stock like. Awesome

The templates are in this thread, and on Github.

It's a moot point for your rom though - it doesn't have cruise and non-cruise maps?

I do not find out the Cruise/Non_Cruise Map on 06 EDM WRX A8DH200Y.

That's exactly the point - the 06's don't have cruise and non-cruise maps - only single maps.

I've found ECT to Airflow target tables but there is one problem there are 12 off them!

6 for auto trans;
3 cruise, 3 non cruise

6 for manual trans;
3 cruise, 3 non cruise



Just above ssmbase address you'll find this


note how there's a table address followed by two data addresses so on and so on......
The bottom set of addresses are for auto trans the top for manual. The second last ram address is referenced by the routine that uses these data addresses.

The xrefs at the start of each auto/manual address block takes you to a routine that takes the data from the tables and writes it to the data addresses.

hope that makes sense?

Found these too these tables form the upper and lower limits

Yes.
This is not uncommon as the code changed over the years. Now you just have to sort out the table selection criteria and what it's based on. Are you having fun yet?

Table selection is based on the extended parameter E Idle Speed Map Selection Ext_E49.

1 = table A

2 = table B

4 = table C

My Ecu seems to be pegged at 4 or table C but maybe dissecting that parameter can be my next project.



I always have fun!

Besides it fills in time! I hope others can benefit from it too.

My car idles quite rough and RPM oscillates -+ 50-100Rmp at times and I'm still running stock injectors. I also have this intermittent issue where my car almost stalls when it tries to return to idle under low load like when I'm driving in a car park.

I Think increasing The lower Airflow limits and adjusting the targets will help..... well I hope.

I contacted reid-o regarding this comment and we had a discussion via PM. This discussion caused me to really think about how this table works. Nowhere in this thread does it actually explain how this 3D tables works. Granted, I am sure that those of you who are going through the assembly simply scan the code and see how it works. I'm actually not one of those people. I probably should invest the time ...

Anyhow - here is a copy and paste of my latest PM to reid-o. This should help others.

"Yup yup. I had already set the "Overrun Fueling Resume RPM Threshholds". You said that you thought the best strategy would be to set it 100rpm over the target idle. I disagree . The best strategy (I think) is to set it with the same delta as the stock settings. At operational coolant temp, the delta is around 250rpm IIRC (stock idle is 700rpm and the fuel resume is at 950rpm). I have my idle at 850rpm so I raised my fuel resume to 1100rpm before I contacted you about the idle stability table. This change makes a really really nice difference. I never had a problem with the car stalling. But, when slowing down to a stop this table really helps smooth things out.

With regard to the changes you made to idle stability - THANK YOU. What you did was you actually forced me to really think about how this 3D table is used and I believe I fully understand it now. I made bigger changes than what you made. Here are my thoughts/results:

The Y-axis (vertical) is the change in RPMs. This is the rise and fall of the idle. If the idle is falling - you have a negative delta for current engine RPM. Therefore, you want a positive change to MAP-related airflow in order to stop the engine speed from falling. This explains why you must have positive values for cases where you are both below and above the target idle. If you are above the target idle, but engine RPM is falling drastically, you need to catch this condition and prevent it from going below the target idle. Thus, a positive number is needed. If the current engine RPM is increasing (positive y-axis values), and you are above the target idle, then you need negative values to bring it inline. However, if the engine RPMs are increasing greatly and you are below the target idle, you may wish to use slightly negative values in order to ensure you don't go FAR over the target (keep in mind that the RPMs are already increasing so even though you are currently below the target idle the car is in a state where it is moving rapidly toward that idle - thus, you don't want positive values here).

Since I have AccessTUNER Race, I used the live tracing in order to watch which cells were being used during my oscillating idle. It actually wasn't using the extremes. I was within the -75 to +200 region. This signified to me that my 0 to -75 area had numbers that were too positive causing it to shoot up to that +200 area.

Thanks you again for this discussion. I really appreciate it. If you want to see the changes that I made, send me your e-mail and I'll get a screenshot and e-mail it to you.

Tim"

Sounds like I need to provide definitions for the logger parameters

What parameters are you logging - I'll define them so that others can use the same strategy as proposed above.

Oddly enough, I didn't have to log due to AccessTuner Race's ability to do live tracing. So, I simply enabled live tracing and visually watched the highlighting of cells in this table as they became active. If I were logging then I would want to log delta RPM and target idle error. Technically you don't need delta RPM since you could simply calculate that for yourself in Excel from the Engine Speed. Additionally, you don't really need target idle error since that could also be calculated using Engine Speed and the knowledge of what your idle speed is set to. But, it's always nice not to have to do any calculations

Tim

it's possible to make a calculated parameter then?
Use this to overlay on rr logger and rr table

I've already got both of the defined, and Dale's allocated E numbers to them in terms of the official logger defs, so I'll start pulling them out for people.