So far V3 is pretty great. Cold start is far improved over V2, especially with Honda K series and wasted spark on cranking, it no longer struggles but fires right up almost as if it was on the OEM ECU.
I also love the redefined acceleration enrichment section as well as the DBW calibration.
My only request, if possible, could we get a timer for overrun? I do enjoy overrun but having it continuously in overrun at negative timing until I either put my foot on the clutch or go below the deactivation RPM is a bit annoying. So a timer would be much appreciated if possible.
Would it be possible to make the Function name longer / add “description” field to the function?
Would be nice to have possibility to add “description” to inputs/outputs as well.
You have 2 sets of overrun tables. So if I understand you correctly, you can create function that will switch from “aggressive overrun” to soft overrun after for example 2 sec. and use it to switch between tables.
Creating V3 we tried to make it more flexible than V2 so the user can make own behavior of strategies without need to add new parameters.
I’ve checked and it copy / paste only from Black V2 not classic (we will fix it in the future classic updates).
What I can suggest is to load Classic project to EMU BLACK V2 software and then copy tables.
I feel like you have a specific issue. I’m not sure what though. All of the things you said don’t work in V3 work really good for me. Very responsive and easy to dial in.
My setup is an Audi A3, VR6. DBW (Bosch throttle body I believe). Responds to the idle correction well, the idle target tracks within 50 rpm of whatever I set it to providing the airflow table has appropriate values for the RPM. I don’t have any Subaru experience. All VW/Audi stuff for me. I can put my map up if you want to take a look…it’s not apples to apples…but might help narrow down what the Subaru needs to get it under control
One of my more recent maps can be found here actually
I was working through torque table stuff …but idle was all set by this point
Thanks! I’m looking through it now but the differences are very minor. I used values from 0 to 100 in active state airflow and absolutely nothing changed.
I would like to enable overrun to under MAP pressure as an additional condition. Is it possible ?
Also, I only have one function (Fn) available for switch overrun table. Is it possible to add more Fn. (I use 4 Fn for the Can Switch Bord V3 output and I have a lot of operations available)
Appreciate it! idle issue.emublog3 (60.3 KB) Idle issue Map.emub3 (54.8 KB)
Whenever I blip the throttle it goes into a much higher idle target-1400 RPM and begins to misfire like crazy. I have it set to 700. i found a way to escape this rough elevated idle by toggling cyclic idle, otherwise there is no way to revert to lower RPM.
I combine some operations into a single function (Fn) to activate an output or a strategy or a table change…
I sometimes use the result of one function as an argument in another. (I save on the available operations )
I use full 12/12 functions (Fn)
Does EMU Black hardware limit the number of functions (Fn)?
I still have about 10/32 operations available.
