New software 3.053 available!

New version of V3 is available!

Link to the software:
https://www.ecumaster.com/files/EMU_BLACK_V3/EMUBlackV3Setup_3_053a.exe

EDL firmware ver 21 required for V3 firmware in version 3.051 and higer
[https://www.ecumaster.com/files/EMU_BLACK_V3/edl_firmware_1_21.zip ]

Change log file: changeLogV3.pdf

CHANGE LOG:

SHORT TERM TRIM:

  • Engine afterstart delay added
  • Disable switch added

IDLE

  • Option to control idle ignition via PID or the ignition-correction table

SENSORS WIZARD

  • Support for Syltech temperature sensors: MSCS-4P-A05-N8, MSCS-4P-G10-N8, MSTS-2P-CST-SS-E20, MSTS-2P-EAT-SS-G25, MSTS-2P-LAT-SS-G15, MSTS-2P-M14-AL-G15

TRIGGER WIZARD

  • Added BMW M54B30 engine support.

V2 IMPORTER

  • VVT-i & VTEC settings import added
  • Boost settings import added
  • More accurate Alternator-PID conversion

IGNITION

  • With dual coils in wasted-spark mode, each output now toggles exactly once per spark (minor issue)

HELP

  • Added language selection to the Help Panel. Currently supported languages: English, Polish, Spanish.
3 Likes

Please, I still miss the diff. control strategy option for controlling the Dual H-Bridge stepper motor of the Haldex 1st gen. differential. I was promised that the engineers would do it, thank you

1 Like

Please add function to assign 2 ignition outputs per cylinder. Like in V2 firmware. When using twin spark engines with double fire coils in wasted spark theres currently no way of running them in V3 firmware without changing wiring to : 1 ouput = Firing both plugs of 1 cylinder

If you are running wasted spark and assign coils like this then it will fire:

Coil 1+3
Coil 2+4
Coil 3+1
Coil 4+2

1 Like

I understand, this works . But its all over confusing again like in v2. Simple is best

Now you assign cylinder to coil. It is very different conecpt than in v2. But it is simple to assign.
Also wasted spark autonaticaly pairs the coils based on the firing order.
The system was rewritten to make it much simpler for most of the engines.
Your case is something what is an exception, and now there is no simple option to add coils pair for the user.

Any update for the Evo X CAN coolant display scaling?

Please try this firmware and let me know if it requires further modification.

This is perfect.. now it doesn’t really rise above normal value until around 215f. Maybe could make 215-220 a little higher on the scale, but everything below 210f is finally reading normal on the coolant gauge like stock ECU. Great work! If possible to release this on a latest V2 firmware that would be great as well as I have many clients not switched over to the V3 just yet that complain about the coolant display issue

I do. I plan new v2 software in 2 weeks

1 Like

When downshifting without touching pps, overrun cut doesn’t come in again, even though rpm riseabove threshold.

Yes, we could configured outputs by ourselves in V2, it was much better.
In V3 we got a lot more things for example to configure with Idle, so I think that ignition should also stay way much more free.
Not sure if wasted spark during cranking works as supposed, haven’t noticed any better starting(maybe beacause synchronization is brilliant in V3). By the next occasion with even number of cylinders, I will try to disconnect cam sensor to get sure:-)

Not sure if that was reported already. I have newest software. When I’m on a Graph (log) and I want to change Channels to check different things, the menu always defaults to random value and not the one I had there before. Like I have Engine Oil Pressure on the graph and I want to change it to Engine Oil Temperature. I select Change Channel option and it goes to random value from the list , like TPS. Then you need to scroll up again to select what you wanted.


In this example if I have Engine Oil Pressure and I choose option to change it, the Select Channel window should select same opttion - Engine Oil Pressure and not something random

I will test it. It is possible bug.
Wasted spark option works only for even number of cylinders right now.

Will be fixed for next build

Might be me but the stuck throttle position seems a bit short on options.
Now whenever I try to brake-boost to make some boostpressure, the stuck throttle protection kicks in.

Would it be possible to add a ‘only activate if PPS is over X’
or perhaps a TPS and PPS mismatch while brake is activated.

Thanks

good test, the engine does not smoke oil… I see the light at the end of the tunnel… there is still a problem, with the engine warm at idle rpm I have 0.80/0.78 lambda to work correctly… I do not understand where I have to look for the problem, the mapping is basic but similar to the one used before this
The logbook show always map,knock,dbw and i don’t have a fuel sensor pressure and regulator,is the original system without fuel return
15 7 25 test.emub3 (67.9 KB)
15 7 25 log test.emublog3 (1.9 MB)

I also have the problem of Idle fluctuations that we were unable to figure out.
I will be changing the injectors to eliminate that possibility, but I’ve tried putting back an old tune, disabling PID etc.

1 Like

I have to try… I know I can make ECU errors because I’m self-taught… before the problem and for two years I had a car capable of challenging a 4.2 V8 biturbo Ferrari… we’ll find the solution